Re: glibc2.3
John Dalbec <[email protected]> Mon, 16 Feb 2004 09:23:20 -0500
| Newsgroups | gmane.linux.redhat.release.seawolf |
|---|---|
| Message-ID | <[email protected]> |
> From: "vvor" <[email protected]> > To: "Linux" <[email protected]> > Date: Sat, 14 Feb 2004 13:34:14 -0500 > Subject: glibc2.3 > Reply-To: [email protected] > > i upgraded python. now, the only way to control my seawolf is thru ssh, because > i have lost keyboard control. i get a login window (either kde, gnome, > whatever), mouse functions (if i don't use my omniview switcher), but *any* > keyboard input is...idiosyncratic, to say the least. any keystroke makes the > monitor blank out and change resolution: 640x480 -> key -> 800 x 600 -> key -> > 1024 x 7xx, etc. so, i have to log in remotely (ssh). apparently, my x is toast. > i can't run xconfigurator because that results in a segmentation fault. is this > good usability, or what? > > what i want to do, is shut down my xserver "telinit 3" will do that until you reboot. If you want to shut down X for the long run, you should change the default runlevel in /etc/inittab from 5 to 3. You can also type Ctrl-Alt-F1 at the X screen to switch to a text console (although if your keyboard is flaky, this may not work). so i can upgrade xfree so i can > upgrade kde so i can use kde on cygwin so i don't have to deal with my omniview > malfunctioning everytime i switch back and forth between win2k and seawolf when > i want to do upgrades. i would like my server to just stay in console mode, but > then a bunch of services don't start! i think i understand how to fix that > though. "chkconfig" allows you to control which services start and stop in each runlevel. > > but i upgraded python to 2.2...so my lpd now (silly me for not anticipating > this!) suddenly has no printer specified, because it (presumably?) needs (now > that it sees i'm using python 2.2) glib2.3 (rather than 2.2, which is what i > have) and can't do printconf, or something needing widgets. Actually this sounds like you need to upgrade your Tk/Tcl packages for the new python. How did you upgrade python? Did you install a binary RPM that was built against glibc 2.3? Or did you build it from source? I assume from your Subject: header and the version number that "glib" is a typo for "glibc". Did you upgrade other RPMs as well? > > but glib2.3 won't install because...it needs binutils, a new gcc, and > linuxthreads, and thinks my kernel is 2.4.2, not 2.4.9! fun! i installed > binutils, new gcc, and let glibc go with 2.4.2, but linuxthreads won't > configure/make/make install without an advanced degree in exoskeletel > amniopsyrioasistology, and i thought i had them anyway? > > 1. will glib2.3 build on seawolf? Never tried it. If you intend to continue using glibc 2.3, I recommend upgrading your system to Red Hat 8.0 or higher. FreshRPMs.net or Fedoralegacy.org are good starting points for doing a network upgrade. Do you have broadband? Does your Linux box have a network connection or do you have to download packages to your Windows box first? > 2. what version of linuxthreads? can't find a howto... Linuxthreads seems to be an optional feature of glibc. Maybe a glibc-howto? > 3. how do i specify my printer without a gui? it's an ethernet printer, and my > seawolf serves for it for my net. I believe LPRng still uses /etc/printcap. > 4. if i remove my new python (i upgraded to help a friend compile a module...so > much for generosity), how can i convince my system that it doesn't need > glibc2.3? I thought you only needed glibc 2.3 for lpd. > > > :( > > vora John