Hi,
Attached is a patch to make a Netmos PCI parallal port card working.
Card is a PCI card with a Netmos 9705 controller and an Atmel serial
eeprom.
Regards,
Igmar
--
--
Igmar Palsenberg
JDI Media Solutions
Jansplaats 11
6811 GB Arnhem
The Netherlands
mailto
Hi,
Wrong patch. Attached is the (hopefully) correct one. Or replace the
PCI_VENDOR_ID_NETMOS_9705 with PCI_DEVICE_ID_NETMOS_9705
Regards,
Igmar
--
--
Igmar Palsenberg
JDI Media Solutions
Jansplaats 11
6811 GB Arnhem
The Netherlands
mailto: [EMAIL PROTECTED]
PGP
Hi,
kernel 2.2.18 hates my Maxtor drive :
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: Maxtor 96147H6, 32253MB w/2048kB Cache, CHS=65531/16/63, (U)DMA
Actual (correct) parameters : CHS=119112/16/63
Looks like some short int (2 bytes) overflowing. I'll try the ide patches.
Regards,
Hi,
Just tried the ide patches for 2.2.18, and same result :((
Any patches / suggestions I can try ??
Regards,
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read t
> You have a hard destroke clipping on the drive.
> Go look at you logs.
Yep, logs indicate that..
Sven, how did you kill the clipping ??
Or in generic, how do I kill the clipping ?
Regards,
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-ke
Hi,
Forget the question on killing the drive clipping. I forgot to RTFM :)
Regards,
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Thu, 4 Jan 2001, Andre Hedrick wrote:
>
> You have a hard destroke clipping on the drive.
> Go look at you logs.
Yeah.. I removed the clipping, and the machine won't boot. It halts after
PnP init. Any way to use full capacity with the clipping enabled ?
Regards,
Ig
> I did'nt know something like that even existed :)
>
> Just plugged the drive into the ide controller (single drive on a
> promise ata100 in a dec alpha) and it worked.
Ah.. This is a i386 machine, UDMA33 capable, and the bloody thing won't
boot with the clipping removed, and with clipping I c
On Thu, 4 Jan 2001, Torrey Hoffman wrote:
> I had exactly this problem with the Maxtor 61 GB drive on my
> Pentium based server. Theoretically a BIOS upgrade could fix it,
> but ASUS quit making BIOS upgrades for my motherboard two years
> ago.
Ah well, join the club in my case :)
> I solved
> No. 2.2.* handles large drives since 2.2.14.
> This looks more like you used the jumper to clip the drive to 32GB.
> Don't use it and get full capacity.
> If your BIOS hangs when it sees such a large drive so that you
> cannot avoid using the jumper, use setmax in your boot scripts,
> or use a
> I had a similar situation except I was more interested in the performance
> difference. Went from ~4MB/s with the 430HX controller to ~12.5MB/s with
> the promise. This on an old Pentium system.
The network is 10 mbit, so 4 MB/sec is no good in this case.
I've got the thing running, with (ibm)
> > Sven, how did you kill the clipping ??
> > Or in generic, how do I kill the clipping ?
>
> Go set the jumpers right. (anyhow, IBM drives are delivered unclipped,
> not sure why Maxtors seem to be)
It's not that simple.. The maxtor comes clipped,. but Linux can't kill the
clip. So it sticks
On Sat, 6 Jan 2001, Mike wrote:
> Hi!
>
> I am getting getting "/var/log/messages" on my console. It doesn't save
> it in /var/log.
> I have checked entries in /etc/syslog.conf file. Its correct.
> Can someone help me.
Syslog isn't running
>
> Regards,
> Mike
Igmar
-
To unsubscrib
On Sat, 6 Jan 2001 [EMAIL PROTECTED] wrote:
> > It's not that simple.. The maxtor comes clipped,. but Linux can't kill the
> > clip. So it sticks with 32 MB
>
> > ibmsetmax.c does a software clip, but that bugs a bit. Sometimes even
> > Linux doesn't see 61 GB, but only 32, sometimes the full ca
On Mon, 8 Jan 2001, Chris Meadors wrote:
> On Mon, 8 Jan 2001, David S. Miller wrote:
>
> > This definitely seems like the classic "/etc/nsswitch.conf is told to
> > look for YP servers and you are not using YP", so have a look and fix
> > nsswitch.conf if this is in fact the problem.
>
> What
> > 2.2.18 sometimes sees 61 GB, sometimes 32 GB.
> > I don't call that hard to understand.
>
> The same kernel has varying behaviour?
> Maybe not hard to understand, but rather surprising.
> You are the first to report nondeterministic behaviour.
You're not the only one that is suprised :
1)
> # cat /proc/meminfo
> total:used:free: shared: buffers: cached:
> Mem: 130293760 123133952 71598080 30371840 15179776
^^
It means shared process memory, not shm.
One thing to watch : PowerTweak. Seems
On Mon, 8 Jan 2001, Scott Laird wrote:
>
> Is syslog running correctly? When syslog screws up, it very frequently
> results in this sort of problem.
Indeed, or no DNS when talking remote logins.
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
> Probably you confused the proper way to use ibmsetmax with
> the proper way to use setmax. For setmax, and a Maxtor disk,
> you do not use a different machine, put the jumper to clip,
> now the boot succeeds, and you let Linux unclip.
> Either with a patched kernel that knows about these things
On Thu, 11 Jan 2001, Nguyen Truong Sinh wrote:
> I am using Redhat 7.0 for my system. After install new kernel (2.4.0). My system
>always inform
> NET: 3 messages suppressed
>
> What does it mean ? and how to fix it, I don't want it appears on the console at all.
man syslog
messages supresse
Hi,
on plain 2.4.0 vanilla any mouse access kills the keyboard. Only way to
restore functionality is to kill gpm.
gpm writes 'protocol error' to syslog. I have access to this machine on
monday, so I can post details then.
Changing the IRQ is totally unrelated, machine works in 2.2.x with the
s
Hi,
kernel : 2.4.0 vanilla
iproute2 version : ss001007
After building I've got a few problems :
./ip rule list
RTNETLINK answers: Invalid argument
Dump terminated
Version should be OK according to the Changes file.
config is attached
Regards,
Igmar
--
--
> On Sat, Jan 13, 2001 at 05:37:01PM +0100, Igmar Palsenberg wrote:
> > Hi,
> >
> > kernel : 2.4.0 vanilla
> > iproute2 version : ss001007
> >
> > After building I've got a few problems :
> >
> > ./ip rule list
> > RTNETLINK answe
the call gives in case
MULTIPLE_TABLES isn't set. -EINVAL is ugly, -ENOSYS should make the error
more clear..
> Later,
> David S. Miller
> [EMAIL PROTECTED]
Thanx,
Igmar
--
--
Igmar Palsenberg
JDI Media Solutions
Jansplaats 11
6811 GB Arnhem
The Neth
> Igmar Palsenberg writes:
>
> > we might want to consider changing the error the call gives in case
> > MULTIPLE_TABLES isn't set. -EINVAL is ugly, -ENOSYS should make the error
> > more clear..
>
> How do I tell the difference between using the wrong syst
ut that's not
> too bad, given the work it saves. e.g. rusty's code usually has a debug option
> that you can set and where each EINVAL outputs a error message; i always found
> that very useful and sometimes hacked that into other subsystems in my
> private tree.
Still means
> People must be really suffering right now, and we ought to get
> /proc/errno_strings implemented as soon as possible... :-)
First the help describing large tables should be changed. It's wrong.
String errors don't belong in kernel space IMHO.
Igmar
--
--
Igma
> > Using textual strings means you can't use standard functions. An option
> > would be to extend the call so that if the userspace app wants to know
> > what really went wrong he can ask the kernel.
>
> That will not work. Consider an application that has multiple rtnetlink
> sockets open, whi
Hi,
2.4.0ac9 still kills the mouse on this machine. dmesg is attached.
Something I find interesting is that the PCMCIA bridge is on IRQ12.
We can't change the mouse or the PCMCIA bridges' interrupt.
I'll be happy to provide additional info.
Regards,
Igmar
Jan 16 08
On Wed, 17 Jan 2001, Rajiv Majumdar wrote:
>
>
> Sorry..the topic does not fit here. But wanted to know, how can we check
> validity of an email id "in advance"
You can't. Only think you can check is a valid domain that will in theory
accept mail, no way to check if it really dilivers.
> so t
> The underlying problem is of course that all those sanity checks should
> be done in user space, not in the kernel.
>
> (See also ftp://icaftp.epfl.ch/pub/people/almesber/slides/tmp-tc.ps.gz
> The bitching starts on slide 11, some ideas for fixing the problem on
> slide 16, but heed the warnin
> Nope stat should return the details of the symlink
> whereas lstat should return the details of the symlink target.
It's the other way around according to the manpage, and my code also says
it's the other way around.
It's logical the way it is..
I use lstat to check if a config file is a sy
On Thu, 18 Jan 2001, Mike Castle wrote:
> On Thu, Jan 18, 2001 at 09:52:02PM +0100, Igmar Palsenberg wrote:
> > I use lstat to check if a config file is a symlink, and if it is, it
> > refuses to open it.
>
> Nice race condition.
Agree, but still better then opening thing
On Wed, 15 Nov 2000, Peter Samuelson wrote:
>
> [Ian Grant]
> > In 2.2.x we were able to build a kernel with RAID modules and have it
> > autodetect RAID partitions at boot time - so we could use raid root
> > partitions.
>
> Really? Funny, because IIRC RAID autodetection does not even exist i
On Thu, 16 Nov 2000, Andreas S. Kerber wrote:
> We need to handle files which are about 10GB large.
> Is there any way to do this with Linux? Some pointers would be nice.
Install a kernel / glibc that handles LFS. Search for LFS on Freshmeat,
you'll end up with the right patch.
You'll probably
On Fri, 17 Nov 2000, M.Kiran Babu wrote:
> sir,
> i am getting some problem with graphics mode. my system is opening in text
> mode only. upto yesterday it is ok. but now it is failing to open in
> graphics mode. i am using startx, xinit and Xconfigurator all options. but
> even it is showing err
On Mon, 20 Nov 2000, Charles Turner, Ph.D. wrote:
These are hardware problems, not software. Programs like gcc and ld
segfaulting like this is NOT a software problem.
Please don't turn up with some 'hey, it worked with my disk', that's no
clue that the distrib is bad. The same arguments as 'i
Hi,
Support for some 53c400 cards is still bad (the non-PnP), so I'll start
fixing this.
I'll be my fist kernel job, so please spare me :))
Issues :
53c400a non-PNP still lock this system hard. It starts barking about a
busy SCSI bus, and then I can fsck again.
To Alan : How hard is it to ge
On Tue, 21 Nov 2000, Dunlap, Randy wrote:
> JE's UHCI driver (drivers/usb/uhci.[hc]) uses
> nested_lock() and nested_unlock() for this.
> Maybe it could help.
I may should solve the nested spinlock issue.. It however doesn't solve
the 100Kb+ pile of spaghetti the code is.
I think I'll just star
On Tue, 21 Nov 2000, Joseph Gooch wrote:
> My RaptorNT 6.5 firewall rejects all connections from my linux box when ECN
> is enabled. The error is attached. Perhaps this feature should be disabled
> by default? Or is there already an option of the sort that i'm missing? I
> only got the idea t
> -i and -m have never been in the base code. -i in depmod is a Redhat
> add on, only in their distribution. I have no idea what -m does, apart
> from -m in insmod which is supported. Blame the distributors.
-m == -F in depmod (RH anyways)
Igmar
-
To unsubscribe from this list: sen
> > #define __bad_udelay() panic("Udelay called with too large a constant")
Can't we change that to :
#error "Udelay..."
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.
On Wed, 22 Nov 2000, Daniel Stone wrote:
> Hi,
> I've been having a bit of a problem with Rik's new VM, in particular the bad
> process-killer. Basically put, I have a reasonably underpowered system
> (P166) running Helix GNOME & Sawfish, and half the time when I load my Eterm
> (admittedly, tran
> |> > > #define __bad_udelay() panic("Udelay called with too large a constant")
> |>
> |> Can't we change that to :
> |> #error "Udelay..."
>
> No.
?? I think I'm missing something here.
> Andreas.
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
> CPU0
> 0:1415829 XT-PIC timer
> 1: 10361 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 3: 70687 XT-PIC serial
> 5: 0 XT-PIC Intel ICH
> 9: 3134 XT-PIC 3c574_cs
> [snip a boring troll]
Please, don't insult my mother in law. She's not that boring ;P
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
> Indeed, you are correct. Is vpnd broken then, for assuming
> that it can gather the required randomness in one read?
Yep. It assumes that if the required randommness numbers aren't met a read
to /dev/random will block.
And it's not the only program that assumes this : I also did.
/dev/rand
> For a blocking fd, read(2) has always blocked until some data is
> available. There has never been a guarantee, for any driver, that
> a read(2) will return the full amount of bytes requested.
I know. Still leaves lot's of people that assume that reading /dev/random
will return data, or will
> "totally block"?
>
> For a blocking fd, read(2) has always blocked until some data is
> available. There has never been a guarantee, for any driver, that
> a read(2) will return the full amount of bytes requested.
Hmm.. Some came to mind :
Making /dev/random block if the amount requirements
> > I know. Still leaves lot's of people that assume that reading /dev/random
> > will return data, or will block.
> >
> > I've seen lots of programs that will assume that if we request x bytes
> > from /dev/random it will return x bytes.
>
> I find this really humorous honestly. I see a lot of
> > Making /dev/random block if the amount requirements aren't met makes sense
> > to me. If I request x bytes of random stuff, and get less, I probably
> > reread /dev/random. If it's entropy pool is exhausted it makes sense to be
> > to block.
>
> This is the job of the program accessing /dev/
> Well, that's the Unix interface you. I you don't like it, why don't you
> become a Windows programmer and try your hand at the Win32 interface? :-)
>
> Seriously, doing something different for /dev/random compared to all
> other read(2) calls is a bad idea; it will get people confused. The
> This is standard stuff... You are really pissing into the wind here ;)
Guess I am. Still isn't an explaination why I see a lot of broken code out
there regarding this issue.
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, 31 Aug 2000, Ibrahim El-Shafei wrote:
> Hi,
> When I tried to install the pcmcia-cs-3.1.19, I got a message that I
> attached it with this E-Mail, so I stopped the installation until I find the
> answer.
Date doesn't like that no timezone is set. Try setting one.
man date might be help
On Fri, 1 Sep 2000, Jim Garlick wrote:
> Can someone point me to MTBF data for Linux? I realize this is kind of
> vague. Ideally I would like MTBF for kernel 2.2.14 running on SMP Alpha,
> but any data is better than nothing. This is to help win an argument to
> put linux on a large cluster.
On Fri, 1 Sep 2000, Matthew Dharm wrote:
> I agree that the MTBF can be very misleading...
>
> But put it this way: My server ran 2.2.14 for over 400 days before I
> rebooted it. It was down for about 5 minutes while rebooting (probably
> less).
>
> My NT Server gets a nightly reboot. I can'
On Fri, 1 Sep 2000, Michael Bacarella wrote:
>
> Q: Why do we need threads?
> A: Because on some operating systems, task switches are expensive.
No. threads share variable and code memory, processes do not. And
sometimes it can make your life a lot easier. Even if you can use things
such as SHM
> ...
> Linux PCMCIA Card Services 3.1.11
> options: [pci] [cardbus] [pm]
> Yenta IRQ list 0698, PCI irq11
> ...
The PCMCIA IRQ probes can hang the system if it probes the wrong IRQ. Fix
your PCMCIA config.
> Without the next line. I don't know what's wrong on my side --
> kernel 2.2.1
> >You can not go after people for patches.
>
> Hi,
>
> >there is no GPL issue. Upon Microsoft's adpotion of the model they will
>
> of course you can. Just don't release a patch but grab the driver
> you're patching against (which is GPL), add your modifications and
> release your driver wit
Sorry for the last mail. Wrong button.
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
> But they can take the ideas and methods demonstrated by the code in the
> patch. Its not that they are going to take what he wrote and run patch
> against their code. They can take a good idea, sit a skilled programmer in a
> room and adapt the concepts without a bit of a problem.
I call this
> Ugh. What rubbish.
>
> The moment I detect my provider changing anything beyond a TTL is the
> moment I find a new provider.
The 'problem' is a bunch of stupid American politics (excuse anyone
American), than passed a law that all spam containing a remove adress is
legal.
So that means I ge
> 4.21, IIRC. Check the BUGTRAQ. Nobody had provided a full analysis, let
> alone exploit, but there was an example of headers making pine _very_
> unhappy (attempt to save the mailbox after any modifications => screwed
> mailbox). I didn't attempt to dig in the source - Mark et.al. got such a
>
On Thu, 7 Sep 2000, David Woodhouse wrote:
>
> [EMAIL PROTECTED] said:
> > Which Linux companies are profitable? **NONE**.
That's a statement with balls, which I would really see with some
numbers..
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> [root@pepsi /tmp]# su adam
> [adam@pepsi /tmp]$ touch blah
> [adam@pepsi /tmp]$ chmod -w blah
> [adam@pepsi /tmp]$ echo hi > blah
> bash2: blah: Permission denied
> [adam@pepsi /tmp]$ exit
> exit
> [root@pepsi /tmp]# echo hi > blah
> [root@pepsi /tmp]# ls -l blah
> -r--r--r--1 adam a
> Correct me if I'm wrong, but I believe that all non-TOS
> unices have behaved this way since the 70s.
I see no reason why it shouldn't behave this way. Root can do su - user
and screw up the file that way.
Users with UID 0 are capable of doing about anything possible.
Igmar
-
To un
> No, not true. The mixing into the entropy pool uses a twisted LFSR, but
> all outputs from the pool (to either /dev/random or /dev/urandom)
> filters the output through SHA-1 as a whitener. The key here, though,
> and what makes this fundamentally different from yarrow, is that since
> we're f
On Fri, 15 Sep 2000, David Ciemiewicz wrote:
> [4.] Linux version 2.2.14-5.0 ([EMAIL PROTECTED]) (gcc version
Don't report bugs with this old version.
[root@base igmar]# uname -a
Linux base.jdimedia.nl 2.2.17acl #2 Mon Sep 11 02:23:03 CEST 2000 i586
unknown
[root@base igmar]# cat /proc/tty/dri
> Igmar,
>
> Thanks for attempting to validate that the problem is fixed in a
> later release. However, I still stand by my submission.
The problem was that the kernel was overwriting a userspace buffer, used
to copy the data to. I can have a look at the code to see if it is really
fixed.
It
On Sat, 16 Sep 2000, David Ford wrote:
> There was a round of discussion about /proc.../serial back in May. It
> covered corruption and bad addresses. Although it didn't specifically say
> "I'm fixing the segmentation fault that some people are going to report",
> they did indeed discuss the ba
On Sun, 17 Sep 2000, Bruce A. Locke wrote:
>
> Hello...
>
> The organization I do some work for purchased a rackmount server from
> Dell with the intent of running some webconferencing software under
> Linux. The salesman we had spoken to assured us that Linux fully
> supported the machine.
On Sun, 17 Sep 2000 [EMAIL PROTECTED] wrote:
> hi everyone,
>
> suppose i allocate some kernel memory in a module by calling kmalloc,
> can that memory be swapped out, for example in AIX even the kernel memory
> which is allocated by rmalloc is swappable!!
No, kernel memory is not swappable.
On Sun, 17 Sep 2000 [EMAIL PROTECTED] wrote:
> The aacraid driver was submitted to Alan Cox, but rejected because it has
> too many "NTism's" in it, which are being addressed. Please see the Red Hat
> Linux "Pinstripe" beta kernel source RPM for the source code, or contact me
> privately.
In my
> reproduce the exact kernel configuration of my running 2.2.14 system
> and a 2.2.17 kernel. (It would be extremely useful to have a pointer
> to a tool which would duplicate the configs rather than going through
> the manual process of configuring the kernel build).
cp .config new_kernel_dir
> >>EIP; c01527b9<=
> Trace; c015357b
> Trace; c01363d8
> Trace; c012c1e7
> Trace; c01371a9 <__user_walk+4d/58>
> Trace; c012c23b
> Trace; c011d630
> Trace; c0108d83
> Code; c01527b9
> <_EIP>:
> Code; c01527b9<=
>0: f6 43 34 40 tes
Hi,
Patch looks not necessary. The compiler executes the statements until it
encounters a break.
> - case BTN_EXTRA: if (list->mode > 1)
>{ index = 4; break; }
> + case BTN_EXTRA: if (list->mode > 1)
Hi,
This machine is running 2.2.17aa2 (I needed LFS), and I'm able to lock it
hard. This is what was in the logs :
Sep 21 23:55:38 fs1 kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 21 23:55:38 fs1 kernel: hdc: dma_intr: error=0x40 { UncorrectableError
}, LBAsect=16373
On Fri, 22 Sep 2000, Alan Cox wrote:
> > This machine is running 2.2.17aa2 (I needed LFS), and I'm able to lock it
> > hard. This is what was in the logs :
> >
> > Sep 21 23:55:38 fs1 kernel: hdc: dma_intr: status=0x51 { DriveReady
> > SeekComplete Error }
>
> A disk seek failed
>
> > Sep 21 2
On Fri, 22 Sep 2000, Carsten Lang wrote:
> i don't think that we can blame the disks!
> I have 3 different drives, which produce this error after 24 hrs under heavy load.
This one chokes after about 10 mins. Total meltdown. Drives are brandnew,
so I doubt the failure.
If I md5sum the files aft
> This is the following problem
>
> hda: Maxtor 71626 AP, 1554MB w/128kB Cache, CHS=789/64/63, DMA
> hdb: Maxtor 91021U2, 9641MB w/512kB Cache, CHS=1229/255/63, (U)DMA
> hdc: Maxtor 91021U2, 9641MB w/512kB Cache, CHS=19590/16/63, (U)DMA
I'll put both UDMA drives on ide1 and kick it's ass again.
> Do you have stuff logged about trying to access out of range blocks ?
No. It start to bark about the DMA mode and then dies.
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://w
On Fri, 22 Sep 2000, Andries Brouwer wrote:
> On Fri, Sep 22, 2000 at 02:34:16PM +0200, Igmar Palsenberg wrote:
>
> > It could be that it is choking on the fact that one drives is LBA, one
> > drive isn't. Drives are identical, but dmesg gives different CHS for each
&
On Fri, 22 Sep 2000, Russell King wrote:
> You're telling us that:
>
> if (list->mode > 1) {
> index = 4;
> break;
> }
>
> is the same as:
>
> if (list->mode > 1)
> index = 4;
> break;
No, it isn't.. Ws confused with switch() {
>
> > Do you have stuff logged about trying to access out of range blocks ?
Putting primary to secondary slave (two UDMA devices on the same
bus) fixed the lockup.
The second drive was ginging errors in some cases, and sometimes it
didn't. Was the reason I couldn't reproduce the unrecoverable e
On Fri, 22 Sep 2000, Andre Hedrick wrote:
> On Fri, 22 Sep 2000, Andries Brouwer wrote:
>
> > Here 1.4 MB is wasted on hdb because the BIOS has invented
> > this 1229/255/63 translation. The disk access methods on
> > hdb and hdc is the same.
>
> Yes, and soon CHS will go away completely with 4
On Sun, 24 Sep 2000, MOHAMMED AZAD wrote:
> Hi all,
>
> Any one using crystal lan cs8920 adapters.??? .. mine is a cs8920
> crystal lan adapter.. as per the driver source.. driver does not support
> pnp.. and i need to disable it... after disabling pnp and giving an irq and
> i/o address the
On Thu, 19 Oct 2000, KMF AV wrote:
> First, the 2.4 kernel is years late and doesn't work
> right, and keeps getting rewritten because it's a
> festering hunk of fetid spaghetti inside.
Well, in that case shut up and write your own. Second, don't hide behind a
yahoo.com adress when making these
On 23 Oct 2000, Patrick J. LoPresti wrote:
> If you send SIGSTOP to syslogd on a Red Hat 6.2 system (glibc 2.1.3,
> kernel 2.2.x), within a few minutes you will find your entire machine
> grinds to a halt. For example, nobody can log in.
>
> This happens because once the /dev/log buffer fills,
> You obviously don't understand the communication channel being used.
> "/dev/log" is a UNIX DOMAIN SOCKET -- AF_UNIX. Datagrams are unreliable
> for _IP_ (AF_INET). Traffic on an AF_UNIX socket is always reliable.
>
> Ok, smarty, go change the syslogd source to open /dev/log as SOCK_STREAM
>
> Ulrich Drepper <[EMAIL PROTECTED]> writes:
>
> > If anything has to be changed it's (as suggested) the configuration
> > or even the implementation of syslogd. Make it robust.
>
> OK, but my current syslogd only listens to /dev/log as a SOCK_DGRAM.
> If I wanted reliable syslogging, it would
On 23 Oct 2000, Patrick J. LoPresti wrote:
> Jesse Pollard <[EMAIL PROTECTED]> writes:
>
> > Don't configure syslogd to do reverse lookups.
>
> Our syslogd has no option to disable the reverse lookups.
Requires a recompile.
> > You can NEVER guarantee that the reverse lookup will succeed, and
> No, I didn't say they "should" be dropped but merely that dropping them
> would fix your problem. Personally, I'd look closely at your setup to
> determine exactly why this has become a problem. named is being blocked
> on writing to /dev/log. This should only happen if there is sufficient
>
> Perhaps syslogd is not giving higher priority to local messages; if it
> did, maybe it could recover from the deadlock. But this would not be
> a reliable solution; the only reliable solution is for syslogd to be
> independent of any processes which need to talk to it.
In that case, don't do
On Wed, 25 Oct 2000, Anil kumar wrote:
> Hi,
> After I create a RAID setup on the drives,The
> superblock will be generated at the end of the drives.
> If I move these drives to other linux system, will
> this
> system recognise the RAID setup without reconfiguring
> the Linux ?
If the CHS / L
> This is not an option for us, unfortunately. Many of our IP addresses
> are dynamically assigned, with the DNS tables dynamically updated.
Not an option in that case.
> Thank you for the patch to syslogd, though! Can you try to get your
> "-x" option into the standard distributions of sysl
> Sadly, you WILL still lose entries if the system crashes before fs metadata
> has been flushed to disk. Unless the inode has the correct size stored, the
> crap fsync()ed to disk doesn't make much difference.
Yep. I can't really think of a case where you wouldn't lose data in case
of for exam
> Hello,
>
> For one of our projects here, we've crashed head first into the 2 gig file size
> limitation in Linux 2.2 kernels. While I know that this has been solved in
> 2.3/2.4, has there been any work to backport this feature into a Linux 2.2
> kernel? I'm looking for a temporary solution un
On Fri, 27 Oct 2000, [iso-8859-1] Jakob Østergaard wrote:
> On Fri, Oct 27, 2000 at 10:56:16AM -0700, Anil kumar wrote:
> > Hi,
> >
> > I have a problem with mkraid
>
> This is Linux-RAID specific and not material for the linux-kernel
> list.
>
> Please, just post your questions to linux-r
On Sun, 29 Oct 2000, Peter Samuelson wrote:
> [Wakko Warner]
> > While this subject is fresh, what would be wrong with using the
> > entire drive as opposed to creating a partition and adding the
> > partition to the raid?
>
> Does it autodetect an entire drive? The autodetect logic for
> parti
> > It was NOT ignored. If syslogd dies, then the system SHOULD stop, after a
>
> Huh? "SHOULD"? Why? If syslog dies for any reason (bug, DOS, hack,
> admin stupidity) then I sure don't want the system freezing up.
In some cases, I find the syslog messages of more importance then a
working
1 - 100 of 202 matches
Mail list logo
