Concerning the new way initrd works in 2.4...
I'm trying to get the system to the point where I can free the memory
used by the initrd. I'm quite well aware of how to do this in a bash
script, but I want to know how to do the same from a C program.
Currently, something's keeping /dev/ram0 busy,
On Mon, 18 Jun 2001, Richard Gooch wrote:
> Alexander Viro writes:
> >
> >
> > On Mon, 18 Jun 2001, Richard Gooch wrote:
> >
> > > - Widened locking in and
> >
> > No, you hadn't. Both vfs_readlink() and vfs_follow_link() are blocking
> > functions, so BKL is worthless there.
>
> Huh? Th
Hi all.
I'm having ~2 lockups a day. The following happens:
If I was under X, i only can use the magic-key, but no other keyboard (eg
numlock) or mouse response, the screen freezes, processes stop.
If i was using textmode:
numlock still works
cursor blinks
processess stop (eg, gpm doesn'
Alexander Viro writes:
>
>
> On Mon, 18 Jun 2001, Richard Gooch wrote:
>
> > - Widened locking in and
>
> No, you hadn't. Both vfs_readlink() and vfs_follow_link() are blocking
> functions, so BKL is worthless there.
Huh? The BKL will protect against other operations which might cause
the d
On Mon, 18 Jun 2001, Richard Gooch wrote:
> - Widened locking in and
No, you hadn't. Both vfs_readlink() and vfs_follow_link() are blocking
functions, so BKL is worthless there.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROT
Quoting [EMAIL PROTECTED] from ml.linux.kernel:
:There has been a bug in the 2.4.x series of kernels for a long time (at
:least -pre9) concerning SMP and ne2k-pci.
:
:Symptoms: Network driver locks up. Repeated messages of "ETH0: Transmit
:timeout" occurs. Unloading and reloading network drivers
Hi, all. Version 181 of my devfs patch is now available from:
http://www.atnf.csiro.au/~rgooch/linux/kernel-patches.html
The devfs FAQ is also available here.
Patch directly available from:
ftp://ftp.??.kernel.org/pub/linux/kernel/people/rgooch/v2.4/devfs-patch-current.gz
AND:
ftp://ftp.atnf.c
I'd like to monitor CPU, memory, and I/O utilization in a
long-running multithreaded daemon under kernels 2.2, 2.4,
and possibly also Solaris (#ifdefs are ok).
getrusage() looked promising, and might even work for CPU utilization.
Dunno if it returns info for all child threads yet, haven't tried
Here is a small patch for the adjtime behavour (strictly adjtimex when
called with ADJ_OFFSET_SINGLESHOT) to make it work more like the
adjtime found in *BSD based kernels where large deltas are allowed to
slew at a greater rate.
In the current Linux code (in 2.2 and 2.4) the slew rate is limited
> FWIW, I believe Intel's Linux drivers will support this card under
> 2.4, and I believe (not 100% certain on this) that they're GPL. I'll
> have to check on that.
The e100 driver from intel claims to support these cards (the 100 S
desktop adaptor, that is), but in fact the drivers lock up unde
Ivan Vadovic writes:
> Well, are there any utilities to merge diffs? I couldn't find any on freshmeat.
> So what are you using to stack many patches onto the kernel tree? Just manualy
> modify the diff? I'll try to write something more automatic if nothing comes up.
Try dirdiff - ftp://ftp.samba
On Sun, Jun 17, 2001 at 05:25:11PM -0700, Daniel Bertrand wrote:
> > if the driver in the kernel is that old, could we try merging a newer
> > release? is there any reason why it has not been done yet?
>
> A patch was submitted to Alan in April but appears to have never made it
> in, I'm not sur
Hi,
by default the limit for max_threads is such that
the system will try to allocate up to half the
physical memory in task_structs.
Because for each 8kB task struct we'll often want
a struct_mm, a page directory, 3 page tables and
some more structures, this means that a fork bomb
will leave th
Currently getdents64() returns d_off values that have been truncated
to 32 bits and then sign extended for all but the last directory entry
it returns. This is because the filldir functions have been typedef'd
and declared as taking an 'off_t offset' instead of a 'loff_t offset'.
This patch fix
Moving the "partition shift"
block += partition_start;
from the bowels of SCSI and IDE drivers to ll_rw_blk.c
(something that must wait for 2.5) I changed sd_init a bit
and noticed that the present version is buggy:
static struct gendisk sd_gendisk = {
SCSI_DISK0_MAJOR, /* M
At 2:34 AM +0200 2001-06-18, Ivan Vadovic wrote:
>Very often the case is that they indeed can be merged automagically.
>For example two patches inserting few lines right after the #include
>lines.
>
>patch1:
>@@ 10,1 10,2 @@
> #include
>+#include <1.h>
>
>patch2:
>@@ 10,1 10,2 @@
> #include
>+
> > I like to build kernels with a bunch of patches on top to test
> > new stuff. The problem is that it takes a lot of effort to fix
> > all the failed hunks during patching that really wouldn't have
> > to be failed if only patch was a little more inteligent and
> > could merge several patc
On 17 Jun 2001 17:25:11 -0700, Daniel Bertrand wrote:
> On 17 Jun 2001, Robert Love wrote:
> > if the driver in the kernel is that old, could we try merging a newer
> > release? is there any reason why it has not been done yet?
>
> A patch was submitted to Alan in April but appears to have never
On 17 Jun 2001, Robert Love wrote:
> On 17 Jun 2001 15:17:41 -0700, Daniel Bertrand wrote:
> > Can you give the CVS driver a try? Snapshots are available here:
> > http://opensource.creative.com/snapshot.html
> >
> > The driver in the kernel is based on a CVS snapshot from last summer, the
> > pr
On Sun, Jun 17, 2001, Dylan Griffiths <[EMAIL PROTECTED]> wrote:
> dmesg log:
> usb.c: registered new driver dc2xx
> dc2xx.c: v1.0.0 David Brownell, <[EMAIL PROTECTED]>
> dc2xx.c: USB Camera Driver for Kodak DC-2xx series cameras
> PCI: Found IRQ 5 for device 00:04.2
> PCI: The same IRQ used for d
> Can you give the CVS driver a try? Snapshots are available here:
> http://opensource.creative.com/snapshot.html
>
> The driver in the kernel is based on a CVS snapshot from last summer, the
> problem may be fixed in CVS.
So why noone sends updated driver to Alan?
Regards,
Nerijus
-
To unsubs
Hi Ivan.
> I like to build kernels with a bunch of patches on top to test
> new stuff. The problem is that it takes a lot of effort to fix
> all the failed hunks during patching that really wouldn't have
> to be failed if only patch was a little more inteligent and
> could merge several patc
On 17 Jun 2001 15:17:41 -0700, Daniel Bertrand wrote:
> Can you give the CVS driver a try? Snapshots are available here:
> http://opensource.creative.com/snapshot.html
>
> The driver in the kernel is based on a CVS snapshot from last summer, the
> problem may be fixed in CVS. Also, the CVS driver
Another thing I was happy to find working better in 2.4.5, was USB. I had
just dumped off ~70 high res pics (which would've taken forever via the
usual RS232 method), and was deleting the last pics when gphoto froze. The
dmesg log has the same messages it had before when I experimented with 2.4.
Hi,
I like to build kernels with a bunch of patches on top to test new stuff. The
problem is that it takes a lot of effort to fix all the failed hunks during
patching that really wouldn't have to be failed if only patch was a little more
inteligent and could merge several patches into one ( if po
Hello,
I just upgraded to Red Hat 7.0 from 6.2, and I am now trying to build
kernel-2.4.5.
After executing bzImage, at "Install db development libraries" I got the
following error:
aicasm_symbol.c:39:19: acidb.h: No such file or directory
make[5]: *** [aicasm] Error 1
make[5]: Leaving d
I own one of these last BX motherboards released with an extra
UDMA 66/100 interface: the ASUS CUBX. In this case, this
model comes with a CMD-648 UDMA66 chip.
Following some trouble I had with driver support to the chip (I also
use Win2K) I decided to buy a Promise Ultra100 PCI interfa
On Sun, Jun 17, 2001 at 02:37:03PM +0200, Ronald Bultje wrote:
> system = p-II 400 MHz, 128 MB swap, 440BX (abit p6b) mainboard
> memory is (133 MHz) SDRAM memory (running at 100 MHz)
The question is, does it configure your SDRAMs correctly? I assume it's
on auto config, then the BIOS has to fig
On Sun, 17 Jun 2001, Daniel Phillips wrote:
> typeof? It's rather popular in the kernel already. Besides, who is going to
Really? 5 instances in PPC arch-specific code, 1 (absolutely gratitious)
in drivers/mtd, 2 - in m68k (also useless), 4 - in drivers/video, 2 -
in AFFS and 1 - in netfilt
On Sun, 17 Jun 2001, Dan Podeanu wrote:
> Is there any logical reason why if, given fd is a connected, AF_INET,
> SOCK_STREAM socket, and one does a write(fd, buffer, len); close(fd);
> to the peer, over a rather slow network (read modem, satelite link, etc),
> the data gets lost (the remote rece
<[EMAIL PROTECTED]> wrote:
>with 2.4.6pre3 or not. I have
>also applied the latest patch from reiserfs.org
>I have intel i810, celeron 566, 384MB
i also use reiserfs (only) on my systems and
experience samen problems with 2.4.5-ac11 and up.
Somehow the machine seems to "hang" on unmounting
the
On Sun, 17 Jun 2001, Dylan Griffiths wrote:
> Kernel 2.4.5 has a working emu10k1 driver (all apps which hung with
> 2.2.19's driver worked fine, none of the working ones stopped working).
> Could we perhaps see this backported to the 2.2.20 prepatches so that us 2.2
> lovers can enjoy worki
On Sun, Jun 17, 2001 at 05:13:43PM -0400, Albert D. Cahalan wrote:
> > Is there any logical reason why if, given fd is a connected, AF_INET,
> > SOCK_STREAM socket, and one does a write(fd, buffer, len); close(fd);
> > to the peer, over a rather slow network (read modem, satelite link, etc),
> > t
On Sun, 17 Jun 2001 20:58:35 +0200, you wrote:
>I have a database server with 1G phys and 1G swap. It uses 950+ MB for cache,
>as it should, and doesn't even *touch* swap. This is 2.4.5.
I thought the new rule is:
total_memory = max(physical, swap);
And the old rule was:
total
Jim Randell writes:
> I've recently been getting strange system lock-ups - often my system
> just dies, but occasionally I get messages in dmesg. I've tried to
> isolate the problem by increasing the available swap (I now have > 2x
> RAM), removing my reiserfs partitions (I'm now running with ext2
On Sunday 17 June 2001 22:37, Alexander Viro wrote:
> On Sun, 17 Jun 2001, Daniel Phillips wrote:
> > Well, since we are still beating this one to death, I'd written a "knew"
> > macro as well, and put it aside. It does the assignment for you too:
> >
> >#define knew(p) ((p) = (typeof(p)) kma
> "Jeff" == Jeff Garzik <[EMAIL PROTECTED]> writes:
[snip]
Jeff> It's the preference of the maintainer. It's a tossup: using
Jeff> the type in the kmalloc makes the type being allocated obvious.
Jeff> But using sizeof(*var) is a tiny bit more resistant to change.
Ok, thanks. I was lookin
Starting today, Paul Mackerras ([EMAIL PROTECTED]) is taking over as
maintainer of the Linux/PPC 32-bit tree and will continue as the Linux/PPC
64-bit tree maintainer.
The stable and development trees (2.2 and 2.4) will be moving away from
the FSMLabs ftp/rsync/BitKeeper repository to the vger.ke
On Sun, 17 Jun 2001, Daniel Phillips wrote:
> > macro that behaves like `new' in C++:
> > | #define knew(type, flags) (type *)kmalloc(sizeof(type), (flags))
> >
> > If the types in the assignment don't match, gcc will tell you.
>
> Well, since we are still beating this one to death, I'd writte
Alan Cox <[EMAIL PROTECTED]> writes:
> > > Specifically
> > > 1.If the receiver closes and there is unread data many TCP's forget
> > > to RST the sender to indicate that data was lost.
> >
> > Do at least FreeBSD, Solaris and NT sent RST correctly?
>
> I dont believe so
There is als
On Sunday 17 June 2001 21:18, Geert Uytterhoeven wrote:
> On Sun, 17 Jun 2001, Jeff Garzik wrote:
> > David Flynn wrote:
> > > > Daniel Phillips wrote:
> > > > > - if ((card->mpuout = kmalloc(sizeof(struct emu10k1_mpuout),
GFP_KERNEL))
> > >
> > > > > + if ((card->mpuout = kmalloc(siz
On Sun, Jun 17, 2001 at 07:42:33PM +0100, David Flynn wrote:
> ive done the badblock test, and compiled a list of 2302 bad blocks on this
> disk ... however, when running mke2fs -l badblocfile /dev/hdc1
>
> i got this interesting errormessage for every one of the bad blocks :
>
> Bad block 1006
On Sun, Jun 17, 2001 at 08:17:27PM +0200, Pavel Machek wrote:
> > 2. There is a flaw in the TCP protocol itself that is extremely unlikely
> > to bite people but can in theory cause wrong data in some unusual
> > circumstances that Ian Heavans found and has yet to be fixed by
> > the
On Sun, Jun 17, 2001 at 10:31:47PM +0300, Dan Podeanu wrote:
> > Yes, I know there's no hard and fast rule for the exact ammount of ram/swap one
> > needs that will always work. However, in 2.2 for a 'workstation' one could
> > usually quite happily get away with having 128:128 and never have muc
> > Specifically
> > 1. If the receiver closes and there is unread data many TCP's forget
> > to RST the sender to indicate that data was lost.
>
> Do at least FreeBSD, Solaris and NT sent RST correctly?
I dont believe so
> > 2. There is a flaw in the TCP protocol itself that is extremely
> Yes, I know there's no hard and fast rule for the exact ammount of ram/swap one
> needs that will always work. However, in 2.2 for a 'workstation' one could
> usually quite happily get away with having 128:128 and never have much of a
> problem. with 2.4.0 and up this isn't the case. This has
On Sun, 17 Jun 2001, Jeff Garzik wrote:
> David Flynn wrote:
> > > Daniel Phillips wrote:
> > > > Yep, the only thing left to resolve is whether Jeff had coffee or not.
> > ;-)
> > > >
> > > > - if ((card->mpuout = kmalloc(sizeof(struct emu10k1_mpuout),
> > GFP_KERNEL))
> > > > + if ((
On Sun, Jun 17, 2001 at 10:12:39PM +0300, Dan Podeanu wrote:
> On Sun, Jun 17, 2001 at 10:48:36AM -0700, Tom Rini wrote:
> > 'lo all. I've got a question about swap and RAM requirements in 2.4. Now,
> > when 2.4.0 was kicked out, the fact that you need swap=2xRAM was mentioned.
> > But what I'm
On Sun, Jun 17, 2001 at 10:48:36AM -0700, Tom Rini wrote:
> 'lo all. I've got a question about swap and RAM requirements in 2.4. Now,
> when 2.4.0 was kicked out, the fact that you need swap=2xRAM was mentioned.
> But what I'm wondering is what exactly are the limits on this. Right now
> I've g
On Sun, 17 Jun 2001, Jeff Chua wrote:
> Try to add "options eepro100 options=0" to your /etc/modules.conf
> to default the speed to 10Mbps if you're using 10BaseT.
I'm not using modules for this driver (can't see the point, really); does
this fix anything if I change it to 0x20 for 100BaseT?
Ta
On Sun, Jun 17, 2001 at 08:58:35PM +0200, Jakob ?stergaard wrote:
> On Sun, Jun 17, 2001 at 10:48:36AM -0700, Tom Rini wrote:
> > 'lo all. I've got a question about swap and RAM requirements in 2.4. Now,
> > when 2.4.0 was kicked out, the fact that you need swap=2xRAM was mentioned.
> > But what
On Sun, Jun 17, 2001 at 10:48:36AM -0700, Tom Rini wrote:
> 'lo all. I've got a question about swap and RAM requirements in 2.4. Now,
> when 2.4.0 was kicked out, the fact that you need swap=2xRAM was mentioned.
> But what I'm wondering is what exactly are the limits on this. Right now
> I've g
> hi guys,
> Since its relativley quiet at the moment, please excuse me for
> asking for some advice about the following problem.
>
i dont usually like following up my own sensless ramblings, but here is an
interesting twist (probabally caused by my ill understanding of the issues
involv
I had already two crashes with ac15. The system was still ping-able, but
login over the network didn't work anymore.
The first crash happened after I started xosview and noticed that the
system almost used up the swap (for no apparent reason). The second
crash happened shortly after I started fsc
Probably what happens is that your BIOS stores some data in the top
megabyte of RAM, but doesn't set up the memory map to reflect this.
Therefore, Linux overwrites whatevers up there, causing problems.
On Sun, Jun 17, 2001 at 09:26:50PM +0200, Ronald Bultje wrote:
> P6b has three mem-slots. I wou
'lo all. I've got a question about swap and RAM requirements in 2.4. Now,
when 2.4.0 was kicked out, the fact that you need swap=2xRAM was mentioned.
But what I'm wondering is what exactly are the limits on this. Right now
I've got an x86 box w/ 128ram and currently 256swap. When I had 128, I'
On 17 Jun 2001 06:10:02 -0700, Colonel wrote:
> In clouddancer.list.kernel, you wrote:
> >
> >Hi,
> >
> >I just added 128 MB of RAM to my machine which already had 128 MB and
> >which has 128 MB swap. 128 MB RAM + 128 MB swap (either the new or the
> >old 128 MB RAM) works, but the combination of
hi guys,
Since its relativley quiet at the moment, please excuse me for
asking for some advice about the following problem.
for a while now ive had a disk that causes errors to occur during reads,
however, ive finally got round to doing a
# badblocks -c 32 -o mybadblocks -w -v -s /dev/h
Hi!
> My MIPS machine has no any disks or flopies. So i obliged to use a RAM
> disk with a file system on it, which is mounted as root.
What machine is that? Some kind of handheld?
Pavel
PS: linux-vr list seems dead, right? It would
Hi!
> Attached is a patch to enforce a non-blinking, FreeBSD-syscons like
> block cursor in console mode.
>
> This is useful for laptop types, or people like me who really really
> detest a blinking cursor.
>
> NOTE: It disables the softcursor escape codes
> (/usr/src/linux/Documentation
On Sun, 17 Jun 2001 [EMAIL PROTECTED] wrote:
> On Sun, Jun 17, 2001 at 12:05:10PM +0200, Mike Galbraith wrote:
> >
> > It _juuust_ so happens that I was tinkering... what do you think of
> > something like the below? (and boy do I ever wonder what a certain
> > box doing slrn stuff thinks of it.
David Flynn wrote:
>
> > Daniel Phillips wrote:
> > > Yep, the only thing left to resolve is whether Jeff had coffee or not.
> ;-)
> > >
> > > - if ((card->mpuout = kmalloc(sizeof(struct emu10k1_mpuout),
> GFP_KERNEL))
> > > + if ((card->mpuout = kmalloc(sizeof(*card->mpuout), GFP_KER
Try to add "options eepro100 options=0" to your /etc/modules.conf
to default the speed to 10Mbps if you're using 10BaseT.
add to /etc/modules.conf ...
# options=0x30 100mbps full duplex
# options=0x20 100mbps half duplex
# options=0 10mbps half duplex
options eepro100 options=0
then run "dep
> Daniel Phillips wrote:
> > Yep, the only thing left to resolve is whether Jeff had coffee or not.
;-)
> >
> > - if ((card->mpuout = kmalloc(sizeof(struct emu10k1_mpuout),
GFP_KERNEL))
> > + if ((card->mpuout = kmalloc(sizeof(*card->mpuout), GFP_KERNEL))
>
> Yeah, this is fine. The
Daniel Phillips wrote:
> Yep, the only thing left to resolve is whether Jeff had coffee or not. ;-)
>
> - if ((card->mpuout = kmalloc(sizeof(struct emu10k1_mpuout), GFP_KERNEL))
> + if ((card->mpuout = kmalloc(sizeof(*card->mpuout), GFP_KERNEL))
Yeah, this is fine. The original post
On Sunday 17 June 2001 14:27, [EMAIL PROTECTED] wrote:
> Daniel Phillips wrote:
> > > because then you would be allocating the size of a pointer, not the
> > > size of a structure
> >
> > Whoops Jeff, you didn't have your coffee yet:
>
> Whoops yourself. The following patch brings your example int
> > > > I currently try to debug why the sisfb driver crashes my machine. (SIS 630
> > > > based laptop - linux-2.4.5-ac13).
> > >
> > > You can do one of two things. Post both System.map and the complete oops
> > > or you can run ksymoops on the oops. I can find the problem then. Thanks.
> >
>
Hi!
Note that you have the VIA IDE driver disabled in your setup.
Vojtech
On Sat, Jun 16, 2001 at 07:02:03PM -0300, Peter Cordes wrote:
> This is a bug report about the VIA IDE driver. I'm forwarding it here
> because [EMAIL PROTECTED] bounced.
>
> - Forwarded message from Mail Delivery
In clouddancer.list.kernel, you wrote:
>
>Hi,
>
>I just added 128 MB of RAM to my machine which already had 128 MB and
>which has 128 MB swap. 128 MB RAM + 128 MB swap (either the new or the
>old 128 MB RAM) works, but the combination of that, 256 MB RAM + 128 MB
>swap, crashes the compu during st
On Sun, Jun 17, 2001 at 12:05:10PM +0200, Mike Galbraith wrote:
>
> It _juuust_ so happens that I was tinkering... what do you think of
> something like the below? (and boy do I ever wonder what a certain
> box doing slrn stuff thinks of it.. hint hint;)
>
I'm sorry to say this box doesn't real
Hi,
I just added 128 MB of RAM to my machine which already had 128 MB and
which has 128 MB swap. 128 MB RAM + 128 MB swap (either the new or the
old 128 MB RAM) works, but the combination of that, 256 MB RAM + 128 MB
swap, crashes the compu during startup with either an "unresolved-
symbols in in
Daniel Phillips wrote:
>
> > because then you would be allocating the size of a pointer, not the size
> > of a structure
>
> Whoops Jeff, you didn't have your coffee yet:
Whoops yourself. The following patch brings your example into line with
the driver code. mpuout is a pointer to a structure
[EMAIL PROTECTED] wrote:
> I remember seeing something about how some via ide chipsets (686b I
think)
> and [some?] ide promise controllers had problems with data corruption on
> the IBM dtla-series udma drives, and that IBM stated the problem was
with
> the controllers. Is there a chance a
> It seems, that 2.4.5 is supposed to support K7 Machine Check Exception
> in arch/i386/kernel/bluesmoke.c. However mcheck_init() is called from
The changes needed for this are not yet fully merged from -ac. Your change
looks fine
-
To unsubscribe from this list: send the line "unsubscribe linux
Kernel 2.4.5 has a working emu10k1 driver (all apps which hung with
2.2.19's driver worked fine, none of the working ones stopped working).
Could we perhaps see this backported to the 2.2.20 prepatches so that us 2.2
lovers can enjoy working sound?
--
www.kuro5hin.org -- technology an
Hi folks!
It seems, that 2.4.5 is supposed to support K7 Machine Check Exception
in arch/i386/kernel/bluesmoke.c. However mcheck_init() is called from
init_intel() in arch/i386/kernel/setup.c only. Therefore it is never
invoked from init_amd() - so not enabled.
I tried following patch:
--- arch
On Sunday 17 June 2001 03:32, Jeff Garzik wrote:
> Bill Pringlemeir wrote:
> > Why is the struct type referenced for the allocation size? Why not,
> >
> > if ((card->mpuout = kmalloc(sizeof(card->mpuout), GFP_KERNEL))
>
> because then you would be allocating the size of a pointer, not the
In clouddancer.list.kernel, you wrote:
>
>[EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>> I have to ask, is this something you wrote, or an actual log from
>> something you wrote? (=:]
>
>What? Moi, perpetrate a trifling and crude hoax? You wound me, sir,
>by supposing I would ever stoop to such gauch
On Saturday 16 June 2001 23:54, Rik van Riel wrote:
> On Sat, 16 Jun 2001, Daniel Phillips wrote:
> > > Does the patch below do anything good for your laptop? ;)
> >
> > I'll wait for the next one ;-)
>
> OK, here's one which isn't reversed and should work ;))
>
> --- fs/buffer.c.orig Sat Jun 16
On Sat, 16 Jun 2001, Daniel Phillips wrote:
> On Saturday 16 June 2001 23:06, Rik van Riel wrote:
> > On Sat, 16 Jun 2001, Daniel Phillips wrote:
> > > As a side note, the good old multisecond delay before bdflush kicks in
> > > doesn't really make a lot of sense - when bandwidth is available the
I've recently been getting strange system lock-ups - often my system
just dies, but occasionally I get messages in dmesg. I've tried to
isolate the problem by increasing the available swap (I now have > 2x
RAM), removing my reiserfs partitions (I'm now running with ext2) and
downgrading from kerne
On Sun, 17 Jun 2001, SATHISH.J wrote:
> Hi,
>
> Every file system has a magic number. Can you please tell me what for this
> magic number is used. When do we really use this unique magic number of
> the file system and why?
find . -name *.[chS] >/tmp/list
xargs http://vger.kernel.org/majordom
On Sun, 17 Jun 2001, SATHISH.J wrote:
> Hi,
> Every file system has file_system_type structure defined. Where else this
> structure is referred. Does register_filesystem() refer this structure.
> Does sys_mount refer to this structure by any means?
Umm... No offense, but
* all of these
Hi,
Bill Pringlemeir wrote:
>
> I have been looking at the emu10k1 driver and I had a few questions
> about general idioms used there.
Warning I've not looked at that particular driver and would concider
myself a Linux kernel newbie. 20 years kernel hacking but only 9
months Linux with two driv
Hi,
Every file system has file_system_type structure defined. Where else this
structure is referred. Does register_filesystem() refer this structure.
Does sys_mount refer to this structure by any means?
Please help me with the info.
Thanks in advance,
Regards,
sathish.j
-
To unsubscribe from
Hi,
Every file system has a magic number. Can you please tell me what for this
magic number is used. When do we really use this unique magic number of
the file system and why?
Thanks in advance.
With Regards,
sathish
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Hi,
Sorry to disturb you all.
In the d_alloc() function in the vfs layer of the filesystem(2.2.14
kernel) we can see the following:
dentry->d_mounts = dentry;
dentry->d_covers = dentry;
Why should both the above be assigned the values of dentry. Wher elase is
this used
87 matches
Mail list logo