Bug#387767: Installation Failure

[Keith Parkansky]

FYI
The new Debian Installer using the
2.6.17 kernel does NOT fix the
CD drive problem that is covered
by bug 387767.  I just downloaded
the Net Install image and tried to
install from it and had the same
problem.




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#387767: Installation Failure

[Sven Luther]

On Wed, Nov 15, 2006 at 02:19:51AM -0600, Keith Parkansky wrote:
> FYI
> The new Debian Installer using the
> 2.6.17 kernel does NOT fix the
> CD drive problem that is covered
> by bug 387767.  I just downloaded
> the Net Install image and tried to
> install from it and had the same
> problem.

Please try it with the new 2.6.18 kernels, which are scheduled for the etch
release, and should enter d-i soon.

There where some CD related fixes which where applied recently.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: release notes

[Andreas Barth]

* dann frazier ([EMAIL PROTECTED]) [061115 01:47]:
> I've updated the text in svn, and added some more to help with a
> couple of the open bugs in your list. I would really appreciate it if
> others from the kernel team could review it for accuracy, especially
> the initramfs-tools/yaird stuff.

Another question: What is the recommended installation order for this
upgrade? We have different variants: From 2.2, 2.4 or 2.6-kernels (where
we have different default kernel versions on different arches)?

First packages, then kernel? Or first kernel? Or kernel first if it is
2.2 or 2.4, otherwise packages first? Or ...?


Cheers,
Andi
-- 
  http://home.arcor.de/andreas-barth/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: release notes

[Andreas Barth]

* dann frazier ([EMAIL PROTECTED]) [061115 01:47]:
> aba: Let me know if you need any help incorporating this text, and
> once its merged, let me know so that I can kill off the version in
> svn.

I know merge it to the release notes (should be visible with the next
build).

There are two changes I didn't merge:
| 
| [ it needs documentation about the new s390 hardware configuration]
| 

This one is IMHO already part of bug #360582: s390 network.

Waldi, when can we expect updates from you on that bug?


| 
| For example, an rx1600 with a single built-in serial port plus
| an MP has these ports:
|Old Old
|   MMIO (EFI console(EFI console
|  addresson builtin) on MP port)  New
| --   -
| builtin 0xff5ettyS0   ttyS1  ttyS0
| MP UPS  0xf8031000ttyS1   ttyS2  ttyS1
| MP Console  0xf803ttyS2   ttyS0  ttyS2
| MP 20xf8030010ttyS3   ttyS3  ttyS3
| MP 30xf8030038ttyS4   ttyS4  ttyS4

I don't think we need this detailed level on the release notes. If we
should have more details then we have now (and I even believe now it is
already too detailed), one should create an extra document / wiki page /
whatever, and we could cross-reference.



About the open kernel-related bug reports:
| #383982: release-notes: Describe replace of kernel-image package with
| linux-image package

has happened now.

| #271315: kernel-image-2.6.8-1-sparc64: sun keyboard unusable

does this bug affect us at all now? If so, we need some more input.

| #341225: Etch: Upgrade path from devfs to udev needs documenting

This should be also done now.

| #325568: Upgrade path for udev needs documenting

This has not happened yet, and also, it seems the answer "in which order
should the upgrade happen" is related to that.

| #343892: Should document NIC naming issue with udev

This should be done now.

| #395174: linux-2.6: Dell CERC ATA100/4ch with F/W >6.61 not supported in etch

We need more info on that I think.

| #360582: s390 network
open, see above.




Cheers,
Andi
-- 
  http://home.arcor.de/andreas-barth/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: release notes

[dann frazier]

On Wed, Nov 15, 2006 at 12:06:52PM +0100, Andreas Barth wrote:
> * dann frazier ([EMAIL PROTECTED]) [061115 01:47]:
> > I've updated the text in svn, and added some more to help with a
> > couple of the open bugs in your list. I would really appreciate it if
> > others from the kernel team could review it for accuracy, especially
> > the initramfs-tools/yaird stuff.
> 
> Another question: What is the recommended installation order for this
> upgrade? We have different variants: From 2.2, 2.4 or 2.6-kernels (where
> we have different default kernel versions on different arches)?
> 
> First packages, then kernel? Or first kernel? Or kernel first if it is
> 2.2 or 2.4, otherwise packages first? Or ...?

I don't know of any issues with upgrading everything (in any order)
before rebooting.

-- 
dann frazier


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#398136: Failure to reclaim swap in 2.6.18-2-ixp4xx

[Michael S. Zick]

The usual disk attachment for machines running this 
kernel is the USB ports.

Could this be a similar problem to that of running
swap over the network? (NFS/NBD)

A recent discussion is here:


I.E: Does usb-storage have to allocate memory to
get its job done?  Does it have a reserve pool?

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#398470: Acknowledgement (mysterious, possibly race-y oops in key/keyring code)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 398470 linux-2.6
Bug#398470: mysterious, possibly race-y oops in key/keyring code
Warning: Unknown package 'linux-image-2.6.18-1-686'
Bug reassigned from package `linux-image-2.6.18-1-686' to `linux-2.6'.

> retitle 398470 2.6.18: mysterious, possibly race-y oops in key/keyring code
Bug#398470: mysterious, possibly race-y oops in key/keyring code
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310982: plan to include in sarge 2.4 update

[dann frazier]

On Mon, Nov 13, 2006 at 12:22:59PM -0800, Steve Langasek wrote:
> Yes, because this is a kernel security bug.  The smbmount patch was
> entertained pre-sarge only as a stopgap due to the proximity to release; the
> right place to fix this is still in the kernel (upstream as appropriate).

I've done some testing and verified that 2.6.18 honors uid= and 2.6.8
does not. It looks like this was fixed upstream:
  http://linux.bkbits.net:8080/linux-2.6/[EMAIL 
PROTECTED]|src/|src/fs|src/fs/smbfs|related/fs/smbfs/inode.c

So, I plan to use this patch for 2.6.8, and attempt to backport it to
2.4.27. If backporting becomes overly complicated/risky, I'll revert
to using something like Horms' patch. I'll also see about getting a
CVE assigned.

Everyone cool with this plan?

-- 
dann frazier



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#80878: In preparation for

[Gerardo]

Stop the girls from laughing.
Stop being a boy, and become a man.
What we are trying to say isget a larger (d)ick.

Site Domain: bdman.net
**Cut and paste site domain into browser

Have a large day;

Donna Gomes
The Extenders

No more?
bdman.net/r.php



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310982: plan to include in sarge 2.4 update

[Horms]

On Wed, Nov 15, 2006 at 05:54:52PM -0700, dann frazier wrote:
> On Mon, Nov 13, 2006 at 12:22:59PM -0800, Steve Langasek wrote:
> > Yes, because this is a kernel security bug.  The smbmount patch was
> > entertained pre-sarge only as a stopgap due to the proximity to release; the
> > right place to fix this is still in the kernel (upstream as appropriate).
> 
> I've done some testing and verified that 2.6.18 honors uid= and 2.6.8
> does not. It looks like this was fixed upstream:
>   http://linux.bkbits.net:8080/linux-2.6/[EMAIL 
> PROTECTED]|src/|src/fs|src/fs/smbfs|related/fs/smbfs/inode.c
> 
> So, I plan to use this patch for 2.6.8, and attempt to backport it to
> 2.4.27. If backporting becomes overly complicated/risky, I'll revert
> to using something like Horms' patch. I'll also see about getting a
> CVE assigned.
> 
> Everyone cool with this plan?

Ack

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]