I've had problems.
The installation went okay, no problems like I had a couple of releases ago. I was unhappy that the boot options for LILO still did not include a floppy disk. I have to choose "none" and reboot with
linux root=/dev/hde6 ro
using the CD. Then I'm able to install LILO on a floppy through VASM.
USER IDs ARE STILL NUMBERED STARTING AT 1001!!!! Forgive the shouting, but this makes a total MESS if we're mounting a system with an earlier version of VL where the USERID starts at 1000. You can't get access to your /home directory on the mounted partition of an earlier VL. This complicates nfs networking and makes it impossible to access your /home directory on an nfs-networked computer.
So when I found to my horror that my user account was AGAIN numbered at 1001 instead of 1000, I looked for the place to change it. Unfortunately, there is no obvious way to edit a user account. Google was my friend as usual and I discovered I could change this at /etc/passwd and /etc/group. It seemed to need a reboot to get the number changed.
Possibly related to this user ID thing, I can't start X as user. Or I may just have a problem similar to some reports here. I tried to switch from HAL to VL-HOT, but when I rebooted I couldn't get a GUI at all, not even to log in. Just a blank screen with no keyboard or mouse operational, requiring me to press the OFF button on the computer. So I started in tui mode and switched back to HAL. Now the GUI starts, but I can't get KDE running as user. When I try to log in, I get an error window that says "kstartupconfig4 does not exist or could be " (the rest doesn't fit in the unresizable message box). If I log in as root, KDE starts fine, no error messages. I figure this is a permission problem. I couldn't see what I might change in kstartupconfig4. Being unwilling to run as user, I didn't try much of anything in KDE. I wonder if this problem is related to the user ID I had to change.
I can't start the GUI if I log in with run level 2. I prefer run level 2 but if I try to startx, I get a "cannot open display 'default display'", which I have no idea how to get around.
So I'm dead in the water until I'm able to run KDE as user. I'm running beta 3 on my 1.3 GHz Celeron Tualatin with an ATI Radeon 9200 video card with 128 megs of video RAM.
A couple of comments on the installer:
*When it asks what to do with the selected partition where you will install, it would probably be confusing to many newbies. The dropdowns for Mountpoint are meaningless to anyone not familiar with mounting. I've installed VL dozens of times and I got confused by that dropdown.
*Then choosing the format type would be very difficult for a newbie. There is no explanation of the advantages and disadvantages of the various options. I chose ext3 because I'm familiar with it (as well as ext2 and reiserfs). But I have no idea why I might choose ext4 or xfs or the other one--which I've never heard of before. The Help button did offer a a bit of information on the mount point but nothing on the file systems.
I have a question about your kde issue on the part of the config. Before the question though, I wanted to let people know that you can put the cursor into that window and "click n drag" the mouse to see the rest of that line. Pretty much it says check installation because the file does not exist, etc. ,etc.
Now the question is...
During installation, at the user setup, did you select to reset everything in that list?
If you did this this, then there lies the problem. I have to run through the instller again to be accurate, but I believe that skipping the selection to ".KDE" will work well for you.
Since you've probably done as said here's a quick fix -- sort of.
Remove your ~Home/.kde
Now switch user and login under the username. KDE will generate files. After desktop loads, log out.
(back to root)
Copy from etc/skel/share/config. Open the config and copy all files to your config overwriting when prompted. It is important NOT to replace the config directory, but the contents from within.
Now you'll need to edit the permissions of this directory to make it readable and writeable by ALL +all files and sub diectories.
Note: this last step may have be of some security issue, but is better than trying to guess which files in there should be done this way and not .... better to do the skip mentiond above.
I think we may have a fix for this, but we have yet to do internal testing on it. Thanks so much for the report.