Available at:
ftp://ftp.kernel.org/pub/linux/kernel/people/davem/zerocopy-2.4.3p3-1.diff.gz
This is basically identical to the networking in Alan's current
patches. It is only provided for people who want the zerocopy
stuff but for some reason don't feel like getting all the other
changes in A
Andre Hedrick writes:
>On Thu, 15 Mar 2001, CODEZ wrote:
>> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
>> I have ASUS 440BX/F mb with intel PIIX4 chipset..
>
>All of the 440*X Chipsets using a PIIX4/PIIX4AB/PIIX4EB are broken beyond
>repair.
Well, that may be so; but I get t
I've performed a test on the routing capacity of a Linux 2.4.2 box versus a
FreeBSD 4.2 box. I used two Pentium Pro 200Mhz computers with 64Mb memory,
and two DEC 100Mbit ethernet cards. I used a Smartbits test-tool to measure
the packet throughput and the packet size was set to 64 bytes. Linux dr
On Mon, Mar 12, 2001 at 03:56:20PM +0100, Trond Myklebust wrote:
> > " " == Chris Jensen <[EMAIL PROTECTED]> writes:
>
> >> Details please, the minimum info required being 'which kernel
> >> is your client running'?
> >>
>
> > Oh yeah, whoops, sorry The server is a 586 and t
>But wouldn't falling back to dummycon prevent the driver specific
>suspend/resume calls from working? Or at a minimum, make handling those
>calls more complex?
Not if suspend/resume are handled on the fbdev driver level. Dummycon
would only shutdown fbcon on explict open of /dev/fb. Also note
>>I'd go for a fallback to dummycon. It's of no use to waste power on
>>creating graphical images of the text console when asleep. And the
>>fallback to dummycon is needed anyway while a fbdev is opened (in
>>2.5.x).
>
>We do already have the backup image since we need to backup & restore the
>fr
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 wai
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? Ther
>>So the fbdev drivers would register PM with fbcon, not PCI, correct?
>
>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
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 o
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 mak
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 r
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 O_D
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 u
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 c
Instead of putting arch-specific ifdefs in drivers, would it be
reasonable to add a per-arch flag UNALIGNED_PROFITABLE? Arch-specific
ifdefs all over the default rx_copybreak values in net drivers are the
example I have in mind, but it seems like it would be good knowledge
that can be easily expo
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. [...]
> 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 is that we were detect
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 PIIX4
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
tha
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
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 sp
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 PCM
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
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
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 devel
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 unless
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. grumbles for Bryce.
You are lucky that you have to burned the mainb
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, th
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 ac
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, in
-- 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
Micio
[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 shoul
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
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.
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
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'
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.
OK, so path_walk() gives us (
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
>
David Kleikamp writes:
> 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
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 jdorse01
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 ru
[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
> 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 repor
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
[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 tha
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.
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 t
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
On Wed, Mar 14, 2001 at 02:11:57PM -0500, Lars Kellogg-Stedman wrote:
> > Put LABEL= 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
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
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 p
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 a
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 utilities
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
> >
On Wed, 14 Mar 2001, Lars Kellogg-Stedman wrote:
> > Put LABEL= 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 no
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() w
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
co
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 e
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 --ver
Lars writes:
> > Put LABEL= 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 yo
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/applicati
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.
A
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
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
> Put LABEL= 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 yourself from the problems
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 DL3
On Wed, 14 Mar 2001, Christoph Hellwig wrote:
> Put LABEL= 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 remember from the last ro
> I have a problem with the 2.4 series kernel running on a number of
> Compaq ProLiant DL360 servers. The 2.2.x kernels and 2.4.0 work fine,
> however from 2.4.1 onwards the boxes just hang at the following position
> on bootup:
> Partition check:
> ida/c0d0:
> I have also tested with 2.4.2-a
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
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
> dev
On Tuesday, March 13, 2001 08:24:55 PM +0100 "Manfred H. Winter"
<[EMAIL PROTECTED]> wrote:
> Hi!
>
> A few minutes ago, my system crashed on Linux 2.4.3-pre2. I attach the
> log of the crash and what ksymoops says about it.
Hmm, oops looks bogus, and the trace in the log file has some symbo
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 n
> -Ursprüngliche Nachricht-
> Von: Tim Wright [mailto:[EMAIL PROTECTED]]
> Gesendet: Mittwoch, 14. März 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.
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 imp
On Sun, Mar 11, 2001 at 09:03:09PM -0800, Greg KH wrote:
> On Sun, Mar 11, 2001 at 06:06:24PM +0100, Martin Bruchanov wrote:
> >
> > Bug report from Martin Bruchanov ([EMAIL PROTECTED], [EMAIL PROTECTED])
> >
> >
> > [1
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
I have a problem with the 2.4 series kernel running on a number of
Compaq ProLiant DL360 servers. The 2.2.x kernels and 2.4.0 work fine,
however from 2.4.1 onwards the boxes just hang at the following position
on bootup:
Partition check:
ida/c0d0:
I have also tested with 2.4.2-ac20 and the sa
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 (
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 infomatio
Hi Andries.
>> -o util-linux 2.10o # fdformat --version
>> +o util-linux # 2.10o# fdformat --version
> 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
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 abou
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
[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
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 card
> Many systems have mount (and bsdutils) separated from util-linux
> as a binary package. Built from the same source, indeed, but...
I hope that this habit is dying. Long ago that was
reasonable, but these days (years) it only causes extra work.
>> Concerning Console Tools: maybe kbd-1.05 is uni
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
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
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 th
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 corne
On Wed, Mar 14, 2001 at 10:39:53AM +, Riley Williams wrote:
> -o util-linux 2.10o # fdformat --version
> +o util-linux # 2.10o# fdformat --version
Looking at fdformat to get the util-linux version is perhaps
not the most reliable way - some p
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. Th
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 that the machine in
question had about 40 dis
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'
David Balazic wrote:
>
> 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
> > > > ord
Hi,
I'm trying to use a bond device using two (2) ethernet NICs for two RH Linux nodes.
The link between the 2 Linux nodes is made it using 2 crossover cables for each NIC.
I did not find any additional docs for this except kernel help and something
in iputils package and probably I'm going wron
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
>> 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 since I installed it
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 o
1 - 100 of 125 matches
Mail list logo
