On Sat, Oct 15, 2005 at 09:59:21PM +0200, Jonas Smedegaard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> -while getopts "d:km:o:r:" flag; do
> - case $flag in
> - d)
> - echo "$PROG: $flag unsupported"
> +TEMP=`getopt -o d:km:o:r: --long
> supported-host-version:,supported-targ
On Sat, Oct 15, 2005 at 10:16:48PM +0200, Mattia Dongili wrote:
> On Sat, Oct 15, 2005 at 08:36:11PM +0200, Sven Luther wrote:
> > I would be extremely grateful if someone could take the time and implement
> > this ASAP, as we need this to upload 2.6.13-2 and finish the support.
>
> It's not entir
On Sat, Oct 15, 2005 at 09:42:54PM +0200, Erik van Konijnenburg wrote:
> On Sat, Oct 15, 2005 at 06:15:04PM +0200, Jonas Smedegaard wrote:
> > I would really like to have the choice of both approaches, also for
> > less common tasks like switching from 2.4 or preparing an alien bootup
> > (either f
On Sat, Oct 15, 2005 at 09:08:17PM +0200, Ralf Hildebrandt wrote:
> On Saturday 15 October 2005 20:38, you wrote:
>
> > > Versions of packages linux-image-2.6.13-1-k7 depends on:
> > > ii initrd-tools 0.1.82 tools to create initrd
> > > image for p ii module-init-tools
On Sat, Oct 15, 2005 at 10:25:54PM -0400, Michael Gilbert wrote:
> > Now, those wanting to compile third party drivers like the nvidia ones,
> > should
> > take the nvidia package (or whatever it is called) and build it following
> > to
> > instructions, or even better, the new policy should cal
> Now, those wanting to compile third party drivers like the nvidia ones, should
> take the nvidia package (or whatever it is called) and build it following to
> instructions, or even better, the new policy should call for pre-compilation
> for all official flavours of those modules, like it is al
On Sat, 15 Oct 2005, Brad Boyer wrote:
Apple switched over to bmac for onboard ethernet at some point. I
know that is what is in my wallstreet powerbook. I do recall many
of the earlier models having mace as mentioned above. Even my
Mac Quadra 840AV has mace for the onboard ethernet, and that's
On Fri, Oct 14, 2005 at 04:01:11PM -0300, Rog?rio Brito wrote:
> On Oct 14 2005, Hans Ekbrand wrote:
> > Yes, but that would be a different kernel then. Does anyone know what
> > NICs are most common in oldworld macs (since the nic-drivers must be
> > compiled in)? I have a de2104x PCI Ethernet in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I had a look at the patch by Erik, and ended up doing the following
improvements:
* Use GNU getopt to properly handle long-opts
* Quote echo'ed strings
* Redirect error messages to stderr
* Use test -n
* Emit error when failing version
On Sat, Oct 15, 2005 at 08:36:11PM +0200, Sven Luther wrote:
> On Sat, Oct 15, 2005 at 12:19:04PM +0200, Sven Luther wrote:
> > Hello,
> >
> > Now that we have a solution for the ramdisk generation tool mess, we can go
> > ahead, and outline a plan for bringing 2.6.13 to sid, and then go ahead and
On Sat, Oct 15, 2005 at 06:15:04PM +0200, Jonas Smedegaard wrote:
> On Sat, 15 Oct 2005 16:34:57 +0200 Erik van Konijnenburg <[EMAIL PROTECTED]>
> wrote:
> > On Sat, Oct 15, 2005 at 08:57:31AM +0200, Sven Luther wrote:
> > > On Sat, Oct 15, 2005 at 08:47:57AM +0200, Erik van Konijnenburg wrote:
>
Hi John,
regarding your bug report "cramfsprogs: Extremely inefficient
performance on large trees":
mkfs.cramfs (shipped with the util-linux package) already uses md5sums
the way you suggest them. Can you confirm that mkfs.cramfs fixes your
problem?
cu
Adrian
--
"Is there not promis
On Saturday 15 October 2005 20:38, you wrote:
> > Versions of packages linux-image-2.6.13-1-k7 depends on:
> > ii initrd-tools 0.1.82 tools to create initrd
> > image for p ii module-init-tools 3.2-pre9-2 tools for
> > managing Linux kernel mo
> >
> > linux-image
On Sat, Oct 15, 2005 at 08:15:49PM +0200, Ralf Hildebrandt wrote:
> Package: linux-image-2.6.13-1-k7
> Version: 2.6.13-1
> Severity: normal
>
>
> 2.6.12-1-k7 works OK, the USB mouse works.
> Booting 2.6.13-1-k7 results in problems with the USB controller and IRQ
> 11 issues.
>
> I attached dmesg
On Sat, Oct 15, 2005 at 08:45:06PM +0200, Bastian Blank wrote:
> On Sat, Oct 15, 2005 at 08:22:30PM +0200, Sven Luther wrote:
> > I think to remember that ~ is only allowed for etch+1, since we need to
> > handle
> > sarge->etch upgrades. not sure about dak though.
>
> AFAIK sarge supports ~ in t
On Sat, Oct 15, 2005 at 12:19:04PM +0200, Sven Luther wrote:
> Hello,
>
> Now that we have a solution for the ramdisk generation tool mess, we can go
> ahead, and outline a plan for bringing 2.6.13 to sid, and then go ahead and do
> the same with 2.6.14 shortly after that, while 2.6.12 is safely i
On Sat, Oct 15, 2005 at 08:22:30PM +0200, Sven Luther wrote:
> I think to remember that ~ is only allowed for etch+1, since we need to handle
> sarge->etch upgrades. not sure about dak though.
AFAIK sarge supports ~ in the tools, but dak does not.
Bastian
--
You! What PLANET is this!
On Sat, Oct 15, 2005 at 08:11:40PM +0200, Bastian Blank wrote:
> On Sat, Oct 15, 2005 at 07:43:02PM +0200, Sven Luther wrote:
> > In the light of this, i would indeed vote to move our package to 2.6.14-rc4
> > (versioned at 2.6.13.99.rc4 or something, and maybe with 2.6.14-0 abi name),
>
> 2.6.13+
Package: linux-image-2.6.13-1-k7
Version: 2.6.13-1
Severity: normal
2.6.12-1-k7 works OK, the USB mouse works.
Booting 2.6.13-1-k7 results in problems with the USB controller and IRQ
11 issues.
I attached dmesg output for kernel 2.6.12 and 2.6.13; maybe the diff
between the two can give some ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 9 Oct 2005 10:17:06 +0200
Sven Luther <[EMAIL PROTECTED]> wrote:
[other parts of this old mail discussed already]
> On another note, the yaird document you mentioned, which was a very
> nice read on the train yesterday :), mentioned adding cu
On Sat, Oct 15, 2005 at 07:43:02PM +0200, Sven Luther wrote:
> In the light of this, i would indeed vote to move our package to 2.6.14-rc4
> (versioned at 2.6.13.99.rc4 or something, and maybe with 2.6.14-0 abi name),
2.6.13+2.6.14-r4 or 2.6.14~rc4, I don't know if the later is now
supported by da
On Sat, Oct 15, 2005 at 06:02:53PM +0100, Mark Hymers wrote:
> Hi,
>
> I did a quick patch audit for 2.6.14-rc4 based on the 2.6.13-1 source
> tree and was asked on IRC to post it here so that it doesn't get lost.
Very very cool, it is work like this which will allow us to go forward and
maybe do
Package: linux-image-2.6.12-1-powerpc
Version: 2.6.12-10
Severity: critical
Tags: security
Justification: root security hole
The non-suid command "loadkeys" can be used by any local user having
console access. It does not just apply to the current virtual console
but to all virtual consoles and i
Hi,
I did a quick patch audit for 2.6.14-rc4 based on the 2.6.13-1 source
tree and was asked on IRC to post it here so that it doesn't get lost.
=== patches_triage-2.6.14rc4.txt
Status as of 2.6.14-rc4
based on the linux-2.6 2.6.13-1 debian source package
Applied upstream
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 15 Oct 2005 17:51:40 +0200
Sven Luther <[EMAIL PROTECTED]> wrote:
> Well, etch will not ship with a 2.6.8 kernel, so the upgrade path to
> 2.6.8 is not something we need to concern ourself with. the upgrade
> path from 2.6.8 is another mather,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[trimming recipients to lessen duplicates]
On Sat, 15 Oct 2005 16:34:57 +0200
Erik van Konijnenburg <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 15, 2005 at 08:57:31AM +0200, Sven Luther wrote:
> > On Sat, Oct 15, 2005 at 08:47:57AM +0200, Erik van Konij
> we do not support closed drivers.
> anyway as this bug has not seen much activity since,
> i guess it is resolved in between.
>
> reopen if pain subsist with plain nv and linux image 2.6.12 in unstable
> or 2.6.13 in experimental.
>
> --
> maks
>
This actually was a kernel bug and the PCI_I
On Sat, Oct 15, 2005 at 11:41:07AM +0200, Jonas Smedegaard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sat, 15 Oct 2005 08:57:31 +0200
> Sven Luther <[EMAIL PROTECTED]> wrote:
>
> > > The patch claims support for 2.6.8, which is where development
> > > started, but later yaird
On Sat, Oct 15, 2005 at 04:34:57PM +0200, Erik van Konijnenburg wrote:
> On Sat, Oct 15, 2005 at 08:57:31AM +0200, Sven Luther wrote:
> > On Sat, Oct 15, 2005 at 08:47:57AM +0200, Erik van Konijnenburg wrote:
> > > On Fri, Oct 14, 2005 at 12:53:41PM +0200, Jonas Smedegaard wrote:
>
> > Hey, i didn
On Sat, Oct 15, 2005 at 08:57:31AM +0200, Sven Luther wrote:
> On Sat, Oct 15, 2005 at 08:47:57AM +0200, Erik van Konijnenburg wrote:
> > On Fri, Oct 14, 2005 at 12:53:41PM +0200, Jonas Smedegaard wrote:
> Hey, i didn't know the mkinitrd wrapper was shell, or i would have done it
> myself. I wonde
On Sat, Oct 15, 2005 at 04:21:48PM +0200, Bastian Blank wrote:
> On Sat, Oct 15, 2005 at 03:51:37PM +0200, Sven Luther wrote:
> > One solution would be for each kernel to provide a virtual
> > linux-abi-, and have each module package [build-]depend on it or
> > something such, in a way similar to h
On Sat, Oct 15, 2005 at 03:51:37PM +0200, Sven Luther wrote:
> One solution would be for each kernel to provide a virtual
> linux-abi-, and have each module package [build-]depend on it or
> something such, in a way similar to how ocaml handles its abi versioning. Need
> some thoughts still.
A dep
On Sat, Oct 15, 2005 at 01:57:19PM +0200, maximilian attems wrote:
> [snipping the cc list ]
>
> On Sat, 15 Oct 2005, Bastian Blank wrote:
>
> > > The other issue is that 2.6.14 is scheduled for release in the not so
> > > distant
> > > future, so we may skip uploading .13-3 to unstable and go f
On Sat, Oct 15, 2005 at 02:29:59PM +0200, Jeroen van Wolffelaar wrote:
> tags 331391 = confirmed
> thanks
>
> On Thu, Oct 13, 2005 at 12:57:49PM +0200, Sven Luther wrote:
> > Iti s an sarge -> etch upgrade problem if anything, let's remove them for
> > now,
> > and once we sorted out the module b
On Sat, Oct 15, 2005 at 09:00:38PM +0900, Horms wrote:
> > > > The other issue is that 2.6.14 is scheduled for release in the not so
> > > > distant
> > > > future, so we may skip uploading .13-3 to unstable and go for .14-1
> > > > directly,
> > > > depending on status of newly introduced breaka
tags 331391 = confirmed
thanks
On Thu, Oct 13, 2005 at 12:57:49PM +0200, Sven Luther wrote:
> Iti s an sarge -> etch upgrade problem if anything, let's remove them for now,
> and once we sorted out the module build issues, we can always readd them fori
> etch if really needed.
It'd be convenient
[snipping the cc list ]
On Sat, 15 Oct 2005, Bastian Blank wrote:
> > The other issue is that 2.6.14 is scheduled for release in the not so
> > distant
> > future, so we may skip uploading .13-3 to unstable and go for .14-1
> > directly,
> > depending on status of newly introduced breakage in .
On Sat, Oct 15, 2005 at 01:13:31PM +0200, Sven Luther wrote:
> On Sat, Oct 15, 2005 at 01:07:38PM +0200, Bastian Blank wrote:
> > On Sat, Oct 15, 2005 at 12:19:04PM +0200, Sven Luther wrote:
> > > the plan for solving the ramdisk issues is done in three stages, current
> > > svn
> > > 2.6.13 packa
On Sat, Oct 15, 2005 at 01:07:38PM +0200, Bastian Blank wrote:
> On Sat, Oct 15, 2005 at 12:19:04PM +0200, Sven Luther wrote:
> > the plan for solving the ramdisk issues is done in three stages, current svn
> > 2.6.13 packages implement stage 1, i have patches for both initrd-tools and
> > initramf
On Sat, Oct 15, 2005 at 12:19:04PM +0200, Sven Luther wrote:
> the plan for solving the ramdisk issues is done in three stages, current svn
> 2.6.13 packages implement stage 1, i have patches for both initrd-tools and
> initramfs-tools in svn, and the yaird folk adapted it for yaird, so we may go
>
Hello,
Now that we have a solution for the ramdisk generation tool mess, we can go
ahead, and outline a plan for bringing 2.6.13 to sid, and then go ahead and do
the same with 2.6.14 shortly after that, while 2.6.12 is safely in etch.
As mentioned in :
...
the plan for solving the ramdisk iss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 15 Oct 2005 08:57:31 +0200
Sven Luther <[EMAIL PROTECTED]> wrote:
> > The patch claims support for 2.6.8, which is where development
> > started, but later yaird versions only have had testing with
> > newer kernels. If we could get away with
On Sat, Oct 15, 2005 at 07:06:05AM +0200, Sven Luther wrote:
> On Fri, Oct 14, 2005 at 10:43:34PM +0200, Marc Haber wrote:
> > I now know what was going on. Despite debian/rules not directly using
> > make-kpkg, the build process somehow uses code delivered by
> > kernel-package, which in turn hono
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[dropping yaird@ from this
On Sat, 15 Oct 2005 08:47:57 +0200
Erik van Konijnenburg <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 14, 2005 at 12:53:41PM +0200, Jonas Smedegaard wrote:
> > That said, I also think I should be able to implement those option
Hey.
I'm going to apologize upfront for taking a bit of a
tangent from the initial direction of this report. I
have seen similar symptoms, but there's no sign of
similar issues in the linux-source-2.6.12 bug reports.
Maybe my experiences could be of some help?
> Can you, and everyone else encoun
On Sat, Oct 15, 2005 at 08:47:57AM +0200, Erik van Konijnenburg wrote:
> On Fri, Oct 14, 2005 at 12:53:41PM +0200, Jonas Smedegaard wrote:
> > That said, I also think I should be able to implement those options to
> > the mkinitrd.yaird wrapper - if upstream doesn't beat me to it ;-).
>
> Is that
46 matches
Mail list logo
