[EMAIL PROTECTED] (David S. Miller) writes:
Jeffrey Butler writes:
I've noticed that poll() calls on IPv4 sockets do
not behave the same under linux 2.4 vs. linux 2.2.14.
Linux 2.4 will return POLLHUP for a socket that is not
connected (and has never been connected) while Linux
2.2
Rik van Riel wrote:
On Wed, 14 Mar 2001, Martin Dalecki wrote:
Not the embedded folks!!! The server folks laugh histerically all
times they go via ssh to a trashing busy box to see what's wrong and
then they see top or ps auxe under linux never finishing they job:
That's a separate
Nathan Walp wrote:
David Balazic wrote:
Nathan Walp ([EMAIL PROTECTED]) wrote :
Also, sometime between ac7 and ac18 (spring break kept me from testing
stuff inbetween), i assume during the new aic7xxx driver merge, the
order of detection got changed, and now the ide-scsi virtual
Le 13 Mar 2001 22:58:08 -0700, Andreas Dilger a crit :
Luckily, after the symlink is created it ignores the size, and only uses
the i_blocks count to determine if the symlink is stored in the inode
itself or in another block (the fast symlink will be NUL terminated).
It could well have been
[Alan Olsen]
Alert on LAN makes the system up from power management type sleep when
there are packets to be processed. Why you would ever have sleep mode on
a server is beyond me.
No, that's Wake on LAN.
From the web page. http://www.pc.ibm.com/us/desktop/alertonlan/
Alert on LAN
Hi all.
As a result of private email correspondance I have recently received, I
became aware that the current system of identifying the versions of the
various subsystems required to support any particular kernel version is
inadequate, and decided to do something about it. The enclosed patch is
According to SysRq-P, my system gets in an infinite loop on bootup with
notifier_call_chain calling irda_device_event repeatedly.
This is triggered by toshoboe_open calling register_netdevice.
This is with everything irda-related built-in (I don't like modules); it was
working in 2.4.1-ac8.
As per my previous e-mail (on l-k), built-in irda causes an infinite loop
during bootup (ie, a lockup) by double-registering the same notifier.
This happens because irda_proto_init is both called by init/main.c and set as
a module_init() function which is then mapped to __initcall when built
On Wed, 14 Mar 2001, george anzinger wrote:
Is it REALLY necessary to prevent them from seeing an
inconsistent state? Seems to me that in the total picture (i.e.
system wide) they will never see a consistent state, so why be
concerned with a small corner of the system.
You're right. All we
On Wed, Mar 14, 2001 at 01:32:18AM -0500, Dalton Calford wrote:
I have searched the archives, hunted through the adaptec site, tried
multiple patches, compilers, revisions.
Me too...
I have a DPT/Adaptec DPT RAID V century card. This has been a topic of
much discussion in the past on
Rik van Riel wrote:
reschedule:
orl $PF_HONOUR_LOW_PRIORITY,flags(%ebx)
call SYMBOL_NAME(schedule)# test
andl $~PF_HONOUR_LOW_PRIORITY,flags(%ebx)
jmp ret_from_sys_call
Wonderful !
I think we'll want to use this, since we can use it for:
1. SCHED_IDLE
2.
I think registering fbcon as a PM client and doing the above when the
fbdev suspend/resume hooks are called should work. A memory backup is
worked on until the resume is run and the backup is restored to the
display.
So the fbdev drivers would register PM with fbcon, not PCI, correct?
Either
Anthony wrote:
Perhaps I'm blissfully unaware of all sorts of vile
race conditions, but why can't the *automounter* chase
the symlinks even if mount shouldn't? Or am I missing
a neater solution?
The automounter could indeed chase those symlinks.
Also, if the automounter creates a symlink
Hello,
I have a basic question. Can we build a PnP ISA driver in kernel
with ISAPNP kernel option enabled so that kernel PnP does the job of
allocating the resources for the driver. The problem being that the
/etc/isapnp.conf should be executed before the device driver. I tried this
On Wed, 14 Mar 2001, Benjamin Herrenschmidt wrote:
I think registering fbcon as a PM client and doing the above when the
fbdev suspend/resume hooks are called should work. A memory backup is
worked on until the resume is run and the backup is restored to the
display.
So the fbdev drivers
Mike Galbraith wrote:
If crashes are routine on this machine, I'd recommend that you take
a serious look at your ram. (or if you're overclocking, don't)
Crashes were routine, and I was not overclocking, so I took Mike's
advice and bought a new 256MB DIMM. The computer hasn't crashed
once
Hi,
Francois Groenewald noted that the RIO driver under Linux didn't
implement the TIOMGET and related IOCTLs. Attached is a patch
that fixes this.
Alan, sorry for being so late with this: I was waiting for an "yep it
works" from Francois...
Roger.
--
** [EMAIL
Using ioctl(CDROMREADAUDIO) with nframes argument being larger than 8 and
not divisible by 8 causes kernel to read and return more audio data than
was requested. This is bad since it clobbers up processes memory
(I noticed this when my patched cdparanoia segfaulted).
This _might_ also have a
Alex Baretta wrote:
[alex@localhost /home]$ free -m
total used free sharedbuffers
cached
Mem: 251209 42 60
61 92
I strongly doubt this can be a bug in the kernel. Could anyone
explain to me why this might happen?
[EMAIL PROTECTED] wrote:
Hello,
I have a basic question. Can we build a PnP ISA driver in kernel
with ISAPNP kernel option enabled so that kernel PnP does the job of
allocating the resources for the driver. The problem being that the
/etc/isapnp.conf should be executed before
On Wed, Mar 14, 2001 at 03:06:09PM +0100, Alex Baretta wrote:
Mike Galbraith wrote:
If crashes are routine on this machine, I'd recommend that you take
a serious look at your ram. (or if you're overclocking, don't)
Crashes were routine, and I was not overclocking, so I took Mike's
On Wed, 14 Mar 2001, Benjamin Herrenschmidt wrote:
Either that, or the fbdev would register with PCI (or whatever), _and_
fbcon would too independently. In that scenario, fbcon would only handle
things like disabling the cursor timer, while fbdev's would handle HW
issues. THe only problem
I have the same problem with my K7VZA board. I replaced the onboard sound
with a real card for now.
- Original Message -
From: "jens" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, March 13, 2001 10:02 PM
Subject: Sound problems with Asus K7V board using the via82cxxx drivers
Jonathan Morton wrote:
If crashes are routine on this machine, I'd recommend that you take
a serious look at your ram. (or if you're overclocking, don't)
Crashes were routine, and I was not overclocking, so I took Mike's
advice and bought a new 256MB DIMM. The computer hasn't crashed
Martin Dalecki wrote:
Jonathan Morton wrote:
The kernel itself takes up some RAM, which is simply subtracted from the
"total memory available" field in the memory summaries available to
user-mode processes. This is perfectly normal.
The kernel reserves 4m for hilself. The off by
Rik van Riel wrote:
On Wed, 14 Mar 2001, george anzinger wrote:
Is it REALLY necessary to prevent them from seeing an
inconsistent state? Seems to me that in the total picture (i.e.
system wide) they will never see a consistent state, so why be
concerned with a small corner of the
On Wed, Mar 14, 2001 at 10:36:40AM -0500, John Jasen wrote:
The problem:
[ Device name slippage ]
Possible solutions(?):
Solaris uses an /etc/path_to_inst file, to keep track of device ordering,
et al.
Maybe we should consider something similar, where a physical device to
logical
On Wed, 14 Mar 2001 [EMAIL PROTECTED] wrote:
+o Console Tools # 0.3.3# loadkeys -V
+o Mount # 2.10e# mount --version
Concerning mount: (i) the version mentioned is too old,
(ii) mount is in util-linux. Conclusion: the mount line
should be
Hi,
I'm having some problems using SCSI-generic (sg loaded as module) to
access my scanner on linux 2.4 (using SANE).
I've been using 2.2.0 - 2.2.19pre17 without any problems, but when I
changed to 2.4 the problems started. 2.4.1 gave the following entries in
my kernel log file (id 7 = scsi
[EMAIL PROTECTED] writes:
Looking at fdformat to get the util-linux version is perhaps
not the most reliable way - some people have fdformat from fd-utils or so.
Using mount --version would be better - I am not aware of any
other mount distribution.
Bad idea. RedHat has mount and util-linux in
Stephen,
Your BIOS isn't reporting any ACPI capability. If it were you would have at
least two more entries in the e820 output that say ACPI NVS and ACPI
Reclaim. Have you been able to install a MS OS and have it recognize ACPI?
Are there any other BIOS settings that might be related (what
Hi all,
The following appeared on my home box running 2.4.2-ac20. I have
X, netscape, and broadcast2000 running on it when this happened.
The system is still up, though I have the slightest idea what to
check next... any ideas?
Mar 15 00:58:25 mmj kernel: Trying to vfree() nonexistent vm area
Hi Alan,
there appears to a bug in update_vm_cache_conditional
that manifests itself only on S/390:
update_vm_cache_conditional is called with a source_address
parameter that can either be a kernel or a user space virtual
address, depending on how get_fs() is set.
update_vm_cache_conditional
-Ursprngliche Nachricht-
Von: Tim Wright [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 14. Mrz 2001 00:04
An: Hartmut Holz
Cc: [EMAIL PROTECTED]
Betreff: Re: 2.4.x: Netfinity 4500 SMP freezes without any trace
Reboot with 'nmi_watchdog=0'. That will "fix" it for now.
Still
On Wed, Mar 14, 2001 at 08:27:10AM -0800, Tim Wright wrote:
This would currently be massive overkill for Linux, but DYNIX/ptx avoids this
problem entirely by keeping a device naming database. This became necessary
when we added support for multi-path fibre-channel connected disks. Most
In article [EMAIL PROTECTED] you wrote:
The problem:
drivers change their detection schemes; and changes in the kernel can
change the order in which devices are assigned names.
For example, the DAC960(?) drivers changed their order of
detecting controllers, and I did _not_ have fun, given
On Wed, 14 Mar 2001, Christoph Hellwig wrote:
Put LABEL=label set with e2label in you fstab in place of the device name.
Christoph
P.S. UUID= work, too - but I prefer a human-readable label...
There are a lot of different devices besides disks, e.g. tape drives etc.
I seem to
Put LABEL=label set with e2label in you fstab in place of the device name.
Which is great, for filesystems that support labels. Unfortunately,
this isn't universally available -- for instance, you cannot mount
a swap partition by label or uuid, so it is not possible to completely
isolate
Marcus Meissner wrote:
Workaround: run the kernel with the 'noapic' option on its commandline.
The ServerWorks chipset used in this Compaq Server somehow does not pass
the the relevant information to Linux mapping routines. :/
I have attached lspci -xxx and dmesg output of our DL360
Christoph writes:
In article [EMAIL PROTECTED] you
wrote:
drivers change their detection schemes; and changes in the kernel can
change the order in which devices are assigned names.
For example, the DAC960(?) drivers changed their order of
detecting controllers, and I did _not_ have
From: Riley Williams [EMAIL PROTECTED]
[Yes, I wrote, replying to your mail, just because I happened
to notice the incorrect or debatable lines in your patch.
Let me cc the Changes maintainer - maybe Chris Ricker.]
-o util-linux 2.10o # fdformat
Lars writes:
Put LABEL=label set with e2label in you fstab in place of the device name.
Which is great, for filesystems that support labels. Unfortunately,
this isn't universally available -- for instance, you cannot mount
a swap partition by label or uuid, so it is not possible to
Hey kernel developers,
I'm getting repeated oopses and occasional freezes on a server I've
set up to host a giant (180G) reiserfs system atop lvm, served by nfs(v2).
(I've applied the reiserfs and nfs patches to the vanilla kernel,
which is otherwise pretty minimally compiled). They seem to be
On Wed, 14 Mar 2001, Lars Kellogg-Stedman wrote:
Put LABEL=label set with e2label in you fstab in place of the device name.
Which is great, for filesystems that support labels. Unfortunately,
this isn't universally available -- for instance, you cannot mount
a swap partition by label or
On Mon, 12 Mar 2001, Alexander Viro wrote:
On Mon, 12 Mar 2001, Guennadi Liakhovetski wrote:
I need to collect some info on processes. One way is to read /proc
tree. But isn't there a system call (ioctl) for this? And what are those
Occam's Razor. Why invent new syscall when read() works?
On Wed, 14 Mar 2001, Szabolcs Szakacsits wrote:
On Mon, 12 Mar 2001, Alexander Viro wrote:
On Mon, 12 Mar 2001, Guennadi Liakhovetski wrote:
I need to collect some info on processes. One way is to read /proc
tree. But isn't there a system call (ioctl) for this? And what are those
On Wed, 14 Mar 2001, Jamie Lokier wrote:
2. load control, when the VM starts thrashing we can just
suspend a few processes to make sure the system as a
whole won't thrash to death
Surely it would be easier, and more appropriate, to make the
processes sleep when they next page
On Wed, Mar 14, 2001 at 02:11:57PM -0500, Lars Kellogg-Stedman wrote:
Put LABEL=label set with e2label in you fstab in place of the device name.
Which is great, for filesystems that support labels. Unfortunately,
this isn't universally available -- for instance, you cannot mount
a swap
On Wed, 14 Mar 2001, Christoph Hellwig wrote:
In article [EMAIL PROTECTED] you
wrote:
The problem:
drivers change their detection schemes; and changes in the kernel can
change the order in which devices are assigned names.
For example, the DAC960(?) drivers changed their order of
On Wed, 14 Mar 2001, Alexander Viro wrote:
On Wed, 14 Mar 2001, Szabolcs Szakacsits wrote:
read() doesn't really work for this purpose, it blocks way too many
times to be very annoying. When finally data arrives it's useless.
Huh? Take code of your non-blocking syscall. Make it -read() for
[EMAIL PROTECTED] wrote:
I'm having some problems using SCSI-generic (sg loaded as module) to
access my scanner on linux 2.4 (using SANE).
[snip output showing timeouts]
This is most likely caused by a bug in SANE 1.0.3 and
1.0.4 which sets timeouts on commands to 10 seconds
rather than
On Wed, 14 Mar 2001, Szabolcs Szakacsits wrote:
On Wed, 14 Mar 2001, Alexander Viro wrote:
On Wed, 14 Mar 2001, Szabolcs Szakacsits wrote:
read() doesn't really work for this purpose, it blocks way too many
times to be very annoying. When finally data arrives it's useless.
Huh?
Hello LKML!
i686 2.4.2 UP+kdb+lm_sensors+pcmcia
after APM laptop suspend to disk
8139too is build-in, not pcmcia
I often get hangups after suspend-to-disk if I'm connected to a
hub/switch.
This is the first oops I've actually seen and copied it by hand:
I remember a similar bug report.
[I am not subscribed at the moment (don't ask :), so please cc me.]
A few months ago there was a brief discussion about the FastTrak100 card
and the driver that Promise provides, and just what all can (technically)
be done. It eventually became a debate about what may (legally) be done
with the
What version of Solaris should the poll() call behave
like? I tried the test program that I posted in the
original post on this thread on a couple of versions
of Solaris, and they all behaved like Linux 2.2, not
Linux 2.4.
The following version strings are from sysinfo on the
Solaris machines
Hello!
True, this behavior was changed from 2.2.x. We now match the behavior
of other svr4 systems, in particular Solaris.
Damn, we did not test behaviour on absolutely new clean never
connected socket... Solaris really may return 0 on it.
However, looking from other hand the issue looks as
On 14 Mar 2001 14:39:57 +0100, Geert Uytterhoeven wrote:
On Wed, 14 Mar 2001, Benjamin Herrenschmidt wrote:
I think registering fbcon as a PM client and doing the above when the
fbdev suspend/resume hooks are called should work. A memory backup is
worked on until the resume is run and the
The abyss driver will not load on 2.4.2 or 2.4.3-pre4, or 2.4.2-ac20,
however it works fine in 2.4.1
Mar 14 13:48:40 jdorse01 kernel: tms380tr.c: v1.08 14/01/2001 by Christoph
Goos, Adam Fritzler
Mar 14 13:48:40 jdorse01 kernel: abyss.c: v1.02 23/11/2000 by Adam
Fritzler
Mar 14 13:48:40
IBM says, as quoted by Terje Malmedal:
With the latest release, Alert on LAN 2 now extends IT
capabilities to remotely manage and control their
networked PCs:
Remote system reboot upon report of a critical failure
Repair Operating System
Update BIOS image
On Mon, 12 Mar 2001, Keith Owens wrote:
On Mon, 12 Mar 2001 03:53:07 -0500,
"Eric S. Raymond" [EMAIL PROTECTED] wrote:
But if we're going to push Linus and the kernel crew to switch to
CML2, then why invite the political tsuris of trying to get a large
patch into 2.4 now? Maybe I'm missing
On Wed, 14 Mar 2001, Petr Vandrovec wrote:
Hey, it is reproducible:
mount -t vfat /dev/hda1 /dos/c
mount --bind / /xxx
echo "a" /xxx/dos/c
and it stops here... ^C does not work. umount /dos/c fixes it
(creat() returns EISDIR)
Very interesting. thinks
OK, so path_walk() gives us
Hi Alan, Linus,
could you please apply Marty's patch for the next pre-kernel ?
thanks,
Rik
-- Forwarded message --
Date: Wed, 14 Mar 2001 15:17:05 -0500
From: Marty Leisner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: found small type in Documentation/sysctl/vm.txt
I was
Al writes:
On Wed, 14 Mar 2001, Andreas Dilger wrote:
The AIX vgimport will not corrupt /etc/fstab with duplicate mounts, nor for
that matter with duplicate LV names (AIX has a single namespace for all LVs).
If a conflict is found with an LV name, a new name like "lv01" is used (the
LV
On Wed, 14 Mar 2001, Andreas Dilger wrote:
David Kleikamp writes:
AIX stores all of this information in the LVM, not in the filesystem.
The filesystem itself has nothing to do with importing and exporting
volume groups. Having the information stored as part of LVM's metadata
allows
Let me start with a disclaimer stating that it's been a few years since
I've worked with AIX, but this is what I believe happens.
mount itself doesn't do anything except read /etc/filesytems (AIX's
version of /etc/fstab). LVM maintains the information primarily in the
ODM (yuck). The
You write:
For the same reason that the UUID and LABEL are stored in the superblock:
you want this infomation kept with the filesystem and not anywhere else,
otherwise it will quickly get out-of-date. Wherever you mounted the
filesystem last is where it would be mounted if you import the
On Wed, 14 Mar 2001, Andreas Dilger wrote:
The AIX vgimport will not corrupt /etc/fstab with duplicate mounts, nor for
that matter with duplicate LV names (AIX has a single namespace for all LVs).
If a conflict is found with an LV name, a new name like "lv01" is used (the
LV names are not
Al writes:
On Tue, 13 Mar 2001, Andreas Dilger wrote:
On AIX, it is possible to import a volume group, and it automatically
builds /etc/fstab entries from information stored in the fs. Having the
"last mounted on" would have the mount point info, and of course LVM
would hold the
On Wed, Mar 14, 2001 at 02:32:21PM -0500, Alexander Viro wrote:
Sorry - .last.mounted in the root of filesystem, indeed.
The writing side can't be done in userland without basically making
mount(8) know about the superblock layout of each and every filesystem:
That's a wonderful reason
On Wed, Mar 14, 2001 at 10:26:50AM -0700, Andreas Dilger wrote:
Let me put it that way: I don't understand why (if it is useful at all)
it is done in the fs. Looks like a wrong level...
For the same reason that the UUID and LABEL are stored in the superblock:
you want this infomation kept
AIX stores all of this information in the LVM, not in the filesystem.
The filesystem itself has nothing to do with importing and exporting
volume groups. Having the information stored as part of LVM's metadata
allows the utilities to only deal with LVM instead of every individual
file system.
On Wed, 14 Mar 2001, Andreas Dilger wrote:
Obviously, the whole vgimport stuff is going to be in userland. The only
part that needs to go in the kernel is storing the mountpoint in the
filesystem superblock. It is _not_ OK to just put it in /.last.mounted.
Quite often a data/application
David Kleikamp writes:
AIX stores all of this information in the LVM, not in the filesystem.
The filesystem itself has nothing to do with importing and exporting
volume groups. Having the information stored as part of LVM's metadata
allows the utilities to only deal with LVM instead of
In article [EMAIL PROTECTED] you wrote:
Alert on LAN makes the system up from power management type sleep when
there are packets to be processed. Why you would ever have sleep mode on
a server is beyond me.
Most professional UPS with Network Management Cards can go a sever to sleep
mode if
On Wed, Mar 14, 2001 at 03:58:01PM -0500, Phil Edwards wrote:
[I am not subscribed at the moment (don't ask :), so please cc me.]
A few months ago there was a brief discussion about the FastTrak100 card
and the driver that Promise provides, and just what all can (technically)
be done. It
[EMAIL PROTECTED] (Bob_Tracy) writes:
Unfortunately, when I execute
echo "base=0xd800 size=0x10 type=write-combining" | /proc/mtrr
I get a 2MB region instead of the 1MB region I expected...
Oops, it got broken by the MTRR 32-bit support in 2.4.0-testX. The
patch below should fix
-- Forwarded by Robert Miciovici/Romania/ADSW/A-D on
03/15/2001 12:42 AM ---
Robert Miciovici
03/14/2001 11:11 PM
To: "ServeRAID For Linux" [EMAIL PROTECTED]
cc:
Subject: Re: IBM ServerRAID 4L firmware 4.40.03 (Document link: Robert
Marko/Dalton/Unfortunate person searching for working DPT drivers,
I too once felt your pain.
Searched far and wide, etc.
But then I stumbled upon ftp://ftp.suse.com/pub/people/mantel/next/
Which has patches for everything you could ever want, all integrated, if
you choose them to be.
Anyway,
Hi all,
I was courious, and I tried what happens if I power down my harddisk (ie
manually pull the power plug out), and then power it on again after a few
secs (put the plug back).
I do not know if the system should survive happily such an 'accident', but
it hadn't:
A few secs after the next
On Wed, Mar 14, 2001 at 08:29:53PM +0100, [EMAIL PROTECTED] wrote:
There is no other source. Some people like to repack but that
has no influence on versions.
I believe that RedHat don't build mount and util-linux from the same tree.
Maybe they do internally, but when you look at the RPMs,
Balazs
OH the funwhat do you think you are doing?
Since you have not issued a power down command nor deregisterd the device,
because I have not publish hotswap-ata yetthus you can not do this in
a pretty way.ata grumbles for Bryce.
You are lucky that you have to burned the
Got the following oops while starting quake2 (one time) and running
mpg123 (another time). It seems pretty reproduceable. Kernel version
2.4.2-ac17, motherboard is a i810 chipset eMachines
Caveat emptor, this was typed by hand, but the two oopsen, after being
entered, where identical, so
Here is the latest preemptible kernel patch. It's much cleaner and
smaller than previous versions, so I've appended it to this mail. This
patch is against 2.4.2, although it's not intended for 2.4. I'd like
comments from anyone interested in a low-latency Linux kernel solution
for the 2.5
Kernel 2.4.2 on a uniprocessor Pentium-MMX.
Kernel PCMCIA 3.1.22 is built-in.
PCMCIA 3.1.24 package is added.
Cardinfo applet was used in ejecting the network card.
Network configuration applet was not used so the network driver
must have thought that the network interface was still active.
Base
jdow wrote:
Miles, if these babies are the 32 processor monsters that UniSys
has been making recently there IS interest to get Linux on it.
But the people I know who have mentioned "interest", mostly from
a curiosity standpoint, have their hands neatly tied by Microsoft.
Ya see, the
On Wed, Mar 14, 2001 at 10:15:26AM -0800, Greg KH wrote:
[My ramblings on device naming database deleted]
This comes up a lot with regards to USB devices too. One of the
usb-serial drivers (the edgeport driver) did something like this by
looking at the topology of the USB bus and where a
Re-sending with correction to typographical error.
The version number for the modutils rpm (2.4.2-1)
matches the version number for the kernel non-rpm (2.4.2).
Sorry if the typo in my previous message might have led to
an incorrect diagnosis.
Kernel 2.4.2 on a uniprocessor Pentium-MMX.
Kernel
On Wed, Mar 14, 2001 at 05:53:16PM -0800, Tim Wright wrote:
Well, if it sounds useful, I can look into putting up the design documentation
(yes, shock, horror, there is some :-). It's pretty thorough and covers most
of the issues involved, and hence might be a good talking point, even if we
A bug report I was charged with fixing (qla2x00 driver doesn't see all luns or
sees multiple identical luns in different scenarios) was not a bug in the
qla2x00 driver. The recent changes to allow max luns in the mid layer to be
7 seems to have caused this problem. However, the proper fix is
hi
is it possible to determine the maximum number of processes at runtime?
I know about #define NR_TASKS, but that might not work if the binary is run
on a different machine than the one the program was compiled on.
PS
I'm not looking for the maximum number of processes per user. I've found
Ello folkz,
Ummm the same problem I am facing whenevr I try to mount my cdrom. I am
using kernel 2.4.2 ac-18 and yep ofcourse I am not removing my cdrom power
supply..
I tried hdparm -T and got
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
I have ASUS 440BX/F mb with intel
Hi,
The solution is not to go down the path2inst road, that is full of
its own traps. You want volume labels via a volume manager (do lvm and raid
already do this?) and/or filesystem labels (see e2fslabel). This won't solve
all of the ills associated with device instance changes, but it will
Doug Ledford wrote:
Patches welcomed. The one I sent already works on a fiber channel setup (the
qla2x00 in question is fc and so is the Clariion array it's connected to, no
detrimental side effects from scanning the box) and so I'm not inclined to add
a REPORT LUNs section to the code
Pete Zaitcev wrote:
Date: Wed, 14 Mar 2001 21:28:14 -0500
From: Doug Ledford [EMAIL PROTECTED]
A bug report I was charged with fixing (qla2x00 driver doesn't see all luns or
sees multiple identical luns in different scenarios) was not a bug in the
qla2x00 driver. [...]
The bug
fdatasync() is the same as fsync(), in linux. until fdatasync() is
implimented (ie, syncs the data only), there's no reason to define O_DSYNC.
just use:
#ifndef O_DSYNC
# define O_DSYNC O_SYNC
#endif
On Sat, Mar 10, 2001 at 01:03:57PM +0600, Denis Perchine wrote:
one small question... Will
Alexy wrote:
Damn, we did not test behaviour on absolutely new
clean never connected socket... Solaris really may
return 0 on it.
However, looking from other hand the issue looks as
absolutely academic and not related to practice in
any way.
Hi,
I'm not sure this issue is really that
Alexander Viro writes:
On Wed, 14 Mar 2001 [EMAIL PROTECTED] wrote:
+o Console Tools # 0.3.3# loadkeys -V
+o Mount # 2.10e# mount --version
Concerning mount: (i) the version mentioned is too old,
Exactly why? Mere missing features don't make for a
On Thu, 15 Mar 2001, CODEZ wrote:
Ello folkz,
Ummm the same problem I am facing whenevr I try to mount my cdrom. I am
using kernel 2.4.2 ac-18 and yep ofcourse I am not removing my cdrom power
supply..
I tried hdparm -T and got
ide_dmaproc: chipset supported ide_dma_timeout func only:
On Wed, Mar 14, 2001 at 09:35:43PM -0500, Pete Zaitcev wrote:
16384 LUNs for Fibre Channel. As you see, scanning is out of the
question. You must issue REPORT LUNs and fall back on scanning
if the device reports a check condition. I did that when I worked
Why wait for a check condition?
Bob Frey wrote:
On Wed, Mar 14, 2001 at 09:35:43PM -0500, Pete Zaitcev wrote:
16384 LUNs for Fibre Channel. As you see, scanning is out of the
question. You must issue REPORT LUNs and fall back on scanning
if the device reports a check condition. I did that when I worked
Why wait for a
1 - 100 of 228 matches
Mail list logo
