Re: What to do with multiple kernel images

[gary turner]

David Witbrodt wrote:



Thanks, I ran purge on the four oldest.  Three of them reported an error:

rmdir: failed to remove `/lib/modules/2.6.22-3-486': Directory not empty
dpkg - warning: while removing linux-image-2.6.22-3-486, directory 
`/lib/modules/2.6.22-3-486' not empty so not removed.






Do these belong to a package, or would I simply rm them?


The package manager is telling you that files that were NOT part of the
package are present in a directory that it should be able to delete.
Either you, or some other package you installed, placed that file there.

I get this warning myself, because I use the proprietary NVidia modules
instead of the Debian packages.  (The NVidia installer compiles a kernel
module and places it in /lib/modules, and makes no attempt to use my nice
package management system -- unlike the ATI proprietary drivers, which
creates actual DEBs.)

Since my leftover 'nvidia' module is not track by APT, I _do_ just use
'rm':

# cd /lib/modules
# rm -vrf 2.6.22-3-486

The last command verbosely removes the directory for that kernel's
modules, and any files in it.  Only use a command like that if you are
SURE the kernel has been removed (i.e., 'aptitude purge ')
and the directory really is not needed.  Any slip of the keyboard, or
PEBKAC attack, and you cannot get back the files you lost!


Brain-farts are high on my list of mortal fears. :)

Thanks for the background info.  All is done now.  Thanks, too, to Alex 
and Andrei.


cheers,

gary
--
Anyone can make a usable web site. It takes a graphic
designer to make it slow, confusing and painful to use.
begin:vcard
fn:Gary Turner
n:Turner;Gary
org:Gary Turner, Web Developer
adr:;;USA
email;internet:[EMAIL PROTECTED]
title:Czar
x-mozilla-html:FALSE
url:http://gtwebdev.com/
version:2.1
end:vcard

Re: What to do with multiple kernel images

[David Witbrodt]

> Thanks, I ran purge on the four oldest.  Three of them reported an error:
> 
> rmdir: failed to remove `/lib/modules/2.6.22-3-486': Directory not empty
> dpkg - warning: while removing linux-image-2.6.22-3-486, directory 
> `/lib/modules/2.6.22-3-486' not empty so not removed.
> 
> koko:/lib/modules/2.6.22-3-486$ ls -al
> total 12
> drwxr-xr-x 2 root root 4096 2008-08-15 05:33 .
> drwxr-xr-x 7 root root 4096 2008-08-15 05:26 ..
> -rw-r--r-- 1 root root 1303 2007-12-07 22:19 modules.seriomap
> koko:/lib/modules/2.6.22-3-486$
> 
> Do these belong to a package, or would I simply rm them?

The package manager is telling you that files that were NOT part of the
package are present in a directory that it should be able to delete.
Either you, or some other package you installed, placed that file there.

I get this warning myself, because I use the proprietary NVidia modules
instead of the Debian packages.  (The NVidia installer compiles a kernel
module and places it in /lib/modules, and makes no attempt to use my nice
package management system -- unlike the ATI proprietary drivers, which
creates actual DEBs.)

Since my leftover 'nvidia' module is not track by APT, I _do_ just use
'rm':

# cd /lib/modules
# rm -vrf 2.6.22-3-486

The last command verbosely removes the directory for that kernel's
modules, and any files in it.  Only use a command like that if you are
SURE the kernel has been removed (i.e., 'aptitude purge ')
and the directory really is not needed.  Any slip of the keyboard, or
PEBKAC attack, and you cannot get back the files you lost!


HTH,
Dave W.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: What to do with multiple kernel images

[Alex Samad]

On Fri, Aug 15, 2008 at 05:52:05AM -0500, gary turner wrote:
> Alex Samad wrote:
>> On Fri, Aug 15, 2008 at 01:06:39AM -0500, gary turner wrote:
>>> Through upgrades, etc., I've accumulated six kernel images.
>>>
>>> [EMAIL PROTECTED]:~$ ls /boot
> 
>>> Can I safely rm those I don't want to keep?  Are there other 
>>> directories  and files that need to be included in the clean-up?
>> as suggested in other email [from Andrei Popescu] don't rm them, use 
>> aptitude purge, but I
>> would keep atleast 2 versions, incase a upgrade fails
>>
> Thanks, I ran purge on the four oldest.  Three of them reported an error:
>
> rmdir: failed to remove `/lib/modules/2.6.22-3-486': Directory not empty
> dpkg - warning: while removing linux-image-2.6.22-3-486, directory  
> `/lib/modules/2.6.22-3-486' not empty so not removed.
>
> koko:/lib/modules/2.6.22-3-486$ ls -al
> total 12
> drwxr-xr-x 2 root root 4096 2008-08-15 05:33 .
> drwxr-xr-x 7 root root 4096 2008-08-15 05:26 ..
> -rw-r--r-- 1 root root 1303 2007-12-07 22:19 modules.seriomap
> koko:/lib/modules/2.6.22-3-486$
>
> Do these belong to a package, or would I simply rm them?
dpks -S  is your friend.  But from memory
modules.seriomap is a generated file so just rm -fr
/lib/modules/2.6.22-3-486


>
> gary
> -- 
> Anyone can make a usable web site. It takes a graphic
> designer to make it slow, confusing and painful to use.

> begin:vcard
> fn:Gary Turner
> n:Turner;Gary
> org:Gary Turner, Web Developer
> adr:;;USA
> email;internet:[EMAIL PROTECTED]
> title:Czar
> x-mozilla-html:FALSE
> url:http://gtwebdev.com/
> version:2.1
> end:vcard
> 


-- 
Skinner: If you can't keep you head, it's OK to step away.
Scully: That's exactly what they want.

"The X-Files: Aprocrypha"


signature.asc
Description: Digital signature

Re: What to do with multiple kernel images

[gary turner]

Alex Samad wrote:

On Fri, Aug 15, 2008 at 01:06:39AM -0500, gary turner wrote:

Through upgrades, etc., I've accumulated six kernel images.

[EMAIL PROTECTED]:~$ ls /boot


Can I safely rm those I don't want to keep?  Are there other directories  
and files that need to be included in the clean-up?

as suggested in other email [from Andrei Popescu] don't rm them, use aptitude 
purge, but I
would keep atleast 2 versions, incase a upgrade fails


Thanks, I ran purge on the four oldest.  Three of them reported an error:

rmdir: failed to remove `/lib/modules/2.6.22-3-486': Directory not empty
dpkg - warning: while removing linux-image-2.6.22-3-486, directory 
`/lib/modules/2.6.22-3-486' not empty so not removed.


koko:/lib/modules/2.6.22-3-486$ ls -al
total 12
drwxr-xr-x 2 root root 4096 2008-08-15 05:33 .
drwxr-xr-x 7 root root 4096 2008-08-15 05:26 ..
-rw-r--r-- 1 root root 1303 2007-12-07 22:19 modules.seriomap
koko:/lib/modules/2.6.22-3-486$

Do these belong to a package, or would I simply rm them?

