Shouldn't there be a sigclose() and other operations to make the API
orthogonal. sigopen() should be selective about the signals it allows
as argument. Try and make sigopen() thread specific, so that if one
thread does a sigopen(), it does not imply it will do all the signal
handling for all the
Tim Timmerman wrote:
>
> > "kees" == kees <[EMAIL PROTECTED]> writes:
>
> kees> Hi,
>
> kees> I tried 2.4.5 but after a couple of hours I lost all network
> kees> connectivety. The log shows:
>
> Can I just add a me too here ?
>
> System: Abit BP6, Dual Celeron,
> "kees" == kees <[EMAIL PROTECTED]> writes:
kees> Hi,
kees> I tried 2.4.5 but after a couple of hours I lost all network
kees> connectivety. The log shows:
Can I just add a me too here ?
System: Abit BP6, Dual Celeron, Ne2k-pci, usb ohci and
scanner; 128 Mb Ram,
ÃÖ½ÅÇüPC
CPU¡¦¡¦¡¦.933 (ÀÎÅÚ)
RAM¡¦¡¦¡¦128 (»ï¼ºÁ¤Ç°133)
HDD¡¦¡¦¡¦30 G
MONITER.17"(»ï¼º77E)
¸ðµÎ43¸¸¿ø
°ü½ÉÀÖÀ¸¼¼¿ä
http://comzon.atozpia.com/news/news.html
À̸®·Î ¿À¼¼¿ä
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Mohammad A. Haque wrote:
>Why do this in the kernel when it's available in userspace?
Because the userspace implementations aren't equivalent.
In particular, it is not so easy for them to enforce the following
restriction:
(*) If a non-root user requested the chroot, then setuid/setgid
hi all
I have in a confusion regarding the creation of
processes by the kernel. Let I have two processes P1 and P2, both are childs
of P0. I want to know the following facts regarding P1 and P2. I have created
two processes by forking. Everyone knows that when P1 and P2
Hello all,
I've been looking through the sound drivers in the 2.4.5-ac series
.
drivers/sound/soundcard.c has a few lock_kernel()/unlock_kernel() calls,
esp. in the read() and write() functions. Could these calls be easily
replaced with semaphores or spinlock calls? I vaguely remember
Albert D. Cahalan wrote:
>
> Normal users can use an environment provided for them.
>
> While trying to figure out why the "heyu" program would not
> work on a Red Hat box, I did just this. As root I set up all
> the device files needed, along Debian libraries and the heyu
> executable itself.
--On Tuesday, June 26, 2001 05:54:37 -0700 Dan Kegel <[EMAIL PROTECTED]> wrote:
> Once upon a time a hacker named Xman
> wrote a library that used aio, and decided
> to use sigtimedwait() to pick up completion
> notifications. It worked well, and his I/O
> was blazing fast (since was using a
David T Eger wrote:
> when I read documentation (Documentation/pci.txt) which mentions that
> remove() can be called from interrupt context.
ignore that. You can sleep in remove, and it will not be called from
interrupt context.
> Reading code in my sister frame buffer devices, I see that
>
> I personally don't feel that the cache should be allowed to grow over
> 50% of the system's memory at all, we've got so much in the cache at
> that point, that we're probably not hitting it all that much.
That depends very much on what you're using the system for. Suppose you're
running a
I'm not on this list, followups set to my email address.
Trying to compile 2.4.5 with gcc-3.0 gives me this:
,
| gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall \
| -Wstrict-prototypes -O2 -fomit-frame-pointer \
| -fno-strict-aliasing -pipe \
| -mpreferred-stack-boundary=2
H. Peter Anvin writes:
> [somebody]
>> Have you ever wondered why normal users are not allowed to chroot?
>>
>> I have. The reasons I can figure out are:
>>
>> * Changing root makes it trivial to trick suid/sgid binaries to do
>> nasty things.
>>
>> * If root calls chroot and changes uid, he
So I'm writing some code for a PCI card that is a framebuffer device, and
happily filling in the functions for the probe() and remove() functions
when I read documentation (Documentation/pci.txt) which mentions that
remove() can be called from interrupt context.
Now in order to properly tear
After sending util-linux out, I booted a kernel that had kdev_t
a pointer type, to see whether that still works.
And all (minus md/lvm/nfs that didnt compile) was fine
except that kswapd produced an oops. Investigation shows
that it was caused by the combination of what calls
"Ugly ugly ugly
>
>You need to be root to do mknod. You need to do mknod to create /dev/zero.
>You need /dev/zero to get anywhere near the normal behaviour of the system.
>
Sure, but we're not necessarily looking for a system that behaves
normally in all aspects. The example given was that of a paranoid
I like the assurances that the PowerPC is a "capable" processor. Perhaps
even adequate. Perhaps we should note that Dave has yet to take me up on
my challenge to the sparc to sissy-slap the PowerPC...
} +++ /tmp/Configure.help Tue Jun 26 10:36:21 2001
} @@ -171,7 +171,7 @@
} Power PC
Rob Landley wrote:
>
> On Monday 25 June 2001 11:13, you wrote:
>
> > 1937 claude shannon A Symbolic Analysis of Relay and Switching Circuits,"
> >
> > 1948 claude shannon A mathematical theory of information.
> >
> > without those you're kind in trouble on the computing front...
>
> Yeah, I
On Tue, 26 Jun 2001, Paul Menage wrote:
> But only root can set this up, since you currently have to be root in
> order to chroot(). The (only) advantage of the user chroot() patch would
> be that users would be able to do the same thing without root
> intervention.
You need to be root to do
In mailing-lists.linux-kernel, you wrote:
> I have discovered that while running 2.4.6pre5, the kernel does not
> see all available RAM - I have 1GB and the kernel only sees ~899MB.
The 1GB memory option in the kernel configuration is really the 896MB
memory option. So for more than 896MB, you
On Tuesday 26 June 2001 12:15, Daniel Phillips wrote:
> On Tuesday 26 June 2001 17:15, Joel Jaeggli wrote:
> > On Tue, 26 Jun 2001, Jocelyn Mayer wrote:
> >
> > you get DR-DOS = Digital Research DOS, then you get Novell DOS, then
> > you get Caldera OpenDOS, currently opendos is owned by lineo
>
>Paul Menage wrote:
>> This could be regarded as the wrong way to solve such a problem, but
>> this kind of bug seems to be occurring often enough on BugTraq that it
>> might be useful if you don't have the resources to do a full security
>> audit on your program (or if the source to some of your
On Tuesday 26 June 2001 08:57, Patrick O'Callaghan wrote:
> Ah, fame at last :-)
You seem to have been inexplicably excluded from "a quarter century of unix"
by peter salus. (You're not in the index, anyway.) Haven't read "life with
unix" yet...
> I'm not on the linux-kernel list but a
On Tuesday 26 June 2001 11:09, Jonathan Lundell wrote:
> >account of the speech didn't mention it. The Fehrenbachers give the
> >old-timers' recollections a D. The evidence, the scholars say,
> >"suggests that this is a case of reminiscence echoing folklore or
> >fiction."
I don't feel NEARLY
Paul Menage wrote:
> This could be regarded as the wrong way to solve such a problem, but
> this kind of bug seems to be occurring often enough on BugTraq that it
> might be useful if you don't have the resources to do a full security
> audit on your program (or if the source to some of your
SUMMARY:
The bad network behavior was due to shared irqs somehow screwing
things up. This explained most but not all of the problems.
DETAILS:
Many people emailed me that they were experiencing similar problems.
Even though the cause of my problem is not kernel related, I'm hoping
my
It is not rocket science to populate a chroot environment with enough
files to make many interesting applications work. Don't expect a general
solution---chroot is not a silver bullet---but it is useful. (Note also
that whether you can populate a chroot environment sufficiently is roughly
Paul Menage wrote:
>It could potentially be useful for a network daemon (e.g. a simplified
>anonymous FTP server) that wanted to be absolutely sure that neither it
>nor any of its libraries were being tricked into following a bogus
>symlink, or a "/../" in a passed filename. After
Hello Marcelo,
This is follow-up to the mail in February. You may perhaps forget the
context, it's the bug of MM about cache flushing for swapped-in-pages.
I see this bug on SuperH port (SH-4).
I think that we have this issue on the machine whose flush_dcache_page()
is defined. In current
H. Peter Anvin wrote:
>By author:Jorgen Cederlof <[EMAIL PROTECTED]>
>> If we only allow user chroots for processes that have never been
>> chrooted before, and if the suid/sgid bits won't have any effect under
>> the new root, it should be perfectly safe to allow any user to chroot.
>
>Safe,
Followup to: <[EMAIL PROTECTED]>
By author:Paul Menage <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> It could potentially be useful for a network daemon (e.g. a simplified
> anonymous FTP server) that wanted to be absolutely sure that neither it
> nor any of its libraries were
On Tue, Jun 26, 2001 at 08:43:33PM -0400, Dan Maas wrote:
> (hrm, maybe I could hack up my own manual read-ahead/drop-behind with mmap()
> and memory locking...)
Just to argue portability for a moment (portability on the expected
results, that is, vs APIs).
Would this technique work across a
> Windows NT/2000 has flags that can be for each CreateFile operation
> ("open" in Unix terms), for instance
>
> FILE_ATTRIBUTE_TEMPORARY
> FILE_FLAG_WRITE_THROUGH
> FILE_FLAG_NO_BUFFERING
> FILE_FLAG_RANDOM_ACCESS
> FILE_FLAG_SEQUENTIAL_SCAN
>
There is a BSD-originated convention for
In article <[EMAIL PROTECTED]>,
you write:
>
>Safe, perhaps, but also completely useless: there is no way the user
>can set up a functional environment inside the chroot. In other
>words, it's all pain, no gain.
>
It could potentially be useful for a network daemon (e.g. a simplified
anonymous
Interesting. . .
What country is that? What is it about the computer that won't allow it to
run things other than Windows - or is the TV just mistaken (I suspect so)?
Richard Schilling
-Original Message-
From: lk [mailto:[EMAIL PROTECTED]]
> Speaking of:
> A TV station in my country
Hi All,
I have discovered that while running 2.4.6pre5, the kernel does not see all
available RAM - I have 1GB and the kernel only sees ~899MB. The stock
Redhat 7.1 kernel sees the full 1024MB. Adding mem=1024M on boot does not
help either.
I'm running an IBM x340, dual 1GHz cpu.
Have I
On Tue, Jun 26, 2001 at 03:48:09PM -0700, Jeffrey W. Baker wrote:
> These flags would be really handy. We already have the raw device for
> sequential reading of e.g. CDROM and DVD devices.
Not going to help 99% of the applications out there.
mrc
--
Mike Castle [EMAIL PROTECTED]
Ted, could you comment on sanity checks in ext2_new_block()?
a)
if (tmp == le32_to_cpu(gdp->bg_block_bitmap) ||
tmp == le32_to_cpu(gdp->bg_inode_bitmap) ||
in_range (tmp, le32_to_cpu(gdp->bg_inode_table),
"H. Peter Anvin" wrote:
:: It's neither a bug nor undocumented.
Kenneth Johansson wrote:
: Interesting but I wonder how much this helps someone that not already know
: what it is. Should not the ls manual also contain something that explains
In fact the best info is on the stat page:
...
On Tue, Jun 26, 2001 at 12:25:32AM +0200, Daniel Phillips wrote:
> > This is only true without the COMPAT_DIR_INDEX flag. Since e2fsck _needs_
> > to know about every filesystem feature, it will (correctly) refuse to touch
> > such a system for now. You could "tune2fs -O ^FEATURE_C4 /dev/hdX"
Just released: util-linux-2.11g
* MCONFIG & configure: fix for gcc 3.0
Note that nfsmount_xdr.c may give warnings with gcc 3.0, essentially
because of defines in that use things like ntohl(*buf++)
where ntohl(x) is a macro with several occurrences of x.
* blockdev: support for the get/set
Followup to: <20010627014534.B2654@ondska>
By author:Jorgen Cederlof <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Have you ever wondered why normal users are not allowed to chroot?
>
> I have. The reasons I can figure out are:
>
> * Changing root makes it trivial to trick
On Tue, 26 Jun 2001, Robert Love wrote:
> me. I took issue with the MAINTAINERS file when Eric brought it up
> originally. However, I don't think drastic measures need to be taken.
> I have seen a lot of ideas, including Meta-data in the kernel source.
>
> What I think we need is the simple
Hi,
Have you ever wondered why normal users are not allowed to chroot?
I have. The reasons I can figure out are:
* Changing root makes it trivial to trick suid/sgid binaries to do
nasty things.
* If root calls chroot and changes uid, he expects that the process
can not escape to the old
Kenneth Johansson writes:
> Do linux even support the sticky bit (t) I can't see a reason
> to use it, why would I want the file to be stored in the swap ??
It is not currently supported. Swapping out executables would
be very nice when using an NFS or CD-ROM filesystem, because
swap space is
Hi,
Is it possible to pass any local variable as an
argument in the signal handler function.Basically I
want to print the value of the local variable in the
signal handler function.
In the below program I want to print the value of a in
the timeout function(siganl handler), whenever the
Alaram
On Wed, 27 Jun 2001, Stefan Hoffmeister wrote:
> : On Tue, 26 Jun 2001 18:42:56 -0300 (BRST), Rik van Riel wrote:
>
> >On Tue, 26 Jun 2001, John Stoffel wrote:
> >
> >> Or that we're doing big sequential reads of file(s) which are
> >> larger than memory, in which case expanding the cache size
Speaking of:
A TV station in my country said that the most pirated products belong to
M$ because computers cannot work wothout the GUI M$ windows provides.
In my country about 75% percent of M$ software are illegal copies :)
> > I suppose they received some pression from M$, but if people
> Do linux even support the sticky bit (t) I can't see a reason to use it, why would I
>want the file to be stored in the swap ??
For files I think it was used in days when there was no VM, so that you could
hint the system to put frequently used executables always in memory (like vi,
sh,
Yep, me again. I've been playing around with ac17 on my old 486 machine
for a few days (it seems strange that the 486 works fine while the K6
doesn't, but I digress) and I noticed today something that made my hair
stand on end:
Jun 26 16:17:27 debian kernel: VM: Bad swap entry 0033da00
Jun 26
Greetings, and thanks for this. If I recall, there is some facility
for this in the tulip cards too, no? Can one get any benefit with
100Mbps, or is the copy too fast anyway? Is the source code for Tux
available somewhere? This is probably the best bet. It seems as
though the source for X15
On Tue, 26 Jun 2001, Ilya Konstantinov wrote:
> How can I find out the module name which handles a /dev/dsp* device
> and/or the full name of the Sound Card I'd be addressing by it?
If you use ALSA this is very simple. See:
http://www.alsa-project.org
I feel that ALSA provides a superior
: On Tue, 26 Jun 2001 18:42:56 -0300 (BRST), Rik van Riel wrote:
>On Tue, 26 Jun 2001, John Stoffel wrote:
>
>> Or that we're doing big sequential reads of file(s) which are
>> larger than memory, in which case expanding the cache size buys
>> us nothing, and can actually hurt us alot.
>
>That's
Urgh, learn something new everyday (ipcs, ipcrm). My apologies; apropos
didn't catch it on my boxes. :-(
--
Ken.
[EMAIL PROTECTED]
On Tue, Jun 26, 2001 at 02:09:16PM -0700, Ken Brownfield wrote:
| With RedHat's new Samba 2.0.10 RPM (the one to patch the latest
| vulnerability) they seem to
Interesting but I wonder how much this helps someone that not already know what it is.
Should not the ls manual also contain something that explains the meaning instead of
just the mapping from bits to symbol.
Do linux even support the sticky bit (t) I can't see a reason to use it, why would I
>On 26 Jun 2001 15:35:09 -0600, MEHTA,HIREN (A-SanJose,ex1) wrote:
>> I tried to build the 2.4.2 kernel after applying patch ac28
>> (patch-2.4.2-ac28) and it failed :-((
>>
>> When it failed it gave the following message :
>>
>> *** Install db development libraries
>>
>> I thought kernel
It does not seem to work for me like I want it to. Basically,
it seems that it always takes the entire timeout (50-80 ms in my
case), but at least the socket descriptor is SET when select returns. I want
it to return as soon as the socket is writable, which at low (56kbps)
speed on a 100bt NIC
On Tue, Jun 26, 2001 at 06:21:21PM -0300, Rik van Riel wrote:
> > * If we're getting low cache hit rates, don't flush
> > processes to swap.
> > * If we're getting good cache hit rates, flush old, idle
> > processes to swap.
>
> ... but I fail to see this one. If we get a low
On Tue, 26 Jun 2001, John Stoffel wrote:
> >> * If we're getting low cache hit rates, don't flush
> >> processes to swap.
> >> * If we're getting good cache hit rates, flush old, idle
> >> processes to swap.
>
> Rik> ... but I fail to see this one. If we get a low cache hit rate,
> Rik> couldn't
On 26 Jun 2001 15:35:09 -0600, MEHTA,HIREN (A-SanJose,ex1) wrote:
> I tried to build the 2.4.2 kernel after applying patch ac28
> (patch-2.4.2-ac28) and it failed :-((
>
> When it failed it gave the following message :
>
> *** Install db development libraries
>
> I thought kernel build should
Hi All,
I tried to build the 2.4.2 kernel after applying patch ac28
(patch-2.4.2-ac28) and it failed :-((
When it failed it gave the following message :
*** Install db development libraries
I thought kernel build should be independent of any userland libraries.
Any thoughts ?
TIA
-hiren
-
>> * If we're getting low cache hit rates, don't flush
>> processes to swap.
>> * If we're getting good cache hit rates, flush old, idle
>> processes to swap.
Rik> ... but I fail to see this one. If we get a low cache hit rate,
Rik> couldn't that just mean we allocated too little memory for the
Romain Dolbeau wrote:
> If on your console you do a 'fbset -depth 16 -rgba 5,6,5,0' followed by
> a 'fbset -depth 16 -rgba 5,5,5,1' [1], any driver using fbdev will end
That should have been 'fbgen', sorry for the momentary lapse
On Tue, Jun 26, 2001 at 11:16:27AM -0400, Rob Landley wrote:
> On Monday 25 June 2001 15:23, Kai Henningsen wrote:
>
> > The AS/400 is still going strong. It's a virtual machine based on a
> > relational database (among other things), mostly programmed in COBOL (I
> > think the C compiler has
On Tue, Jun 26, 2001 at 10:44:53AM -0400, Rob Landley wrote:
> Okay, so they're 2.4 megabyte removable cartridges? How big? Are they tapes
> or disk packs? (I.E. can you run off of them or are they just storage?) I
> know lots of early copies of unix were sent out from Bell Labs on RK05
>
On Tue, 26 Jun 2001, Jason McMullan wrote:
> If we take all the motivations from the above, and list
> them, we get:
>
> * Don't write to the (slow,packeted) devices until
> you need to free up memory for processes.
> * Never cache reads from immediate/fast devices.
>
> This happens every time you VC switch.
[snip]
> But because of the way the current console system
> is designed the colormap will always be set on VC switches.
The fix wasn't intended for VC switch, but for any change of
fb_var_screeninfo parameter. Those can happen without VC switching,
On Tue, Jun 26, 2001 at 03:51:33PM -0400, Richard B. Johnson wrote:
> I just got a bunch of messages from vger.kernel.org, sent to
> [EMAIL PROTECTED], claiming a "local configuration error"
> and some kind of a loop.
Weird... I don't recall any bounces..
Logs show *one*
With RedHat's new Samba 2.0.10 RPM (the one to patch the latest
vulnerability) they seem to have sniffed enough glue to start using SysV
IPC semaphores which apparently leak until SEM??? are reached. semget()
is returning "No space left on device", and disk/inodes/memory are all
fine.
In the get_zeroed_page()function, address = page_address(page)
1)Does address point to a contiguous block of 4KB of physical memory? i.e.can I
access the individual bytes by *address++?
2)How is page_address() function defined? I did a grep and found something like:
#define
There seems to be a bug in the mail routing again. It may be related to the
recent problem with ditto copier history outbreaks on Linux S/390 and the
infamous 'pdp-11 memory subsystem' article routing bug that plagued
comp.os.minix once.
In the meantime can people check that their mailer hasnt
> It would be nice to have it working under 2.4, so is there someplace
> that outlines some of the major things that would have changed so I can
> update the module accordingly?
Within a week or so, "Linux Device Drivers" second edition should hit the
shelves. It will also hit the net, but
At 10:44 AM -0400 2001-06-26, Rob Landley wrote:
>"A quarter century of unix" mentions RK05 cartridges several times, but never
>says much ABOUT them.
>
>Okay, so they're 2.4 megabyte removable cartridges? How big? Are they tapes
>or disk packs? (I.E. can you run off of them or are they just
On 26 Jun 2001 16:03:05 -0300, Rik van Riel wrote:
> On Tue, 26 Jun 2001, Holzrichter, Bruce wrote:
>
> > respect Eric, and all the developers work. How about starting
> > with a simple MAINTAINERS file maintainer? Someone to actively
> > follow project developers and contact info?
>
> That's
On Tue, 26 Jun 2001, Martin Wilck wrote:
> Hi,
>
> > Shhh ;-) Last time that hack was mentioned, someone wanted to _remove_
> > it. It's a very nice little hack to have around, and IKD uses it.
>
> I am not saying it should be removed. But IMO it is a legitimate (if
> not the originally
> For the color component, yes, but you can't use a memcmp
> on the 'fb_var_screeninfo', as some member of the struct
> are irrelevant to colormap switching (you don't want
> to reinstall the colormap if only the refresh rate changed,
> for instance).
But it does. If you look at the console
Hi,
this patch fixes the hard hang (no SYSRQ) on inserting
any PCMCIA ATA/IDE card (e.g. CompactFlash, Clik40 etc)
to a PCI-Cardbus bridge add-in card.
Thanks David for his valuable explanation about what happens:
ide-probe registers it's irq handler too late! After it
triggers the interrupt
On Monday 25 June 2001 16:19, [EMAIL PROTECTED] wrote:
> Hi again,
>
>
>
> some old brain-cells got excited with the "good-ol-days" and other names
> have surfaced like "Superbrain","Sirius" and "Apricot".Sirius was Victor in
> the USA. If you go done the so-called IBM compatible route then the
On Monday 25 June 2001 15:23, Kai Henningsen wrote:
> The AS/400 is still going strong. It's a virtual machine based on a
> relational database (among other things), mostly programmed in COBOL (I
> think the C compiler has sizeof(void*) == 16 or something like that, so
> you can put a database
Here's my first pass at a VM requirements document,
for the embedded, desktop, and server cases. At the end is
a summary of general rules that should take care of all of
these cases.
Bandwidth Descriptions:
immediate: RAM, on-chip cache, etc.
fast: Flash reads,
On Tue, Jun 26, 2001 at 06:59:11PM +0100, Philip Blundell wrote:
> This would be a bit bad, because it would require people to guess
> whether they might have a card that parport_serial can drive and/or
> try loading the module to see what happens.
Not necessarily. The module has a PCI device
I just got a bunch of messages from vger.kernel.org, sent to
[EMAIL PROTECTED], claiming a "local configuration error"
and some kind of a loop.
There is no configuration that has changed on that machine for
at least two years although our firewall got updated last week
to fix the ECN bug.
I
Mihai Gata wrote:
>
> Trying to use an AIC7890 SCSI controller with kernel 2.4.5 I have
> the problem reported into the attached log files. Same problems with
> kernel 2.4.3. Kernels below 2.4 doesn't even see it. In MS Windows 95
> it works without any problems. I used 3 variations of SCSI
Dear LKML,
(Please CC your replies to me, since I'm not subscribed)
How can I find out the module name which handles a /dev/dsp* device
and/or the full name of the Sound Card I'd be addressing by it?
For /dev/mixer* devices, there's a SOUND_MIXER_INFO ioctl to retrieve
the Mixer chip name, but
At 18:59 26/06/2001, Jari Ruusu wrote:
>[EMAIL PROTECTED] wrote:
> > From [EMAIL PROTECTED] Tue Jun 26 10:20:51 2001
> >
> > This patch fixes the problem. Please consider applying.
> >
> > --- linux-2.4.6-pre5/drivers/block/loop.cSat Jun 23 07:52:39 2001
> > +++
My association with VA Linux Systems (and Precision Insight before that)
ended last month. At this stage, it is unclear whether I will continue
working on the various open source 3D graphics projects (DRI, Mesa etc)
or not. My work is being transitioned to the remaining members of the
PI group
Hi -
I'm interested in multi-path IO in the linux scsi mid-layer.
Are there developers working on changes to the scsi layers/interfaces?
I've seen references about such work, but no details.
Anyone else interested in or working on multi-path IO in the mid-layer?
I've looked at the code as to
>- change parport_pc so that it doesn't request parport_serial at
> init. In this case, how will parport_serial get loaded at all?
> Perhaps with some recommended /etc/modules.conf lines (perhaps
> parport_lowlevel{1,2,3,...})?
This would be a bit bad, because it would require people to
[EMAIL PROTECTED] wrote:
> From [EMAIL PROTECTED] Tue Jun 26 10:20:51 2001
>
> This patch fixes the problem. Please consider applying.
>
> --- linux-2.4.6-pre5/drivers/block/loop.cSat Jun 23 07:52:39 2001
> +++ linux/drivers/block/loop.cTue Jun 26 09:21:47 2001
> @@
>What happens now when somebody takes over responsibility for a file
>or subsystem and the MAINTAINERS file doesn't get patched, either because
>that person forgets to send a MAINTAINERS update or Linus doesn't
>happen to take the MAINTAINERS patch for a while?
>What happens when I look at a
At 7:14 PM +0200 2001-06-26, Martin Wilck wrote:
>Hi,
>
>> Shhh ;-) Last time that hack was mentioned, someone wanted to _remove_
>> it. It's a very nice little hack to have around, and IKD uses it.
>
>I am not saying it should be removed. But IMO it is a legitimate (if
>not the originally
Hi,
I tried 2.4.5 but after a couple of hours I lost all network connectivety.
The log shows:
Jun 25 19:34:17 schoen3 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jun 25 19:34:17 schoen3 kernel: eth0: Tx timed out, lost
interrupt? TSR=0x3, ISR=0Jun 25 19:34:19 schoen3 kernel: NETDEV
> kernel 2.4.3. Kernels below 2.4 doesn't even see it. In MS Windows 95
> it works without any problems. I used 3 variations of SCSI controllers
> built upon AIC7890, so I don't think all 3 are bad. One was made for
> Compaq and two for Dell. The AIC7890 is around since a while so that's
>
Trying to use an AIC7890 SCSI controller with kernel 2.4.5 I have
the problem reported into the attached log files. Same problems with
kernel 2.4.3. Kernels below 2.4 doesn't even see it. In MS Windows 95
it works without any problems. I used 3 variations of SCSI controllers
built upon
On Tue, Jun 26, 2001 at 06:55:54PM +0200, Martin Wilck wrote:
> I (being new to kernel hacking) have yet to understand what needs
> to happen for patches to enter the main branches.
You mail them to Linus, with a cc to linux-kernel.
If he likes the patch it will be part of the next
On Sat, Jun 16, 2001 at 11:29:00PM +1000, Rusty Russell wrote:
> Hi all,
>
> http://sourceforge.net/projects/lhcs/
>
> Version 0.3 (untested) of the HotPlug CPU Patch is out, with
> ia64 and x86 support.
Here's a patch to the patch that adds /sbin/hotplug support (sorry, I
couldn't
Hi,
> Shhh ;-) Last time that hack was mentioned, someone wanted to _remove_
> it. It's a very nice little hack to have around, and IKD uses it.
I am not saying it should be removed. But IMO it is a legitimate (if
not the originally intended) use of "start" to serve as a pointer to
a memory
It's amazing what masquerades as news. It's also noteworthy that they
didn't bother to have a native speaker of English to edit the article:
An executive of another affiliated company said that he felt the passion
of IBM, which is determined to invest US$1 billion, this year alone, in
Linux.
> [go to ftp://ftp.XX.kernel.org/pub/linux/kernel/people/aeb/ or so
> and get patches 01*, 02*, ... and apply them successively to 2.4.6pre5.
> complain to [EMAIL PROTECTED] if anything is wrong]
I see, you're going for a much deeper patch. No objections whatsoever,
that's certainly a better
From: Alan Cox <[EMAIL PROTECTED]>
Subject: Re: Problems with 2.4.5ac1[78]
Date: Tue, 26 Jun 2001 16:04:22 +0100 (BST)
Message-ID: <[EMAIL PROTECTED]>
Thanks a lot, Alan ! :o)
That's it! My build-script only did a make dep _clean_ bzImage modules
modules_install.
With a make distclean before
1 - 100 of 387 matches
Mail list logo
