Re: Kernel 6.13 & choice Init or SystemD for the user on Debian 13

On Fri, 22 Nov 2024 11:41:48 -0800, Steve Langasek wrote: >On Fri, Nov 22, 2024 at 02:29:31AM +0100, phil995511 - wrote: >> Devuan offers users several init managers to choose from, this is what >> Debian should have offered since Debian 8 in 2015... you should never have >> argued about this and

Re: Kernel 6.13 & choice Init or SystemD for the user on Debian 13

On Fri, Nov 22, 2024 at 02:29:31AM +0100, phil995511 - wrote: > Devuan offers users several init managers to choose from, this is what > Debian should have offered since Debian 8 in 2015... you should never have > argued about this and made the Debian project lose developers who preferred > to stay

Re: Kernel 6.13 & choice Init or SystemD for the user on Debian 13

On Fri, Nov 22, 2024 at 02:29:31AM +0100, phil995511 - wrote: > Devuan offers users several init managers to choose from, this is what > Debian should have offered since Debian 8 in 2015... you should never have > argued about this and made the Debian project lose developers who preferred > to stay

Re: Kernel 6.13 & choice Init or SystemD for the user on Debian 13

phil995511 - writes: you say using backports is for advanced users yet you want users to be able to choose their init systems? that's backwards. most users do not care about the init system they use. adding backports and installing a new kernel is not actually that difficult to do, and is easier

Re: Kernel 6.13 & choice Init or SystemD for the user on Debian 13

On Fri, Nov 22, 2024 at 3:58 AM Johannes Schauer Marin Rodrigues wrote: > > Hi, > > Quoting phil995511 - (2024-11-22 02:29:31) > > Only kernel 6.13 will support the new GPUs that will be released in early > > 2025, the new Intel CPUs, the same for a whole bunch of new hardware... > > > > To be sat

Re: Kernel 6.13 & choice Init or SystemD for the user on Debian 13

Hi, Quoting phil995511 - (2024-11-22 02:29:31) > Only kernel 6.13 will support the new GPUs that will be released in early > 2025, the new Intel CPUs, the same for a whole bunch of new hardware... > > To be satisfied with kernel 6.12 would in my opinion be a big strategic > mistake jeopardizing c

Re: Kernel 6.13 & choice Init or SystemD for the user on Debian 13

Em qui., 21 de nov. de 2024, 22:29, phil995511 - escreveu: > Hello, > > I discussed all this a few days ago by email with your leader Andreas > Tille who advised me to post this here. > > My goal is therefore to let you think about the question and then discuss > it among yourselves... > > > Only

Re: Kernel 6.13 & choice Init or SystemD for the user on Debian 13

Hello, I discussed all this a few days ago by email with your leader Andreas Tille who advised me to post this here. My goal is therefore to let you think about the question and then discuss it among yourselves... Only kernel 6.13 will support the new GPUs that will be released in early 2025, t

Re: Kernel 6.13 & choice Init or SystemD for the user on Debian 13

On Thu, Nov 21, 2024 at 1:57 PM phil995511 - wrote: > > Hello, > > For the next release of Debian 13, I hope you will use the 6.13 kernel which > brings many essential revisions especially in terms of hardware support > (Rpi5, news AMD GPU, news Intel CPU, BTRFS performance and fonctions, etc,

Re: Kernel 6.5 from Experimental working

Also updated this to 6.5.1 today and still works Den tors 7 sep. 2023 kl 08:37 skrev Luna Jernberg : > > Hey! > > Just installed Kernel 6.5 from experimental during Debcamp 2023 on my > ThinkPad Edge 0217A16 and it works as intended on this laptop :) > > //Luna bittin Jernberg

Re: Kernel building question (Is -j8 safe and correct?)

On Sun, 2021-06-13 at 15:07 +0200, Philipp Hahn wrote: [...] > > 3. If both of the above are true, why isn't something like that suggested > > on [1]? > > Debian does not know your specifics and thus does not use parallel build > by default. > Debian *does* use parallel builds by default. But

Re: Kernel building question (Is -j8 safe and correct?)

On Fri, 2021-06-11 at 19:34 -0600, Antonio Russo wrote: > Hello, > > I'm trying to build a Debian bullseye kernel (with KASAN enabled, but that's > irrelevant). > I'm following [1], and the critical command > > $ fakeroot make -f debian/rules.gen binary-arch_i386_none_real > > does not suggest

