Re: glibc2.3

> From: "vvor" <[email protected]>
> To: <[email protected]>
> Subject: RE: glibc2.3
> Date: Mon, 16 Feb 2004 14:24:06 -0500
> Reply-To: [email protected]
> 
> thank you john,
> 
> i fixed the python thing by using some symlinks, but it sounds like a hack to
> me. also, i fixed the printer thing thereby. so i guess i don't need glibc2.3
> anymore. i think you are right about tcl/tk. i can't seem to get Xconfigurator,
> which seems to me is the likely culprit with my kbd problem, to run. 

Xconfigurator normally runs from a console window.  What error messages do you 
get?  You can also try "$EDITOR /etc/X11/XF86Config-4" where $EDITOR is your 
favorite text editor (try dropping the -4 if it can't find the file).

i also
> can't kill my x server, 

What are you doing to try to kill the X server?

it fails with the message that thousands of others have
> reported on usenet, with apocryphal reports of solvage: can't connect to server,
> display not set, already running, remove /tmp-locks, etc. but none of these
> things work: my solution is to reinstall X11. but i can't kill the xserver,
> because my term window won't accept cnt-alt-backspace input.

How about using "ps ax" to find its process number and then "kill <number>"?
> 
> i should probly build another offline server and replace my main one when it is
> shaken down, using redhat 9. computers are great.
> 
> but the spectre of my server's direct kbd input failure haunts me hourly. and
> the fear that if i try to reboot at this point, i'm screwed. 

Is this a production box?  How many users do you have?

if i telinit 3,
> then a bunch of my services go down. 

Which ones?

i must have configured certain services to
> only come up at runlevel 5 or something. i had no idea how ignorant i was!

Do "chkconfig --list" and see what services are different between runlevels 3 
and 5.  Then do "chkconfig --level 3 <service> on" for the services that get 
killed.  Is ssh one of the services that gets killed?

Are you using any third-party software (i.e., not from Red Hat)?  Does it 
require an X server to run?
> 
> is there a big difference between the way 8.0 handles services and connectivity
> and 7.1?

No, it's just that 8.0 is built against glibc 2.3.  If you don't need glibc 2.3, 
then you don't need to upgrade to 8.0.

HTH,
John
> 
> thanks,
> vora
> 
> 
>>
>>
>>>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
>>
>>
>>_______________________________________________
>>Seawolf-list mailing list
>>[email protected]
>>https://www.redhat.com/mailman/listinfo/seawolf-list
> 
> 
> 
> 
> 
> --__--__--
> 
> _______________________________________________
> Seawolf-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/seawolf-list
> 
> 
> End of Seawolf-list Digest
>