gary
--
Anyone can make a usable web site. It takes a graphic
designer to make it slow, confusing and painful to use.
begin:vcard
fn:Gary Turner
n:Turner;Gary
org:Gary Turner, Web Developer
adr:;;USA
email;internet:[EMAIL PROTECTED]
title:Czar
x-mozilla-html:FALSE
url:http://gtwebdev.com/
version:2.1
end:vcard

Re: What to do with multiple kernel images

[Alex Samad]

On Fri, Aug 15, 2008 at 01:06:39AM -0500, gary turner wrote:
> Through upgrades, etc., I've accumulated six kernel images.
>
> [EMAIL PROTECTED]:~$ ls /boot
> config-2.6.18-5-486  initrd.img-2.6.25-2-486
> config-2.6.21-2-486  initrd.img-2.6.25-2-486.bak
> config-2.6.22-2-486  System.map-2.6.18-5-486
> config-2.6.22-3-486  System.map-2.6.21-2-486
> config-2.6.24-1-486  System.map-2.6.22-2-486
> config-2.6.25-2-486  System.map-2.6.22-3-486
> grub System.map-2.6.24-1-486
> initrd.img-2.6.18-5-486  System.map-2.6.25-2-486
> initrd.img-2.6.18-5-486.bak  vmlinuz-2.6.18-5-486
> initrd.img-2.6.21-2-486  vmlinuz-2.6.21-2-486
> initrd.img-2.6.22-2-486  vmlinuz-2.6.22-2-486
> initrd.img-2.6.22-3-486  vmlinuz-2.6.22-3-486
> initrd.img-2.6.22-3-486.bak  vmlinuz-2.6.24-1-486
> initrd.img-2.6.24-1-486  vmlinuz-2.6.25-2-486
> initrd.img-2.6.24-1-486.bak
> [EMAIL PROTECTED]:~$
>
> Can I safely rm those I don't want to keep?  Are there other directories  
> and files that need to be included in the clean-up?
as suggested in other email don't rm them, use aptitude purge, but I
would keep atleast 2 versions, incase a upgrade fails

>
> cheers,
>
> gary
> -- 
> Anyone can make a usable web site. It takes a graphic
> designer to make it slow, confusing and painful to use.

> begin:vcard
> fn:Gary Turner
> n:Turner;Gary
> org:Gary Turner, Web Developer
> adr:;;USA
> email;internet:[EMAIL PROTECTED]
> title:Czar
> x-mozilla-html:FALSE
> url:http://gtwebdev.com/
> version:2.1
> end:vcard
> 


-- 
"We ought to make the pie higher."

- George W. Bush
02/15/2000
South Carolina Republican Debate


signature.asc
Description: Digital signature

Re: What to do with multiple kernel images

[Andrei Popescu]

On Fri,15.Aug.08, 01:06:39, gary turner wrote:
> Through upgrades, etc., I've accumulated six kernel images.
>
> [EMAIL PROTECTED]:~$ ls /boot
> config-2.6.18-5-486  initrd.img-2.6.25-2-486
> config-2.6.21-2-486  initrd.img-2.6.25-2-486.bak
> config-2.6.22-2-486  System.map-2.6.18-5-486
> config-2.6.22-3-486  System.map-2.6.21-2-486
> config-2.6.24-1-486  System.map-2.6.22-2-486
> config-2.6.25-2-486  System.map-2.6.22-3-486
> grub System.map-2.6.24-1-486
> initrd.img-2.6.18-5-486  System.map-2.6.25-2-486
> initrd.img-2.6.18-5-486.bak  vmlinuz-2.6.18-5-486
> initrd.img-2.6.21-2-486  vmlinuz-2.6.21-2-486
> initrd.img-2.6.22-2-486  vmlinuz-2.6.22-2-486
> initrd.img-2.6.22-3-486  vmlinuz-2.6.22-3-486
> initrd.img-2.6.22-3-486.bak  vmlinuz-2.6.24-1-486
> initrd.img-2.6.24-1-486  vmlinuz-2.6.25-2-486
> initrd.img-2.6.24-1-486.bak
> [EMAIL PROTECTED]:~$
>
> Can I safely rm those I don't want to keep?  Are there other directories 
> and files that need to be included in the clean-up?

Don't rm them, use 'aptitude purge' (or similar).

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

What to do with multiple kernel images

[gary turner]

Through upgrades, etc., I've accumulated six kernel images.

[EMAIL PROTECTED]:~$ ls /boot
config-2.6.18-5-486  initrd.img-2.6.25-2-486
config-2.6.21-2-486  initrd.img-2.6.25-2-486.bak
config-2.6.22-2-486  System.map-2.6.18-5-486
config-2.6.22-3-486  System.map-2.6.21-2-486
config-2.6.24-1-486  System.map-2.6.22-2-486
config-2.6.25-2-486  System.map-2.6.22-3-486
grub System.map-2.6.24-1-486
initrd.img-2.6.18-5-486  System.map-2.6.25-2-486
initrd.img-2.6.18-5-486.bak  vmlinuz-2.6.18-5-486
initrd.img-2.6.21-2-486  vmlinuz-2.6.21-2-486
initrd.img-2.6.22-2-486  vmlinuz-2.6.22-2-486
initrd.img-2.6.22-3-486  vmlinuz-2.6.22-3-486
initrd.img-2.6.22-3-486.bak  vmlinuz-2.6.24-1-486
initrd.img-2.6.24-1-486  vmlinuz-2.6.25-2-486
initrd.img-2.6.24-1-486.bak
[EMAIL PROTECTED]:~$

Can I safely rm those I don't want to keep?  Are there other directories 
and files that need to be included in the clean-up?


cheers,

gary
--
Anyone can make a usable web site. It takes a graphic
designer to make it slow, confusing and painful to use.
begin:vcard
fn:Gary Turner
n:Turner;Gary
org:Gary Turner, Web Developer
adr:;;USA
email;internet:[EMAIL PROTECTED]
title:Czar
x-mozilla-html:FALSE
url:http://gtwebdev.com/
version:2.1
end:vcard

Re: How and where do i remove old kernel images to make space for new ones :o)

[Michelle Konzack]

Am 2008-05-03 12:40:25, schrieb Mr Smiley:
> FilesystemSize  Used Avail Use% Mounted on
> /dev/hda5 250M  216M   21M  92% /

Since new kernles will grow with the time (2.4.27 has  already  35 MByte
and the 2.4.35 now 29 MByte) the partition  which  seems  to  hold  /bin,
/boot, /etc, /lib and /sbin has to bee bigger.

Maybe you should reorganize your Hardrive?

Like:

/dev/hda5   3400M   /
/dev/hda6 
/dev/hda7   1000M   /var
/dev/hda8 ???
/dev/hda9 
/dev/hda10  3200M   /home

which mean, drop /dev/hda6 and /dev/hda9 and put the others together but
I do not recomment to push /var into the / partiton which I would  never
do.

Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
+49/177/935194750, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Re: How and where do i remove old kernel images to make space for new ones :o)

[Tzafrir Cohen]

