Sounds like a nice computer, but without the model number, cores, bus
speed it's hard to tell just how fast it can work or move a Tb or two of
data.
You're right.
Supermicro X9SR
Intel Xeon E5 1620v2
4 cores / 8 threads
3.7 GHz / 3,9 GHz
10 Mo cache
64Go DDR3 ECC 1600 MHz
Debian 8 stable.
I'
On 02/07/2018 12:27 AM, Stéphane Rivière wrote:
Thanks Jimmy for your help,
I would use 'apt-mark'. # apt-mark hold 'package-name'
and # apt-mark unhold 'package-name'
It appears that apt-mark hold and aptitude hold have same effects, you
could obtain the same with some tricks with dpkg.
If
Thanks Jimmy for your help,
I would use 'apt-mark'. # apt-mark hold 'package-name'
and # apt-mark unhold 'package-name'
It appears that apt-mark hold and aptitude hold have same effects, you
could obtain the same with some tricks with dpkg.
If I used apt-get, it should be wise to use apt-mar
On 02/06/2018 09:00 AM, Stéphane Rivière wrote:
Hi all,
I wanted to avoid kernel updates after the Spectre/Meltdown 'bug', also
known as KPTI or kaiser CPU flaw. In my specific context, these patches
are useless or even harmful.
Before applying an aptitude update/upgrade to all the servers
At first thanks you all for you good advices.
I will follow them, update kernels and apply the appropriate options
(thanks for the link). I did not find what exactly is the nokaiser
option and I will use nopti.
I agree dpkg-jiu-jitsu is an uncomfortable sport and understand i've
hold the wro
On 2018-02-06 at 12:00, Stéphane Rivière wrote:
> Hi all,
>
> I wanted to avoid kernel updates after the Spectre/Meltdown 'bug',
> also known as KPTI or kaiser CPU flaw. In my specific context, these
> patches are useless or even harmful.
As indicated by Andy Smith, you should probably upgrade a
Stéphane Rivière wrote:
> I wanted to avoid kernel updates after the Spectre/Meltdown 'bug', also
> known as KPTI or kaiser CPU flaw.
No, it is not known as this.
> In my specific context, these patches are useless or even harmful.
Possible. You do know you can just add "pti=off" to the kerne
Hello,
On Tue, Feb 06, 2018 at 06:00:16PM +0100, Stéphane Rivière wrote:
> So, after an aptitude search ~i~linux- I hold theses meta-packages :
>
> aptitude hold linux-image-amd64
> aptitude hold linux-headers-amd64
I think you also would need to hold package
linux-image-4.9.0-4-amd64.
> Hopefu
Hi all,
I wanted to avoid kernel updates after the Spectre/Meltdown 'bug', also
known as KPTI or kaiser CPU flaw. In my specific context, these patches
are useless or even harmful.
Before applying an aptitude update/upgrade to all the servers and VMs
I'm in charge, I've done a little test
Scott
Per your subject and attachments. Hope this will be helpful.
I don't think your problem can be resolved at the current time because
of your kernel patch.
Below find correspondence and URLs which explain why.
* Brian Almeida:
> I've been unable to find an official debian kernel which
Wayne Topa wrote:
> H.S.([EMAIL PROTECTED]) is reported to have said:
>> Wayne Topa wrote:
>>> H.S.([EMAIL PROTECTED]) is reported to have said:
>>>> Hello,
>>>>
>>>> How come I cannot see newer kernel packages available with dpkg:
>>&
H.S.([EMAIL PROTECTED]) is reported to have said:
> Wayne Topa wrote:
> > H.S.([EMAIL PROTECTED]) is reported to have said:
> >> Hello,
> >>
> >> How come I cannot see newer kernel packages available with dpkg:
> >> $> dpkg -l linux-image-*
>
Wayne Topa wrote:
> H.S.([EMAIL PROTECTED]) is reported to have said:
>> Hello,
>>
>> How come I cannot see newer kernel packages available with dpkg:
>> $> dpkg -l linux-image-*
>
> Maybe because dpkg show whats installed, not available?
>
>> doesn
Wayne Topa wrote:
> H.S.([EMAIL PROTECTED]) is reported to have said:
>> Hello,
>>
>> How come I cannot see newer kernel packages available with dpkg:
>> $> dpkg -l linux-image-*
>
> Maybe because dpkg show whats installed, not available?
>
>> doesn
On 7/14/07, H.S. <[EMAIL PROTECTED]> wrote:
dpkg also lists packages that are not installed (2.6.21 is listed below
because I just now installed it):
$> dpkg -l linux-image-2.6.*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/
Wayne Topa wrote:
> H.S.([EMAIL PROTECTED]) is reported to have said:
>> Hello,
>>
>> How come I cannot see newer kernel packages available with dpkg:
>> $> dpkg -l linux-image-*
>
> Maybe because dpkg show whats installed, not available?
Please see my other p
H.S.([EMAIL PROTECTED]) is reported to have said:
>
> Hello,
>
> How come I cannot see newer kernel packages available with dpkg:
> $> dpkg -l linux-image-*
Maybe because dpkg show whats installed, not available?
>
> doesn't list kernels 2.6.2* at all. However, I
Douglas Allan Tutty wrote:
>>
>
> dpkg -l lists info for debs it knows about, ie. installed ones. It
dpkg also lists packages that are not installed (2.6.21 is listed below
because I just now installed it):
$> dpkg -l linux-image-2.6.*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst
On Sat, Jul 14, 2007 at 02:16:37PM -0400, H.S. wrote:
>
> Hello,
>
> How come I cannot see newer kernel packages available with dpkg:
> $> dpkg -l linux-image-*
>
> doesn't list kernels 2.6.2* at all. However, I can get some hits if I
> try to install such a p
Hello,
How come I cannot see newer kernel packages available with dpkg:
$> dpkg -l linux-image-*
doesn't list kernels 2.6.2* at all. However, I can get some hits if I
try to install such a package:
$> sudo aptitude -s install linux-image-2.6.21*
Reading package lists... Do
Am 2007-03-17 20:11:57, schrieb dranger003:
>
> Indeed it was the debug causing the issue. After disabling all DEBUG lines
> in the .config the kernel is now of the correct size.
:-)
Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian G
Indeed it was the debug causing the issue. After disabling all DEBUG lines in
the .config the kernel is now of the correct size.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I have exactly the same problem. Also running Feisty.
I used the following to compile the kernel:
sudo make-kpkg --initrd --append-to-version=-1-Custom kernel_image
kernel_headers
My /lib/modules/$(uname -r) folder is huge as well. All the modules have bigger
than normal sizes - every modules
Am 2007-03-06 22:04:59, schrieb Matt Price:
> this? the vmlinuz produced by the package is of normal size, but the
> initrd is huge -- 43 megs! -- and /lib/modules/kernel-version-number/ is
> on the order of 530 megs!!!
Sorry, but with the infos you have provided I can not help you.
Please, c
hi
obviously a half-gig-sized kernel package is not optimal, i'd very much
like to figure out what's going on here... also i should say that the
after the build process, the source directory becomes enormous -- 2.7
gigs with ubuntu's 2.6.20 as opposed to a more restrained 700megs back
in the ol
i,
i'm having a problem using make-kpkg to build kernel packages on my
laptop, which runs ubuntu feisty and currently has make-kpkg version
10.065ubuntu4. this happens with upstream, debian, and ubuntu sources,
as far as I can tell, but most of my experimentation has been with
ubuntu&#x
Nic Ferrier wrote:
> Does anyone know what I have to do to get a skas host kernel?
Why not take the patch directly from its origin?
http://www.user-mode-linux.org/~blaisorblade/patches/skas3-2.6/
Regards,
Dennis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
Tim Ruehsen <[EMAIL PROTECTED]> writes:
> Hi Nic,
>
> do you *really* need SKAS? UML works without SKAS, but I heard it should be
> somewhat slower without it. I have 2 UML envs running on my SID desktop (an
> old SID and a very old SuSE system). They are pretty well used by my
> collegues as d
.12 kernel installed from the debian source package:
>
>linux-source-2.6.12
>
> I have the package:
>
>linux-patch-debian-2.6.12
>
> installed as well.
>
> But I don't seem to have the skas patches.
>
>
> There is the package:
>
&g
as patches.
There is the package:
kernel-patch-skas
But this seems to apply to the old kernel-*** packages and not the new
linux-*** ones.
Does anyone know what I have to do to get a skas host kernel?
Nic Ferrier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of &q
I am looking for 2.6.12 for i386. apt-get does not show anything available and
google finds it for other platforms. Where can it be found? I don't want the
generic and I don't want to have to "make menuconfig" but am looking for a
standard config file.
Regards,
David Koski
[EMAIL PROTECTED]
-
On Sunday 03 July 2005 05:13, Jansen Carlo Sena wrote:
> Hi friends,
>
> I need to apply the grsecurity patch and compile a
> new kernel for a server. In this server, I am using a
> kernel image from the 2.6.8 version. Then, I
> downloaded both the kernel-source-2.6.8 package and
> the kernel-patch
Hi friends,
I need to apply the grsecurity patch and compile a new kernel for a
server. In this server, I am using a kernel image from the 2.6.8
version. Then, I downloaded both the kernel-source-2.6.8 package and the
kernel-patch-grsecurity2.
But I am not able to apply the kernel patch beca
starmoon wrote:
> Alexander Toresson wrote:
> > I removed the older kernel-image-* packages I had today, and kept only
> > 2.6.8-2-686.
> > However, when I restarted, it seems like there's a big problem related
> > to the modules.
> > The sound card module (cs4232) ain't loaded, and if I try to mod
Alexander Toresson wrote:
I removed the older kernel-image-* packages I had today, and kept only
2.6.8-2-686.
However, when I restarted, it seems like there's a big problem related
to the modules.
The sound card module (cs4232) ain't loaded, and if I try to modprobe
it, I get an error saying it's
I removed the older kernel-image-* packages I had today, and kept only
2.6.8-2-686.
However, when I restarted, it seems like there's a big problem related
to the modules.
The sound card module (cs4232) ain't loaded, and if I try to modprobe
it, I get an error saying it's not found. The same is true
I'm curious if anyone knows if kernel packages for stable have been
released that address the issue described here:
http://linuxreviews.org/news/2004/06/11_kernel_crash/
I would have thought that Debian would have released an update by now,
but my perusal of http://www.debian.org/security
Dan Korostelev wrote:
Hello.
I have a tarball linux-2.6.6.tar.bz2. Can I build the
kernel-image-2.6.6-1-k7 package _exactly_ like in Debian repositories? I
don't want to download kernel-image package on my modem, but I download
updates for vanilla kernels (patches for example from 2.6.5 to 2.6.6).
Hello.
I have a tarball linux-2.6.6.tar.bz2. Can I build the
kernel-image-2.6.6-1-k7 package _exactly_ like in Debian repositories? I
don't want to download kernel-image package on my modem, but I download
updates for vanilla kernels (patches for example from 2.6.5 to 2.6.6).
Please CC me.
--
Hello Ross!
On Mon, Mar 01, 2004 at 10:28:40AM -0800, Ross Boylan wrote:
> > > For 2.4.2[1245] and 2.6.3 they are on the mirrors, see
> > > apt-cache search kernel-patch-debian
^^^
> The patches applied to the Debianized sources in kernel-source-xxx are
> NO
On Mon, Mar 01, 2004 at 07:22:08PM +0300, Nikita V. Youshchenko wrote:
>
> > Hello Nikita!
> >
> > On Mon, Mar 01, 2004 at 06:42:28PM +0300, Nikita V. Youshchenko wrote:
> > > kernel-image-* packages available in Debian archive have a number of
> > > patches applied (listed in README.Debian).
> >
> Hello Nikita!
>
> On Mon, Mar 01, 2004 at 06:42:28PM +0300, Nikita V. Youshchenko wrote:
> > kernel-image-* packages available in Debian archive have a number of
> > patches applied (listed in README.Debian).
> > Are individual patches listed there available in ready-to-download
> > from from an
Hello Nikita!
On Mon, Mar 01, 2004 at 06:42:28PM +0300, Nikita V. Youshchenko wrote:
> kernel-image-* packages available in Debian archive have a number of
> patches applied (listed in README.Debian).
> Are individual patches listed there available in ready-to-download from
> from anywhere?
For
Hello.
kernel-image-* packages available in Debian archive have a number of
patches applied (listed in README.Debian).
Are individual patches listed there available in ready-to-download from
from anywhere?
Please CC replies to my e-mail, I'm currently not on the list.
--
To UNSUBSCRIBE, ema
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I usually boot into my backup image, dpkg -r the kernel-package, and then
dpkg-i the new kernel-package. This for the same version. For different
version of the kernel (where the /lib/modules directory is not shared), I
just skip the first and second
/lib/modules of the kernel I'm
> replacing and then install the new package before booting back into the
> kernel of the new package. I'm questioning whether this is really
> necessary. I know that with Red Hat, new kernel packages are simply
> installed, no questions asked
and then install the new package before booting back into the
kernel of the new package. I'm questioning whether this is really
necessary. I know that with Red Hat, new kernel packages are simply
installed, no questions asked (if they are not on the "packages to
skip" list).
Hi there,
I'd just like to say that thanks to the helpful and speedy replies to my
question, I have sucessfully upgraded the kernel on all my Debian
machines.
Another victory for moving away from the Red Hat RPM system.
(Yes, I am a recent adopter of Debian)
Thanks again.
Colin
> On Fri, Dec
On Fri, Dec 19, 2003 at 08:25:55AM -, [EMAIL PROTECTED] wrote:
> Can someone explain how it is that my machine even boots when according
> the package manager, there is no kernel image installed?
It's a long-standing buglet in boot-floppies that it just plonks the
kernel into place without ins
Hello
[EMAIL PROTECTED] (<[EMAIL PROTECTED]>) wrote:
> I am looking to upgrade the kernel on my machine to deal with the
> vulnerability that knocked over the main Debian servers. From what I
> understand, a kernel upgrade is something that isn't done
> automatically by apt.
>
> Can someone expl
Hi there,
I've been reading this list for a little while, and it seems to be the
most appropriate forum for my question. I apologise if it has been asked
before, however I can't seem to get my head around the way in which this
is supposed to work. I have looked around using Google, but to be hones
On Wed, 15 Oct 2003 10:40:34 -0500, Kirk Strauser wrote:
> Is anyone using the 2.6.0-test* kernel packages -- successfully? I
I do not use the debian packages but compile the source from kernel.org
since test1.
> installed the -test4 image to play around, and I immediately noticed
Is anyone using the 2.6.0-test* kernel packages -- successfully? I
installed the -test4 image to play around, and I immediately noticed three
things:
1) I can't log in to a KDE session using KDM.
2) My motherboard's Promise IDE controller is detected, but neither of the
drives
ystem). During the installation phase, I was given a warning
| > that this image requires an initial ramdisk - which I am not using, as
| > far as I am aware, with the stock 2.4.18-bf2.4 kernel that originally
| > came with woody (now sarge).
| >
| > Are all debian kernel packages creat
re, with the stock 2.4.18-bf2.4 kernel that originally
> came with woody (now sarge).
>
> Are all debian kernel packages created with initrd? If so, is justing
> proceeding with the install sufficient, or is there some special way
> to modify my menu.lst for grub to handle this (the
The Debian kernel images are compiled to use initrd. Your new kernel will not
work unless you have installed the appropriate packages. From memory I think
apt-get initrd-tools will do the trick, but don't hold me to this.
If you really don't want to use initrd you will so far as I know need to
sarge).
Are all debian kernel packages created with initrd? If so, is justing
proceeding with the install sufficient, or is there some special way to
modify my menu.lst for grub to handle this (the install gives
instructions for lilo, but I don't use lilo).
Thanks.
nl
--
To UNSUBSCRIBE,
Hello
Le Sun Jun 08 2003 à 10:17:05PM -0700, [EMAIL PROTECTED] ecrivit :
[cut]
> I'm not clear about this:
>
> > For the unstable distribution (sid) these problems are fixed in the
> > 2.4.20 series kernels based on Debian sources.
>
> Does that mean only the 2.4.20 *debian* kernel sources are
A question about:
> - --
> Debian Security Advisory DSA 311-1 [EMAIL PROTECTED]
> http://www.debian.org/security/ Matt Zimmerman
> June 8th, 2003 http://
Greetings,
I was just going to report this one as a bug, but I'm not sure which
package is in fact causing the problem. I found a few older postings by
people who'd had similar problems, but it seemed that the maintainers
of each package blamed the maintainers of the *other* package, so I
tho
Hi,
I found out why my custom packages were ignored. I had
the same problem with the new XFree86 4.2 packages, so
I started to wonder about my apt config in general.
All I had in /etc/apt/source.list was:
APT::Default-Release "testing";
In contrast to what I was expecting this meant that
"unc
On Thu, 2002-06-20 at 21:38, Derrick 'dman' Hudson wrote:
> On Thu, Jun 20, 2002 at 12:24:51PM -0500, Derrick 'dman' Hudson wrote:
> | On Thu, Jun 20, 2002 at 12:58:21PM +0200, Patrick Ohly wrote:
> |
> | | I have built a patched kernel 2.4.18 with make-kpkg
> |
> | | I used epochs,
> |
> | Unne
n a repository that
> apt can query.
I did that:
> I generated a Package.gz and changed the sources.list so that
> apt-get correctly finds my kernel-image-2.4.18 with revision
> pallas.2.1.
I believe I did this correctly, because I can do an
"apt-get --reinstall install" o
On Thu, Jun 20, 2002 at 12:24:51PM -0500, Derrick 'dman' Hudson wrote:
| On Thu, Jun 20, 2002 at 12:58:21PM +0200, Patrick Ohly wrote:
|
| | I have built a patched kernel 2.4.18 with make-kpkg
|
| | I used epochs,
|
| Unnecessary. Just make the version different (eg "custom.3").
I should also
On Thu, Jun 20, 2002 at 12:58:21PM +0200, Patrick Ohly wrote:
| I have built a patched kernel 2.4.18 with make-kpkg
| I used epochs,
Unnecessary. Just make the version different (eg "custom.3").
| "apt-get install kernel-headers-2.4.18" insists that the installed
| 2.4.18-5 is the most recent
Hi,
I have built a patched kernel 2.4.18 with
make-kpkg --initrd --revision=3:pallas.2.1 kernel_image kernel_headers
kernel_doc
I generated a Package.gz and changed the sources.list so that
apt-get correctly finds my kernel-image-2.4.18 with revision
pallas.2.1.
I used epochs, just to be sure, b
On Tue, Apr 09, 2002 at 01:19:04PM -0400, Curtis Dean Smith wrote:
> As above, what is the difference between the regular kernel packages and
> "bf" varients in testing?
>
Read the "README.txt" -
http://ftp.us.debian.org/debian/dists/testing/main/disks-i386/curr
As above, what is the difference between the regular kernel packages and
"bf" varients in testing?
Thanks!
--
Curtis Dean Smith ¥v°ê¿³
Asst. Professor of Chinese
Coordinator of East Asian Studies
Dept. of Modern Langs & Lits
Grand Valley State University
Allendale,
On Mon, Dec 10, 2001 at 07:57:39PM -0500, Tom Allison wrote:
| I make my own kernel packages.
|
| I have one question.
|
| How do I remove the obsolete ones from the dselect tree? I think I just
| did the dselect equivelant of dpkg -r kernel-image and it totally
| messed up my lilo.
In
I make my own kernel packages.
I have one question.
How do I remove the obsolete ones from the dselect tree? I think I just
did the dselect equivelant of dpkg -r kernel-image and it totally
messed up my lilo.
Is there a right & wrong way of doing this?
On Sun, Oct 14, 2001 at 01:47:29PM -0700, Charles Baker wrote:
> Okay, here's my debian-newbie question for the week.
> When installing a stock debian kernel package, how do
> I get and install the modules that match that kernel
> w/o killing off the modules that match my old kernel.
> The particul
On Sun, Oct 14, 2001 at 01:47:29PM -0700, Charles Baker wrote:
| Okay, here's my debian-newbie question for the week.
| When installing a stock debian kernel package, how do
| I get and install the modules that match that kernel
| w/o killing off the modules that match my old kernel.
| The particul
Okay, here's my debian-newbie question for the week.
When installing a stock debian kernel package, how do
I get and install the modules that match that kernel
w/o killing off the modules that match my old kernel.
The particular kernels are 2.2.18pre21 and 2.4.6-6 .
=
-
[EMAIL PROTECTED]
Hacki
Hi to all!
I am running Debian 2.2.2r plus 2.2.17 kernel. I want to study about
compiling kernels, so that, and following the
Debian University document, I have to apt-get install the following
packages:
a) kernel-source-2.2.17
b) bin86
c) kernel-package
d) task-c-dev
e) libncurses5-dev
f) tas
Hi!
I am running Debian 2.2.2r plus 2.2.17 kernel. I want to study about
compiling kernels, so that I have to apt-get install (from Debian University):
a) kernel-source-2.2.17
b) bin86
c) kernel-package
d) task-c-dev
e) libncurses5-dev
f) task-tcltk-dev
while apt-get install a)-c) went fine, ap
Hallo,
> I was told, just recently in debian-devel, that only the kernel needs
> to be patched (and only the top-level Makefile). Apparently, the
> patch applies cleanly to 2.2.17, not sure about 2.4.x
Looks like that's right. The kernel modules are now installed in
/lib/modules/2.2.17-adder
> "Klaus" == Klaus Reimer <[EMAIL PROTECTED]> writes:
Klaus> Yes, that's exactly what I wanted to know. I have read in
Klaus> that Flavour-patch-file that klogd needs to patched to. Is
Klaus> the klogd in Debian 2.2 already patched?
I was told, just recently in debian-devel, that
Hallo,
> You shouldn't be using the --flavour option unless you
> have patched the kernel using the patch supplied in
> /usr/doc/kernel-package/Flavours.gz
Ah, haven't known that. Thanks.
> Klaus> the modules? And are these module packages compatible with
> Klaus> all kernel 2.2.17
> "Klaus" == Klaus Reimer <[EMAIL PROTECTED]> writes:
Klaus> make-kpkg --bzImage --flavour adder --revsion 2.2.17-1
Klaus> buildpackage
[...]
Klaus> Second problem: The kernel-image does install its modules
Klaus> in /lib/modules/2.2.17. But if I compile the additional
Hi,
I have created some kernel packages with make-kpkg and now I want to build
the alsa- and pcmcia-modules for these kernels. For example I have two
different kernel packages:
kernel-image-2.2.17-mamba
- This is a standard kernel with no additional patches
kernel-image-2.2.17-adder
Hi,
I have some strange problems using make-kpkg. I'm trying to create debian
packages for a heavily patched 2.2.17 kernel. I choosed "uni" as flavour and
currently I am at revision "12". I create the packages with the command
make-kpkg --bzImage --flavour uni --revision 12 buildpackage
The
"Aaron M. Stromas" wrote:
> Brian Servis wrote:
>
> > *- On 23 Apr, Aaron M. Stromas wrote about "removing old kernel packages"
> > >
> > > hi,
> > >
> > > i upgraded my kernel from 2.0.34 to 2.0.36. then, using dpkg -r, i went
On Fri, Apr 23, 1999 at 06:19:05AM -0400, Aaron M. Stromas wrote:
> i ran dpkg --purge kernel-source-2.0.34 and it looked it did.
>
> mortirolo:# dpkg --purge kernel-source-2.0.34
> (Reading database ... 28636 files and directories currently installed.)
> Removing kernel-source-2.0.34 ...
> Purg
Brian Servis wrote:
> *- On 23 Apr, Aaron M. Stromas wrote about "removing old kernel packages"
> >
> > hi,
> >
> > i upgraded my kernel from 2.0.34 to 2.0.36. then, using dpkg -r, i went
> > to remove kernel-[image|source]-2.0.34 but it complained ab
*- On 23 Apr, Aaron M. Stromas wrote about "removing old kernel packages"
>
> hi,
>
> i upgraded my kernel from 2.0.34 to 2.0.36. then, using dpkg -r, i went
> to remove kernel-[image|source]-2.0.34 but it complained about
> /lib/modules/2.0.34 and a number of dir
dpkg --purge it is. thanks,
-a
Dpk wrote:
> On Fri, 23 Apr 1999, Aaron M. Stromas wrote:
>
>
>hi,
>
>i upgraded my kernel from 2.0.34 to 2.0.36. then, using dpkg -r, i
>went to remove kernel-[image|source]-2.0.34 but it complained about
>/lib/modules/2.0.34 and a number of direct
On Fri, 23 Apr 1999, Aaron M. Stromas wrote:
hi,
i upgraded my kernel from 2.0.34 to 2.0.36. then, using dpkg -r, i
went to remove kernel-[image|source]-2.0.34 but it complained about
/lib/modules/2.0.34 and a number of directories under
/usr/source/kernel-source-2.0.34 not
hi,
i upgraded my kernel from 2.0.34 to 2.0.36. then, using dpkg -r, i went
to remove kernel-[image|source]-2.0.34 but it complained about
/lib/modules/2.0.34 and a number of directories under
/usr/source/kernel-source-2.0.34 not being empty an didn't remove them.
i'm tempted to remove those ma
On Wed, 3 Sep 1997, Nathan E Norman wrote:
> Argh. I lost my copy of Manoj's very helpful HOWTO email regarding
> using kernel-package ... has it been put on the web somewhere? Or would
> someone be kind enough to email it to me?
I would suggest hitting the Mailing List Archives at
http://www.d
Hi,
>>"Nathan" == Nathan E Norman <[EMAIL PROTECTED]> writes:
Nathan> Argh. I lost my copy of Manoj's very helpful HOWTO email
Nathan> regarding using kernel-package ... has it been put on the web
Nathan> somewhere? Or would someone be kind enough to email it to me?
I think it should be
Argh. I lost my copy of Manoj's very helpful HOWTO email regarding
using kernel-package ... has it been put on the web somewhere? Or would
someone be kind enough to email it to me?
My apologies, when the cfni server went down I lost a lot of saved
email.
TIA
--
Nathan Norman
MidcoNet
410 South
auses dselect to treat this as "available version 0"
>
> All the kernel packages are named like this.
>
I believe this is being done so that you can install more than one kernel
source. Thus the "name" of the package is: kernel-source-2.0.23, and it is
version 0 (as they
I have this problem in "frozen" too.
The full name of the package is kernel-image-2.0.25, the version is 1.00 .
The dselect screen is just wide enogh to show kernel-package without the
2.0.25, although you see the full name in the description.
The name is that way so that you can install multiple k
Hello,
why are some packages named in this way, with the underscore behind
the version number,
kernel-source-2.0.23_0.deb
^
and not in the form
kernel-source_2.0.23-0.deb ?
This causes dselect to treat this as "available version 0"
All the kernel packages are
> # dpkg --install kernel-source-2.0.0-0.deb
> Selecting previously deselected package kernel-source-2.0.0.
> (Reading database ... 27285 files and directories currently
> installed.)
> Unpacking kernel-source-2.0.0 (from kernel-source-2.0.0-0.deb) ...
> Setting up kernel-source-2.0.0 ...
> dpkg (
Hi,
I seem to be having a lot of trouble installing or removing
the kernel image/header/source packages. dpkg fails, and then the
packages get marked as needing reinstallation before they can be
configured or removed. This happened with both the 1.99.7 and the
2.0.0 packages :-(
[EMAIL PROTECTED] (Brian C. White) wrote on 30.05.96 in <[EMAIL PROTECTED]>:
> > >> There is indeed a Debian-ized version of the kernel. The package is
> > >> called kernel-image.
> >
> > You could also grab the raw source and use kernel-package
> > package to generate your new image pack
> > You could also grab the raw source and use kernel-package
> > package to generate your new image package. This is the recommended
> > method for generating custom kernel images.
>
> Could you point me to exactly where this is recommended?
>
> In any case, though, I have no des
Hi,
>>"Dale" == Dale Scheetz <[EMAIL PROTECTED]> writes:
Dale> In the past these source/image packages clobbered the
Dale> modules.dep file for the currently running kernel. I understand
Dale> that they no longer do that, however, I have not been happy with
Dale> the position taken by the package
On Thu, 30 May 1996, Brian C. White wrote:
> > >> There is indeed a Debian-ized version of the kernel. The package is
> > >> called kernel-image.
> >
> > You could also grab the raw source and use kernel-package
> > package to generate your new image package. This is the recommended
> > m
1 - 100 of 101 matches
Mail list logo