Re: Kernel building question (Is -j8 safe and correct?)

Hello Anionio, Am 12.06.21 um 03:34 schrieb Antonio Russo: I'm trying to build a Debian bullseye kernel (with KASAN enabled, but that's irrelevant). I'm following [1], and the critical command $ fakeroot make -f debian/rules.gen binary-arch_i386_none_real does not suggest using -j8 (or -jnumb

Re: Kernel parameters protecting fifos and regular files

On Thu, 30 Jan 2020 at 05:26, Moritz Mühlenhoff wrote: > I'm in favour of setting both to 1. From a quick search Ubuntu carried a > patch > in their systemd package to set this as well (LP 1845637). > > protected hardlinks/symlinks are enabled via a Debian-specific kernel patch > by default, so I

Re: Kernel parameters protecting fifos and regular files

On Wed, 2020-01-29 at 10:13 -0800, Moritz Mühlenhoff wrote: > Craig Small schrieb: > > --4806c5059d3edeb1 > > Content-Type: text/plain; charset="UTF-8" > > > > Hi, > > About 2 years ago the procps package added protection for hard and soft > > symlinks. The bug report was 889098 and

Re: Kernel parameters protecting fifos and regular files

Craig Small schrieb: > --4806c5059d3edeb1 > Content-Type: text/plain; charset="UTF-8" > > Hi, > About 2 years ago the procps package added protection for hard and soft > symlinks. The bug report was 889098 and has seemed to work fine. > > There is also now bug #914859 which would ext

Re: Kernel parameters protecting fifos and regular files

On 1/28/20 9:23 PM, Craig Small wrote: > My personal preference is to lock them down by default, by setting both > to mode 2. FWIW: I agree. Unless massive breakage is expected, the default should be the most secure option. If you default to secure and that breaks something, people will be motivate

Re: kernel nvidia dkms rebuild after upgrade?

Hello Dan — thanks kindly, I had indeed not noticed…. I guess I’ll have a chance to test if the libelf-dev issue is really the fix when the patches do roll out. In that vein, I would like to note that https://security-tracker.debian.org/tracker/CVE-2017-5754

Re: kernel nvidia dkms rebuild after upgrade?

Thanks, Yao — in messing around with this, I did end up finding a thread that suggested installing libelf-dev — I did so, but I guess the order in which I did it make me recompile my dkms modules manually. Thanks for the note! -- Boyan Penkov www.boyanpenkov.com > On Jan 7, 2018, at 18:31, Yao

Re: kernel nvidia dkms rebuild after upgrade?

On 01/07/2018 07:47 PM, Boyan Penkov wrote: > and a backport (4.14.0-bpo2) -- in light of meltdown -- To avoid a false sense of security: according to [1], [2], [3], the current stretch-bpo kernel (linux-image-4.14.0-0.bpo.2-$arch) does *NOT* yet include any mitigations against meltdown. Daniel

Re: kernel nvidia dkms rebuild after upgrade?

It is caused by a missing dependency libelf-dev. It is already reported against linux-headers-4.14.0-3-amd64: https://bugs.debian.org/886474 I have the same symptom of broadcom-sta-dkms On Mon, 8 Jan 2018 at 02:47 Boyan Penkov wrote: > Hello, > > After the latest update to 4.9.0-5, and a backpo

Re: kernel module i915 - 3d-acceleration missing after update

> That you didn't read, yes. :( > > Mraw, > KiBi. I read, I read. And I will wait, what will happen. And watch. And next time write to another list. :) Thanky for your help anyway! Have fun Hans -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscrib

Re: kernel module i915 - 3d-acceleration missing after update

Hans-J. Ullrich (18/06/2011): > Yes, it is userspace. Pity I don't have the logs any more (Xorg.log.0), where > the error was shown. It showed me, that the *_dri.so could not found (so GLX > could not be started). They originally reside below /usr/lib/dri/, but the > driver search them below /u

Re: kernel module i915 - 3d-acceleration missing after update

Am Samstag, 18. Juni 2011 schrieb Cyril Brulebois: > Hans-J. Ullrich (18/06/2011): > > Well, I thought the problem is not related to i915, as this is part of > > the kernel, and I did not change the kernel. > > Just to clarify: You mentioned a .so, not a .ko; there are i915 bits in > the kernel,

Re: kernel module i915 - 3d-acceleration missing after update