On Sun, May 04, 2008 at 01:35:32AM -0500, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 05/03/08 15:52, Tzafrir Cohen wrote:
> > On Sat, May 03, 2008 at 02:49:02PM -0500, Ron Johnson wrote:
> >>
> >> On 05/03/08 14:40, Mr Smiley wrote:
> >>> Hi all,
> >>>
> >>> I'm doing my daily apt-get update and updating my
> >>> kernal-image is reporting the following.
> >>>
> >>>
> >>> Unpacking replacement linux-image-2.6.18-6-686 ...
> >>> dpkg: error processing
> >>> /var/cache/apt/archives/linux-image-2.6.18-6-686_2.6.18.dfsg.1-18etch3_i386.deb
> >>> (--unpack):
> >>>  failed in buffer_write(fd) (9, ret=-1): backend
> >>> dpkg-deb during
> >>> `./lib/modules/2.6.18-6-686/kernel/net/bridge/netfilter/ebt_dnat.ko':
> >>> No space left on device
> >>>
> >> [snip]
> >>>
> >>> as can be seen, 
> >>>
> >>> /dev/hda5 250M  216M   21M  92% /
> >>>
> >>> is a bit full
> >>>
> >>> or could it be /usr that's causing the problems.
> >>>
> >>> I'm not sure what to delete safely
> >> # apt-get clean
> > 
> > This provides extra space in /var . And the space seems to be missing in
> > / .
> 
> Ah.  Shame on me for not noticing that.  What exactly is in /?  Doug
> Tutty's mention of kernels, and thus /boot, is a good starting point.

du -x /

/lost+found ?

Anyway, that partitioning scheme looks like a nice way of shooting
himself in the foot.

-- 
Tzafrir Cohen | [EMAIL PROTECTED] | VIM is
http://tzafrir.org.il || a Mutt's
[EMAIL PROTECTED] ||  best
ICQ# 16849754 || friend


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How and where do i remove old kernel images to make space for new ones :o)

[Ron Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/03/08 15:52, Tzafrir Cohen wrote:
> On Sat, May 03, 2008 at 02:49:02PM -0500, Ron Johnson wrote:
>>
>> On 05/03/08 14:40, Mr Smiley wrote:
>>> Hi all,
>>>
>>> I'm doing my daily apt-get update and updating my
>>> kernal-image is reporting the following.
>>>
>>>
>>> Unpacking replacement linux-image-2.6.18-6-686 ...
>>> dpkg: error processing
>>> /var/cache/apt/archives/linux-image-2.6.18-6-686_2.6.18.dfsg.1-18etch3_i386.deb
>>> (--unpack):
>>>  failed in buffer_write(fd) (9, ret=-1): backend
>>> dpkg-deb during
>>> `./lib/modules/2.6.18-6-686/kernel/net/bridge/netfilter/ebt_dnat.ko':
>>> No space left on device
>>>
>> [snip]
>>>
>>> as can be seen, 
>>>
>>> /dev/hda5 250M  216M   21M  92% /
>>>
>>> is a bit full
>>>
>>> or could it be /usr that's causing the problems.
>>>
>>> I'm not sure what to delete safely
>> # apt-get clean
> 
> This provides extra space in /var . And the space seems to be missing in
> / .

Ah.  Shame on me for not noticing that.  What exactly is in /?  Doug
Tutty's mention of kernels, and thus /boot, is a good starting point.

- --
Ron Johnson, Jr.
Jefferson LA  USA

We want... a Shrubbery!!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIHVk0S9HxQb37XmcRArz2AKDbq8N7o3NiRx6IoE0TZqjRopjn2wCfRV1y
z6z/b1Re3AFmr0bGCA/4DUM=
=sA4e
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How and where do i remove old kernel images to make space for new ones :o)

[Douglas A. Tutty]

On Sat, May 03, 2008 at 12:40:25PM -0700, Mr Smiley wrote:
> I'm doing my daily apt-get update and updating my
> kernal-image is reporting the following.
[snip]
> No space left on device
> 
> 
> df -alh says
> 
> 
> FilesystemSize  Used Avail Use% Mounted on
> /dev/hda5 250M  216M   21M  92% /
[snip]
> /dev/hda6 2.8G  2.4G  234M  92% /usr
> /dev/hda7 1.3G  323M  909M  27% /var
[snip]
> 
> I'm not sure what to delete safely

I'd check to see if you have old versions of the kernel installed.  You
can check with aptitude or just look in /lib.  You should have room for
at least 3 kernels, 2 at a minimum.  You need to have room to update a
kernel to a new version while keeping the old version in case of
problems.  Updating to the same version shouldn't use up any space in
either /lib or /boot.

I suggest that you have the linux-image-2.6-[arch] meta-package
installed, which will depend on the specific most current kernel.  Note
that this doesn't automatically remove old kernels as new ones are
installed.  You have to use aptitude and search for all the kernels and
delete those you don't need.

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How and where do i remove old kernel images to make space for new ones :o)

[Tzafrir Cohen]

On Sat, May 03, 2008 at 02:49:02PM -0500, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 05/03/08 14:40, Mr Smiley wrote:
> > Hi all,
> > 
> > I'm doing my daily apt-get update and updating my
> > kernal-image is reporting the following.
> > 
> > 
> > Unpacking replacement linux-image-2.6.18-6-686 ...
> > dpkg: error processing
> > /var/cache/apt/archives/linux-image-2.6.18-6-686_2.6.18.dfsg.1-18etch3_i386.deb
> > (--unpack):
> >  failed in buffer_write(fd) (9, ret=-1): backend
> > dpkg-deb during
> > `./lib/modules/2.6.18-6-686/kernel/net/bridge/netfilter/ebt_dnat.ko':
> > No space left on device
> > 
> [snip]
> > 
> > 
> > as can be seen, 
> > 
> > /dev/hda5 250M  216M   21M  92% /
> > 
> > is a bit full
> > 
> > or could it be /usr that's causing the problems.
> > 
> > I'm not sure what to delete safely
> 
> # apt-get clean

This provides extra space in /var . And the space seems to be missing in
/ .

-- 
Tzafrir Cohen | [EMAIL PROTECTED] | VIM is
http://tzafrir.org.il || a Mutt's
[EMAIL PROTECTED] ||  best
ICQ# 16849754 || friend


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How and where do i remove old kernel images to make space for new ones :o)

[Ron Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/03/08 14:40, Mr Smiley wrote:
> Hi all,
> 
> I'm doing my daily apt-get update and updating my
> kernal-image is reporting the following.
> 
> 
> Unpacking replacement linux-image-2.6.18-6-686 ...
> dpkg: error processing
> /var/cache/apt/archives/linux-image-2.6.18-6-686_2.6.18.dfsg.1-18etch3_i386.deb
> (--unpack):
>  failed in buffer_write(fd) (9, ret=-1): backend
> dpkg-deb during
> `./lib/modules/2.6.18-6-686/kernel/net/bridge/netfilter/ebt_dnat.ko':
> No space left on device
> 
[snip]
> 
> 
> as can be seen, 
> 
> /dev/hda5 250M  216M   21M  92% /
> 
> is a bit full
> 
> or could it be /usr that's causing the problems.
> 
> I'm not sure what to delete safely

