At 11:56 AM +0200 2001-05-16, Chemolli Francesco (USI) wrote:
We could do something like baptizing disks.. Fix some location
(i.e. the absolutely last sector of the disk or the partition table or
whatever) and store there some 32-bit ID
(could be a random number, a progressive number, whatever).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
However, in testing a directory with lots (~177000) of files, we get the
following oops (copied by hand, and run through ksymoops on a Red Hat box
since the Debian one segfaulted :( )
Can you describe your testing beyond using a directory with
At 4:57 PM +0200 2001-05-16, Vojtech Pavlik wrote:
On Wed, May 16, 2001 at 07:37:45AM -0700, Jonathan Lundell wrote:
At 10:02 AM +0200 2001-05-16, Vojtech Pavlik wrote:
It's also true that some buses simply don't yield up physical
locations (ISA springs to mind,
ISA is quite
Hi,
Whenever I boot (2.4.4-ac6) I get this error message if there is a zip
disk in the drive.
hdb: 98288kB, 196576 blocks, 512 sector size, hdb: 98304kB, 96/64/32 CHS,
4096 kBps, 512 sector size, 2941 rpm ide-floppy: hdb: I/O error, pc = 5a,
key = 5, asc = 24, ascq = 0
The drive seems to work
On Wed, 16 May 2001, Heinz J. Mauelshagen wrote:
Linus, Alan et al.: maybe you could think about it again and
accept one larger LVM patch. Thanks.
I'm all for it right now. I'm running LVM on practically all my
machines and would really like to have the latest bugfixes in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yesterday, Timothy A. Seufert ([EMAIL PROTECTED]) wrote:
Why not take it a step further than just devices? This is a perfect
model for supporting named forks.
Because this only works on filesystems where directories can't themselves
have
On Wed, May 16, 2001 at 05:33:12AM -0700, Jalaja Devi wrote:
Hi!
Could you please tell me how you fixed the udelay
problem. cuz, I am encountering the same problem in my
driver.
I am not a kernel expert. You should ask it on the kernel mailing
list.
Thanks for your time,
Jalaja
In
I lifted the following kernel-thread code from
../linux/drivers/net/8139too.c, just added a procedure to call.
static int gpib_thread(void *unused)
{
unsigned long timeout;
daemonize();
spin_lock_irq(current-sigmask_lock);
sigemptyset(current-blocked);
Hi HPA, Linus, Alan,
On Mon, May 14, 2001 at 12:19:34PM -0700, H. Peter Anvin wrote:
Linus Torvalds has requested a moratorium on new device number
assignments. His hope is that a new and better method for device space
handing will emerge as a result.
Alan Cox has requested that I maintain
Andrea,
I doubt that it applies against -ac and I have only very few hard disk space,
so please don't beat me I could not try... (I tried the second-to-last but
it didn't apply either)
But 2.4.3-ac7 works very fine with your older patch.
As noticed, I now solved by CONFIG_RWSEM_GENERIC_SPINLOCK=y
On 16 May 2001 15:28:03 +0200, Helge Hafting wrote:
Oystein Viggen wrote:
Quoth Helge Hafting:
This could be extended to non-raid use - i.e. use the raid autodetect
partition type for non-raid as well. The autodetect routine could
then create /dev/partitions/home,
On Wed, May 16, 2001 at 09:30:46AM -0700, Miles Lane wrote:
On 16 May 2001 15:28:03 +0200, Helge Hafting wrote:
Oystein Viggen wrote:
Quoth Helge Hafting:
This could be extended to non-raid use - i.e. use the raid autodetect
partition type for non-raid as well. The
On Tue, May 15, 2001 at 01:18:09PM -0700, Linus Torvalds wrote:
On Tue, 15 May 2001, Jonathan Lundell wrote:
Keep it informational. And NEVER EVER make it part of the design.
What about:
1 (network domain). I have two network interfaces that I connect to
two different network
Anton Altaparmakov wrote:
True, but I was under the impression that Linus' master plan was that the
two would be in entirely separate name spaces using separate cached copies
of the device blocks.
Nothing was said about the superblock at all.
-hpa
--
[EMAIL PROTECTED] at work,
On Wed, May 16, 2001 at 03:41:40PM +0200, Geert Uytterhoeven wrote:
On Tue, 15 May 2001, H . J . Lu wrote:
Here is a patch for 2.4.4. linux_logo_bw is used in hgafb.c, which
can be compiled as a module. But linux_logo_bw is not exported.
linux_logo_bw is __initdata.
How about this
At this point of the discussion I would like to point to the Device Registry
patch (http://www.tjansen.de/devreg) that already solves these problems and
offers stable device ids for the identification of devices and finding their
/dev nodes.
Does your approach solve the problem of
This may be way off, but have you flashed the BIOS to the most
current revision? This machine should work properly. How many
processors and what SR card are you using?
ps ([EMAIL PROTECTED]) [010516 03:07]:
- I'm trying to run Linux RH 7.1 on the rack-mounted
- IBM xSeries 240 with ServeRAID
On Wed, May 16, 2001 at 02:09:32PM +0200, Thomas Kotzian wrote:
From: Helge Hafting [EMAIL PROTECTED]
Partition id's seems more interesting than disk id's - we normally
mount partitions not whole disks.
RAID do this well - the raid autodetect partition stores an ID in the
last block,
So what is your solution for preventing a boot failure after disks/partitions
change ?
volume labels/UUID ?
As a sys-admin, let me add a vote for this. Having (one day) a prom monitor
program that looks at all the disks, and gives a menu of which one to boot
from would make life so nice.
I
Hallo,
I have a linux system with kernel 2.4.4-ac9 and a win2k partition with
ntfs. Since because of the new ntfs version rw support is disabled, I
wondered how much rw support is broken, why and if I could try at least.
Or maybe some help is appreciated?
Thanks a lot,
Axel Siebenwirth
-
To
On Wed, 16 May 2001, Alexander Viro wrote:
Linus, patch is the first chunk of rootfs stuff. I've tried to
get it as small as possible - all it does is addition of absolute root
on ramfs and necessary changes to mount_root/change_root/sys_pivot_root
and follow_dotdot. Real root is
[EMAIL PROTECTED] (Hacksaw) writes:
So what is your solution for preventing a boot failure after disks/partitions
change ?
volume labels/UUID ?
As a sys-admin, let me add a vote for this. Having (one day) a prom monitor
program that looks at all the disks, and gives a menu of which one
mmap is fine for a fb, but please don't remove read/write.
I can now do a screendump with cat /dev/fb/0 file,
because everything is a file.
Having
/dev/fb/0/brightness
/dev/fb/0/opengl
and so on seems to be a better approach.
One I like to name of the file system to be something else.
On Wed, 16 May 2001, Andrea Arcangeli wrote:
On Tue, May 15, 2001 at 08:33:05PM -0700, dean gaudet wrote:
apache since 1.3.15 has defined SINGLE_LISTEN_UNSERIALIZED_ACCEPT ...
That's definitely a good thing.
hmm, i'm not so sure -- 1.3.x is our stable release, and it sounds like
this
hi,
this old problem I had been faced with had been solved with 2.4.3-ac13/14,
but now with kernel 2.4.4-ac9 and all other 2.4.4-acx it came up again.
It's a Realtek 8139C chip on a AT2500 (allied telesyn or sumpin like that)
Instead the former
Apr 24 16:16:57 bello kernel: eth1: Setting
I tested 2.4.4-ac9 today on A7V133 machine. It booted up, but can't stand
any load. It will deadlock (without oops) when the network/disk system faces
any load.
There is also some new bug in VIA IDE driver. It misdetects cable as 80-w
when it's only 40-w and causes some CRC errors and speed
Yes, I have the newest BIOS and SR Firmware.
I have 2 x 1GHz CPUs and IBM PCI ServeRAID 4.71.00 ServeRAID 4L
-- Piotr Szymanek
Leah Cunningham wrote:
This may be way off, but have you flashed the BIOS to the most
current revision? This machine should work properly. How many
On Wed, May 16, 2001 at 10:25:32AM -0700, dean gaudet wrote:
On Wed, 16 May 2001, Andrea Arcangeli wrote:
On Tue, May 15, 2001 at 08:33:05PM -0700, dean gaudet wrote:
apache since 1.3.15 has defined SINGLE_LISTEN_UNSERIALIZED_ACCEPT ...
That's definitely a good thing.
hmm, i'm not
Well, if you want I can try and reproduce your issue once I have
access to this machine. It may be about a week or so. RH 7.1 has
been tested on this machine, but not with ServeRaid 4.71.
ps ([EMAIL PROTECTED]) [010516 10:29]:
- Yes, I have the newest BIOS and SR Firmware.
- I have 2 x 1GHz
Hi,
I have recently upgraded the kernel from 2.2.19 to 2.4.4 and discovered
that it assigns the /dev/sd... devices in the wrong order with respect both
to the behavior of kernel 2.2.19 and to the `scsihosts' boot option which I
specified at the boot prompt.
I have a scsi-only machine with an
Christoph Rohland wrote:
Hi Linus,
On Wed, 16 May 2001, Linus Torvalds wrote:
Looks ok, but it also feels like 2.5.x stuff to me.
Also, there's the question of whether to make ramfs just built-in,
or make _tmpfs_ built in - ramfs is certainly simpler, but tmpfs
does the same
Hi Linus,
On Wed, 16 May 2001, Linus Torvalds wrote:
Looks ok, but it also feels like 2.5.x stuff to me.
Also, there's the question of whether to make ramfs just built-in,
or make _tmpfs_ built in - ramfs is certainly simpler, but tmpfs
does the same things and you need that one for
On 16 May 2001, Christoph Rohland wrote:
cr:/speicher/src/u4ac9 $ ls -l mm/shmem.o*
-rw-r--r--1 cr users 154652 Mai 16 19:27 mm/shmem.o-tmpfs
-rw-r--r--1 cr users 180764 Mai 16 19:24 mm/shmem.o+tmpfs
cr:/speicher/src/u4ac9 $ ls -l fs/ramfs/ramfs.o
-rw-r--r--
Linus Torvalds wrote:
What the hell are you doing? Compiling with debugging or something?
I'll bet he's using a rootkit 'ls' that shows file sizes in bits.
;-)
regards,
David
--
David L. Parsley
Network Administrator, Roanoke College
If I have seen further it is by standing on ye
Hi,
while examining the makefiles of kernel-2.4.4 I noticed that the top Makefile
contains a specific reference to the aic7xxx driver which should IMHO be
referenced only by the drivers/scsi/Makefile.
This was changed post v6.1.5 of the aic7xxx driver. Apply the latest
patch for 2.4.4 from
On Wed, May 16, 2001 at 01:38:37PM +0200, Massimo Dal Zotto wrote:
Hi,
I have recently upgraded the kernel from 2.2.19 to 2.4.4 and discovered
that it assigns the /dev/sd... devices in the wrong order with respect both
to the behavior of kernel 2.2.19 and to the `scsihosts' boot option
Andrzej Krzysztofowicz writes:
OK, just correct me if I get this wrong, but this code is taking the LAST 2
characters of the device name and verifying that it is cd. Which would
mean that the standard states that /dev/ginsucd would be a CD-ROM drive?
That is why I feel a name of a
On 16 May 2001, Christoph Rohland wrote:
Why do you use ramfs? Most of it is duplicated in tmpfs and ramfs is a
minimal _example_ fs. There was some agreement that this should stay
so.
Because what I need is an absolute minimum. Heck, I don't even use
regular files (in the full variant of
Hi there,
has anyone possibly ported the /dev/poll patch from linux-scalability project
to 2.2.19 kernel ?
Thank you in advance.
Krzysztof
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Wed, 16 May 2001, Massimo Dal Zotto wrote:
Hi,
I have recently upgraded the kernel from 2.2.19 to 2.4.4 and discovered
that it assigns the /dev/sd... devices in the wrong order with respect both
to the behavior of kernel 2.2.19 and to the `scsihosts' boot option which I
specified at
Geert Uytterhoeven writes:
On Tue, 15 May 2001, Richard Gooch wrote:
Alan Cox writes:
len = readlink (/proc/self/3, buffer, buflen);
if (strcmp (buffer + len - 2, cd) != 0) {
fprintf (stderr, Not a CD-ROM! Bugger off.\n);
exit
This is the problem with all sorts of ID-based naming. In this case
the kernel could simply change the conflicting names a bit,
and leave the cleanup to the administrator. (Who probably
is around as he just inserted those disks)
NO, NO, NO, NO, NO.
The kernel, when asked to report on the
On 16 May 2001, Christoph Rohland wrote:
cr:/speicher/src/u4ac9 $ ls -l fs/ramfs/ramfs.o
-rw-r--r--1 cr users 141452 Mai 16 19:27 fs/ramfs/ramfs.o
_What_?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
(Please CC your replies to me because I am not on the list.)
Hi!
Does anyone happen to know who is responsible for the file cache and
disk management in Linux?
On different systems I have measured strange differences in
performance depending on whether I open a file with O_SYNC and
let the
On Wed, 16 May 2001, Linus Torvalds wrote:
On Wed, 16 May 2001, Alexander Viro wrote:
Linus, patch is the first chunk of rootfs stuff. I've tried to
get it as small as possible - all it does is addition of absolute root
on ramfs and necessary changes to
Hello,
eth0 locked after 20-30 seconds stress test, different setups:
- SMP with 2 CPUs and 2 3c905B Cyclone 100baseTx cards
- SMP with 1 CPU (maxcpus=1) and the same 2 cards
No eth lock problems with 2.2.19 UP
The scenario, a throughput test setup:
flood -
Hi Linus,
On Wed, 16 May 2001, Linus Torvalds wrote:
On 16 May 2001, Christoph Rohland wrote:
cr:/speicher/src/u4ac9 $ ls -l mm/shmem.o*
-rw-r--r--1 cr users 154652 Mai 16 19:27 mm/shmem.o-tmpfs
-rw-r--r--1 cr users 180764 Mai 16 19:24 mm/shmem.o+tmpfs
On Wed, 16 May 2001, Massimo Dal Zotto wrote:
Hi,
I have recently upgraded the kernel from 2.2.19 to 2.4.4 and discovered
that it assigns the /dev/sd... devices in the wrong order with respect both
to the behavior of kernel 2.2.19 and to the `scsihosts' boot option which I
Richard Gooch wrote:
Geert Uytterhoeven writes:
On Tue, 15 May 2001, Richard Gooch wrote:
Alan Cox writes:
len = readlink (/proc/self/3, buffer, buflen);
if (strcmp (buffer + len - 2, cd) != 0) {
fprintf (stderr, Not a CD-ROM! Bugger off.\n);
Hi Alan,
the fast IP checksum update in ip_decrease_ttl appears
to be broken (at least on big endian machines) since 2.2.18.
Even on little endian machines IMO the overflow is incorrect
in two cases:
0xfeff goes to 0x instead of 0x
0x goes to 0x instead of 0x0100
On big
Hi Alexander,
On Wed, 16 May 2001, Alexander Viro wrote:
Because what I need is an absolute minimum. Heck, I don't even use
regular files (in the full variant of patch, that is). They might
become useful, but I can live with mkdir() and mknod().
So what about adding shmem_mknod and
On Mon, May 07, 2001, Shane Wegner [EMAIL PROTECTED] wrote:
On Mon, May 07, 2001 at 11:02:50AM -0700, Johannes Erdfelt wrote:
On Mon, May 07, 2001, Shane Wegner [EMAIL PROTECTED] wrote:
That does indeed correct the problem. 2.2.20pre1 now works
as expected.
Hmm, that uses a VIA
Hi
I'm experiencing reproductible oopses on my stock 2.2.19 (with BadRAM
patches, though I seriously doubt thet can affect described behaviour). The
system is Slackware-current, kernel compiled from sources, on Pentium 120
with 32Mb RAM. The oops report is from mc but any process trying to read
H. Peter Anvin writes:
Richard Gooch wrote:
Argh! What I wrote in text is what I meant to say. The code didn't
match. No wonder people seemed to be missing the point. So the line of
code I actually meant was:
if (strcmp (buffer + len - 3, /cd) != 0) {
This is still a really
On Wed, May 16, 2001 at 08:25:56PM +0300, Jussi Laako wrote:
I tested 2.4.4-ac9 today on A7V133 machine. It booted up, but can't stand
any load. It will deadlock (without oops) when the network/disk system faces
any load.
There is also some new bug in VIA IDE driver. It misdetects cable as
I very often had to move disks from one platform to another, and changing ID's
on the was hard or impossible in some cases, and required in others. Being
able to find the disk by a label is a thousand times better.
Did you ever try grub?? This a gnu project, a boot-loader, with an
Richard Gooch wrote:
H. Peter Anvin writes:
Richard Gooch wrote:
Argh! What I wrote in text is what I meant to say. The code didn't
match. No wonder people seemed to be missing the point. So the line of
code I actually meant was:
if (strcmp (buffer + len - 3, /cd) != 0) {
On Wed, May 16, 2001 at 01:05:47PM -0700, James Simmons wrote:
Did you ever try grub?? This a gnu project, a boot-loader, with an embedded
shell... You can read ext2fs and select, your kernel, your root disk, your
params, etc...
Yes I have tried it. Pretty cool. The only thing is
Hello,
we are experiencing deadlocks when running the RedHat stress test
suite. The test case is basically compiling a kernel on a file
system mounted via NFS from localhost (while this is obviously not
particularly sensible, it should nevertheless work ...), while
putting memory pressure on
On Wed, May 16, 2001 at 01:05:47PM -0700, James Simmons wrote:
Did you ever try grub?? This a gnu project, a boot-loader, with an embedded
shell... You can read ext2fs and select, your kernel, your root disk, your
params, etc...
Yes I have tried it. Pretty cool. The only thing is what
Last time I checked (that was 5 minutes ago :-) )only the last two ones
were supported...
On Wed, May 16, 2001 at 01:16:50PM -0700, James Simmons wrote:
On Wed, May 16, 2001 at 01:05:47PM -0700, James Simmons wrote:
Did you ever try grub?? This a gnu project, a boot-loader, with an
On Wed, 16 May 2001, Richard Gooch wrote:
This is still a really bad idea. You don't want to tie this kind of
things to the name.
Why do you think it's a bad idea?
Well, one reason names are bad is that they don't always exist.
If you only have the fd (remember that unix notion of
As announced 3 weeks ago, we have set up external CVS write access now.
We hereby kindly invite major contributors like Andreas Dilger to join in :-)
In order to set an account up, please send your address information
(including postal, e-mail, phone and fax contacts) to me.
We reserve the
I wonder if DFI has a bios or chipset patch available and whether that would
help ?
Maybe disabling the VIA chipset support in the kernel and running generic
drivers would help ?
Play with ideas see what you find out. You might strike lucky. So far nobody
else has
-
To unsubscribe from this
Linus Torvalds writes:
On Wed, 16 May 2001, Richard Gooch wrote:
This is still a really bad idea. You don't want to tie this kind of
things to the name.
Why do you think it's a bad idea?
Well, one reason names are bad is that they don't always exist.
If you only have the
Subject says it all...
The patch is the driver portion for the Mwave applied against the 2.4.4
kernel proper..
It was a little big to send directly to the list.. So... You'll be able
to pick it up at http://www.ibm.com/linux/ltc/ shortly.. Until it goes up
there, it will be available at
I don't mean to suggest that ioctls be used to deduce device types
(except in the case of overlapping ioctl numbers, which shouldn't be
all *that* common (I hope)). I mean to suggest that the question
What device type are you? usually shouldn't even be asked!
But people need to ask it.
I tried porting a network driver from kernel2.2.x to
2.4. When i tried loading the driver, it shows the
unresolved symbols for
copy_to_user_ret
if(copy_to_user(...))
return -EFAULT
outs
Has not gone away, your includes are wrong
__bad_udelay
You
Linus, please apply the patch below (device_init as initcall).
BTW, if -pre3 didn't break the init sequence I would be very surprised -
chr_dev_init() is moved _way_ past the other device initialization stuff.
Al
diff -urN
H. Peter Anvin writes:
Richard Gooch wrote:
H. Peter Anvin writes:
Richard Gooch wrote:
Argh! What I wrote in text is what I meant to say. The code didn't
match. No wonder people seemed to be missing the point. So the line of
code I actually meant was:
if (strcmp
Can someone please confirm if my assumptions below are correct:
1) Unless someone specifically tampered with my driver's device since the OS
bootup, the mapping of the PCI base address registers to virtual memory will
remain the same (just as seen in /proc/pci, and as reflected in subj)? If
not,
Please CC replies as I'm not subscribed.
I seem to be having some problems with sound ioctl's.
I've attached a short c file that opens /dev/dsp, prints the fd, tries
to issue SNDCTL_DSP_NONBLOCK ioctl, then does the same with /dev/audio.
Both calls to ioctl for NONBLOCK yield Invalid Invalid
Richard Gooch wrote:
Because you are now, once again, tying two things that are
completely and utterly unrelated: device classification and device
name. It breaks every time someone comes out with a new device
which is kind of like an old device, but not really, like
CD-writers
Khachaturov, Vassilii wrote:
Can someone please confirm if my assumptions below are correct:
1) Unless someone specifically tampered with my driver's device since the OS
bootup, the mapping of the PCI base address registers to virtual memory will
remain the same (just as seen in /proc/pci,
Michael Meissner writes:
On Tue, May 15, 2001 at 01:18:09PM -0700, Linus Torvalds wrote:
This is what we have now. Network devices are called eth0..N, and nobody
is complaining about the fact that the numbering is basically random. It
is _repeatable_ as long as you don't change your
I'm getting messages saying clock timer configuration lost - probably
a VIA686a from 2.2.19 running on a board using the Serverworks HE
chipset. Reading the list archives it sounds like this problem has
previously been attributed to a possible bug in the VIA chipset.
According to RedHat's
On Wed, May 16, 2001 at 02:36:44PM -0700, H. Peter Anvin wrote:
But all devices which export a CD-ROM interface will do so. So the
device node that is associated with the CD-ROM driver will export
CD-ROM semantics, and the trailing name will be /cd.
Other interfaces a device exports,
Ingo Oeser wrote:
We do this already with ide-scsi. A device is visible as /dev/hda
and /dev/sda at the same time. Or think IDE-CDRW: /dev/hda,
/dev/sr0 and /dev/sg0.
All at the same time.
... and if you don't know about this funny aliasing, you get screwed.
This is BAD DESIGN, once
Jeff,
Many thanks for the clarifications.
From: Jeff Garzik
Khachaturov, Vassilii wrote:
[snip]
bootup, the mapping of the PCI base address registers to
virtual memory will
remain the same (just as seen in /proc/pci, and as
reflected in subj)? If
not, is there a way to freeze it for
Followup to: [EMAIL PROTECTED]
By author:Alexander Viro [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Well, since all I actually use in the full variant of patch is sys_mknod(),
sys_chdir() and sys_mkdir()... IMO tmpfs is an overkill here. Maybe we
really need minimal rootfs in the
On Wed, May 16 2001, H. Peter Anvin wrote:
Ingo Oeser wrote:
We do this already with ide-scsi. A device is visible as /dev/hda
and /dev/sda at the same time. Or think IDE-CDRW: /dev/hda,
/dev/sr0 and /dev/sg0.
All at the same time.
... and if you don't know about this funny
The attatched file is the format for reporting bugs.
1) While playing mp3's on mpg123 it'll lock up for 3/4 seconds, and XMMS just stops
all together
2) May 16 05:46:10 virii kernel: cmpci: dma timed out??
May 16 06:05:43 virii kernel: cmpci: write: chip lockup? dmasz 65536 fragsz 1024
Four adapters need to produce data to a
descriptor queue which is consumed by a
user process. A lock mechanism was implemented
to sync the adapters. However, this causes
a performance hit. Is it possible to use
CMPXCHG on Intel's i-386 to avoid the locking?
Where can I find some doc and some
On Wed, 16 May 2001, virii wrote:
The attatched file is the format for reporting bugs.
Too bad my mailreader doesn't quote that thing .. oh well, lets
just replace your bugreport with mine ;)
I'm seeing a similar thing on 2.4.4-pre[23], but in a far less
serious way. Using xmms the music
At 5:37 PM -0400 2001-05-16, Jeff Garzik wrote:
This is not a safe assumption, because the OS may reprogram the PCI BARs
at certain times. The rule is: ALWAYS read from dev-resource[] unless
you are a bus driver (PCI bridges, for example, need to assign
resources).
Would you please elaborate?
H. Peter Anvin writes:
Ingo Oeser wrote:
We do this already with ide-scsi. A device is visible as /dev/hda
and /dev/sda at the same time. Or think IDE-CDRW: /dev/hda,
/dev/sr0 and /dev/sg0.
All at the same time.
... and if you don't know about this funny aliasing, you get
On 16 May 2001, H. Peter Anvin wrote:
Followup to: [EMAIL PROTECTED]
By author:Alexander Viro [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Well, since all I actually use in the full variant of patch is sys_mknod(),
sys_chdir() and sys_mkdir()... IMO tmpfs is an overkill
Hello people,
I triggered an invalid operand oops in linux-2.4.4-ac9 today, and could
trace it back to the line mm/slab.c:1244. I did nothing really special
when this happened, and I was not able to log in onto any console or
terminal afterwards (probably because tty_open failed very miserably
Jonathan Lundell wrote:
At 5:37 PM -0400 2001-05-16, Jeff Garzik wrote:
This is not a safe assumption, because the OS may reprogram the PCI BARs
at certain times. The rule is: ALWAYS read from dev-resource[] unless
you are a bus driver (PCI bridges, for example, need to assign
Woopsthis is for 2.4.5-pre2
I guessed - its ok by default in -ac because I do a test build with everything
I can build built as modules
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Alexander Viro wrote:
In full variant of patch I don't _have_ mount_root(9). It's done by
mount(2). Period. Initrd or not. Notice that rootfs stays absolute root
forever - it's much more convenient for fs/super.c, since you can get rid
of many kludges that way. So I'm not too happy about
May 13 14:24:41 sunny kernel: PCI: Found IRQ 10 for device 00:0e.0
May 13 14:24:41 sunny kernel: PCI: The same IRQ used for device 00:0a.0
0e is my PCI sound card, and 0a is my PCI ethernet card. The messages apppear in
the following environment: I send from another linux
Richard Gooch wrote:
H. Peter Anvin writes:
Ingo Oeser wrote:
We do this already with ide-scsi. A device is visible as /dev/hda
and /dev/sda at the same time. Or think IDE-CDRW: /dev/hda,
/dev/sr0 and /dev/sg0.
All at the same time.
... and if you don't know about
Are FireWire (and USB) disks always detected in the same order? Or does it
behave like ADB, where you never know which mouse/keyboard is which
mouse/keyboard?
USB disks are required (haha etc) to have serial numbers. Firewire similarly
has unique disk identifiers.
-
To unsubscribe from
On Wed, 16 May 2001, H. Peter Anvin wrote:
Alexander Viro wrote:
In full variant of patch I don't _have_ mount_root(9). It's done by
mount(2). Period. Initrd or not. Notice that rootfs stays absolute root
forever - it's much more convenient for fs/super.c, since you can get rid
of
One else case in wd7000.c did not have a release_region().
Most of these are fixed in -ac and have been for a while. Im not sure if this
one is but do double check the -ac patches for these. I've yet to have
Linus bandwidth to feed them all on
-
To unsubscribe from this list: send the line
hm, page 0009f000 reserved twice.
hm, page 000a reserved twice.
WARNING: MP table in the EBDA can be UNSAFE
These are ok...
ENABLING IO-APIC IRQs
...changing IO-APIC physical APIC ID to 14 ... ok.
BIOS bug, IO-APIC#1 ID is 15 in the MPC table!...
... fixing up to 15. (tell your hw
Alan Cox wrote:
Are FireWire (and USB) disks always detected in the same order? Or does it
behave like ADB, where you never know which mouse/keyboard is which
mouse/keyboard?
USB disks are required (haha etc) to have serial numbers. Firewire similarly
has unique disk identifiers.
I have tcl/tk8.3.2 installed and make xconfig (for both 2.2.18 and 2.4.2)
just hang. I've been told by the listed maintainer that a new GUI is on its
way and the existing make xconfig is orphaned, but this does not solve the
immediate problem.
I have therefore fixed this problem myself and
Richard Gooch wrote:
Erm, let's start again. My central point is that you can use devfs
names to reliably figure out what kind of device a FD is, as a cleaner
alternative to comparing major numbers. Therefore, I'm challenging the
notion that you need to reserve magic major numbers in order
301 - 400 of 448 matches
Mail list logo
