From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Marek Szuba <scriptkiddie@wp.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.5] A bunch of various minor bugs not fixed since 2.6.4
Date: Sun, 4 Apr 2004 23:12:19 +0100 [thread overview]
Message-ID: <20040404231219.D17113@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040404235411.7ffde014.scriptkiddie@wp.pl>; from scriptkiddie@wp.pl on Sun, Apr 04, 2004 at 11:54:11PM +0200
On Sun, Apr 04, 2004 at 11:54:11PM +0200, Marek Szuba wrote:
> 1. 'make *config' fails with missing header files
Only people who try to build userspace programs against current
kernel header files experience this problem.
> 2. Platform-specific 'asm' symlink doesn't get created by 'make *config'
This is only a problem for people trying to build userspace programs
against current kernel header files.
> 3. 'make clean' seems to remove too much
See 2.
These three complaints seem to revolve around your attempt to use
the kernels header files for building user space programs against.
This is something which hasn't really been supported by the kernel
for many versions (since before 2.4) as you will find when searching
the LKML archives.
/usr/include/{asm,linux} are supposed to be a copy of the sanitised
kernel headers which were used *when glibc was built* (the words
between the '*' are the important ones here.)
> 4. Floppy LED remains on whenever LILO boots the kernel quickly
This is a lilo bug - lilo is supposed to turn off the floppy motor before
calling the kernel; the kernel has dropped its work-around for this bug
and expects the boot loader to do it.
Alternatively, build a kernel with floppy support built in.
> 6. (not really a bug) It would be nice if the ieee1394 subsystem got
> sysfs'ed soon...
sysfs'ing subsystems is a complex task, one which requires very careful
analysis. Don't expect ieee1394 to change overnight (or if it does,
expect your kernel to be unstable.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-04-04 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 21:54 [2.6.5] A bunch of various minor bugs not fixed since 2.6.4 Marek Szuba
2004-04-04 22:12 ` Russell King [this message]
2004-04-05 23:23 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040404231219.D17113@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=scriptkiddie@wp.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox