From: Newt <gen...@gm...> - 2009-08-25 18:43:30
|
Hello All, Here are my notes on 1.17, install r733 (I think): >> Bootloader Installation: >> -The bootsector option is still only offering the bootsector of my /home (sda2) >> directory, rather than my / directory (sda1). Aside from that, the bootsector >> option fails to install. >> -I like the added message about clicking back to try again on a failed bootloader >> installation, however this message is only presented when Grub fails to install. >> If you could implement the same message when lilo fails then that should be >> sufficient. >> -When installing grub, even though it only shows one entry that will be added to >> the boot options it adds the 'recovery mode' boot option by default. Lilo does >> not do this and it would be nice if it did to give the user a way back into a TUI >> interface in case they borked their xorg/gui. >> -When clicking back after a failed installation the bootloader configuration >> screen is still frozen. The 'Saving Configuration...Please Wait' message is >> still display, and nothing below that message can be edited. However, the user >> CAN chose a different location to install the bootloader and switch between >> loaders so, effectively, the bootloader installation can still take place. It >> would be nice to have this screen reset to default when going back to it. >> >> System Administrator Account: >> -There's still some kind of wierdness going on with the 'Next' button. There >> are still instances where it will enable (or stay enabled) allowing the user to >> bypass root password creation. However, it's slightly different that before. >> Let's see if I can describe what I'm seeing: >> -User clicks 'next' from regional settings and gets to system administrator >> account page. The 'next' button initially disables for about 1/2 second, but >> then it enables and will stay enabled until the mouse is moved into the System >> Administrator Account region. You can however move you mouse along the >> horizontal lower button plane, up the process overview area, and across the >> vectorlinux banner and the 'next' button will stay enabled. I hope that all >> makes sense. >> >> First boot: >> -wifi-rader service fails to start (perhaps a conflict with another service? e.g. wicd) >> -VasmCC start, however when I simply click on 'UTILITIES' I get a fatal error: >> [-1]Unable to load image. Mfiles.?.0 >> -VasmCC - Filesystem/Bootloader only offers lilo - needs updated to include grub >> -VasmCC - ALSASound doesn't seem to do anything - or does it just take a really long time? >> -VasmCC - Hardware Config message cannot be read (the lower 3/4 is cut off) >> -VasmCC - SAMBA Networking - Should we start Samba SWAT? Yes. Failed, cannot start SWAT. >> -VasmCC - CUPS Printing - Same deal as Samba SWAT. Tries to start it but cannot - failed. >> -Ooo - Extension Manager problem persists Hope this helps. Again, mostly minor things. No show stoppers by any means, just some normal bugs - most are minor but a couple are bigger than that. Still a great release and speedy too (pun intended). Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Monday, August 24, 2009, 10:59:48 PM, you wrote: ua> New ISO's ua> new kde pkgs ua> new installer ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17.iso ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17-CD2.iso >> >> vectorlinux:$ md5sum VL6.0-SOHO-A1.17.iso ua> 470aaed434786ef543f79fe0c5ebb965 VL6.0-SOHO-A1.17.iso ua> vectorlinux:$ md5sum VL6.0-SOHO-A1.17-CD2.iso ua> 991d0d49974b88ee0b20f973bcab0853 VL6.0-SOHO-A1.17-CD2.iso |