# apt-get clean

- --
Ron Johnson, Jr.
Jefferson LA  USA

We want... a Shrubbery!!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIHMGuS9HxQb37XmcRAuGlAJ0YOvBDiwE6YEmgj6skJ6Es+C/vJgCfcN/Z
AORtzEreLO1x7jC5MPA6+Eo=
=IQRw
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

How and where do i remove old kernel images to make space for new ones :o)

[Mr Smiley]

Hi all,

I'm doing my daily apt-get update and updating my
kernal-image is reporting the following.


Unpacking replacement linux-image-2.6.18-6-686 ...
dpkg: error processing
/var/cache/apt/archives/linux-image-2.6.18-6-686_2.6.18.dfsg.1-18etch3_i386.deb
(--unpack):
 failed in buffer_write(fd) (9, ret=-1): backend
dpkg-deb during
`./lib/modules/2.6.18-6-686/kernel/net/bridge/netfilter/ebt_dnat.ko':
No space left on device


df -alh says


FilesystemSize  Used Avail Use% Mounted on
/dev/hda5 250M  216M   21M  92% /
tmpfs 173M 0  173M   0%
/lib/init/rw
proc 0 0 0   -  /proc
sysfs0 0 0   -  /sys
procbususb   0 0 0   - 
/proc/bus/usb
udev   10M   80K   10M   1% /dev
tmpfs 173M 0  173M   0% /dev/shm
devpts   0 0 0   -  /dev/pts
/dev/hda102.8G  2.5G  160M  95% /home
/dev/hda9 221M  4.1M  205M   2% /tmp
/dev/hda6 2.8G  2.4G  234M  92% /usr
/dev/hda7 1.3G  323M  909M  27% /var
binfmt_misc  0 0 0   - 
/proc/sys/fs/binfmt_misc


as can be seen, 

/dev/hda5 250M  216M   21M  92% /

is a bit full

or could it be /usr that's causing the problems.

I'm not sure what to delete safely


Many thanks

Ken





.




  __
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Kernel images in etch broke? (was: pre-installation script returned error during package installation)

[T]

On Sun, 25 Jun 2006 16:19:48 -0400, T wrote:

> I got the "pre-installation script returned error" during package
> installation. Is there any solution / workaround? What else should I
> check?
> 
> thanks
> 
> Tong
> 
> PS. here is the full info:
> 
> Installing linux-image-2.6.15-1-k7 under etch failed:
> 
> % apt-get install linux-image-2.6.15-1-k7 Suggested packages:
>   linux-doc-2.6.15 linux-source-2.6.15 lilo grub fdutils
> Recommended packages:
>   libc6-i686
> The following NEW packages will be installed:
>   linux-image-2.6.15-1-k7
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Preconfiguring packages ...
> (Reading database ... 52510 files and directories currently installed.)
> Unpacking linux-image-2.6.15-1-k7 (from
> .../linux-image-2.6.15-1-k7_2.6.15-8_i386.deb) ... Ok, Aborting
> dpkg: error processing
> /var/cache/apt/archives/linux-image-2.6.15-1-k7_2.6.15-8_i386.deb
> (--unpack):
>  subprocess pre-installation script returned error exit status 1
> Errors were encountered while processing:
>  /var/cache/apt/archives/linux-image-2.6.15-1-k7_2.6.15-8_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

I just format the disk and did a clean base system installation then tried
again. Same error. 

Installing linux-image-2.6.15-1-686 is broken too:

The following extra packages will be installed:
  linux-image-2.6.15-1-686
Suggested packages:
  linux-doc-2.6.15 linux-source-2.6.15 lilo grub fdutils
Recommended packages:
  libc6-i686
The following NEW packages will be installed:
  linux-image-2.6.15-1-686
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0B/15.8MB of archives.
After unpacking 45.1MB of additional disk space will be used.
Do you want to continue [Y/n]? 
Preconfiguring packages ...
(Reading database ... 7356 files and directories currently installed.)
Unpacking linux-image-2.6.15-1-686 (from 
.../linux-image-2.6.15-1-686_2.6.15-8_i386.deb) ...
Ok, Aborting
dpkg: error processing 
/var/cache/apt/archives/linux-image-2.6.15-1-686_2.6.15-8_i386.deb (--unpack):
 subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/linux-image-2.6.15-1-686_2.6.15-8_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

cannot install kernel images anymore

[Dan Leitner]

Two recent attempts to install kernel images failed.

My stock backup kernel failed to upgrade yesterday.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287085

and now trying to add another as a backup also failed, but for different 
reasons???

In both cases the initrd image could not be created.

[EMAIL PROTECTED]:~$ sudo apt-get install kernel-image-2.6.8-9-amd64-k8
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
  lilo
The following NEW packages will be installed:
  kernel-image-2.6.8-9-amd64-k8
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 13.0MB of archives.
After unpacking 43.5MB of additional disk space will be used.
Get:1 http://mirrors.kernel.org testing/main kernel-image-2.6.8-9-amd64-k8 
2.6.8-5 [13.0MB]
Fetched 11.1MB in 2m51s (64.8kB/s)
Selecting previously deselected package kernel-image-2.6.8-9-amd64-k8.
(Reading database ... 96123 files and directories currently installed.)
Unpacking kernel-image-2.6.8-9-amd64-k8 (from 
.../kernel-image-2.6.8-9-amd64-k8_2.6.8-5_i386.deb) ...
Setting up kernel-image-2.6.8-9-amd64-k8 (2.6.8-5) ...
cpio: (0x): No such file or directory
cp: cannot stat `(0x)': No such file or directory
run-parts: /usr/share/initrd-tools/scripts/e2fsprogs exited with return code 1
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.8-9-amd64-k8 (--configure):
 subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
 kernel-image-2.6.8-9-amd64-k8
E: Sub-process /usr/bin/dpkg returned an error code (1)
[EMAIL PROTECTED]:~$


My current kernel kernel-image-2.6.8-9-amd64-k8-smp runs OK, but no backup.

There exists some type of bug, but in which package?

I'm far from being an expert, so any help or suggestions? 

DL




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

newbie: kernel images and raid

[Martin]

Hi,

I'd like to use debian for a server project on a Dell 400SC. I want to
stick to a platform that is easily upgradable but one which will also
support booting from software raid.

Is there a kernel image with raid built in (i.e. not as a loadable module)?

If not I understand that I will need to build a custom kernel and turn
raid on in the kernel. If I take this route I believe future kernel
upgrades will always need to built from source?

Now say I build a 2.4.22 system today customise the kernel move the
install to my raid disks etc. I carry on building new 2.4 versions from
source using the kernel package utils.

In a year or so when 2.6 becomes testing and I want to use that am I going
to have to build a new non raid system with a 2.6 image and go through the
same steps of customising and moving the install to raid to do a full dist
upgrade to solve depend issues?

My understanding of the apt system is that by sticking to the standard
kernel images I can just continue to upgrade as new versions become
available without compatability/depend issues(very appealing). I've just
done an apt-get install of the latest kernel image and it pulled
everything in very nicely.

