Hello
Sven Heinicke (<[EMAIL PROTECTED]>) wrote:
> $ apt-cache search kernel-image 2.4.18 686
> kernel-image-2.4.18-686 - Linux kernel image 2.4.18 on
> PPro/Celeron/PII/PIII/PIV. kernel-image-2.4.18-686-smp - Linux kernel
> image 2.4.18 on PPro/Celeron/PII/PIII/PIV SMP.
>
$ apt-cache search kernel-image 2.4.18 686
kernel-image-2.4.18-686 - Linux kernel image 2.4.18 on PPro/Celeron/PII/PIII/PIV.
kernel-image-2.4.18-686-smp - Linux kernel image 2.4.18 on PPro/Celeron/PII/PIII/PIV
SMP.
kernel-image-2.4.18-1-686 - Linux kernel image 2.4.18 on PPro/Celeron/PII/PIII
Richard Lyons wrote:
> Andreas Janssen wrote:
> > apt-get install kernel-image-2.4.18-686
> Well, that was easy. Don't know what to say: I expect things to go
> wrong.
The only thing that usually "goes wrong" here is that the
bootstrapping kernel has a lot of devic
On 03-08-03 21:09 +0200, Andreas Janssen wrote:
> Richard Lyons (<[EMAIL PROTECTED]>) wrote:
> > It seems, after _huge_ help from Andrew McGuinness and others, that I
> > am going to have to change from the bf2.4 flavour to
> > kernel-image-2.4.18-686. Now, I am sca
On Sunday 03 August 2003 20:09, Andreas Janssen wrote:
[...]
> apt-get install kernel-image-2.4.18-686
[...]
> If you use lilo, it will already have a section "LinuxOLD"
> additionally to "Linux", so simply rerunning lilo after installing
[...]
Well, that was eas
On Sun, 03 Aug 2003 20:40:08 +0200, Richard Lyons wrote:
> It seems, after _huge_ help from Andrew McGuinness and others, that I
> am going to have to change from the bf2.4 flavour to
> kernel-image-2.4.18-686. Now, I am scared of messing with kernels
> anyway, and new to apt
Hello
Richard Lyons (<[EMAIL PROTECTED]>) wrote:
> It seems, after _huge_ help from Andrew McGuinness and others, that I
> am going to have to change from the bf2.4 flavour to
> kernel-image-2.4.18-686. Now, I am scared of messing with kernels
> anyway, and new to apt as wel
It seems, after _huge_ help from Andrew McGuinness and others, that I
am going to have to change from the bf2.4 flavour to
kernel-image-2.4.18-686. Now, I am scared of messing with kernels
anyway, and new to apt as well. I don't see in the apt HOWTO exactly
how to "upgrade" a
Well, a little over a year after I posted the question, I found
the solution to my question. TeXlive contains a readlink program
which was earlier in the path that /bin/readlink. That's it. I
exited dselect, changed the path in the shell, and reran the
installation. The same thing happened with
On Thu, Sep 19, 2002 at 02:12:40PM -0400, Travis Crump wrote:
> I was also never able to figure out what you could do with it anyway.
From what I understand, this allows you to move around in the initrd
image, in other words, the initial root. You could probaby trojan some
kerenl modules somehow
Walter Tautz wrote:
> just curious since it allows anyone to get a root shell with getting prompted
> for a root passwd.
>
If someone is watching the bootup then couldn't they just as easily boot
from a floppy or CD or hold down alt+shift during boot and type '
init=/bin/sh'? Though I guess
just curious since it allows anyone to get a root shell with getting prompted
for a root passwd.
Also if one hits enter and then exit it fails to mount the root fs, VFS error
occurs. NOTE this does not happen if the kernel is allowed to boot normally.
walter
--
To UNSUBSCRIBE, email to [EMAI
On Fri, 2002-05-24 at 18:58, Petro wrote:
> On Fri, May 24, 2002 at 09:50:29AM -0500, Ken Causey wrote:
> > > On 05/24 05:07 Ken Causey wrote:
> > > > VFS: Cannot open root device "802" or 08:02
> > > > Please append a correct "root=" boot option
> > > > Kernel panic: VFS: Unable to mount root fs o
On Fri, May 24, 2002 at 09:47:52AM -0500, Ken Causey wrote:
> > Well, it makes sense to make the kernel executable, but
> > that doesn't seem to be the problem as the kernel seems to be
> > executing already (all that output is from the kernel, I think).
> >
> > It all looks normal until the end, w
> On 05/24 05:07 Ken Causey wrote:
> > ...
> > VFS: Cannot open root device "802" or 08:02
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on 08:02
> >
> > I have a single SCSI drive (2 partitions, first is swap, second is
> root)
> > connected via a
> Well, it makes sense to make the kernel executable, but
> that doesn't seem to be the problem as the kernel seems to be
> executing already (all that output is from the kernel, I think).
>
> It all looks normal until the end, when the kernel can't mount>
> the root partition. You say you have a
>From /boot/config-2.4.18-686-smp
CONFIG_SCSI=m
CONFIG_SCSI_AIC7XXX=m
Should provide what's necessary for Adaptec 29160 no?
Ken
On Thu, 2002-05-23 at 23:16, Greg Madden wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Read the /boot/config-kernel-image-xxx file and see what scsi
On Thu, 2002-05-23 at 17:45, Robert Webb wrote:
> I am new to Linux but doesn't your /boot/initrd.img-2.4.18-686-smp file
> need to be -rwxr-xr-x
>
> This is the way mine is
>
My first inclination was to say "No." My second inclination was to give
it a try. Thanks for the suggestion but
On 05/24 05:07 Ken Causey wrote:
...
VFS: Cannot open root device "802" or 08:02
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:02
I have a single SCSI drive (2 partitions, first is swap, second is root)
connected via an Adaptec 29160.
I didn't see
:
> I am new to Linux but doesn't your /boot/initrd.img-2.4.18-686-smp file
> need to be -rwxr-xr-x
>
> This is the way mine is
>
> Ken Causey wrote:
>
> >I'm running into trouble trying to boot using
> >kernel-image-2.4.18-686-smp_2.4.18-5_i386
I am new to Linux but doesn't your /boot/initrd.img-2.4.18-686-smp file
need to be -rwxr-xr-x
This is the way mine is
Ken Causey wrote:
I'm running into trouble trying to boot using
kernel-image-2.4.18-686-smp_2.4.18-5_i386 from testing,
Linux version 2.4.18-686-smp ([EMAIL
I'm running into trouble trying to boot using
kernel-image-2.4.18-686-smp_2.4.18-5_i386 from testing,
Linux version 2.4.18-686-smp ([EMAIL PROTECTED]) (gcc version 2.95.4
20011002 (Debian prerelease)) #1 SMP Sun 2BIOS-provided physical RAM
map:
Davi Leal wrote:
> My original installation, which I have upgraded, is from a woody CD-ROM
> with 2.2.20 kernel. I am running now a 2.4.18 kernel compiled from source
> (make xconfig dep bzImage modules modules_install + lilo). Note that I do
> not use-compile initrd ramdisk support on it. Why my
On Sun, 2002-03-17 at 10:03, Davi Leal wrote:
> Installing the kernel-image-2.4.18-686 package I get:
>
>
> You are attempting to install an initrd kernel image (version 2.4.18-686)
> This will not work unless you have configured your boot loader to use
> initrd.
> As a
On Sun, Mar 17, 2002 at 08:03:51PM +0100, Davi Leal wrote:
> Installing the kernel-image-2.4.18-686 package I get:
> My original installation, which I have upgraded, is from a woody CD-ROM with
> 2.2.20 kernel. I am running now a 2.4.18 kernel compiled from source (make
> xconfig
Installing the kernel-image-2.4.18-686 package I get:
You are attempting to install an initrd kernel image (version 2.4.18-686)
This will not work unless you have configured your boot loader to use
initrd.
As a reminder, in order to configure lilo, you need to
add an 'initrd=/initrd.img
26 matches
Mail list logo
