Philip Prindeville wrote: > * Does it make sense to have the keydisk be a single partition? I'm > thinking that there should be one partition for version independent > stuff, like voice mail, and one or more partitions for configuration.
Perhaps at some point, the keydisk will contain items like voicemail, extra sounds, etc. Password changes, user additions etc might go on a unionfs partition. > * "genkd" could have a maximum configuration size for the partition > (maybe 128MB? that's a lot of configuration data!) > > * There could be a conversion script to take a pre-1332 configuration > disk (or partition) and move the files over into the appropriate format > for the unionfs support in 1332. The unionfs stuff will be in flux for a period of time. It has not been decided if the keydisk will remain permanently or if a unionfs partition will replace it. > * Is there an obvious place to embed the revision number? I'm thinking > it would be handy to get it out via "uname" (for instance) for scripting. The revision number is in /etc/astlinux-release. In a "released" version, this would be the release number. In a build from SVN, this will be the SVN number (for example, astlinux-trunk-1361). > I'm guessing that the genuion script is present, but /etc/rc or > /etc/rc.conf haven't yet been modified to mount the filesystem. At > least, rebooting after running "genunion" doesn't turn anything up when > I run "mount". And grepping for "ASTURW" in /etc/* doesn't turn > anything up either. A script does exist called genunion. It's a bash script which can be found in /usr/sbin. It will create a filesystem which can then be specified as a boot argument. ASTURW=/dev/part# or ASTURW=auto. If using auto, the partition intended for use as the unionfs writable partition must be labeled as ASTURW. > How close is the unionfs stuff to being ready? There are a few quirks that we're looking into. It works right now in many cases. It has not been tested in all cases (specifically in low memory situations). I've changed the password for the root user and that is retained on future boots on the unionfs partition. There is an odd issue that I haven't been able to solve at the moment. Any kernel modules that are loaded are copied to the unionfs partition. > I ask because I think it's an important feature, and I'd like to > contribute in whatever way might get it out there sooner (testing, > writing scripts, etc). There's been some documentation on using unionfs on the Astlinux web page (under documentation). Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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]