I guess to sum up, "what upgrade issues will I have if I customise the
kernel and migrate to raid disks"

Thanks in advance,

Martin.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel-images

[Geoff Thurman]

On Tuesday 09 December 2003 9:08 pm, Andreas Janssen wrote:
> Hello
>
> Geoff Thurman (<[EMAIL PROTECTED]>) wrote:
> > Is it possible for the unwitting to install a kernel-image
> > downloaded from official debian sources that hasn't been patched
> > for the recent exploit, or can all the currently downloadable
> > images (and kernel source packages too, for that matter) be taken
> > to be safe from it? I've
> > switched to woody, and have today installed image-2-4-18-k6  #1,
> > dated Apr 14 2002. Clearly the date suggests no patch has been
> > applied, so is this kernel vulnerable to the exploit, please, or
> > does it not arise in this branch?
>
> Your Kernel is vulnerable. When the ptrace bug was fixed, the
> packages became incompatible to modules compiled for older versions,
> and they were renamed. Install kernel-image-2.4.18-1-k6 from
> security.debian.org. The current version from ftp.debian.org (Woody
> r2) does /not/ fix all vulnerabilities (I even think it is still the
> same one as in Woody r1 because newer packages were rejected from r2
> for some reasons).
>
> best regards
> Andreas Janssen

Sheesh. Thank you. The new one is downloading now.

Cheers,

Geoff


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel-images

[Andreas Janssen]

Hello

Geoff Thurman (<[EMAIL PROTECTED]>) wrote:

> Is it possible for the unwitting to install a kernel-image downloaded
> from official debian sources that hasn't been patched for the recent
> exploit, or can all the currently downloadable images (and kernel
> source packages too, for that matter) be taken to be safe from it?
> I've
> switched to woody, and have today installed image-2-4-18-k6  #1, dated
> Apr 14 2002. Clearly the date suggests no patch has been applied, so
> is this kernel vulnerable to the exploit, please, or does it not arise
> in this branch?

Your Kernel is vulnerable. When the ptrace bug was fixed, the packages
became incompatible to modules compiled for older versions, and they
were renamed. Install kernel-image-2.4.18-1-k6 from
security.debian.org. The current version from ftp.debian.org (Woody r2)
does /not/ fix all vulnerabilities (I even think it is still the same
one as in Woody r1 because newer packages were rejected from r2 for
some reasons).

best regards
Andreas Janssen

-- 
Andreas Janssen
[EMAIL PROTECTED]
PGP-Key-ID: 0xDC801674
Registered Linux User #267976


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

kernel-images

[Geoff Thurman]

Hello,

Is it possible for the unwitting to install a kernel-image downloaded 
from official debian sources that hasn't been patched for the recent 
exploit, or can all the currently downloadable images (and kernel 
source packages too, for that matter) be taken to be safe from it? I've 
switched to woody, and have today installed image-2-4-18-k6  #1, dated 
Apr 14 2002. Clearly the date suggests no patch has been applied, so is 
this kernel vulnerable to the exploit, please, or does it not arise in 
this branch?

Cheers,

Geoff


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 486 kernel images

[David Dumortier]

Hello

> 586 (Pentium classic) won't work.  The 486 (and all pentiums and
> clones) is backwards compatible with the 386 ISA.  That means that any
> valid 386 program can be handled by the 486 (and pentium, etc.)
> processor.  Install the 386 package.  Or build your own (which I
> recommend if you are short on memory and disk and want to minimize the
> size).

Sure it is, by experience, you MUST recompile it!
lspci, libncurses, kernel-packages are your friends !
X not !
Perhaps can help you (simple reply, always recompilr my kernel and job
forces me to do !). Perhaps I will make an help on my page some time
(dudu.prout.be) just for posterity and search in archive !

David Dumortier, kernel builder :-D
"I'm basically a very lazy person who likes to get credit for things other
people actually do."
-- Linus Torvalds


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 486 kernel images

[Derrick 'dman' Hudson]

On Tue, Jan 21, 2003 at 08:29:28AM -0800, machoamerica wrote:
| 
| i'm looking through the kernel-image packages and i see packages for
| all flavors of intel/amd processors except the 486.  can i use
| either kernel-image-2.4.x-386 or kernel-image-2.4.x-586 or do i have
| to muck around with a kernel-source-2.4.x package?

586 (Pentium classic) won't work.  The 486 (and all pentiums and
clones) is backwards compatible with the 386 ISA.  That means that any
valid 386 program can be handled by the 486 (and pentium, etc.)
processor.  Install the 386 package.  Or build your own (which I
recommend if you are short on memory and disk and want to minimize the
size).

-D

-- 
The lot is cast into the lap,
but its every decision is from the Lord.
Proverbs 16:33
 
http://dman.ddts.net/~dman/



msg25397/pgp0.pgp
Description: PGP signature

Re: 486 kernel images

[Greg Madden]

On Tuesday 21 January 2003 07:29 am, machoamerica wrote:
> i'm looking through the kernel-image packages and i see packages for
> all flavors of intel/amd processors except the 486.  can i use either
> kernel-image-2.4.x-386 or kernel-image-2.4.x-586 or do i have to muck
> around with a kernel-source-2.4.x package?
>
> thanks,
> macho

You might consider using the 2.2.x series of kernel. There is so much in a 
2.4.x kernel source that won't apply to a 486. 
-- 
Greg Madden


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 486 kernel images

[Chris Lale]

machoamerica wrote:
> i'm looking through the kernel-image packages and i see packages for
> all flavors of intel/amd processors except the 486.  can i use either
> kernel-image-2.4.x-386 or kernel-image-2.4.x-586 or do i have to muck
> around with a kernel-source-2.4.x package?

AFAIK you want kernel-image-2.4.x-386. This is a kind of "vanilla" 
flavour that will run on anything. You certainly do not want the 586 
version since the 486 processor is not a Pentium!

Cheers,

--
Chris Lale <[EMAIL PROTECTED]>


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 486 kernel images

[Stephen A. Witt]

On Tue, 21 Jan 2003, machoamerica wrote:

>
> i'm looking through the kernel-image packages and i see packages for all
> flavors of intel/amd processors except the 486.  can i use either
> kernel-image-2.4.x-386 or kernel-image-2.4.x-586 or do i have to muck
> around with a kernel-source-2.4.x package?
>

Use the i386 kernel images, they should run fine on a 486. I don't think
the 586 image would work on a 486. I know I once compiled a kernel package
using Pentium as the processor type and then mistakenly tried to install
it on a 486 machine and it crashed almost immediately.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 486 kernel images

[Johan Ehnberg]

machoamerica wrote:

i'm looking through the kernel-image packages and i see packages for
all flavors of intel/amd processors except the 486.  can i use either
kernel-image-2.4.x-386 or kernel-image-2.4.x-586 or do i have to muck
around with a kernel-source-2.4.x package?

thanks, macho


You can't use a kernel compiled for a better machine than you have, but 
yes, you can compile it for your machine from source. It's not that 
hard, but it'll take a while on a 486 :=). Anyway, you are safe with the 
386 version, and the performance loss shouldn't be noticeable.

