Philip Prindeville wrote: >> Philip, >> >> This is not related to what Fred is asking. Fred wasn't talking about >> /oldroot/cdrom remaining mounted. He was talking about var (which does >> not reside on unionfs). >> > > I know he wasn't... but since it came up in the example, I thought I > would ask about it. > Wasn't sure if it was deliberate or if it was a hald/udev oddity...
We're not using hald (yuck). Udev yes, but I see no reason to add hald. Udev doesn't do anything with the file systems that are mounted/unmounted (other than create the devices). > Modified the installer-script. I'll post it if anyone is interested > once I get the bugs out. Of course we'd be interested in seeing it. What functional changes did you make? > BTW: What's necessary to install onto this filesystem multiple > instances of the OS so you can have a fallback version of the OS? You can just leave the astlinux-xxx.run, ...run.conf and ...run.sha1 files. > Every time I install, I first zap the old version of os/ ... since > there's room for two or more images on a 128MB partition, we might as > well keep a fallback version. I need to look at the logic used by the runnix script that gets executed on boot. There's some logic in there to determine which .run file to use. Right now I believe it just halts or dumps you to a shell if there is an error. >> If you don't have enough system memory, you must leave /oldroot/cdrom >> mounted. That's because the image file is still mounted loop back. If >> you have enough system ram that the image file is copied to a ramdisk, >> it should be possible to unmount /oldroot/cdrom. I say should because >> whenever I've tried, the system says there's a file in use and it can't >> be unmounted. >> > > How do you know if you've had enough memory or not? What are the > external signs? I don't have a serial console connected all the time, > so I lose whatever boot-time messages their might have been. The limit is 2XXMB. If there is less than 200MB, the system will use loopback. If there's more than that, it will create a ramfs for the asturo branch. You can see this after boot by looking how the unionfs mount line looks. If it references asturo then it's using a ramdisk (and you should be able to safely unmount /oldroot/cdrom). > If it does make a ramdisk copy, can it deliberately unmount the > partition so we know it doesn't need it any more? In theory yes. In practice, I've had some problems and haven't had time to review what's not happening to allow unmounting. Have a look at linuxrc from target/initrd/target_skeleton if you want. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com Small Business IT Specialists Office: 920.547.4535 Cell: 920.901.3113 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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]
