VtR reviewers: the question is about interoperability of Linux with other OSes. Check the first comment, yes it has a very Linux-ish answer.
Suppose I don't have any USB/CD/DVD etc.
I only have an ISO of any other operating system (in my current case, Win10, but I think it doesn't matter) on my...
@FaheemMitha Yes. This is the spec: OP has no USB, ha no CD, he has only an iso image on his Linux. And now he wants to convert his system into a dual-boot one, with his Linux.
@terdon The answer is that he can use that Windows using qemu/virtualbox/vmware with direct partition access. I can't see why wouldn't it be about Linux.
@FaheemMitha I've found this problem many times, and it was one of the happiest Linux day as I could install something (maybe reinstalling a company win7) using it as a VM with direct partition access.
@peterh Because that seems more about how to install Windows. Linux is completely incidental to the question. But again, SU seems like a perfect fit. Both Linux and Windows are on topic there after all.
@FaheemMitha The essence of the correct answer (the already existing answers are false) that the other OS can be installed in a virtual machine, but using a partition of the physical machine as its physical partition.
@peterh That seems like a non-answer to me. You're using a virtual machine, you're not actually dual booting. You just tell the VM to use a partition. it seems like a much better approach to have your bootloader boot off of the ISO on your hard drive and then install normally.
@FaheemMitha I could do it around 10 years ago first time, with a tricked vmware server. Around 5 years ago it was yet hard to set up, but it went with also others. Today I could do it with minimal configuration trick with virtualbox and qemu, too.
@FaheemMitha This is a very common scenario if you want to convert a machine to dualboot, and something is not okay (typically, either workplace restrictions or your hw is buggy or warranty on the machine of your friend).
@StephenKitt I exterminated grub from my system and went back to lilo. As I've seen, Grub wants to have around 30kb binary data behind the MBR, but before the first partition. This setup is essentially incompatible with partitionless LVM hdd-s.
@StephenKitt Btw, are you really using that? If I google for partitionless LVM hard disks, I find only crap, crap and crap. Also the bootloaders and the installers won't admit this setup. In my opinion, the partition table is an ancient fossil and I expel it everywhere, where I can. But I had always the impression that I am alone on the world with this opinion
@StephenKitt Yes. Also I had, and I found the LILO solution. With LILO, I can make it bootable from all of its hard disks, although it requires a major lilo.conf trickery.
--bootloaderareasize size
Create a separate bootloader area of specified size besides PV's data area. The bootloader
area is an area of reserved space on the PV from which LVM2 will not allocate any extents and
it's kept untouched. This is primarily aimed for use with bootloaders to embed their own data
or metadata. The start of the bootloader area is always aligned, see also --dataalignment
and --dataalignmentoffset. The bootloader area size may eventually end up increased due to
@StephenKitt I exterminated grub from my system and went back to lilo. As I've seen, Grub wants to have around 30kb binary data behind the MBR, but before the first partition. This setup is essentially incompatible with partitionless LVM hdd-s.
something like "${files[1,5]/prefix-me-with-stuff}" --> prefixFiles1 prefixFiles2 prefixFiles3...
I'm also curious to put my finger on zsh's null-expansion-in-array-assignment that's happening by magic there. I was happily surprised to see it happen, I just couldn't find the zsh man page that described it..
To quote the 2013 systemd announcement of the new control group interface (with emphasis added):
Note that the number of cgroup attributes currently exposed as unit properties is limited. This will be extended later on, as their kernel interfaces are cleaned up. For example cpuset or freezer ...
christoph@christoph-laptop-16-04-2:~$ sudo useradd non-privileged-user -m -s /bin/bash christoph@christoph-laptop-16-04-2:~$ sudo su non-privileged-user non-privileged-user@christoph-laptop-16-04-2:/home/christoph$ /mountDropbox.sh mount: only root can do that non-privileged-user@christoph-laptop-16-04-2:/home/christoph$ sudo /mountDropbox.sh [sudo] password for non-privileged-user:
wait, what? do you think it successfully ran that script? it didn't work. it asked the non-privileged user for their password (which there is none cuz i just created that user and didn't set a password)