hth,
/johan


--
Johan Ehnberg
[EMAIL PROTECTED]
"Windows? No... I don't think so."


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

486 kernel images

[machoamerica]

i'm looking through the kernel-image packages and i see packages for all flavors of 
intel/amd processors except the 486.  can i use either kernel-image-2.4.x-386 or 
kernel-image-2.4.x-586 or do i have to muck around with a kernel-source-2.4.x package?

thanks,
macho


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: configuration of kernel-images

[Timothy Webster]

-- Original Message --
From: Ben Collins <[EMAIL PROTECTED]>
Date:  Wed, 10 Oct 2001 22:38:40 -0400

>On Wed, Oct 10, 2001 at 09:58:01PM -0400, tim wrote:
>> 
>> How do I find out the compile configuration of a pre-compiled kernel-image? 
>> Such as kernel-image-2.4.10-k6.
>
>Look for the corresponding /boot/config-* file.

Thank you!

Re: configuration of kernel-images

[Ben Collins]

On Wed, Oct 10, 2001 at 09:58:01PM -0400, tim wrote:
> 
> How do I find out the compile configuration of a pre-compiled kernel-image? 
> Such as kernel-image-2.4.10-k6.

Look for the corresponding /boot/config-* file.

-- 
 .--===-=-==-=---==-=-.
/   Ben Collins--Debian GNU/Linux  \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'

configuration of kernel-images

[tim]

How do I find out the compile configuration of a pre-compiled kernel-image? 
Such as kernel-image-2.4.10-k6.

-Tim.
thanks inadvance.

Re: Kernel images

[Herbert Xu]

Raffaele Sandrini <[EMAIL PROTECTED]> wrote:

> I run woody. At this time i compile the kernel by myself. Yesterday i saw in 
> dselect that there are many kernel images avalible. But they are all 2.2.x 
> kernels and only one, the 2.4.0-test1 from the 2.4.x series.
> Now my question is: Why aren't there all the newer images? Does Debian no 
> more precompile a kernel?
> I know that i can do the same with the kernel-package.

They're still waiting to be moved into testing.  You'll see them if you
use unstable.  They'll probably enter testing within a week.
-- 
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Kernel images

[Raffaele Sandrini]

Hi gents,

I run woody. At this time i compile the kernel by myself. Yesterday i saw in 
dselect that there are many kernel images avalible. But they are all 2.2.x 
kernels and only one, the 2.4.0-test1 from the 2.4.x series.
Now my question is: Why aren't there all the newer images? Does Debian no 
more precompile a kernel?
I know that i can do the same with the kernel-package.

cheers,
Raffaele
-- 
Raffaele Sandrini <[EMAIL PROTECTED]>
For encrypted Mail get my Public Key from "search.keyserver.net"
ID is: 0xEC4950E9
Fingerprint: FFEA 3317 8624 4771 A05D 2AFA 46A2 A22B EC49 50E9

Re: naming kernel images (potato)

[Brad]

On Sat, Jun 03, 2000 at 12:37:11PM -0700, Pann McCuaig wrote:
> 
> I definitely don't want that to happen. It's never happened before under
> slink, hamm, bo, or rex that I recall.
> 
> Deep in the vague recesses of my memory I seem to recall an issue
> similar to this being discussed, with a suggestion for naming kernel
> images to avoid the problem.

As others have said, use epochs or put the thing on hold.

This also happened with the 2.2.5 kernel images, which is probably where
you vaguely remember it from. Since it didn't hit you, you must either
have not been following unstable or not using 2.2.5.


-- 
  finger for GPG public key.


pgpgoa68HQPLH.pgp
Description: PGP signature

Re: naming kernel images (potato)

[Bob Nielsen]

