can't log in with tty error on glibc2.1 & kernel 2.0.35
I guess I'm another unlucky guy who managed to "upgrade" his system to glibc2.1 while running kernel 2.0.35. The installation script gave a warning that some things may not work properly, but it proceeded anyway. End result: I now cannot log in as any user on either the console or remotely because of the following error Unable to change tty /dev/ttyp0: Success It also looks like chown doesn't work and the network doesn't start up properly (or maybe just xinetd). Regardless, I cannot run any of the 2.2.x kernels on my machine because they won't boot (long story, problem with the ESP driver), so I'm stuck with 2.0.35. So, can someone please tell me how to fix my machine at this point? The only reason I even thought of upgrading libc is that the latest version of windowmaker in potato wouldn't work on libc 2.0.105. Can I just download an old deb of libc 2.0.105, boot off the rescue disk, and then use dpkg to force the deb's install? If so, are there any special options I should use? Please cc me on any replies. Thanks, Max -- The hopeful depend on a world without end Whatever the hopeless may say Neil Peart, 1985
glibc2.1 and slink
Hi There, I need a help. I am having an autofs problem with kernel-2.2.9. But I don't have a problem with kernel-2.2.0. What do I need ? Debian-2.1 Slink, SS10 Thanks, P.S.) What is best way to upgrade Potato from slink ? -- = Kumsup Lee (À̱ݼ·) System/Network Administrator Institute for Mathematics and its Applications, University of Minnesota 400 Lind Hall, 207 Church Street S.E., Minneapolis, MN 55455 USA Tel : 612-624-4353 FAX : 612-626-7370 PAGE : 612-608-0112 [EMAIL PROTECTED] www.ima.umn.edu/~klee
Re: New Kernels (Was: new bootdisks available for testing)
Anton Blanchard <[EMAIL PROTECTED]> writes: > > > I suspect that there are serious problems with the 2.2.8 kernel, so > > you might want to go with the 2.2.7 ones. (I will try 2.2.9 RSN - > > Herbert Xu promised to upload an x86 package last sunday, but hasn't > > done so.) > 2.2.7 hangs during booting on some sun4m machines. It would be a good > idea to go with 2.2.9 if possible. The 2.2.7 that we are referring to has a patch to fix this. But I'd like to go with 2.2.9 so we can use pristine source. Steve [EMAIL PROTECTED]
Re: glibc2.1 and potato
Steve Dunham <[EMAIL PROTECTED]> writes: > > > On 13 May 1999, Steve Dunham wrote: > > > > Yeah, glibc should work fine on sparc32 machines with a recent kernel, > > > > there is a patched 2.2.7 kernel and a 2.2.8 kernel at: > > > > > > > >http://www.cse.msu.edu/debian/kernel > Herbert, I see that you are the maintainer for the kernel packages. I > was wondering when you were going to upload the 2.2.8 kernel. This is > desperately needed for the sparc, and I didn't want to upload the > sparc specific stuff before you uploaded the source package. So, just to clarify, is it the case that we need a patched 2.2.7 and 2.2.8, and this is for sparc32 using potato glibc and the new kernels? Does 2.2.9 not need this patch? -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
Re: New Kernels (Was: new bootdisks available for testing)
> I suspect that there are serious problems with the 2.2.8 kernel, so > you might want to go with the 2.2.7 ones. (I will try 2.2.9 RSN - > Herbert Xu promised to upload an x86 package last sunday, but hasn't > done so.) 2.2.7 hangs during booting on some sun4m machines. It would be a good idea to go with 2.2.9 if possible. Cheers, Anton
Re: kernel 2.2.9, slink and Sparc
"Stephen J. Carpenter" <[EMAIL PROTECTED]> writes: > On Tue, May 18, 1999 at 05:33:18PM +0200, Christian Meder wrote: > > On Tue, May 18, 1999 at 04:39:14PM +0200, Andreas Jaehnigen wrote: >>> "Debian 2.1 is not certified for use with the Linux 2.2 >>> kernel. However, if you are willing to download some packages from >>> ftp://ftp.debian.org/debian/dists/unstable/, you should be able to >>> have a functioning system. " >>> What does "some packages" mean here? What packages do I need? I'm >>> also very thankful for further references regarding this >>> topic. :-) See http://www.debian.org/releases/slink/running-kernel-2.2> > I have been runing 2.1x kernels since 2.1.119 on systems from 2.0 on up > and I have personally run into no problems at all. > (on i386 even) Your a lucky one. For most folks, such as myself, slink + kernel 2.2 isn't that bad at all. But see the web page cited above. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
Re: New Kernels (Was: new bootdisks available for testing)
Eric Delaunay <[EMAIL PROTECTED]> writes: > Steve Dunham wrote: > > Eric Delaunay <[EMAIL PROTECTED]> writes: > Hello Steve, > > I got your 2.2.8 kernel images. I will try to package another bootdisks set > next week based on them. > I already downloaded kernel-image-2.2.7*_cvs.19990507_sparc.deb last week. > Are you updated them without changing their name ? No, I think they're there because of a "cp kernel*deb". > btw, there is a 2.2.7 kernel image in the parent directory but I can't access > to it: too restrictive permissions. Is it this one I have to download ? I thought I had copied the updated kernel-image to the kernel directory, but it ended up in the parent directory, so I missed it when I chmod'd the files. It should be in the kernel directory, with correct permissions. I suspect that there are serious problems with the 2.2.8 kernel, so you might want to go with the 2.2.7 ones. (I will try 2.2.9 RSN - Herbert Xu promised to upload an x86 package last sunday, but hasn't done so.) Steve [EMAIL PROTECTED]
