This is simply not true. I run xfs on three systems - none of which have
anything close to the latest cpu. Each system runs faster after
installing xfs. Since linux-kernel is not the place for advocacy I
suggest a comparison be for your particular setup to determine which is
best for
systems - none of which have
anything close to the latest cpu. Each system runs faster after
installing xfs. Since linux-kernel is not the place for advocacy I
suggest a comparison be for your particular setup to determine which is
best for you.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe
perior audio driver. I understand that the
it will become the default kernel driver.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-
driver. I understand that the
it will become the default kernel driver.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
is in /etc/rc.d/rc.inet2.
I'm not sure this is your problem. If you installed slackware new without
upgrading this probably isn't the answer.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
.
I'm not sure this is your problem. If you installed slackware new without
upgrading this probably isn't the answer.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
eem a little like the problems occurring with lvm right now?
A separate tree maintained with the maintainers not wanting others
submitting patches that conflict with their particular tree? It seems
that any project should be able to submit any patch against The One True
Tree: Linus' tree.
James Rich
lvm right now?
A separate tree maintained with the maintainers not wanting others
submitting patches that conflict with their particular tree? It seems
that any project should be able to submit any patch against The One True
Tree: Linus' tree.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from
used (and I
think we may be at that point) and then use .Xdefaults (.Xresources or
whatever) to allow site overrides. And I really do think .Xdefaults and
not .xconfigrc or something. I've already got enough .files and I like
the syntax of .Xdefaults.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from
) and then use .Xdefaults (.Xresources or
whatever) to allow site overrides. And I really do think .Xdefaults and
not .xconfigrc or something. I've already got enough .files and I like
the syntax of .Xdefaults.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubs
On Thu, 8 Mar 2001, Jesse Pollard wrote:
> james rich <[EMAIL PROTECTED]>:
> > On Wed, 7 Mar 2001, Tom Sightler wrote:
> >
> > > 2. Does linux have any problems with large (500GB+) NFS exports, how about
> > > large files over NFS?
> > >
> &
On Thu, 8 Mar 2001, Jesse Pollard wrote:
james rich [EMAIL PROTECTED]:
On Wed, 7 Mar 2001, Tom Sightler wrote:
2. Does linux have any problems with large (500GB+) NFS exports, how about
large files over NFS?
3. What filesystem would be best for such large volumes? We
he time I've used XFS.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
nated patching around don't buy us anything except continued
> "don't use Linux as NFS server" reputation.
If you need journaled file systems and NFS I have been using XFS and it
seems to be fine when exported over NFS (Yes I know it isn't in the main
kernel - hopefully that changes so
(.text+0x170ef): undefined reference to `key_maps'
make[1]: *** [kallsyms] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4-xfs/linux'
make: *** [vmlinux] Error 2
Any ideas what is wrong?
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-k
(.text+0x170ef): undefined reference to `key_maps'
make[1]: *** [kallsyms] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4-xfs/linux'
make: *** [vmlinux] Error 2
Any ideas what is wrong?
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-k
erver" reputation.
If you need journaled file systems and NFS I have been using XFS and it
seems to be fine when exported over NFS (Yes I know it isn't in the main
kernel - hopefully that changes soon).
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscri
I thought I read on the TODO list that the problems regarding lilo configs
such as:
append="ether=5,0x300,,,eth1"
had been resolved. On my machine that is not true (dual ppro with
supermicro mobo). I have a 3c509 and a netgear fa 310tx. With the above
line in my lilo.conf the 3com should get
I thought I read on the TODO list that the problems regarding lilo configs
such as:
append="ether=5,0x300,,,eth1"
had been resolved. On my machine that is not true (dual ppro with
supermicro mobo). I have a 3c509 and a netgear fa 310tx. With the above
line in my lilo.conf the 3com should get
19 matches
Mail list logo
