Martin Rogers wrote: > > Darrick Hartman wrote: >> Martin Rogers wrote: >>> Darrick >>> >>> thanks for the reply. I tried editing /etc/modprobe.conf originally >>> (setting the filesystem to RW etc) but the changes do not make it past a >>> reboot. I also tried storing one on the keydisk in case this could be >>> used to replace the etc one - without success, it does not get copied over. >>> >>> Where is the fundamental copy of the file - it is probably this one I >>> should be editing. >>> >> With unionfs, you don't (and shouldn't) modify the read-write status of >> the system. That's why the changes don't make it past a reboot. If you >> edit a file, the changed file is written to the unionfs partition and >> when seen by the OS, that file is used instead of the file on the image. >> >> (so if /etc/modprobe.conf exists in the image AND >> /oldroot/mnt/asturw/etc/modprobe.conf exists, the latter will be used). >> >> Darrick > > Darrick, > > /oldroot/mnt/ does not exist on my system. Are you suggesting that I > should create /oldroot/mnt/asturw/etc/modprobe.conf? What is the best > practice way of adding to modprobe.conf.
If /oldroot/mnt does not exist on your file system, then something is very wrong. You're either not using unionfs or something stranger than that. What do you see when you issue the 'mount' command? > If I didn't know about this filesystem structuring (oldroot etc) how > would I find out - e.g. is there any documentation which indicates how > to create modprobe.conf settings on Astlinux, or details what files get > overwritten from the keydisk. How for example should I kmow that some > /etc files (e.g. rc.conf and zaptel.conf) are read from the keydisk and > used by the system instead of the image ones but yet others (like > /mnt/kd/etc/modprobe.conf) are not. There is some documentation on unionfs. All you really need to know about unionfs is you can have multiple mount points, 'unionized' into one mount point with a mix of read-only and read-write areas. For Astlinux, when using unionfs, you will see / as type unionfs mounted rw using the two different mount points for the union. The rw mount point is /oldroot/mnt/asturw. The ro mount point is one of two locations, depending on how much system ram you have. If there is less than 256mb of system ram OR if the noram flag is set in the KCMD line (in astlinux-xxx.run.conf), the read-only 'image' remain on a squashfs image mounted loopback on what should be /oldroot/image. If you have more than 256mb and noram is not set, the read-only 'image' is copied to a ramfs location mounted as /oldroot/mnt/asturo. If you look at the mount line for unionfs, it should show something similar: none on / type unionfs (rw,dirs=/oldroot/mnt/asturw=rw:/oldroot/mnt/asturo=ro) That would be all on one line, except it's being wrapped in the email client. > Do you consider that the the problem with MODOPTS not being picked up is > a bug which needs to be raised? It is a bug. Philip has committed a fix to trunk which I have not had time to pickup and use in the 0.6 branch. Darrick ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
