On Thu Oct 15 08:53:07 1998, Christian Meder wrote:
> On Tue, Oct 13, 1998 at 06:46:17PM +0100, Jules Bean wrote:
>
> > [autofs problems. Rebuilding with libc 2.0.95 may help]
>
> I will investigate the problem next week.
I installed autofs_3.1.1-1. What I found was that it mounted the first
t
I elaborated on this earlier, but I decided to be very stupid this morning and
didn't bother cc-ing the mailing list. Oops. So, once more:
> Well.. in 2.0.35, on my SS2 (and I know others have experienced this) you
> cannot suspend processes with ^Z in bash. More accurately, you can suspend
> t
--On Thu, Oct 15, 1998 1:16 pm +0200 "Christian Meder"
<[EMAIL PROTECTED]> wrote:
> On Tue, Oct 13, 1998 at 06:46:17PM +0100, Jules Bean wrote:
>> [^Z doesn't work in bash, and recently ksh]
>
> Could you elaborate ?
>
Well.. in 2.0.35, on my SS2 (and I know others have experienced this) you
c
On Tue, Oct 13, 1998 at 06:46:17PM +0100, Jules Bean wrote:
>
> [autofs problems. Rebuilding with libc 2.0.95 may help]
I will investigate the problem next week.
>
> [^Z doesn't work in bash, and recently ksh]
Could you elaborate ?
> [modprobe problems]
I don't have modprobe problems. SS2 sp
--On Fri, Sep 25, 1998 1:01 am -0500 "Michael Shuey" <[EMAIL PROTECTED]>
wrote:
> Be warned, the following are the insane ramblings of a tired, bored
programmer
> and should not be taken as any sort of reasonable thought. You have been
> warned.
>
OK.
I'm sorry I've been dormant for a couple
Hi,
I'm the guy who started to make a mess by uploading new stuff ;-)
I've uploaded glibc, egcs and some by glibc 2.0.95 broken c++ stuff
like dpkg :-/
egcs seems reasonably ok and glibc has some quirks (see below). I will work
on a fixed glibc, recompile the latest egcs and provide a recent ke
[EMAIL PROTECTED] wrote:
> Michael Shuey writes:
>
> > I'm also seeing the problems with modprobe/insmod. I just can't seem
> > to insert a kernel module, it always complains with the same cryptic
> > error number. Anyone out there have any ideas on this one?
>
> insmod has worked before for m
> glibc has changed in september, so you are compiling with a newer
> glibc while the insmod which has worked for me was probably compiled
> with an older glibc, than the one compiled with the present insmod.
Yes, that is correct. However, the presently available insmod was also built
with an old
Michael Shuey writes:
>
> Oddly enough, I recompiled modutils & insmod/modprobe are working now.
> Unfortunately, autofs no longer works. It was staying up for hours on end,
> but now it's dying after a couple minutes again. Dammit.
glibc has changed in september, so you are compiling with
> > I'm also seeing the problems with modprobe/insmod. I just can't seem
> > to insert a kernel module, it always complains with the same cryptic
> > error number. Anyone out there have any ideas on this one?
>
> insmod has worked before for me. It ceases to work after I upgradded
> to the new
Michael Shuey writes:
> I'm also seeing the problems with modprobe/insmod. I just can't seem
> to insert a kernel module, it always complains with the same cryptic
> error number. Anyone out there have any ideas on this one?
insmod has worked before for me. It ceases to work after I upgradded
On Fri, Sep 25, 1998 at 01:01:06AM -0500, Michael Shuey wrote:
> Be warned, the following are the insane ramblings of a tired, bored programmer
> and should not be taken as any sort of reasonable thought. You have been
> warned.
>
> I like Debian Linux. I also like Sun hardware. I'd really like
Be warned, the following are the insane ramblings of a tired, bored programmer
and should not be taken as any sort of reasonable thought. You have been
warned.
I like Debian Linux. I also like Sun hardware. I'd really like for these
things to start working well together, but there are a whole p
13 matches
Mail list logo