Hans-J. Ullrich (18/06/2011): > Well, I thought the problem is not related to i915, as this is part of > the kernel, and I did not change the kernel. Just to clarify: You mentioned a .so, not a .ko; there are i915 bits in the kernel, and in userspace; in this case, this is about userspace. Mraw,

Re: kernel module i915 - 3d-acceleration missing after update

> Clearly you didn't search for i915_dri.so or swrast_dri.so, which would > have given the answer trivially. (And cFWIW, we have bugs for that > already.) That's a matter which has been communicated upon [1,2]. And > well, when it comes to X, [3] applies (instead of mailing dd@…). > > 1. http:/

Re: kernel module i915 - 3d-acceleration missing after update

Hi. Hans-J. Ullrich (18/06/2011): > /usr/lib/i386-linux-gnu/dri/i915_dri.so > /usr/lib/i386-linux-gnu/dri/swrast_dri.so > > Solution: > As "apt-file search i386-linux-gnu" did not show any package with this > content, > I added the directories manually and created some symlinks to i915_dri.so

Re: Kernel

I demand that Adrian von Bidder may or may not have written... [snip] > As Paul has said, there is a patch to include the Debian logo at boot. As > far as I know, the kernel still displays the traditional penguin at boot if > a framebuffer is used, but note that on recent systems framebuffer has b

Re: Kernel

Hi! Note that there is another way to display a Debian logo at boot. Plymouth: http://wiki.debian.org/plymouth Though it wont show you the logs unless you type Alt+F1, you will have a debian logo at boot time. Besides that: Anyone thought about doing a loading screen from the Debian Swirl go

Re: Kernel

Heyho! On Tuesday 08 February 2011 22.57:51 Pontus Andersson wrote: > Hi. I like to make a request regarding the Debian Linux kernel. > I think the "tux boot" should be compiled with the Debian logo.. > With tux boot I mean that some distros e.g. Arch and slackware boots with > the logo > while di

Re: Kernel

[presumably you are not subscribed, CCing you] On Wed, Feb 9, 2011 at 5:57 AM, Pontus Andersson wrote: > Hi. I like to make a request regarding the Debian Linux kernel. > I think the "tux boot" should be compiled with the Debian logo.. > With tux boot I mean that some distros e.g. Arch and slackw

Re: kernel-wedge does not work as expected.

On 01/23/2011 03:06 PM, Magicloud Magiclouds wrote: > Hi, > I am trying to make a custom debian-installer cd. I have done this > before, things worked fine. But this time, I got a problem. > My running kernel installed from > linux-image-2.6.36.3i686_bfs363.reiser4_i386.deb. It contains a namin

Re: Kernel legacy

On Sun, 2009-02-01 at 23:31 +0100, Klaus Ethgen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am So den 1. Feb 2009 um 18:57 schrieb Luk Claes: > > > With lenny the provided glibc seems to be incompatible to kernel 2.4. > > > There are many systems out there still running with ke

