John, Glad you were able to get things booting up properly.
We're aware of the web interface issue. It's harmless to the functionality. When we switch from unionfs to aufs (another unionfs) the issue goes away. (several projects have moved towards aufs from unionfs) We are planning to actually do a release very soon. When that release is done, we will take what's currently in trunk and branch it to 0.6 (with the 0.6.0 release). Trunk will then have the kernel updated and unionfs will be replaced by aufs. While both unionfs and aufs are both currently maintained and developed projects, there seems to be more momentum behind the aufs project. If anyone is using trunk images, please let me know if you know of any issues. I updated the timezone data last night. You should see images from SVN 1625 later today here: http://www.djhsolutions.com/astlinux Darrick John Novack wrote: > > > John Novack wrote: >> Lonnie Abelbeck wrote: >> >>>> Modified file - >>>> pbx os # cat astlinux-trunk-1615.run.conf >>>> # Kernel command line >>>> KCMD="root=/dev/ram0 rw init=/linuxrc astlinux=geni586 >>>> astimg=astlinux-trunk-1615.run astrw=/dev/hda2 astlive ide=nodma" >>>> >>> This is a problem, it should read "asturw=/dev/hda2" >>> >>> >> ARRGH!! >> Looked at this TOO many times! >> >> Thanks for the proofreading! >> I will TRY AGAIN! >> >> John Novack >> >> > HURRAY!! > > The root password persists, the web interface password persists, looks > like I can now move forward and struggle with the Asterisk 1.4.xx > changes, which is truly a moving target. 1.4.18 already has been > replaced. Seems they broke some Zaptel stuff a couple of weeks ago. > > I know many don't use the web interface - but it seems either I have a > problem or the web interface has a problem. > On the "about" page, the following errors appear > > astlinux-trunk-1615 shell-init: error retrieving current directory: > getcwd: cannot access parent directories: Inappropriate ioctl for device > > > > > > On the status page an even longer list of complaints > > Any clues? > > Also the web interface seems unable to make up its mind regarding the FS > read/write or read only display. > > Should that be ignored, or even removed when using the unionfs scheme? > > Thanks to all for the patience and proofreading to get me this far > along. This certainly seems a better route to installing improvements. > > John Novack > > -- > Dog is my co-pilot > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to [EMAIL > PROTECTED] ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
