On 07/04/2018 02:24 PM, Charles Zeitler wrote:
> I am using vmlinuz-4.9.0-6-amd64
> Have I missed an update?
>
> charles zeitler
>
You have not. Stretch is using the 4.9 series kernel, as it was the LTS
kernel at the time of Stretch's release, and it will likely remain the
default kernel
On Thu 05 Jul 2018 at 10:27:53 (+1200), Ben Caradoc-Davies wrote:
> On 05/07/18 09:24, Charles Zeitler wrote:
> >I am using vmlinuz-4.9.0-6-amd64
> >Have I missed an update?
> >charles zeitler
>
> This is the current default linux-image-amd64 package on stretch:
>
>
On 05/07/18 09:24, Charles Zeitler wrote:
I am using vmlinuz-4.9.0-6-amd64
Have I missed an update?
charles zeitler
This is the current default linux-image-amd64 package on stretch:
https://packages.debian.org/stretch/linux-image-amd64
Depends:
I am using vmlinuz-4.9.0-6-amd64
Have I missed an update?
charles zeitler
--
The Perfect Is The Enemy Of
The Good Enough
On 17/05/16 06:46, tony mollica wrote:
> All of the information and guidance I've found to make one single
> modules don't work.
>
> The kernel source and headers and any supporting packages are
> installed. It appears the
> syntax for getting the module built is the issue. The module source
>
Just trying to build one module for a piece of
hardware I have.
All of the information and
guidance I've found to make one single modules don't work.
The kernel source and headers and any supporting packages
then the updater has wanted to update the kernel image to the same
version as the current kernel, which is 2.6.18-6-k7. I let it do it the
first couple of times since i was new to debian, but it has become an
irritation. Does anyone know why this happens? Is it a bug in the
updater? Can anyone tell
Hi whoever is out there.
I recently installed debian etch in a virtual box vm. Several times
since then the updater has wanted to update the kernel image to the same
version as the current kernel, which is 2.6.18-6-k7. I let it do it the
first couple of times since i was new to debian, but it has
On Sun, Jun 15, 2008 at 08:24:33PM +1000, Andrew Storm wrote:
Hi whoever is out there.
I recently installed debian etch in a virtual box vm. Several times
since then the updater has wanted to update the kernel image to the same
version as the current kernel, which is 2.6.18-6-k7. I let it do
Paul Yeatman wrote:
Hi, I did some searching on this in the archive and found some stuff
but nothing that fully satisfies me. When a new minor 2.6 kernel
revision, 2.6.17, was available for Etch, an aptitude dist-upgrade
wanted to install this new kernel AND remove my 2.6.16 kernel revision
Hi, I did some searching on this in the archive and found some stuff
but nothing that fully satisfies me. When a new minor 2.6 kernel
revision, 2.6.17, was available for Etch, an aptitude dist-upgrade
wanted to install this new kernel AND remove my 2.6.16 kernel revision
(which understandably was
On Mon, Dec 11, 2006 at 11:24:44AM -0800, Paul Yeatman wrote:
I'm perfectly happy with the
package manager leaving my currently installed kernels alone while
simultaneously adding newer kernel versions and releases. If I want to
remove old kernels at some point, I'll do so explicitely.
-In response to your message-
--received from Andrew Sackville-West--
On Mon, Dec 11, 2006 at 11:24:44AM -0800, Paul Yeatman wrote:
I'm perfectly happy with the
package manager leaving my currently installed kernels alone while
simultaneously adding newer kernel versions and releases.
any ideas for me?
Oh the Joys of aptitude. Strangely, I just upgraded to 2.6.18 and it
_didn't_ try to remove my current 2.6.15. Anyway, in your case I would
just bypass aptitude this time and do apt-get install kernel-U-want.
Or, I guess you could put the current kernel on hold and then try
make-kpkg clean; make modules_clean;
make-kpkg --subarch=i686 --initrd --revision=6 --append-to-version=.6
--added_modules qla2x00 modules
When I compile this this will always compile the /usr/src/modules/*
packages with for the currently running kernel, not for the revision I am
passing via
on Mon, 12 Apr 2004 09:53:38PM -0400, Derrick 'dman' Hudson insinuated:
On Mon, Apr 12, 2004 at 06:26:33PM -0400, Nori Heikkinen wrote:
| on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated:
| What version of the dhcp-client package do you have installed?
|
| 2.0pl5-11
on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated:
On Fri, Apr 09, 2004 at 02:41:54PM -0400, Nori Heikkinen wrote:
| on Fri, 09 Apr 2004 01:47:26PM -0400, Derrick 'dman' Hudson insinuated:
| On Fri, Apr 09, 2004 at 12:32:10PM -0400, Nori Heikkinen wrote:
[...]
| | how,
[back on-list]
on Mon, 12 Apr 2004 02:02:06PM -0400, J F insinuated:
I don't have a specific answer to your problem,
but using aptitude seems to ease upgrade problems.
Also, having testing, unstable, and stable all in
/etc/apt/sources.list seems to get aptitude
to converge on a working
On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote:
| on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated:
[...]
| I haven't noticed any changes in networking, but that might be
| dependent on the hardware and what modules I already had configured
| to be loaded.
On Mon, Apr 12, 2004 at 02:11:24PM -0400, Nori Heikkinen wrote:
| [back on-list]
|
| on Mon, 12 Apr 2004 02:02:06PM -0400, J F insinuated:
| I don't have a specific answer to your problem,
| but using aptitude seems to ease upgrade problems.
| Also, having testing, unstable, and stable all in
on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated:
On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote:
| on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated:
[...]
| I haven't noticed any changes in networking, but that might be
|
Derrick 'dman' Hudson wrote:
On Mon, Apr 12, 2004 at 02:11:24PM -0400, Nori Heikkinen wrote:
| on Mon, 12 Apr 2004 02:02:06PM -0400, J F insinuated:
| I don't have a specific answer to your problem,
| but using aptitude seems to ease upgrade problems.
| Also, having testing, unstable, and
On Mon, Apr 12, 2004 at 06:26:33PM -0400, Nori Heikkinen wrote:
| on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated:
| On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote:
| | on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated:
| [...]
| |
Nori Heikkinen escribió:
on Fri, 09 Apr 2004 01:47:26PM -0400, Derrick 'dman' Hudson insinuated:
On Fri, Apr 09, 2004 at 12:32:10PM -0400, Nori Heikkinen wrote:
| after hearing all the brouhaha about the 2.6 kernel, i thought i'd try
| it out. but a simple `apt-get install
-2.6.4-1-686 module-init-tools
0 upgraded, 2 newly installed, 2 to remove and 154 not upgraded.
Need to get 0B/15.4MB of archives.
After unpacking 19.8MB of additional disk space will be used.
Do you want to continue? [Y/n] n
why does it want to remove modutils and my CURRENT kernel image
modules with this kernel.
Suggested packages:
kernel-doc-2.6.4 kernel-source-2.6.4
The following packages will be REMOVED:
kernel-image-2.4.18-1-686 modutils
snip
modutils are ok to remove, it would be replaced by
module-init-tools.
removal of current kernel: i suggest doing with the
# dpkg
-2.6.4
The following packages will be REMOVED:
kernel-image-2.4.18-1-686 modutils
snip
modutils are ok to remove, it would be replaced by
module-init-tools.
cool; thanks.
removal of current kernel: i suggest doing with the
# dpkg -i pathtokernelimage/kernel_image2.6.x.deb
instead
want to continue? [Y/n] n
|
| why does it want to remove modutils and my CURRENT kernel image?
I have no idea. I used to have 2.4 and 2.6 kernels installed
side-by-side with no problem. I still have module-init-tools and
modutils installed because lvm-common depends on it, although I no
longer
/15.4MB of archives.
| After unpacking 19.8MB of additional disk space will be used.
| Do you want to continue? [Y/n] n
|
| why does it want to remove modutils and my CURRENT kernel image?
I have no idea. I used to have 2.4 and 2.6 kernels installed
side-by-side with no problem. I still have
On Fri, Apr 09, 2004 at 02:41:54PM -0400, Nori Heikkinen wrote:
| on Fri, 09 Apr 2004 01:47:26PM -0400, Derrick 'dman' Hudson insinuated:
| On Fri, Apr 09, 2004 at 12:32:10PM -0400, Nori Heikkinen wrote:
[...]
| | how, then, should i go about installing the kernel image?
|
| Try aptitude.
On Friday 09 April 2004 12:41 pm, Nori Heikkinen wrote:
of course, i've totally failed to show the slickness of apt to my
coworker, because as soon as i booted up with 2.6.4, my mouse (neither
USB nor PS2) didn't work, and i wasn't online. (right now, i've
reverted to 2.4 to type this :-P).
On Sun, Apr 21, 2002 at 05:58:12AM -0700, Kapil Khosla wrote:
Hi,
I normally have to recompile my kernel a number of times.
Obviously , the .config file in /usr/src/linux gets overwritten and I
lose my old .config file.
!? It should only be overwritten if you change it, or do a make
Hi,
I normally have to recompile my kernel a number of times.
Obviously , the .config file in /usr/src/linux gets overwritten and I lose my
old .config file. I know I can save it by a unique name but
is there a command/utility which I could use to know the configuration of the
current running
On Sun, Apr 21, 2002 at 05:58:12AM -0700, Kapil Khosla wrote:
Hi,
I normally have to recompile my kernel a number of times.
Obviously , the .config file in /usr/src/linux gets overwritten and I lose my
old .config file. I know I can save it by a unique name but
is there a command/utility
On Sun, Apr 21, 2002 at 05:58:12AM -0700, Kapil Khosla wrote:
Hi,
I normally have to recompile my kernel a number of times.
Obviously , the .config file in /usr/src/linux gets overwritten and I lose my
old .config file. I know I can save it by a unique name but
is there a command/utility
Hi Kapil,
the config files of currently installed kernels can also be found in the same
directory as the kernel images (usually /boot). Provided that you made the
kernel using make-kpkg and dpkg -i .
HTH, Joachim
On Sun, Apr 21, 2002 at 05:58:12AM -0700, Kapil Khosla wrote:
Hi,
I normally
On Wed, 14 Apr 1999, Robbie Huffman wrote:
Subject: Re: Current kernel configuration?
On Tue, Apr 13, 1999 Wayne Topa wrote:
[...] to get a SoundBlaster working 'with-out'
compiling it into the kernel is to purchase the OSS commercial
Sound package for $20. [...]
How about possibly
/sound/alsa{utils -modules -source lib}sounds like it might do the trick
for free
On Tue, 13 Apr 1999, Wayne Topa wrote:
Subject: Re: Current kernel configuration?
Date: Tue, Apr 13, 1999 at 09:23:30PM +0200
In reply to:Bruno Goncalves Russo
Quoting Bruno Goncalves Russo
On Tue, Apr 13, 1999 at 04:43:10PM -0400, Wayne Topa wrote:
The only way I know of to get a SoundBlaster working 'with-out'
compiling it into the kernel is to purchase the OSS commercial
Sound package for $20. That has it's advantages. It is the way
I run my sound blaster.
How about
I have not compiled my kernel yet, but I want to, and I want to see how it
is currently configured. Is there any easy way to do this?
Furthermore, do I really need to? I just want to add SoundBlaster support.
Instead of upgrading the kernel, could I not just get the source for the
current version
William R Pentney [EMAIL PROTECTED] writes:
I have not compiled my kernel yet, but I want to, and I want to see how it
is currently configured. Is there any easy way to do this?
I'm not sure. Look for file /usr/src/linux/.config. I'm not sure if it
gets installed by Debian installer.
/config-2.x.y where x and y are the version numbers of your
kernel. This is the config file. If you copy it to .config in your kernel
source tree, you will get the same configuration as your current kernel as
the default.
Nils
--
Plug-and-Play is really nice, unfortunately it only works 50
William R Pentney wrote:
I have not compiled my kernel yet, but I want to, and I want to see how it
is currently configured. Is there any easy way to do this?
Furthermore, do I really need to? I just want to add SoundBlaster support.
Instead of upgrading the kernel, could I not just get
Arcady Genkin escreveu:
William R Pentney [EMAIL PROTECTED] writes:
I have not compiled my kernel yet, but I want to, and I want to see how it
is currently configured. Is there any easy way to do this?
I'm not sure. Look for file /usr/src/linux/.config. I'm not sure if it
gets
Bruno Goncalves Russo [EMAIL PROTECTED] writes:
I would also like to know if there´s some other possibility. I tried to
compile my kernel, but had some problems, so I´d like to add SB support
temporarily and try to solve the problem later.
Well, you can technocally just compile the modules
Subject: Re: Current kernel configuration?
Date: Tue, Apr 13, 1999 at 09:23:30PM +0200
In reply to:Bruno Goncalves Russo
Quoting Bruno Goncalves Russo([EMAIL PROTECTED]):
Arcady Genkin escreveu:
William R Pentney [EMAIL PROTECTED] writes:
I have not compiled my
for the debian kernel-source package are set to
the same settings as what generated the current kernel?
Thanks in advance.
- Joe
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
47 matches
Mail list logo
