After my original drive ID debacle, I tried the text installer. It couldn't find the installation media (CD in what used to be /dev/hdc and is now /dev/sdd, I think). So the text installer was a no-go. Fortunately the GUI installer worked right the second time.
I had the same problem with the text installer in Alpha 1, but haven't tired it in any of the more recent alphas.
I was confused by the Readme.function and Functions services. What are they? Can I leave them unchecked (I think they are right now and things seem to be working)?
I saw the same thing. I'm pretty sure that is a Vasm error - its picking up files from the /etc/rc.d area. I think I mentioned that problem in one of my messages. Doesn't seem to be a major problem - I just ignored them....
One thing I would DEARLY love: make VASM keep the window size if we've resized it, at least until we're done with VASM. The default text sizes are much too small for my aging eyes and high-res screens and I always resize VASM so I can see all the text. It's very annoying to have to resize the window every time I do something additional.
I'm not too worried by the font size, but I also find the inability to keep the window size correct annoying. I was finding that in several instances, the base window was too small to see any of the text correctly (and in some instances, the entry box was partially hiding things like prompts. When doing something like setting up multiple mount points, it was a pain to have to keep resizing the base window every time it came back.
One thing: I boot with a standard screen and at midpoint in the boot process, the screen changes to a size very small and hard to read. I guess it starts at 640x480 (on a 1280x1024 screen) and then the screen changes to 1280x1024, with the text whizzing by at 640x480, leaving half the screen blank. I don't like this at all and would like to know if I can change it.
That is a 'feature' of more recent kernels. They automatically enable the framebuffer at native resolution. While I always did that anyway with a 'vga=' command in my Grub menu.lst, I find the new method untidy, and would much prefer not to have it happen. I don't think it is changeable, unfortunately.
Alpha 2 seems much more complete than Alpha 1 and I expect that in the next release or two I'll be able to use it as my main system. Meanwhile, I consider RC3 my main system and HOPE that someday we'll get a final release.
I've now built enough 'must have' packages that I can almost use Alpha 2.1 as my main system. It is becoming increasingly urgent that there is a release soon - people using Seamonkey in VL6.0 now have a serious problem - the most recent version fixes a number of security issues, but cannot be built under VL 6.0. Problems of that sort are only going to become more frequent.