On Sat, Jun 03, 2000 at 03:45:39PM -0400, Ben Collins wrote:
> On Sat, Jun 03, 2000 at 12:37:11PM -0700, Pann McCuaig wrote:
> > Whenever I've built a kernel I've used the following syntax:
> > 
> > # make-kpkg --rev tux.1.0 kernel_image
> > 
> > where "tux" identifies the machine to me and "1.0" identifies which of
> > my revisions of the kernel I'm dealing with.
> > 
> > I install the resulting kernel-image-...-.deb with dpkg -i.
> > 
> > I recently upgraded a box to potato, grabbed the source for
> > kernel-2.2.15, and built and installed a kernel. No worries.
> > 
> > But,
> > 
> > # apt-get update ; apt-get -s upgrade
> > 
> > offered to upgrade kernel-image-2.2.15 for me.  :-(
> > 
> > I definitely don't want that to happen. It's never happened before under
> > slink, hamm, bo, or rex that I recall.
> > 
> > Deep in the vague recesses of my memory I seem to recall an issue
> > similar to this being discussed, with a suggestion for naming kernel
> > images to avoid the problem.
> 
> try...
> 
> # make-kpkg --rev 3:tux.1.0 kernel-image
> 
> The 3 is an epoch (not sure that kernel-package will let you use them, but
> give it a try). The epoch will override other versions of a lower epoch
> even if the rest of the version is higher.
> 

Yes, kernel-package will recognize the epoch.  I've been doing exactly
that.

Bob

-- 
Bob Nielsen, N7XY  (RN2)   [EMAIL PROTECTED]
Bainbridge Island, WA  http://www.oz.net/~nielsen
 

Re: naming kernel images (potato)

[Bart Szyszka]

> Whenever I've built a kernel I've used the following syntax:
> # make-kpkg --rev tux.1.0 kernel_image
> where "tux" identifies the machine to me and "1.0" identifies which of
> my revisions of the kernel I'm dealing with.
> I install the resulting kernel-image-...-.deb with dpkg -i.
> I recently upgraded a box to potato, grabbed the source for
> kernel-2.2.15, and built and installed a kernel. No worries.
> # apt-get update ; apt-get -s upgrade
> offered to upgrade kernel-image-2.2.15 for me.  :-(

I had the same problem and ended up putting the kernel-image...
package on hold using dselect. Now I'll just get new versions of
kernel-source-...

-- 
Bart Szyszka  [EMAIL PROTECTED]  ICQ:4982727
GigaBee Interactive  http://www.gigabee.com
PayPal - Securely send money to an e-mail user!
https://secure.paypal.com/refer/[EMAIL PROTECTED]

Re: naming kernel images (potato)

[Ben Collins]

On Sat, Jun 03, 2000 at 12:37:11PM -0700, Pann McCuaig wrote:
> Whenever I've built a kernel I've used the following syntax:
> 
> # make-kpkg --rev tux.1.0 kernel_image
> 
> where "tux" identifies the machine to me and "1.0" identifies which of
> my revisions of the kernel I'm dealing with.
> 
> I install the resulting kernel-image-...-.deb with dpkg -i.
> 
> I recently upgraded a box to potato, grabbed the source for
> kernel-2.2.15, and built and installed a kernel. No worries.
> 
> But,
> 
> # apt-get update ; apt-get -s upgrade
> 
> offered to upgrade kernel-image-2.2.15 for me.  :-(
> 
> I definitely don't want that to happen. It's never happened before under
> slink, hamm, bo, or rex that I recall.
> 
> Deep in the vague recesses of my memory I seem to recall an issue
> similar to this being discussed, with a suggestion for naming kernel
> images to avoid the problem.

try...

# make-kpkg --rev 3:tux.1.0 kernel-image

The 3 is an epoch (not sure that kernel-package will let you use them, but
give it a try). The epoch will override other versions of a lower epoch
even if the rest of the version is higher.

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'

naming kernel images (potato)

[Pann McCuaig]

Whenever I've built a kernel I've used the following syntax:

# make-kpkg --rev tux.1.0 kernel_image

where "tux" identifies the machine to me and "1.0" identifies which of
my revisions of the kernel I'm dealing with.

I install the resulting kernel-image-...-.deb with dpkg -i.

I recently upgraded a box to potato, grabbed the source for
kernel-2.2.15, and built and installed a kernel. No worries.

But,

# apt-get update ; apt-get -s upgrade

offered to upgrade kernel-image-2.2.15 for me.  :-(

I definitely don't want that to happen. It's never happened before under
slink, hamm, bo, or rex that I recall.

Deep in the vague recesses of my memory I seem to recall an issue
similar to this being discussed, with a suggestion for naming kernel
images to avoid the problem.

Details, anyone? Thanks.

Cheers,
 Pann
-- 
geek by nature, Linux by choice L I N U X   .~.
The Choice  /V\
http://www.ourmanpann.com/linux/ of a GNU  /( )\
Generation ^^-^^

Re: various kernel-images

[Bruce Sass]

On Thu, 25 May 2000, Parrish M Myers wrote:

> Hi all,
> 
> anyone know the difference between kernel-images?  There are several to
> choose from:
> 
> kernel-image-2.2.15-idepci_...
> kernel-image-2.2.15-ide_...
> kernel-image-2.2.15-compact_
> etc...
> 
> I can guess what the compact kernel image is but what are the other
> two?

These are the kernels used for the different `flavours' of the i386
boot-floppies for potato.  Checkout:
.../debian/dists/potato/main/disks-i386/current
("..." is the URI for your favorite Debian ftp mirror)
The READMEs scattered around the ftp site explain what each flavour is
for, the images-{1.44,2.88}/{compact,idepci,udma66,}/kernel-config files
contain a copy of the configuration of each kernel.


later,

Bruce

Re: various kernel-images

[Colin Watson]

[EMAIL PROTECTED] wrote:
>anyone know the difference between kernel-images?  There are several to
>choose from:
>
>kernel-image-2.2.15-idepci_...
>kernel-image-2.2.15-ide_...
>kernel-image-2.2.15-compact_
>etc...
>
>I can guess what the compact kernel image is but what are the other
>two?

dpkg is your friend:

[EMAIL PROTECTED] ~]$ dpkg -p kernel-image-2.2.15-idepci
Package: kernel-image-2.2.15-idepci
Priority: optional
Section: base
Installed-Size: 2388
Maintainer: Randolph Chung <[EMAIL PROTECTED]>
Architecture: i386
Version: 2.2.15pre20-1
Provides: kernel-image
Suggests: lilo (>= 19.1)
Filename: 
dists/unstable/main/binary-i386/base/kernel-image-2.2.15-idepci_2.2.15pre20-1.deb
Size: 1152426
MD5sum: 0153d59439737c95206c469d908b41c3
Description: Linux kernel binary image.
 This package contains the Linux kernel image, the System.map file,
 and the modules built by the packager.  It also contains scripts that
 try to ensure that the system is not left in a unbootable state
 after an update.
 .
 This is kernel version 2.2.15pre19
 .
 This version of the kernel image package only has ide and PCI device support.

You can try the rest yourself ...

-- 
Colin Watson [EMAIL PROTECTED]

various kernel-images

[Parrish M Myers]

Hi all,

anyone know the difference between kernel-images?  There are several to
choose from:

kernel-image-2.2.15-idepci_...
kernel-image-2.2.15-ide_...
kernel-image-2.2.15-compact_
etc...

I can guess what the compact kernel image is but what are the other
two?

Thanks 
Parrish

=
---
Academia is a little like child   | Parrish M. Myers
rearing, it provides a chance at  | The Wacked Jester
immortality without the stretch   | [EMAIL PROTECTED]
marks  -- (unknown source)|
---

__
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

Re: user can delete kernel images (cont)

[E.L. Meijer \(Eric\)]

manoj wrote:

>   Safe or not, it is UNIX ;-). Deleting a file is not actually
>  modifying the file, you are really modifying the directory the files
>  reside in. So, if you have write permissions to a directory, you may
>  delete any other file that is in there, as you observed. This can't
>  really be changed (this is the way things have behaved since the
>  beginning of the epoch).

This can actually be changed readily: if you set the sticky bit on the
directory (chmod +t ), then only the file owner (and root) can
remove a file in it, regardless of the fact that others may have write
permission as well.  This is used for scratch directories like /tmp.

Eric

-- 
 E.L. Meijer ([EMAIL PROTECTED])  | tel. office +31 40 2472189
 Eindhoven Univ. of Technology | tel. lab.   +31 40 2475032
 Lab. for Catalysis and Inorg. Chem. (TAK) | tel. fax+31 40 2455054


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: user can delete kernel images (cont)

[Manoj Srivastava]

Hi,
>>"G" == G Kapetanios <[EMAIL PROTECTED]> writes:

 G> So obviously although I hadn;t realised that before if a group you
 G> belong to owns a directory which is writable by the group you can
 G> delete stuff from it without owning the files and without
 G> belonging to the group which owns the files. Is this safe ??

Safe or not, it is UNIX ;-). Deleting a file is not actually
 modifying the file, you are really modifying the directory the files
 reside in. So, if you have write permissions to a directory, you may
 delete any other file that is in there, as you observed. This can't
 really be changed (this is the way things have behaved since the
 beginning of the epoch).

manoj

-- 
 A good awakening have ever Gotama's disciples, whose recollection is
 always established, day and night on the body. 299
Manoj Srivastava  <[EMAIL PROTECTED]> 
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: user can delete kernel images (cont)

[David Wright]

On Fri, 12 Jun 1998, Steve Mayer wrote:

>   I noticed this on my one remaining bo machine.  Hamm seems to have
> taken care of this bug.
> 
> G. Kapetanios wrote:
> > 
> > Following to my previous email I have to say some things.
> > 
> > the /boot directory in my machine is
> > 
> > drwxrwsr-x   2 root disk 2048 Jun 12 17:58 boot
> > the user who can do that belongs to the disk group but the file which was
> > deleted (/boot/vmlinuz.2.0.0) does not belong to the disk group it is
> > root.root So obviously although I hadn;t realised that before if a group
> > you belong to owns a directory which is writable by the group you can
> > delete stuff from it without owning
> > the files and without belonging to the group which owns the files. Is this
> > safe ?? More importantly I don't know if this is a bug of the installation
> > procedure about 1 1/2 years ago but the permission to /boot were set by
> > that procedure and I never changed them. I know users should not probably
 
> > belong to group disk but I could have damaged my system really bad if I

> > had no spare kernels. I guess I must remove the user from the disk group
> > as soon as possible.
> > 
> > By the way why is /boot writable by the group disk?

I don't know the "correct" permissions for /boot files, but in terms of
security, protecting them from disk-group users will be quite ineffective:
the disk group has write permission for raw disk devices.

The point about who can delete files in a directory is of course covered in
the FAQ under IIRC "I've discovered a HUGE security hole in rm!".

Cheers,

-- 
Email:  [EMAIL PROTECTED]   Tel: +44 1908 653 739  Fax: +44 1908 655 151
Snail:  David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA
Disclaimer:   These addresses are only for reaching me, and do not signify
official stationery. Views expressed here are either my own or plagiarised.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: user can delete kernel images (cont)

[Ed Cogburn]

G. Kapetanios wrote:
> 
> Following to my previous email I have to say some things.
> 
> the /boot directory in my machine is
> 
> drwxrwsr-x   2 root disk 2048 Jun 12 17:58 boot
> the user who can do that belongs to the disk group but the file which was
> deleted (/boot/vmlinuz.2.0.0) does not belong to the disk group it is
> root.root So obviously although I hadn;t realised that before if a group
> you belong to owns a directory which is writable by the group you can
> delete stuff from it without owning
> the files and without belonging to the group which owns the files. Is this
> safe ?? More importantly I don't know if this is a bug of the installation
> procedure about 1 1/2 years ago but the permission to /boot were set by
> that procedure and I never changed them. I know users should not probably
> belong to group disk but I could have damaged my system really bad if I
> had no spare kernels. I guess I must remove the user from the disk group
> as soon as possible.
> 
> By the way why is /boot writable by the group disk?
> 
> Sorry for the long email
> George
> 


On my hamm (clean install from v2.0 install disks) system /boot is:

drwxr-xr-x   2 root root 1024 Jun 10 14:14 boot

-- 
Ed



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: user can delete kernel images

[Martin Str|mberg]

In article <[EMAIL PROTECTED]> you wrote:
: Something very strange has happened to my system. I have my kernels in
: /boot (the usual setup ) with permission 644. I have never touched that
: after they are created by the kernel-package. I am doing some experiments
: concerning security. So I tried as a user with no root privileges and no
: root group privileges to delete the files /boot/vmlinuz.2.0.0 and
: /boot/vmlinuz.2.0.27 I was asked whether 644  should be overrided I said
: yes and it removed the files  Why ?? This is of no immediate risk
: since I have several more kernels which I use but this is scary. Can
: anayone explain this ??

What are the permissions of the directory /boot?


Right,

MartinS


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: user can delete kernel images

[sjc]

On Fri, Jun 12, 1998 at 06:02:47PM +0100, G. Kapetanios wrote:
> 
> Hi, 
> 
> Something very strange has happened to my system. I have my kernels in
> /boot (the usual setup ) with permission 644. 

um 644...thats um... owner: rwx group: r other: r  ?
I don't know my octal modes..forgive me :)
anyway...

>I have never touched that
> after they are created by the kernel-package. I am doing some experiments
> concerning security. So I tried as a user with no root privileges and no
> root group privileges to delete the files /boot/vmlinuz.2.0.0 and
> /boot/vmlinuz.2.0.27 I was asked whether 644  should be overrided I said
> yes and it removed the files  Why ??

ahh well...that means that permissions on the directory are wrong ;)
check this out:
I (as root) make a new dir "test" and give it these perms:

drwxrwxrwx   2 root root 1024 Jun 12 15:21 test

in test I make this file:
--   1 root root0 Jun 12 15:22 safe
so noone has permission to do ANYTHING to the file.
now as sjc (normal user) in test:
$ cat safe
cat: safe: Permission denied

then:
$ rm safe
rm: remove `safe', overriding mode ? y
$ ls -l
total 0
$

ok why does this work? rm does not acess the file...it changes teh DIRECTORY
so if the user has write permisions to /boot then they can 
delete ANY file in /boot
even if they don't have acess to thge file.

BTW this is covered in the "Linux FAQ" under "I just found a huge security 
hole in 'rm' " (the answer being "No you didn't")

-Steve


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: user can delete kernel images (cont)

[Steve Mayer]

George,

  I noticed this on my one remaining bo machine.  Hamm seems to have
taken care of this bug.

Steve Mayer
[EMAIL PROTECTED]

G. Kapetanios wrote:
> 
> Following to my previous email I have to say some things.
> 
> the /boot directory in my machine is
> 
> drwxrwsr-x   2 root disk 2048 Jun 12 17:58 boot
> the user who can do that belongs to the disk group but the file which was
> deleted (/boot/vmlinuz.2.0.0) does not belong to the disk group it is
> root.root So obviously although I hadn;t realised that before if a group
> you belong to owns a directory which is writable by the group you can
> delete stuff from it without owning
> the files and without belonging to the group which owns the files. Is this
> safe ?? More importantly I don't know if this is a bug of the installation
> procedure about 1 1/2 years ago but the permission to /boot were set by
> that procedure and I never changed them. I know users should not probably
> belong to group disk but I could have damaged my system really bad if I
> had no spare kernels. I guess I must remove the user from the disk group
> as soon as possible.
> 
> By the way why is /boot writable by the group disk?
> 
> Sorry for the long email
> George
> 
> ---
> George Kapetanios
> Churchill College
> Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED]
> U.K.  WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html
> ---
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

user can delete kernel images (cont)

[G. Kapetanios]

Following to my previous email I have to say some things. 

the /boot directory in my machine is 

drwxrwsr-x   2 root disk 2048 Jun 12 17:58 boot
the user who can do that belongs to the disk group but the file which was
deleted (/boot/vmlinuz.2.0.0) does not belong to the disk group it is
root.root So obviously although I hadn;t realised that before if a group
you belong to owns a directory which is writable by the group you can
delete stuff from it without owning
the files and without belonging to the group which owns the files. Is this
safe ?? More importantly I don't know if this is a bug of the installation
procedure about 1 1/2 years ago but the permission to /boot were set by
that procedure and I never changed them. I know users should not probably
belong to group disk but I could have damaged my system really bad if I
had no spare kernels. I guess I must remove the user from the disk group
as soon as possible. 

By the way why is /boot writable by the group disk?

Sorry for the long email
George  



---
George Kapetanios
Churchill College
Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED]
U.K.  WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html
---



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

user can delete kernel images

[G. Kapetanios]

Hi, 

Something very strange has happened to my system. I have my kernels in
/boot (the usual setup ) with permission 644. I have never touched that
after they are created by the kernel-package. I am doing some experiments
concerning security. So I tried as a user with no root privileges and no
root group privileges to delete the files /boot/vmlinuz.2.0.0 and
/boot/vmlinuz.2.0.27 I was asked whether 644  should be overrided I said
yes and it removed the files  Why ?? This is of no immediate risk
since I have several more kernels which I use but this is scary. Can
anayone explain this ??

Thanks 
George  



---
George Kapetanios
Churchill College
Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED]
U.K.  WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html
---



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]