Posted: Mon 16 Apr 2012, 22:28
Previously I reported the boot time was slashed if I removed the vmlinuz symbolic link from / in the Ubuntu partition. When I wanted to use Ubuntu I simply restored the link.
Now I have found the Ubuntu doesn't need the link to boot since grub.cfg points at the actual vmlinuz kernel in /boot so I have just deleted the link and everything works.
I'd still appreciate someone who understands these things better than I do (not difficult!) explaining what is happening. Why should the existence of Ubuntu's vmlinuz affect the Puppy boot process?
sfeeley: I am still using unetbootin. I tried the universal installer when you suggested it before but it made no difference.
Now I have found the Ubuntu doesn't need the link to boot since grub.cfg points at the actual vmlinuz kernel in /boot so I have just deleted the link and everything works.
I'd still appreciate someone who understands these things better than I do (not difficult!) explaining what is happening. Why should the existence of Ubuntu's vmlinuz affect the Puppy boot process?
sfeeley: I am still using unetbootin. I tried the universal installer when you suggested it before but it made no difference.