On Sun, 21 Apr 2002 01:21, Brian May wrote:
> On Fri, Apr 19, 2002 at 01:29:24PM +0200, Russell Coker wrote:
> > Another possibility is bug 142916. This resulted in one of my machines
> > becoming non-bootable.
>
> Interesting.
>
> I complained loudly about a similar problem ages ago, when
> I ins
On Fri, Apr 19, 2002 at 01:29:24PM +0200, Russell Coker wrote:
> Another possibility is bug 142916. This resulted in one of my machines
> becoming non-bootable.
Interesting.
I complained loudly about a similar problem ages ago, when
I installed a broken version of libc6 without ldconfig,
and it
On Fri, 19 Apr 2002 13:40, Andreas Schuldei wrote:
> * Russell Coker ([EMAIL PROTECTED]) [020419 13:31]:
> > > Did the initrd load at all? If it did then it could be a bug in
> > > initrd-tools. Please show me the boot messages.
>
> an other reason for failiour was that the space in the /boot
> pa
* Russell Coker ([EMAIL PROTECTED]) [020419 13:31]:
> > Did the initrd load at all? If it did then it could be a bug in
> > initrd-tools. Please show me the boot messages.
an other reason for failiour was that the space in the /boot
partion was used up. I made my boot partition just big enough fo
On Fri, 19 Apr 2002 11:47, Herbert Xu wrote:
> Michael Piefel <[EMAIL PROTECTED]> wrote:
> > No Disk
> > The old kernel was handcrafted. The new one makes an initial RAM disk
> > and loads the modules mentioned in /etc/modules. Of course, the disk
> > driver had been compiled in before. I'm not su
Michael Piefel <[EMAIL PROTECTED]> wrote:
> No Disk
> The old kernel was handcrafted. The new one makes an initial RAM disk
> and loads the modules mentioned in /etc/modules. Of course, the disk
> driver had been compiled in before. I'm not sure what to do about this.
> kernel-image _could_ have
#include
Michael Piefel wrote on Thu Apr 18, 2002 um 03:32:59PM:
> The Crash
> Well, simply, it was the wrong kernel. The guide recommends to install
> a new kernel with: apt-get install kernel-image-2.4.18-{386,586tsc,686}
> However, the system has a AMD K6. Of course it's his fault for choosi
Le ven 19/04/2002 à 09:57, Michael Piefel a écrit :
> He just went for the best: 686. It seems that one doesn't work on k6
> anymore.
That one wasn't ever meant for k6, which is not a 686 cpu.
--
.''`. Josselin Mouette/\./\
: :' : [EMAIL PROTECTED]
`. `'
Am 18.04.02 um 16:21:55 schrieb Bob Nielsen:
> > > a new kernel with: apt-get install kernel-image-2.4.18-{386,586tsc,686}
> > > However, the system has a AMD K6. Of course it's his fault for choosing
> > 386, 486, and 586 kernels work fine on a K6. When in doubt use a 386
> > kernel,
> > it'll
Am 19.04.02 um 00:51:24 schrieb Josip Rodin:
> > The old kernel was handcrafted.
> he chose to trash all that and instead follow some random
> newbie instructions? :)
Well, there was a time when I compiled all my kernels myself, but then
one day I got intrigued by our high-quality
Martijn van [EMAIL PROTECTED]@Fri, 19 Apr 2002 09:50:42 +1000:
> The solution to this is to stuff all your own aliases under something like
> /etc/modules/mine or something like that. Then they will never been
> overwritten (except if a package named "mine" decides it needs some modules
> :)
>
On Thu, Apr 18, 2002 at 03:32:59PM +0200, Michael Piefel wrote:
> No Net
> The appropriate alias for eth0 was missing. This is a case of getting
> tired with all those "config file was changed by you or a script"
> messages when very often you are sure that you didn't touch it. In this
> case, a
On Thu, Apr 18, 2002 at 11:52:53PM +0200, Russell Coker wrote:
> On Thu, 18 Apr 2002 15:32, Michael Piefel wrote:
> > The Crash
> > Well, simply, it was the wrong kernel. The guide recommends to install
> > a new kernel with: apt-get install kernel-image-2.4.18-{386,586tsc,686}
> > However, the s
On Thu, Apr 18, 2002 at 03:32:59PM +0200, Michael Piefel wrote:
> The guide recommends to install a new kernel with:
>apt-get install kernel-image-2.4.18-{386,586tsc,686}
>
> The old kernel was handcrafted.
Okay, so this person had a nice tailored kernel done, and instead of simply
upgrading
On Thu, 18 Apr 2002 15:32, Michael Piefel wrote:
> The Crash
> Well, simply, it was the wrong kernel. The guide recommends to install
> a new kernel with: apt-get install kernel-image-2.4.18-{386,586tsc,686}
> However, the system has a AMD K6. Of course it's his fault for choosing
386, 486, and
A friend of mine who's quite well-versed in handling Linux, but not so
experienced with Debian, tried to upgrade his old Potato system to
Woody. It went quite well as he adhered to the instructions on
http://www.debian.org/releases/woody/i386/release-notes/ch-upgrading
Unfortunately, though, the s
16 matches
Mail list logo