Gabriel Rocha wrote:
> you could always compile on one machine and nfs mount the /usr/src/linux
> and do a make modules_install from the nfs mounted directory...
The way I've always managed this sort of thing is to tar up your kernel source,
transfer it to the "compile box" however you please, t
> > When I mount the filesystem to check it out, nothing appears to have
> > anything open on the filesystem. So why am I not able to flush it
> > clean?
>
> Because of a bug present in Linus tree. Try this patch:
Thanks, that seems to have fixed it. There's something else I'm curious about
tho
> If you have a directory called /initrd, in your root file-system,
> you may find that the old initrd is still mounted:
>
> Script started on Mon Jun 18 17:22:20 2001
> # ls /initrd
> bin dev etc lib linuxrc sbin
> # umount /initrd
> # ls /initrd
> # exit
> exit
> Script done on Mon Jun 18 1
At this point, I'm trying to get an initrd working properly. So far, it
works, the system boots, etc. etc., but whenever I try to do a "blockdev
--flushbufs /dev/ram0", I get "device or resource busy"
When I mount the filesystem to check it out, nothing appears to have
anything open on the files
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,
> Hey all,
> I just had an eepro/100 S delivered to me. I haven't dug through specs
> yet, but has anyone looke at this? Supposedly has a 3DES ASIC built in to
> the core.
>
> Any way we can use it?
Good question. I've been wondering how exactly that ASIC would even benefit
Windows users.
Sho
> While I could
> fix this myself manually (and plan to do so), it would be nice to get
> the developer's blessing on this, and also nice to know exactly what
> version number to give this driver in 2.4.5 stock.
F**k me, forget I asked about the version. I just read a little further down
in the
Apologies if this has been posted before. I imagine it has.
In kernel 2.4.5 stock, ov511.c fails to compile. A little intelligent
searching through 2.4.4 source reveals that the following line in 2.4.4:
static const char version[] = "1.28";
is missing in 2.4.5, and this is why it does not com
8 matches
Mail list logo
