@Pierre.Vriens just in case you can see this: thank you for your edits/improvements! Something that I learned when starting to edit, realize that if you edit the text a closed post it puts it into the ReOpen queue, so please continue to write good comments about what you changed, so that the reviewers know it was just typo-fixes and not an attempt to re-open the question. Thank you!
@terdon cue the sad Game Over sound of me not knowing one more thing about the site, but cheers for the excellent work-around idea -- will do; thank you!
From a time when I probably knew something about this:
Currently, this means that a closed question will automatically be added to the reopen queue when it is...
...Edited (body edits only) within 5 days of closure by the author. Or,
...Edited (body edits only) within 5 days of clos...
@terdon whew, good find - thank you! I also don't stand a chance of remembering that, either, but it seems to be a sane approach.
I must have stumbled across the "inadvertent reopen queue" situation when I was editing recently-closed Qs
I should have known, there's a Q&A [here](meta.unix.stackexchange.com) or [here](meta.stackexchange.com) or [here](meta.stackoverflow.com) for almost everything
well those links didn't work sigh stopping for a while :)
@derobert Try the following: put a filesystem on an LV (ext4 will do), and then feed it to a libvirt VM running the Debian installer. I think you'll see that the choices it shows are quite limited, and don't include RAID or LVM. And as for as formatting a particular device, it refuses to include RAID or LVM even if you delete the filesystem partition. I know this sounds weird. I could try to come up with a repro recipe.
I also accidentally downloaded a i386 installer DVD instead of an amd64 one. Go me.
when you install a module in /lib/modules/$(uname -r)/kernel/drivers, is it auto-detected by depmod or is there some kind of configuration file that has to be modified?
What (if any) are the significant differences between netcat-traditional and netcat-openbsd?
I'm having trouble finding any relative information.
Anybody familiar that can offer some insight?
ok, so used virt-manager to create a new vm, and a new lv (vm_wtf_1). About to hit begin install. Just ran mkfs.ext4 /dev/mapper/Zia-vm_wtf_1 on the host.
Using text-mode installer with Stretch DVD 1. Normal install, not expert.
Partition disks: manual. I see what you mean....
Why did your fresh LV have a ext4 volume on it? Anyway, found a workaround in the installer: select the ext4 volume, tell it to erase it. You can cancel a little way through. Then from the partition disks menu, select "go back". Then select "paritition disks again"
Then you can select vda, it'll let you create a new partition table.
I had some problems with the ssh server on one of my computers and decided to reinstall it. I installed both openssh-server and openssh-client. The installation seemed succesful, but I have no ssh_config only the sshd_config file. Does this mean something went wrong?
Making this community wiki to invite contribution from someone familiar with CentOS/RHEL 7.2
The UUIDs come from your blkid output. The paths come from the other output, and the filesystem type and options from /etc/mtab. The dump and fsck order fields are guesses. (I used the same fsck pass bec...
The description of the ssh package explains: This metapackage is a convenient way to install both the OpenSSH client and the OpenSSH server. It provides nothing in and of itself, so you may remove it if nothing depends on it.
@ÉtienneBézout once you've fixed that, please apt-get install etckeeper. That will keep your /etc in version control (git by default), so you can easily recover from mistaken configs.
Another usability issue - the installer seems to make it as hard as possible to run grub-install /dev/sda as well as /dev/sdb. You just get one device. Unless I'm missing something.
@derobert I vote for usability screwup. Worth reporting?
@FaheemMitha right, yeah, if you want /dev/sdb as well, that's harder... I don't think the installer offers that (other than execute a shell, or switch to a different vt). Of course, you can do it once the system is booted.
@FaheemMitha No, perfectly valid to create a degraded raid1.
@FaheemMitha I don't know. It's reasonably common to do it, as it makes the install faster (since the install won't be competing with the initial sync, or writing twice).
Is there a keyboard command from switching between full screen and back? I thought I saw F11, but maybe I'm confused. Plus F11 isn't doing anything anyway.
@derobert In view of my LVM clone debacle I was curious.
Which I'll try again on the VM. Maybe I should recite "The Charge of the Light Brigade" while I do it.
Why did your fresh LV have a ext4 volume on it? Anyway, found a workaround in the installer: select the ext4 volume, tell it to erase it. You can cancel a little way through. Then from the partition disks menu, select "go back". Then select "paritition disks again"
As far as I can tell, the "cancel a little way through" is actually necessary.
@FaheemMitha I think it needs to erase the first few blocks, to wipe the ext4 signature from the block device. Then you need to exit the partitioning menu (by going back to the main menu). After that, when you re-pick partition, it'll rescan the disks and not find the filesystem there.
@FaheemMitha it is, if you use expert mode, or if you go to the main menu and change the debconf priority. Then it'll ask you what type of partition table to create—I think you a dozen choices, msdos and gpt are some of them.
@FaheemMitha There is supposed to be — hit enter on the disk line (not one of the partition ones). It should ask about creating a new empty partition table. But it didn't. That could be a bug.
yeah, it does that if there isn't a filesystem there. But when there is a fs, then it just does nothing. That seems like a bug. It should at least tell you why its refusing.