Hi Linus,
Currently when a zero byte write is done on a regular file
opened with O_APPEND the file offset is set to the end of the
file. For POSIX compliant behaviour this shouldn't happen.
The attached patch fixes this.
Chris.
--- mm/filemap.c.orig Mon Nov 20 14:05:38 2000
+++ mm/filemap.c
Werner,
Thanks for fix. Applied the patch and it's working now.
Linus, please add this patch to the kernel source codes for 2.4.0.
Under 2.2.18, it's working fine without the patch.
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
- Original Message -
From: "Werner Almesberger" <[EMAIL PROTECTED]>
Hi, Linus!
Will you consider applying the following patchset? You will find it at
ftp://ftp.externet.hu/pub/people/zboszor/mtrr-new2.tar.gz
I know that you like plain text patches inlined in the mail
but I do not know how to get pine to inline the (plain text)
attachments...
Here is the README
On Sun, 19 Nov 2000, Linus Torvalds wrote:
> - Asit Mallick: enable the APIC in the official order
What is this intended to fix? Please revert it -- it breaks for i82489DX
APICs configured to the PIC mode upon boot -- local interrupt registers
are hardwired to 0x0001 and cannot be
It seems to me that this code in linux/drivers/char/mem.c
is a bug:
===
static ssize_t write_null(struct file * file, const char * buf,
size_t count, loff_t *ppos)
{
return count;
}
The user-mode port of 2.4.0-test11 is available.
UML is now able to run as a daemon, i.e. with no stdin/stdout/stderr.
The hostfs filesystem now works as a readonly filesystem. It's now
configurable. I'm using it as a module. It ought to work compiled into the
kernel, but I haven't checked
Michael Rothwell write:
> I'm looking for documentation on Ext2's support for sparse superblocks.
> What it the method uses to reduce the number of superblocks? How are
> they laid out before vs after sparse_super is enabled? Any caveats?
In an old-style (non-sparse) filesystem, every block
Hi David,
Yup, I know rpc.portmap isn't running, the point is that it wasn't running on either
2.2.17 or 2.4.X. Isn't run level 1 supposed to only be the bare minimum of running
processes, a few kernel processes, init and getty. No network services...
What's changed in the kernel to elicit
On Sun, Nov 19, 2000 at 05:10:06PM +0100, Petr Vandrovec wrote:
> On Thu, Nov 16, 2000 at 08:40:29PM -0700, Jeff V. Merkey wrote:
> > Petr,
> >
> > NCPFS in 2.2.18-pre21 is not returning volume size via df -h. I checked
> > your code and found this comment:
> >
> > static int ncp_statfs(struct
On Sun, Nov 19, 2000 at 04:09:01PM +0100, Kai Germaschewski wrote:
> On Sun, 19 Nov 2000, Jeff V. Merkey wrote:
>
> > > o Small ISDN documentation fixes (Kai Germaschewski)
> >
> > Alan, On the ISDN issue, isdn4K-utils seems to be out of sync with
> > kernels older than 2.2.16.
On Sun, Nov 19, 2000 at 12:57:35PM +, Alan Cox wrote:
> > > o Small ISDN documentation fixes (Kai Germaschewski)
> >
> > Alan, On the ISDN issue, isdn4K-utils seems to be out of sync with=20
> > kernels older than 2.2.16. Some #define's that used to be in
> > the 2.2.14
David Ford <[EMAIL PROTECTED]> wrote:
>> Please turn this off.
>>
>My vcard size is the same or smaller than the average signature. Using mime,
you
>have the option of easily filtering vcards. Signatures aren't as easily
>identified for filtering.
I think the complaint was due not to the
rpc.portmap isn't running, your login configuration/nss requires yp or something
provided ans an RPC.
-d
"M.H.VanLeeuwen" wrote:
> I had occasion to "telinit 1" today and found that it took a long time
> to login after root passwd was entered. this doesn't happen with 2.2.X
> kernels.
>
> Is
Hello,
The undeclared variables are defined in include/linux/videodev.h , which is included
in videodev.c .
...
#define VID_TYPE_SUBCAPTURE 512
#define VID_TYPE_MPEG_DECODER 1024
#define VID_TYPE_MPEG_ENCODER 2048
#define VID_TYPE_MJPEG_DECODER 4096
#define VID_TYPE_MJPEG_ENCODER 8192
...
Hi Al,
Jeff Chua reported a while ago that BLKFLSBUF returns EBUSY on a RAM disk
that was obtained via initrd. I think the problem is that the effect of
the blkdev_open(out_inode, ...) in drivers/block/rd.c:rd_load_image is
not undone at the end. I've attached a patch for 2.4.0-test11-pre7 that
On Sun, 19 Nov 2000, Rogier Wolff wrote:
> Someone wrote:
> > > > So change the CMOS-settings so that the BIOS changes the boot order
> > > > from A, C, CD-ROM to C first instead. *grin* How long do you want
> > > > to keep playing Tic-Tac-Toe?
> > > Writeprotect the flashbios with the
On Mon, 20 Nov 2000, David Woodhouse wrote:
> On Sun, 19 Nov 2000, Dan Hollis wrote:
> > Writeprotect the flashbios with the motherboard jumper, and remove the
> > cmos battery.
> > Checkmate. :-)
> Only if you run your kernel XIP from the flash. If you load it into RAM,
> it's still possible for
On Sun, Nov 19, 2000 at 04:42:03PM -0600, M.H.VanLeeuwen wrote:
> I had occasion to "telinit 1" today and found that it took a long time
> to login after root passwd was entered. this doesn't happen with 2.2.X
> kernels.
>
> Is this to be expected with the 2.4 series kernels? or a bug?
It
I was going to report this back in pre6, but I thought someone had
caught it already.. When the bttv driver is enbabled as a module in
test11, make modules fails with:
videodev.c: In function `videodev_proc_read':
videodev.c:283: `VID_TYPE_MPEG_DECODER' undeclared (first use in this
function)
On Sun, 19 Nov 2000, Rich Baum wrote:
>
> The patch is in the v2.3 directory. You may want to move it to the
> v2.4 directory so people can find it easier.
Oops. Thanks. Done.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
The patch is in the v2.3 directory. You may want to move it to the
v2.4 directory so people can find it easier.
On 19 Nov 2000, at 18:19, Linus Torvalds wrote:
>
> Ok, test11 is out there. The most noticeable fixes since pre7 are the
> Athlon lockup fix, the PCI routing handling, and getting
=?iso-8859-1?q?Markus=20Schoder?= <[EMAIL PROTECTED]> said:
> --- Linus Torvalds <[EMAIL PROTECTED]> schrieb: >
[...]
> > Markus, can you make the irq13 test the first thing
> > - don't worry about
> > 3dnow as that seems to not be a deciding factor..
> Ok, that was it! It's IRQ 13. Guess I
=?iso-8859-1?q?Markus=20Schoder?= <[EMAIL PROTECTED]> said:
[...]
> I will also try to compile a non AMD specific kernel
> and see if that makes a difference. If just this 40GB
> drive would fsck faster :)
mount -o remount,ro [...]
--
Horst von Brand [EMAIL
Ok, test11 is out there. The most noticeable fixes since pre7 are the
Athlon lockup fix, the PCI routing handling, and getting the Joliet stuff
right for iso9660.
Linus
- final:
- Patrick Mochel: export the ACPI facs table in /proc too
- Brian Gerst: Video4Linux
Gerd Knorr wrote:
> Why? What is the point in compiling bttv statically into the kernel?
Well, I see the modules vs. static flame war is already in progress ;-)
My reason for wanting static kernels is that I usually build many, very
different versions of the same kernel, among which I
On Fri, Nov 03, 2000 at 02:36:22PM -0800, Josue Emmanuel Amaro wrote:
> Andrea,
>
> We will give it a try.
>
> How difficult would it be to move that patch to 2.4?
I moved it to 2.4.0-test11-pre5 (should work with pre7 too):
Hi,
my Dawicontrol 2974 SCSI-adapter fails with kernel 2.4.0-test10
with pre-11 and reiserfs for kernel test-10 patched in:
--
Nov 20 01:30:23 wh36-b407 kernel: scsi : aborting command due to timeout : pid 0,
scsi0, channel 0, id 0, lun 0 Read (10) 00 00 08 c0 6c 00 00 f8 00
Nov 20
On Sat, Nov 18, 2000 at 05:20:34PM -0800, H . J . Lu wrote:
> --- linux/fs/proc/mem.c.lseek Tue Jan 4 10:12:23 2000
> +++ linux/fs/proc/mem.c Sat Nov 18 17:19:28 2000
> @@ -196,14 +196,17 @@ static long long mem_lseek(struct file *
> {
> switch (orig) {
> case 0:
> -
Gerhard Mack <[EMAIL PROTECTED]> writes:
> That looks exactly like the message I get if I tell the bios not to
> assign an interrupt to my video card.
>
unfortunately, i don't get such a choice. and if what you say is true,
isn't the message ("No IRQ known for interrupt pin A of device
Followup to: <[EMAIL PROTECTED]>
By author:Alan Cox <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> > Try reserving ports 0x300-0x31f on the kernel command line
> > ("reserve=0x300,0x20").
> >
> > I'm surprised isapnp uses a port in such a commonly used range,
> > though.
>
> It
On Sun, 19 Nov 2000, Dan Hollis wrote:
> Writeprotect the flashbios with the motherboard jumper, and remove the
> cmos battery.
>
> Checkmate. :-)
Only if you run your kernel XIP from the flash. If you load it into RAM,
it's still possible for an attacker to modify it. You can load new code
On Sun, 19 Nov 2000, Andries Brouwer wrote:
> Moreover, the text Dan Hollis quotes is rather strange
It's from redhat 6.0 man-pages-1.23-3 rpm package.
-Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the
> Try reserving ports 0x300-0x31f on the kernel command line
> ("reserve=0x300,0x20").
>
> I'm surprised isapnp uses a port in such a commonly used range,
> though.
It seems to be a combination of two bugs. The one I posted a patch for and
something odd that is taking port 0x279 before the pnp
Linus, Ingo:
the attached patch, modifies a warning message in md.c which seems to
often cause confusion - the following email includes one example
there-of (there have been others over the months).
Hopefully the new text is clearer.
(patch against 2.4.0-test11-pre7)
NeilBrown
On
Followup to: <[EMAIL PROTECTED]>
By author:Tim Waugh <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Reading from port 0x313 (my ISA NE2000 is at 0x300-0x31f) hangs my
> machine dead. Unfortunately, reading from that port is exactly what
> the isapnp code does on boot, if compiled
> > Is it the network card's fault (probably), or is there a less invasive
> > probe that isapnp could use (unlikely, I guess)?
>
>
> That shouldnt be possible - we are supposed to start at 0x203 and skip the
> problem area.
And a quick read of the code I pasted instead of just pasting
On Sun, 19 Nov 2000, Andre Hedrick wrote:
> On Mon, 20 Nov 2000, Dan Aloni wrote:
>
> > Well, I could patch it so it adds that one sector ;-) But that's not the
> > right way. The true number of sectors is 90069840, since 90069839 doesn't
> > divide by the number of *real* heads (6) and the
That looks exactly like the message I get if I tell the bios not to assign
an interrupt to my video card.
Gerhard
On 19 Nov 2000, Alex Romosan wrote:
> Martin Mares <[EMAIL PROTECTED]> writes:
>
> > > During boot, I get the message:
> > >
> > > PCI: No IRQ known for interrupt pin
> Reading from port 0x313 (my ISA NE2000 is at 0x300-0x31f) hangs my
> machine dead. Unfortunately, reading from that port is exactly what
> the isapnp code does on boot, if compiled into the kernel.
>
> Is it the network card's fault (probably), or is there a less invasive
> probe that isapnp
Oops.. not . The patch below
implements resource limits for ramfs, and unlike the previous version
actually compiles.
--
David Gibson, Technical Support Engineer, Linuxcare, Inc.
+61 2 6262 8990
[EMAIL PROTECTED], http://www.linuxcare.com/
Linuxcare. Support for the revolution.
diff -uNr
On Mon, 20 Nov 2000, Dan Aloni wrote:
> Well, I could patch it so it adds that one sector ;-) But that's not the
> right way. The true number of sectors is 90069840, since 90069839 doesn't
> divide by the number of *real* heads (6) and the number of recording zones
> (15). So it needs fixing.
On Mon, 20 Nov 2000, Taisuke Yamada wrote:
>
> > > > This patch is not good...[snip]
> > >
> > > Please retest with hdc=...
> >
> > Ok, I've booted without the parameter, and without the jumper on
> > clipping mode (I'll do it tommorow, it's 1AM now) got something
> > similiar to what you've
/pub/linux/kernel/people/hedrick/ide-2.2.17/README
/pub/linux/kernel/people/hedrick/ide-2.2.17/ide.2.2.17.all.20001118.patch.bz2
There you go Sean, hope that helps.
Cheers,
On Sun, 19 Nov 2000, Sean B. Estabrooks wrote:
>
> > It is on kernel.org and the README tells you what to do to
Reading from port 0x313 (my ISA NE2000 is at 0x300-0x31f) hangs my
machine dead. Unfortunately, reading from that port is exactly what
the isapnp code does on boot, if compiled into the kernel.
Is it the network card's fault (probably), or is there a less invasive
probe that isapnp could use
Hi,
I have a Sony VAIO Z505JE with ymfpci sound and built-in microphone
and speaker. Everything worked fine with 2.2.17 plus ymfpci patch,
but the 2.2.18-pre22 produces a loud screech starting as sound
initializes and ending when startup scrips load mixer settings.
This happens because of audio
Hi,
Here is how I manage to hit this under 2.4.0-test11-pre6
1. mkfs an ext2 filesystem on a 36G disk
2. do a complex combination of data and metadata io on it by means
of SPECsfs with LOADs high enough to run out of space
3. observe that both high and low memory are almost zero, i.e. about
I have testing a HP 8200e USB CDRW Driver with this version of kernel.
With the vainilla test10, after wrinting 14 MB, the cdrecotrd proccess lock,
and I have the next messsage imn the logs:
Nov 19 22:35:34 localhost kernel: usb_control/bulk_msg: timeout
These doesn't happen with test10. But
> > > This patch is not good...[snip]
> >
> > Please retest with hdc=...
>
> Ok, I've booted without the parameter, and without the jumper on
> clipping mode (I'll do it tommorow, it's 1AM now) got something
> similiar to what you've written, and everything looks ok.
Great, so it worked.
#
On Sat, 18 Nov 2000, Andrew Morton wrote:
>
> This patch removes tq_scheduler from the kernel. All uses of
> tq_scheduler are migrated over to use schedule_task().
>
> Notes:
> - If anyone sleeps in a callback, then all other users of
> schedule_task() also sleep. But there's nothing new
On Mon, 20 Nov 2000, Taisuke Yamada wrote:
> > This patch is not good. It compiles, but when I boot the kernel, it
> > decides to ignore the hdc=5606,255,63 parameter that I pass to the kernel,
> > and limits the number of sectors to fill 8.4GB.
>
> Please retest with hdc=... parameter removed.
I had occasion to "telinit 1" today and found that it took a long time
to login after root passwd was entered. this doesn't happen with 2.2.X
kernels.
Is this to be expected with the 2.4 series kernels? or a bug?
Martin
strace for 2.4.0-test11-pre7
---snip---
gettimeofday({974665658,
> > With this patch, you will be able to use disk capacity above
> > 32GB (or 2GB/8GB depending on how clipping take effect), and
> > still be able to boot off from the disk because you can leave
> > the "clipping" turned on.
>
> I suppose you know that no kernel patch is required (since
>
> It is on kernel.org and the README tells you what to do to enable the stub
> in ide-dma.c If it works let me know!
Andre,
Where on kernel.org are you hiding the README and patch files you
mention?
Regards,
Sean
-
To unsubscribe from this list: send the line
On Sun, Nov 19, 2000 at 05:36:23PM +0100, Andries Brouwer wrote:
> DESCRIPTION
>This call copies data between one file descriptor and
>another. Either or both of these file descriptors may
>refer to a socket. in_fd should be a file descriptor
>
> > Earlier this month, I had sent in a patch to 2.2.18pre17 (with
> > IDE-patch from http://www.linux-ide.org/ applied) to add support
> > for IDE disk larger than 32GB, even if the disk required "clipping"
> > to reduce apparent disk size due to BIOS limitation.
>
> This patch is not good.
> During boot, I get the message:
>
> PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
> using pci=biosirq.
It is related to VGA card (at least on my system).
Enabling 'Assign IRQ for VGA' in BIOS causes the message to disapear.
Pavel
-
To unsubscribe from this list: send
On Sun, Nov 19, 2000 at 09:24:04PM +0100, Pavel Machek wrote:
> Hi!
>
> > > > Anyway, this should be solvable by checking for clock change in the
> > > > timer interrupt. This way we should be able to detect when the clock
> > > > went weird with a 10 ms accuracy. And compensate for that. It
On Sun, 19 Nov 2000 20:03:52 +0100 (CET),
Gerd Knorr <[EMAIL PROTECTED]> wrote:
>On Mon, 20 Nov 2000, Keith Owens wrote:
>> On my list for 2.5. If foo is declared as MODULE_PARM in object bar
>> then you will be able to boot with bar.foo=27 or even foo=27 as long as
>> variable foo is unique
Hello,
After I mounted my windows partition under 2.4.0-test11pre6
the file system was corrupted.
John
-
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
> "dalecki" == dalecki <[EMAIL PROTECTED]> writes:
A few questions after scanning through your patch, it's likely I
missed something but I am kind acurious.
dalecki> The attached patch does the following: 1. Merge the most
dalecki> current version (aka: 1.08) of the MegaRAID driver from
I'm using 2.4.0-test11pre7
I calcute md5sum of some files in a ext2 partition. I move those files
to a vfat partition. I duplicate the directory im the vfat partition. The
duplicate set doesn't pass the md5sum.
I have done various test and I can replicate they don't pass the md5 sum.
Are there
On Sun, Nov 19, 2000 at 08:20:33PM +0100, Martin Mares wrote:
> > During boot, I get the message:
> >
> > PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
> > using pci=biosirq.
>
> Can you send me 'lspci -vvx' output, please?
>
Here you go:
00:00.0 Host bridge: Silicon
Alexander Viro wrote:
> On Sun, 19 Nov 2000, Christer Weinigel wrote:
>
> > In article <[EMAIL PROTECTED]> you write:
> > >On Sun, 19 Nov 2000, Alexander Viro wrote:
> > >> On Sun, 19 Nov 2000, David Lang wrote:
> > >> > there is a rootkit kernel module out there that, if loaded onto your
> > >>
Christer Weinigel wrote:
> In article <[EMAIL PROTECTED]> you write:
> >On Sun, 19 Nov 2000, Alexander Viro wrote:
> >> On Sun, 19 Nov 2000, David Lang wrote:
> >> > there is a rootkit kernel module out there that, if loaded onto your
> >> > system, can make it almost impossible to detect that
[Please help me test this patch (for linux-2.4.0-test10/11)!]
This is my tx performance patch for dmfe, excluding the locking fixes,
which will appear in a separate patch. I would like feedback from testing
and code inspection. New since the last patch is the line printed when a
new card is
Someone wrote:
> > > So change the CMOS-settings so that the BIOS changes the boot order
> > > from A, C, CD-ROM to C first instead. *grin* How long do you want
> > > to keep playing Tic-Tac-Toe?
> >
> > Writeprotect the flashbios with the motherboard jumper, and remove the
> > cmos battery.
Petr Vandrovec wrote:
>
> On Sat, Nov 18, 2000 at 10:43:20PM -0500, John Cavan wrote:
> > Bus 1, device 0, function 0:
> > VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 5).
> > IRQ 16.
> > Master Capable. Latency=64. Min Gnt=16.Max Lat=32.
> >
Just a data point
I'm listening to mp3s now via xmms, running 2.4.0-test11-pre7
# uname -r -s
Linux 2.4.0-test11-pre7
# rpm -q xmms
xmms-1.2.3-0_helix_1
the "flags/features" switch doesn't seem to hurt it:
# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family
Pavel Machek wrote:
> > Actually, I was planning on doing on putting in a hack to do something
> > like that: calculate a checksum after every buffer data update and check
> > it after write completion, to make sure nothing scribbled in the buffer
> > in the interim. This would also pick up some
Hi!
> > > Anyway, this should be solvable by checking for clock change in the
> > > timer interrupt. This way we should be able to detect when the clock
> > > went weird with a 10 ms accuracy. And compensate for that. It should be
> > > possible to keep a 'reasonable' clock running even through
Werner Almesberger <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
> > The code wasn't trivially reusable, and the structures had a lot
> > of overhead.
>
> There's some overhead, but I think it's not too bad. I'll give it a
> try ...
>
> > The rebooting is done the rest is not yet.
>
Hi!
> > book, Ext2 throws safety to the wind to achieve speed. This also ties
> > into Linux' convoluted VM system, and is shot in the foot by NFS. We
> > would need minimally a journaled filesystem and a clean VM design,
> > probably with a unified cache (no separate buffer, directory entry and
Hi1
> > Did you try to load an initrd on a low-memory machine?
> > It shouldn't work and it probably won't ;)
>
> You must be really low on memory ;-)
>
> # zcat initrd.gz | wc -c
> 409600
>
> (ash, pwd, chroot, pivot_root, smount, and still about 82 kB free.)
Your solution requires 400K
Hi!
> >One note for the archives, if you are presented a choice between a OHCI
> >or a UHCI controller, go for the OHCI. It has a "cleaner" interface,
> >handles more of the logic in the silicon, and due to this provides
> >faster transfers.
>
> I'd disagree. UHCI has tons of advantages, not
Martin Mares <[EMAIL PROTECTED]> writes:
> > During boot, I get the message:
> >
> > PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
> > using pci=biosirq.
>
> Can you send me 'lspci -vvx' output, please?
>
i am not the original poster, but i get the same message (save
On Sat, Nov 18, 2000 at 10:43:20PM -0500, John Cavan wrote:
> Bus 1, device 0, function 0:
> VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 5).
> IRQ 16.
> Master Capable. Latency=64. Min Gnt=16.Max Lat=32.
> Prefetchable 32 bit memory at 0xf600
On Mon, 20 Nov 2000, Keith Owens wrote:
> On 19 Nov 2000 12:56:17 GMT,
> [EMAIL PROTECTED] (Gerd Knorr) wrote:
> >Some generic way to make module args available as kernel args too
> >would be nice. Or at least some simple one-liner I could put next to
> >the MODULE_PARM() macro...
>
> On my
Hello!
> I have a motherboard with a broken bios that is unable to set interrupts
> correctly, i.e. it initializes the devices corerctly but swaps the
> interrupts for slot1/slot3 and slot2/slot4.
>
> Now, is there a way to forcefully re-order the pci-interrupts? I do not
> have an io-apic
Hello!
> During boot, I get the message:
>
> PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
> using pci=biosirq.
Can you send me 'lspci -vvx' output, please?
Have a nice fortnight
--
Martin `MJ' Mares <[EMAIL PROTECTED]> <[EMAIL
On Sun, 19 Nov 2000, Andrew Morton wrote:
>
> I don't see a path where David's patch can cause a lost wakeup in the
> way you describe.
Basically, if there are two up() calls, they might end up waking up only
one process, because the same process goes to sleep twice. That's wrong.
It should
On Sun, 19 Nov 2000, David Lang wrote:
> there is a rootkit kernel module out there that, if loaded onto your
> system, can make it almost impossible to detect that your system has been
> compramised. with module support disabled this isn't possible.
Wrong. I've seen messages on bugtraq saying
Hi Vincent and Tony,
Hate to spoil the fun :( but, try the patch Tom Leete commited on Saturday
november 18th.
Since your Oopses are related to get_joliet_filename(), this might just do
the trick?
Luuk
>Hi,
>
>
>The second and third arguments of get_joliet_filename() are swapped.
>
>
>Tom
>
On Sun, 19 Nov 2000, David Ford wrote:
>
> My guess is that it's a plugin, the source for xmms doesn't have "cpuinfo" anywhere
>in it.
>
> -d
>
> Gianluca Anzolin wrote:
>
> > it seems there has been a change in the format of the /proc/cpuinfo file: infact
>'flags: ' became 'features: '
> >
--- Brian Gerst <[EMAIL PROTECTED]> wrote:
> > Ok, that was it! It's IRQ 13. Guess I should
have
> > tried that first. Now everything works perfectly.
> > Thanks everybody.
>
> What motherboard do you have? I can't reproduce
> this on my FIC SD11.
>
> --
>
>
Peter Rottengatter wrote:
>
> Sorry for using this address, there does not appear to be a special maintainer
> for the 3c509 network driver.
>
> 1.
> 3c509 driver broken in 2.4.0-test10, not in -test9
>
> 2.
> The 3c509 network driver worked fine for decades almost ;-) that is 2.0.x,
> 2.2.x,
Sorry for using this address, there does not appear to be a special maintainer
for the 3c509 network driver.
1.
3c509 driver broken in 2.4.0-test10, not in -test9
2.
The 3c509 network driver worked fine for decades almost ;-) that is 2.0.x,
2.2.x, and 2.4.0-test up to 9. In 2.4.0-test10 it
On Sun, Nov 19, 2000 at 04:30:34AM +0900, Taisuke Yamada wrote:
> Earlier this month, I had sent in a patch to 2.2.18pre17 (with
> IDE-patch from http://www.linux-ide.org/ applied) to add support
> for IDE disk larger than 32GB, even if the disk required "clipping"
> to reduce apparent disk size
2.4.0-test11-pre3 kernel said
Nov 19 17:40:25 iapetus kernel: Attempt to read inode for relocated directory
Nov 19 17:40:25 iapetus last message repeated 8 times
while doing a
mount -t iso9660 /dev/hdc /cdrom
cd /cdrom
find -depth |cpio -pdm /dst
Is reproducable here,
> > So change the CMOS-settings so that the BIOS changes the boot order
> > from A, C, CD-ROM to C first instead. *grin* How long do you want
> > to keep playing Tic-Tac-Toe?
>
> Writeprotect the flashbios with the motherboard jumper, and remove the
> cmos battery.
>
> Checkmate. :-)
You can
The original was good, but the changes made to do the callout fail to
return structs that need to be filled. This is my fault.
On Sun, 19 Nov 2000, Dan Aloni wrote:
> On Sun, 19 Nov 2000, Taisuke Yamada wrote:
>
> > Earlier this month, I had sent in a patch to 2.2.18pre17 (with
> > IDE-patch
At 11:26 17/11/2000, Alan Cox wrote:
> > drive problem, considering that another ide drive on the same controller
> > works fine with DMA enabled (a QUANTUM TRB850A) while the Conner
> > Peripherals 1275MB - CFS1275A fails with DMA enabled. They are in fact
> both
>
>And the Conner drives work
On Sun, 19 Nov 2000, Taisuke Yamada wrote:
> Earlier this month, I had sent in a patch to 2.2.18pre17 (with
> IDE-patch from http://www.linux-ide.org/ applied) to add support
> for IDE disk larger than 32GB, even if the disk required "clipping"
> to reduce apparent disk size due to BIOS
On Sun, Nov 19, 2000 at 01:53:00AM +0100, bert hubert wrote:
: On Sat, Nov 18, 2000 at 03:15:28PM -0800, Dan Hollis wrote:
:
::: In that case, the wording of the manpage needs to be changed, as it
::: implies that 'either or both' of the filedescriptors can be sockets.
::
:: Its quite
My guess is that it's a plugin, the source for xmms doesn't have "cpuinfo" anywhere in
it.
-d
Gianluca Anzolin wrote:
> it seems there has been a change in the format of the /proc/cpuinfo file: infact
>'flags: ' became 'features: '
>
> This change broke xmms and could broke any other program
Christer Weinigel wrote:
> >Kernel on writeprotected floppy disk...
>
> So change the CMOS-settings so that the BIOS changes the boot order
> from A, C, CD-ROM to C first instead. *grin* How long do you want
> to keep playing Tic-Tac-Toe?
>
> Of course, using capabilities and totally disabling
Miquel van Smoorenburg wrote:
>
> In article <[EMAIL PROTECTED]>,
> dalecki <[EMAIL PROTECTED]> wrote:
> >This is a multi-part message in MIME format.
> >1. Merge the most current version (aka: 1.08) of the
> > MegaRAID driver from AMI in to the most current kernel
> > (2.4.0-test10 and
> Why not? /me has nearly everything compiled as modules.
Some people have extensive sh, awk and sed scripts to manage their systems, some
have compiled programs.
> > There is an introduced security weakness by using kernels.
>
> ??? Guess you mean "by using modules"? Which weakness? Other
Jeff Garzik wrote:
>
> dalecki wrote:
> > -#if LINUX_VERSION_CODE > 0x020024
> > #include
> > -#endif
>
> *cheer*
I missd this point...
>
> > -u32 RDINDOOR (mega_host_config * megaCfg)
> > +ulong RDINDOOR (mega_host_config * megaCfg)
> > -void WRINDOOR (mega_host_config * megaCfg, u32
On Sun, 19 Nov 2000, Alexander Viro wrote:
> > >Kernel on writeprotected floppy disk...
> Cute. And when (not if) we get hit by new bug in the net/*/* you will drive
> to the location of said router to upgrade the thing.
No, post/email a floppy to tech who swaps the floppy and reboots router.
On Sun, 19 Nov 2000, Christer Weinigel wrote:
> In article <[EMAIL PROTECTED]> you write:
> >On Sun, 19 Nov 2000, Alexander Viro wrote:
> >> On Sun, 19 Nov 2000, David Lang wrote:
> >> > there is a rootkit kernel module out there that, if loaded onto your
> >> > system, can make it almost
1 - 100 of 277 matches
Mail list logo
