So, the reason I need symlinks working is that I'm playing with a little Linux system with it's root file system on a packet writing CDRW. I could say it would make a nifty rescue system that could be updated or an experimental device for testing systems that could damage the file system medium or a guest system so you could operate Linux on someone else's computer without affecting their hard drive. But really I just thought it would be fun.
One trouble is bootstrapping. I can't boot directly to /dev/pktcdvd0, since it requires user space registration. /dev/sg0 is a character device. I can boot to /dev/scd0, but when I try to register /dev/pktcdvd0, I get a message from ioctl saying it can't be done with the device existing on a read only sytem. So I have to boot to an initial RAM disk and change root. I really don't like doing it that way. I can't free the RAM disk, probably because the actual pktcdvd0 and scd0 device files are on the RAM disk. Since busybox init can only be run by the kernel, I have to add another init layer and I can't shut down properly.
So, could ioctl be hacked to let me register pktcdvd? Shouldn't this registration of a device be done in kernel space anyway? I'm guessing that pktsetup is a interim solution until you decide how to get packet writing into the main stream. Anyway, all thoughts would be appreciated. Like I said, I'm just playing around.
Hi,
I tried to do a similar thing with an iso9660 rescue + a r/w udf filesystem
on the same cdrw but I couldn't make it bootable. Did you succeed in booting
from your cdrw? If udf compatible with the El Torito standard?
Another thing that doesn't work for me is creating an udf filesystem in the
second session.
--
Massimo Dal Zotto