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.
> 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/mo
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
>
&g
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
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
&
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-
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 Syste
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,
/bo
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 do
-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 fol
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
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 replace
-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/archive
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,
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
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
?
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
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
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 matte
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 t
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
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 ker
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-sour
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 k
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 a
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
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 t
-- 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-im
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.
--
.--===-=-==-=---==-=-.
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.
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 m
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 D
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
hav
appen. 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.
>
&
> 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
t 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 i
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,
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
[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
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
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
>
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
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
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)
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
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 :)
anyw
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
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 i
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
ro
49 matches
Mail list logo