Re: Kernel legacy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am So den 1. Feb 2009 um 18:57 schrieb Luk Claes: > > With lenny the provided glibc seems to be incompatible to kernel 2.4. > > There are many systems out there still running with kernel 2.4 cause > > stability. (My servers which needs to be stable

Re: Kernel legacy

On Sun, Feb 01, 2009 at 05:26:30PM +0100, Klaus Ethgen wrote: > With lenny the provided glibc seems to be incompatible to kernel 2.4. The Linux 2.4 support ended with the Etch release. Even for Etch it is only supported for upgrades. > Is there any scenario what happens to such systems when lenny

Re: Kernel legacy

Klaus Ethgen wrote: > Just to bring that back to discussion: > > With lenny the provided glibc seems to be incompatible to kernel 2.4. > There are many systems out there still running with kernel 2.4 cause > stability. (My servers which needs to be stable all run Kernel 2.4.) s/lenny/etch/ > Is

Re: Kernel legacy

Klaus Ethgen writes: > Background: The glibc in lenny is compiled to be incompatible with > kernels lower than 2.6. I do not know if there are options to use newer > glibc with older kernels. There is other software in lenny that isn't built to be compatible with older kernels as well. For exam

debian-kernel (Re: kernel 2.6.27 in lenny?)

For kernel-related discussions, ask on debian-kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel 2.6.27 in lenny?

On mar, 2008-10-14 at 07:59 +0200, Peter Jordan wrote: > wouldn't it > be a good idea to take kernel 2.6.27 as the stable kernel in lenny? If we want to release lenny before 2.6.27 is not supported anymore, maybe it's not? -- Yves-Alexis signature.asc Description: This is a digitally signed me

Re: Kernel 2.6.25 broke iPod support for me, but who to bug?

Frank Lichtenheld wrote: > I traced the error back to a change in kernel 2.6.25: Apparently vfat > file system can now become case sensitive in some cases > ("FAT: utf8 is not a recommended IO charset for FAT filesystems, > filesystem will be case sensitive!") > - kernel: I find it unlikely that

Re: Kernel 2.6.25 broke iPod support for me, but who to bug?

On Sat, Jul 12, 2008 at 02:19:58AM +0200, Frank Lichtenheld wrote: > While testing some updates to my gtkpod/libgpod packages I noticed that > I couldn't actually play any songs anymore from my iPod. Which worked > fine some weeks ago. > I traced the error back to a change in kernel 2.6.25: Appar

Re: Kernel 2.6.25 broke iPod support for me, but who to bug?

On Fri, Jul 11, 2008 at 09:11:57PM -0400, James Vega wrote: > On Sat, Jul 12, 2008 at 02:19:58AM +0200, Frank Lichtenheld wrote: > > Hi. > > > > While testing some updates to my gtkpod/libgpod packages I noticed that > > I couldn't actually play any songs anymore from my iPod. Which worked > > fin

Re: Kernel 2.6.25 broke iPod support for me, but who to bug?

On Sat, Jul 12, 2008 at 02:19:58AM +0200, Frank Lichtenheld wrote: > Hi. > > While testing some updates to my gtkpod/libgpod packages I noticed that > I couldn't actually play any songs anymore from my iPod. Which worked > fine some weeks ago. > > I traced the error back to a change in kernel 2.6

Re: Kernel selection in the installation system

IIRC, the kernel udeb in the installer image runs the installer kernel during installation and the installer checks for the CPU type. You can use the 'expert' install option to be given the opportunity to manually select which kernel is installed during installation. - Lawrence On March 26, 2

Re: Kernel selection in the installation system

On Monday 26 March 2007 17:24, Christoph Pleger wrote: > Can anybody tell me how the installer decides which kernel to be > installed? Or tell me where I can find the source code of the selection > process? It is done from the /var/lib/dpkg/base-installer.postinst script, which calls an architect

Re: Kernel 2.6.17 and 2.6.18-3-K7 network problem [SOLVED]

--- Antonio Laterza <[EMAIL PROTECTED]> ha scritto: > Hi all, I posted the question below to debian-user ... > maybe nobody experienced my same issue. How can I > contribute to eventually solve? Which other information > are > necessary in order to focalize the problem? > > > I want to ask if s

Re: Kernel 2.6.17 and 2.6.18-3-K7 network problem [SOLVED]

--- Hendrik Sattler <[EMAIL PROTECTED]> ha scritto: > Am Mittwoch 03 Januar 2007 09:53 schrieb Antonio Laterza: > > :( ). If I choose the kernel 2.6.18 X is OK but I am > not > > > > able to reache many sites. I can navigate very few > sites > > example: www.google.com and www.mozilla.org. Using

Re: Kernel 2.6.17 and 2.6.18-3-K7 network problem

Am Mittwoch 03 Januar 2007 09:53 schrieb Antonio Laterza: > :( ). If I choose the kernel 2.6.18 X is OK but I am not > > able to reache many sites. I can navigate very few sites > example: www.google.com and www.mozilla.org. Using ethereal > seems that the HTTP request go out (i.e. GET / ) but

Re: kernel panic: pivot_root help me

Maybe if you boot using live cd and after that mount your partition and edit /sbin/init and change dev/console for /dev/console. Ozgur Karatas escreveu: Hello, We buy a IBM Blade Server. I choose 2.6 kernel and Grub on Debian 3.1 Sarge Setup. But Debian says me Kernel Panic pivot_root: No such

Re: kernel modules postinst script

Hi, Bernd wrote: > #!/bin/sh > set -e > > SYSTEMMAP=/boot/System.map-_KVERS_ > > if [ -f $SYSTEMMAP ] ; then > depmod -ae -F $SYSTEMMAP _KVERS_ > elif [ "`uname -r`" = "_KVERS_" ] ; then > depmod -a & > fi As of debhelper 5.0.37, dh_installmodules uses the System.map for the tar

Re: kernel modules postinst script

#include * Bernd Schubert [Sat, Jul 22 2006, 03:55:03PM]: > Hi, > > while I just build some kernel module packages for our clients and > installing them, I think I found a bug applying to almost all kernel module > packages. > > Most packages have a file like postinst.modules.in with something l

Re: Kernel bootsplash without recompiling

Loïc Minier schreef: > On Wed, Jun 14, 2006, Paul van der Vlis wrote: > >>I don't like the fact that I need to recompile the kernel to get a >>bootsplash. I don't ask for a bootsplash by default, but I would like a >>way to enable it with a standard kernel. > > Ubuntu starts Linux with a frameb

Re: Kernel bootsplash without recompiling

On Wed, Jun 14, 2006, Paul van der Vlis wrote: > I don't like the fact that I need to recompile the kernel to get a > bootsplash. I don't ask for a bootsplash by default, but I would like a > way to enable it with a standard kernel. Ubuntu starts Linux with a framebuffer atop of the VGA16 video d

Re: Kernel bootsplash without recompiling

Miriam Ruiz schreef: > gensplash and fbsplash might be an option to consider too: > > http://gentoo-wiki.com/HOWTO_fbsplash Interesting... >From the site: http://dev.gentoo.org/~spock/projects/gensplash/ --- This means that if you don't care about having an image in the background of yo

Re: Kernel bootsplash without recompiling

Paul Wise schreef: > On Wed, 2006-06-14 at 13:41 +0200, Paul van der Vlis wrote: > > >>I don't like the fact that I need to recompile the kernel to get a >>bootsplash. I don't ask for a bootsplash by default, but I would like a >>way to enable it with a standard kernel. > > > splashy is a bette

Re: Kernel bootsplash without recompiling

Jérôme Warnier schreef: > Le mercredi 14 juin 2006 à 13:41 +0200, Paul van der Vlis a écrit : > >>Hello, >> >>I don't like the fact that I need to recompile the kernel to get a >>bootsplash. I don't ask for a bootsplash by default, but I would like a >>way to enable it with a standard kernel. >> >

Re: Kernel bootsplash without recompiling

gensplash and fbsplash might be an option to consider too: http://gentoo-wiki.com/HOWTO_fbsplash Miry --- Paul Wise <[EMAIL PROTECTED]> escribió: > On Wed, 2006-06-14 at 13:41 +0200, Paul van der Vlis wrote: > > > I don't like the fact that I need to recompile the kernel to get a > > bootspl

Re: Kernel bootsplash without recompiling

On Wed, 2006-06-14 at 19:55 +0800, Paul Wise wrote: > Your other questions were answered by Jérôme Warnier. I forgot the following pages related to boot splashscreens: http://packages.debian.org/unstable/graphics/kernel-patch-bootsplash http://packages.debian.org/experimental/graphics/splashy ht

Re: Kernel bootsplash without recompiling

On Wed, 2006-06-14 at 13:41 +0200, Paul van der Vlis wrote: > I don't like the fact that I need to recompile the kernel to get a > bootsplash. I don't ask for a bootsplash by default, but I would like a > way to enable it with a standard kernel. splashy is a better alternative to the kernel-patch

Re: Kernel bootsplash without recompiling

Le mercredi 14 juin 2006 à 13:41 +0200, Paul van der Vlis a écrit : > Hello, > > I don't like the fact that I need to recompile the kernel to get a > bootsplash. I don't ask for a bootsplash by default, but I would like a > way to enable it with a standard kernel. > > For many many people all the

Re: Kernel compile fails.

Alejandro Bonilla Beeche wrote: I have a box with Sid with the latest upgrades, (almost cause dist-upgrade wants to remove a lot of stuff) Anyway, fact is that I can't compile any kernel on the Linus tree. This, for more than a month. Could anyone please help me find out which package is

Re: kernel-package hooks transition

On Mon, 26 Dec 2005 10:45:52 +0100, Sven Luther <[EMAIL PROTECTED]> said: > Ok, then this is probably the root of the problem here. > Kernel-package does call db_stop, before calling the hooks, since it > has no guarantee that the hooks will behave properly. Past tense. This has not bee

Re: kernel-package hooks transition

On Sun, Dec 25, 2005 at 01:50:35PM -0800, Steve Langasek wrote: > On Sun, Dec 25, 2005 at 03:34:43PM +, Colin Watson wrote: > > The STOP command causes the debconf frontend to shut down; that would > > certainly break anything trying to talk to debconf after it. May be > > worth removing that a

Re: kernel-package hooks transition

* Colin Watson <[EMAIL PROTECTED]> [051224 18:30]: > The fd 3 redirection (and the corresponding redirection of stdout to > stderr in the shell confmodule) was always acknowledged as a nasty hack > in debconf. At the time, as I understand it, Joey reckoned it was easier > to do that than to try to

Re: kernel-package hooks transition

On Sun, Dec 25, 2005 at 03:34:43PM +, Colin Watson wrote: > On Sun, Dec 25, 2005 at 01:51:00AM +0100, Sven Luther wrote: > > On Sat, Dec 24, 2005 at 05:30:26PM +, Colin Watson wrote: > > > On Sat, Dec 24, 2005 at 05:03:17PM +0100, Sven Luther wrote: > > > > Notice that the debconf helper sc

Re: kernel-package hooks transition

On Sun, Dec 25, 2005 at 01:51:00AM +0100, Sven Luther wrote: > On Sat, Dec 24, 2005 at 05:30:26PM +, Colin Watson wrote: > > On Sat, Dec 24, 2005 at 05:03:17PM +0100, Sven Luther wrote: > > > Notice that the debconf helper scripts provide stdout on &3, so any > > > scripts writing to stdout onl

Re: kernel-package hooks transition

On Sun, Dec 25, 2005 at 01:43:19AM +0100, Sven Luther wrote: > On Sat, Dec 24, 2005 at 05:30:26PM +, Colin Watson wrote: > > On Sat, Dec 24, 2005 at 05:03:17PM +0100, Sven Luther wrote: > > > Notice that the debconf helper scripts provide stdout on &3, so any > > > scripts writing to stdout onl

Re: kernel-package hooks transition

On Sun, 25 Dec 2005, Sven Luther wrote: > Well, you are the expert, i said this, because the > /usr/share/debconf/confmodule script i use in mkvmlinuz and recomended by > debconf-devel says : > > # Redirect standard output to standard error. This prevents common > # mistakes by mak

Re: kernel-package hooks transition

On Sat, Dec 24, 2005 at 05:30:26PM +, Colin Watson wrote: > On Sat, Dec 24, 2005 at 05:03:17PM +0100, Sven Luther wrote: > > Notice that the debconf helper scripts provide stdout on &3, so any > > scripts writing to stdout only need to redirect their output to &3, no > > ? > > No, that won't

Re: kernel-package hooks transition

On Sat, Dec 24, 2005 at 05:30:26PM +, Colin Watson wrote: > On Sat, Dec 24, 2005 at 05:03:17PM +0100, Sven Luther wrote: > > Notice that the debconf helper scripts provide stdout on &3, so any > > scripts writing to stdout only need to redirect their output to &3, no > > My impression is that t

Re: kernel-package hooks transition

On Sat, Dec 24, 2005 at 05:30:26PM +, Colin Watson wrote: > On Sat, Dec 24, 2005 at 05:03:17PM +0100, Sven Luther wrote: > > Notice that the debconf helper scripts provide stdout on &3, so any > > scripts writing to stdout only need to redirect their output to &3, no > > ? > > No, that won't

Re: kernel-package hooks transition

On Sat, Dec 24, 2005 at 05:03:17PM +0100, Sven Luther wrote: > Notice that the debconf helper scripts provide stdout on &3, so any > scripts writing to stdout only need to redirect their output to &3, no > ? No, that won't work; if you send something to fd 3, it will go to the debconf frontend an

Re: kernel-package hooks transition

On Sat, Dec 24, 2005 at 09:19:36AM -0600, Manoj Srivastava wrote: > Hi, > > In the recent 10.X series, kernel package has started > producing image packages whose maintainer scripts use debconf for > user interaction. Unfortunately, this meant that any hook scripts > called in the main

Re: kernel 2.6.14

On Thu, Dec 15, 2005 at 03:16:52PM +0100, Zejn Gasper wrote: > I've had the same experience yesterday, i didn't have time, so i downgraded > to > 2.6.12. > > But there's something wrong with the kernel. Others wrote: > > > > Waiting 2 seconds /sys/block/hda/dev to show up. > > > > /bin/cat:/sy

Re: kernel 2.6.14

I've had the same experience yesterday, i didn't have time, so i downgraded to 2.6.12. But there's something wrong with the kernel. Greetings, Gasper Zejn On Thursday 15 of December 2005 13:23, Andrew Vaughan wrote: > Hi > > On Thu, 15 Dec 2005 22:34, Richard Fojta wrote: > > Hi, > > I've rece

Re: kernel 2.6.14

Hi On Thu, 15 Dec 2005 22:34, Richard Fojta wrote: > Hi, > I've recently try to install new kernel. Somethings go wrong and I cannot > found solution. There is some problem with configuration. It seems to me, > that this problem is not unique. Does anybody know how to solve ti? [This is probably m

Re: kernel security bug #307900

Hi, On Friday 10 June 2005 04:02, Adam Majer wrote: > > > woody's kernels are vulnerable to CAN-2004-1235, a uselib() race > > condition. > > Will this be fixed for Woody? > > I thought the plan was to provide security support for Woody for > > another year? > AFAIK, there is no security support f

Re: kernel security bug #307900

Olaf van der Spek wrote: > Adam Majer wrote: > >> AFAIK, there is no security support for Woody kernels for some time now. >> Use kernel.org and compile your kernels for security sensitive machines. > > > What's the reason for this lack of support? > > I think after Herbert Xu left so did security

Re: kernel security bug #307900

Adam Majer wrote: Olaf van der Spek wrote: woody's kernels are vulnerable to CAN-2004-1235, a uselib() race condition. Will this be fixed for Woody? I thought the plan was to provide security support for Woody for another year? AFAIK, there is no security support for Woody kernels for s

Re: kernel security bug #307900

Olaf van der Spek wrote: > > woody's kernels are vulnerable to CAN-2004-1235, a uselib() race > condition. > > Will this be fixed for Woody? > I thought the plan was to provide security support for Woody for > another year? AFAIK, there is no security support for Woody kernels for some time now.

Re: Re: kernel security bug #307900

> woody's kernels are vulnerable to CAN-2004-1235, a uselib() race condition. Will this be fixed for Woody? I thought the plan was to provide security support for Woody for another year? -- Olaf van der Spek http://xccu.sf.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "

Re: kernel security bug #307900

On Mon, Jun 06, 2005 at 08:28:17AM +1000, Brian May wrote: > > "Steve" == Steve Langasek <[EMAIL PROTECTED]> writes: > Steve> kernel-image packages built against 2.6.8-16 are available > Steve> in sarge for the past week or so for i386, alpha, and ia64. > [...] > Steve> In light

Re: kernel security bug #307900

> "Steve" == Steve Langasek <[EMAIL PROTECTED]> writes: Steve> kernel-image packages built against 2.6.8-16 are available Steve> in sarge for the past week or so for i386, alpha, and ia64. [...] Steve> In light of the announcement at the beginning of May that Steve> sarge is

Re: kernel security bug #307900

On Sun, Jun 05, 2005 at 12:22:07PM +1000, Brian May wrote: > Whats the deal with bug #307900? > As far as I can tell from reading the bug report, the bug has not been > fixed in sarge, will not be fixed for the release, but the bug has > been closed. kernel-source-2.6.8 2.6.8-15 has been in testi

Re: kernel security bug #307900

On Sun, Jun 05, 2005 at 12:22:07PM +1000, Brian May wrote: > As far as I can tell from reading the bug report, the bug has not been > fixed in sarge, will not be fixed for the release, but the bug has > been closed. > > Have we come to the point where making a release is more important > then fixi

Re: Kernel version 100

Ladislav Bodnar wrote: > On Tuesday 26 October 2004 22:15, Norbert Tretkowski wrote: > > > Just curious: any particular reason why the kernel version is > > > reported as "100" on > > > http://packages.debian.org/unstable/allpackages? > > > > > > kernel-image-2.6-386 (100) > > >     Linux kernel im

Re: Kernel version 100

On Tuesday 26 October 2004 22:15, Norbert Tretkowski wrote: > > Just curious: any particular reason why the kernel version is > > reported as "100" on > > http://packages.debian.org/unstable/allpackages? > > > > kernel-image-2.6-386 (100) > >     Linux kernel image for version 2.6 on 386. > > This

Re: Kernel version 100

* Ladislav Bodnar wrote: > Just curious: any particular reason why the kernel version is reported > as "100" on http://packages.debian.org/unstable/allpackages? > > kernel-image-2.6-386 (100) > Linux kernel image for version 2.6 on 386. This is just a meta-package, which depends on the latest

Re: kernel update takes out nvidia drivers

Carl B. Constantine wrote: * Carl B. Constantine ([EMAIL PROTECTED]) wrote: I just did an update on my system. it updated my kernel to a newer version of the same kernel. It also updated all the nvidia packages. But X no longer works. Even though the nvidia packages are installed, the drivers do

Re: kernel update takes out nvidia drivers

* Carl B. Constantine ([EMAIL PROTECTED]) wrote: > I just did an update on my system. it updated my kernel to a newer > version of the same kernel. It also updated all the nvidia packages. But > X no longer works. Even though the nvidia packages are installed, the > drivers do not work, the kernel

Re: Kernel 2.4.18 and GCC 3.3 (not a good mix)

On Sat, Dec 06, 2003 at 05:05:02AM +0100, smurfd said > Seems that gcc 3.3 and kernel 2.4.18 (with grsec patch) dont like > eachother. Yes, this is a well-known problem. Use gcc 2.95.4 (which is still the recommended compiler for 2.4, anyway) or upgrade to 2.4.23. Also, 2.4.18 has at least two l

Re: kernel-patch-acl

On Fri, Dec 05, 2003 at 01:58:27PM +1100, Russell Coker wrote: > Herbert, would it be possible to get the ACL kernel patch included in the > Debian kernel source? I'm afraid that you've missed boat for 2.4.23. I'll consider it for 2.4.24. Please file a bug report against kernel about it. > Muc

Re: kernel-patch-acl

On Fri, Dec 05, 2003 at 01:58:27PM +1100, Russell Coker wrote: > Much of this patch is scheduled to be included in 2.4.24, so the work > required Who claims that?

Re: kernel-patch-acl

On Fri, 5 Dec 2003 13:59, Ben Collins <[EMAIL PROTECTED]> wrote: > > This problem has already bitten several skilled Debian developers at > > various times. Given the problems that are caused for such skilled > > people as a result of this I hate to imagine the consequences for typical > > users!

Re: kernel-patch-acl

> This problem has already bitten several skilled Debian developers at various > times. Given the problems that are caused for such skilled people as a > result of this I hate to imagine the consequences for typical users! But typical users wont be building custom kernels with ACL patches, will

Re: Kernel 2.4.22-k7-1: initrd cannot mount proc from cramfs image

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> If you're using busybox then try regenerating the initrd image with >> BUSYBOX=no. > I did not generate the image, i'm using a stock kernel-image-2.4.22-1-k7 > package, no trace of busybox in the initrd image, and it's not even installed > on this

Re: Kernel 2.4.22-k7-1: initrd cannot mount proc from cramfs image

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for the attention, Herbert. > If you're using busybox then try regenerating the initrd image with > BUSYBOX=no. I did not generate the image, i'm using a stock kernel-image-2.4.22-1-k7 package, no trace of busybox in the initrd image, and it'

Re: Kernel 2.4.22-k7-1: initrd cannot mount proc from cramfs image

Nicola Larosa <[EMAIL PROTECTED]> wrote: > > RAMDISK: cramfs filesystem found at block 0 > RAMDISK: Loading 3532 blocks [1 disk] into ram disk... done. > Freeing initrd memory: 3532k freed > VFS: mounted root (cramfs filesystem). > mount: Usage: mount [-t filesystemtype] [-o options,...] device mo

Re: kernel package names (was Re: Package libc6-dev depends on linux-kernel-headers)

On Thu, Nov 06, 2003 at 01:14:31PM -0600, Steve Greenland wrote: > On 05-Nov-03, 19:14 (CST), Jonathan Dowland <[EMAIL PROTECTED]> wrote: > > I'm in two minds whether or not to ask this, but I've been wondering > > about the naming scheme for linux packages - kernel-*. Why not > > linux-kernel-* o

Re: kernel package names (was Re: Package libc6-dev depends on linux-kernel-headers)

On Wed, Nov 05, 2003 at 08:43:52PM -0500, Greg Folkert wrote: > On Wed, 2003-11-05 at 20:14, Jonathan Dowland wrote: > > I'm in two minds whether or not to ask this, but I've been wondering > > about the naming scheme for linux packages - kernel-*. Why not > > linux-kernel-* or linux-* ? If alterna

  1   2   3   4   5   >