As previously noted, I installed FC5 in a VMWare image. I should have configured it to be a server, but decided to see how much running X affected performance. Well, I noticed a little lag in my xterm window and ran top. The image was running at a load of about 1, with X being the culprit. I think (seriously) it might have been spent those cycles drawing the screensaver in my VMWare window, so I decided to just not run X.
I’ve spent the last 18 months doing mostly Windows work, with some simple Linux tasks here and there. Like Stan and Kyle, I learned something today: these days, the measure of success is not how long it takes you to remember how to do a task, or read the man pages, it’s how quickly can you craft a Google query to find the right page.
I’d forgotten that runlevel 5 starts X, so you can either run at runlevel 3 or modify /etc/inittab (which is what I ended up doing). It took me three different queries to get to “remove gdm.” I think the third entry in that result list talks about exactly what I wanted to do.
Also, it looks like Fedora now uses X to display boot info? Interesting.
Update: looks like Yum is part of the default packages installed (for whatever configuration I picked, think it was development). Nice, I like yum. Now, if I can get it to work…it just hangs when I run it. Wonder if it’s something to do with VMWare? Or the fact that I haven’t installed VMWare Tools yet (there are conflicts with VMT and FC5 that I don’t feel like fixing right now).
Another update: if you try to install the J2SDK 1.4.12 (and probably other versions), it will fail with a message like this:
Unpacking…
tail: cannot open `+511′ for reading: No such file or directory
Checksumming…
After doing some Googling, I found the appropriate thread in the Java forums and the relevant Fedora docs, which say this:
The coreutils package now follows the POSIX standard version 200112. This change in behavior might affect scripts and command arguments that were previously deprecated. For example, if you have a newer system but are running software that assumes an older version of POSIX and uses sortĀ +1 or tailĀ +10, you can work around any compatibility problems by setting _POSIX2_VERSION=199209 in your environment. Refer to the section on standards in the coreutils info manual for more information on this. You can run the following command to read this information.
info coreutils Standards