On Thu, 28 Jan 1999 00:34:30 +0100, Mattias Pantzare wrote:
Why _not_ use -C? What is the point in replacing a file with the same file?
install -C will replace the file if the new file is diffrent.
Aaaah, thank you. I misread the manpage description of -C and didn't
notice and the files
On Wed, 27 Jan 1999 18:42:03 CST, Zach Heilig wrote:
It does update the 'ctime' entry of ld-elf.so.1, so using 'find /usr
\! -ctime 1 -print' right after make world will find all the old
files.
That's fine, then. I figured install -C wouldn't adjust ctime for files
that hadn't changed.
In message 199901280222.vaa14...@khavrinen.lcs.mit.edu, Garrett Wollman
writes:
On Wed, 27 Jan 1999 18:00:54 -0800 (PST), Archie Cobbs arc...@whistle.com
said:
Please do go ahead and update it.. the experts agree!
I haven't seen any experts involved in this discussion yet. It's
probably
:Just curious.. why do you need the (int) cast?
Actually, it could very well be that I don't. I didn't want to spend
the time to check to see if the compiler warned on unsigned-char array
indexes.
When you add casts to quite warnings, please use the minium number of
them.
It would be nice if style(9) documented the options to give indent(1)
to match the `approved' layout convections. (This would reduce the
effort involved in importing large chunks of code).
This is impossible, since indent(1) is buggy and out of date with both
KNF and C.
Well, you can do a
From my uderstanding, SYSINIT should always point to a function with a
CONST argument because the argument is fixed as a constant at link/compile
time.
what functions don't expect a const? and why not?
or am I mising something?
julian
To Unsubscribe: send mail to majord...@freebsd.org
with
:
:From my uderstanding, SYSINIT should always point to a function with a
:CONST argument because the argument is fixed as a constant at link/compile
:time.
:
:what functions don't expect a const? and why not?
:
:or am I mising something?
:
:julian
Most of the functions do not expect a const
On Thursday, 28 January 1999 at 19:19:12 +1100, Bruce Evans wrote:
It would be nice if style(9) documented the options to give indent(1)
to match the `approved' layout convections. (This would reduce the
effort involved in importing large chunks of code).
This is impossible, since indent(1)
Matt,
By now we do know a GREAT deal about you from the way you behave.
Trying to judge your age from that data, 16 years can certainly not
be ruled out conclusively.
I will make no secret of the fact that I was not at all happy with
you becoming a committer, and your behaviour the last
+[ Matthew Dillon ]-
|
| :I think that style(9) should be modified to include
| :Parenthesis may be used to improve the readbility of complex
| :expressions even if not strictly required.
| :instead of the stupid phrase presently there.
| :also:
|
On Thu, Jan 28, 1999 at 06:05:37PM +1030, a little birdie told me
that Greg Lehey remarked
On Thursday, 28 January 1999 at 14:16:25 +1100, Bruce Evans wrote:
It would be nice if style(9) documented the options to give indent(1)
to match the `approved' layout convections. (This would reduce
On Thu, 28 Jan 1999, John Birrell wrote:
Nate Williams wrote:
Anyway, if we're going to -Wall'ify the kernel (as we should)
then we need to update sytle(9) to reflect that.
In fact, style(9) should say:
If at all possible, your code should compile without warnings
when
On Wed, 27 Jan 1999, Matthew Dillon wrote:
: then we need to update sytle(9) to reflect that.
:
: In fact, style(9) should say:
:
: If at all possible, your code should compile without warnings
: when the gcc -Wall flag is given.
:
:I disagree. As has been shown many times in the
How Mr. ignoromous Nate could construe this to mean that I was trying
to brush something under the rug is beyond me. As I said to Julian,
I probably shouldn't have made the committ, but the fact is that I
not only left the module on my hotlist, I also immediately brought
:Matt,
:
:By now we do know a GREAT deal about you from the way you behave.
:
:Trying to judge your age from that data, 16 years can certainly not
:be ruled out conclusively.
:
:I will make no secret of the fact that I was not at all happy with
:you becoming a committer, and your behaviour the
If it is decided that Fortran support will disappear from the base
system and nobody else wants to maintain g77, I will gladly do it.
However, I will only maintain a version that I am using so that means I
will maintain a port once gcc 2.8 is officially brought in as the stock
compiler.
Lets
On Thu, 28 Jan 1999, Matthew Dillon wrote:
Most of the functions do not expect a const argument, though that
may simply be because they didn't bother to use const when they
could have.
However, I know at least the MALLOC initialization objects *can't*
use const
Getting g77 from egcs is the best option right now. However, it seems to
me that this adds a lot of bloat (duplication of C, C++, etc.) to the
system for someone wanting to use FreeBSD as a scientific workstation
platform.
Then update the g77 port to fetch egcs-core-XYZ.tar.gz and
Matt,
Please leave your keyboard now.
Get some sleep, some rest and a couple of days off.
You need it, we need it.
Poul-Henning
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org Real hackers run -current on their laptop.
FreeBSD -- It will take a long
On Wed, 27 Jan 1999, Matthew Dillon wrote:
Right now we have a problem with struct sysinit.
The problem is that some SYSINIT functions supply a function taking
a const void * and a const pointer for data, and other SYSINIT
functions supply a function taking a void * and a
I agree.. and same thing goes for Ethernet drivers. I actually
like the way Linux always has eth0, eth1, ... (which we could
Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
just a matter of taste or is there more to it? I for one don't see any
advantage in
Why _not_ use -C? What is the point in replacing a file with the same file?
install -C will replace the file if the new file is diffrent.
Aaaah, thank you. I misread the manpage description of -C and didn't
notice and the files are the same...
Cleared up, head back on straight. :-)
This
:
:Overloading a struct? Yuck :(
:
:
: So the above cool hack will not work :-(.
:
:Overloading is just a bad hack in concept.
Tell me something I don't know. If it were simple and straightforward,
I'd have simply committed it.
-Matt
:
On Thu, 28 Jan 1999, Harlan Stenn wrote:
Also the eth[0..x] thing means you can replace your ethernet card with a
new one of a different type without having to look through your config
code for references to ed0 or whatever.
Just to ask, what happens when the probe order changes and your
On Thu, 28 Jan 1999, Leif Neland wrote:
On Wed, 27 Jan 1999, Archie Cobbs wrote:
Doug Rabson writes:
And another thing. Why can't we use a non-driver-specific name for the
disk? Most users simply don't care whether the driver was fd, wfd, wd or
anything. They just want to get
I see no evidence of this. vinum sources don't seem to have a single
line in KNF, except accidentally. They have an indentation of 4
instead of 8, lots of per-statement comments, lots of lines longer
than 80 characters, lots of block comments without `/*' and `*/' on
a line by themself, ...
Please do go ahead and update it.. the experts agree!
I haven't seen any experts involved in this discussion yet. It's
probably after bedtime down there in oz.
It's been discussed before and agreed upon.
There was only agreement long ago when the BSD4.4 /usr/src/admin/style
was converted to a
:On Thu, 28 Jan 1999, Matthew Dillon wrote:
:
:OK I understand now..
:theoretically I guess you should have two types of SYSINIT,
:however you are already not able to check the TYPE of the argument due to
:it being passed through the void form, so losing the 'const'-ness is not
:that much of a
Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I
attempted to boot into my 3.0-STABLE system. However, as soon as the kernel
starts to boot I get
panic: cpu class not configured
and the machine reboots (and so on...)
Is this cpu supported?
Thanks,
Mike
--
Mike
:In cases, -Wall is bogus anyway. Here's one:
:foo.c:89: warning: char format, void arg (arg 2)
:void *region;
:printf(mem open failed: %s\n, region);
:
:According to standards, a void pointer may be freely used instead of any
:other type of pointer, both as an lvalue and
On Thu, 28 Jan 1999, Poul-Henning Kamp wrote:
In message 199901280222.vaa14...@khavrinen.lcs.mit.edu, Garrett Wollman
writes:
On Wed, 27 Jan 1999 18:00:54 -0800 (PST), Archie Cobbs
arc...@whistle.com said:
Please do go ahead and update it.. the experts agree!
I haven't seen any
On Wed, 27 Jan 1999, Matthew Dillon wrote:
bug in nfs_access(). nfs/nfs_vnops.c, line 414 or so.
Fixed!
This is a nasty one. I'm surprised it hasn't caused grief before
I can't see the problem in this code. What was the bug?
--
Doug Rabson Mail:
:
:On Wed, 27 Jan 1999, Matthew Dillon wrote:
:
: bug in nfs_access(). nfs/nfs_vnops.c, line 414 or so.
:
: Fixed!
:
: This is a nasty one. I'm surprised it hasn't caused grief before
:
:I can't see the problem in this code. What was the bug?
--- nfs_vnops.c 1999/01/27 22:45:13
pcm is again working correctly with the Yamaha YMF715 based sound system
of my laptop.
It had been working fine up till shortly before secure/libcrypt broke on
-current.
Then I had an array of strange problems.
After testing and logging the various failures with cat, mpg123,
xanim, rvplayer,
not speaking about vinum, but to me, the indentation of 8 char and
line length of 80 chars are almost mutually exclusive.
See e.g. tcp_input.c ip_input.c and many network device drivers as
an example -- basically all places where, for efficiency reasons,
the code tries to expand in-line various
On Wed, 27 Jan 1999, Matthew Dillon wrote:
bug in nfs_access(). nfs/nfs_vnops.c, line 414 or so.
Fixed!
This is a nasty one. I'm surprised it hasn't caused grief before
Never mind, I just read the commit message and managed to actually see the
mistake. I hate those ones...
an example -- basically all places where, for efficiency reasons,
the code tries to expand in-line various block, the depth of
indentation pushes everything to the right end leaving only 20-30
useful chars per line.
See the Linux style guide (linux/Documentation/CodingStyle) for
strong
On Thu, 28 Jan 1999, Matthew Dillon wrote:
:
:On Wed, 27 Jan 1999, Matthew Dillon wrote:
:
: bug in nfs_access(). nfs/nfs_vnops.c, line 414 or so.
:
: Fixed!
:
: This is a nasty one. I'm surprised it hasn't caused grief before
:
:I can't see the problem in this code.
On Thursday, 28 January 1999 at 20:39:03 +1100, Bruce Evans wrote:
not speaking about vinum, but to me, the indentation of 8 char and
line length of 80 chars are almost mutually exclusive.
See e.g. tcp_input.c ip_input.c and many network device drivers as
an example -- basically all places
Mike Zanker wrote:
Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I
attempted to boot into my 3.0-STABLE system. However, as soon as the kernel
starts to boot I get
panic: cpu class not configured
and the machine reboots (and so on...)
Is this cpu
On Thu, 28 Jan 1999, Mike Zanker wrote:
Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I
attempted to boot into my 3.0-STABLE system. However, as soon as the kernel
starts to boot I get
panic: cpu class not configured
and the machine reboots (and so on...)
In cases, -Wall is bogus anyway. Here's one:
foo.c:89: warning: char format, void arg (arg 2)
void *region;
printf(mem open failed: %s\n, region);
Yes, it should say warning: char * format, void * arg (arg 2).
According to standards, a void pointer may be freely used
On Wed, 27 Jan 1999, Brian Somers wrote:
To find out if this is the problem, can you try connecting
interactively. You should see the same delay. You can then try
again, but during the delay, pressing return a few times at the
prompt should wake ppp up. Is this happening ?
Well, I
At 09:53 28/01/99 , Karl Pielorz wrote:
AFAIK it is support - are you sure you had
cpu I686_CPU
In your kernel config?
Thanks, this is the problem - I've only got I586_CPU in my config. I *knew*
I should have kept a GENERIC kernel around!
Thanks to all who answered,
Mike
--
Mike
A warning is just that. It's not an error, so don't treat it like one.
I use different productions to enable different warnings on code with
different histories. For one thing, new revs of the compiler will
otherwise cause trouble when the warning behavior changes.
I also use -Werror.
Chuck Robey wrote:
I'm not sure if this argument is worth pushing anymore, because
FreeBSD's stability and usefulness has become much more well known, but
it did contribute at some point, and I think that is the idea that
Daniel was trying to convey.
Right?
Me? No... Maybe Garret... :-)
From my uderstanding, SYSINIT should always point to a function with a
CONST argument because the argument is fixed as a constant at link/compile
time.
what functions don't expect a const? and why not?
Probably most.
or am I mising something?
Only the initial value of the arg is determined at
On Wed, 27 Jan 1999 18:30:15 -0500 (EST), Robert Watson
rob...@cyrus.watson.org said:
It's not clear to me, when thinking of introducing a new file (say, for
auditing support :), what I should name it. Would it be kern_audit.c or
sys_audit.c?
Depends on what it is auditing. If it
They have an indentation of 4
instead of 8,
[.]
8 spaces is almost always *way* too much if a maximum of 80 columns
is expected. IMHO, the requirement should be to either use TABs and
only TABs or else two or more spaces.
Either way, perhaps it's time someone fixed indent(1) so that it
See the Linux style guide (linux/Documentation/CodingStyle) for
Looks like an oxymoron to me.
Bruce
--
Brian br...@awfulhak.org br...@freebsd.org br...@openbsd.org
http://www.Awfulhak.org
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majord...@freebsd.org
an example -- basically all places where, for efficiency reasons,
the code tries to expand in-line various block, the depth of
indentation pushes everything to the right end leaving only 20-30
useful chars per line.
See the Linux style guide (linux/Documentation/CodingStyle) for
So there are now 2 possibilities for this problem:
a) I was out of sync :(
b) Someone fixed ppp
Last nights commit was for RADIUS support in ppp. There was another
latency problem that I fixed about a week ago - maybe that was it :-)
--
# /AS/
* From: Luke l...@aus.org
* linux_lib port. [why does it install into / anyways]
You can put it anywhere and symlink to it, like sysinstall does now,
but it has to be called /compat (or some other well-known place)
because of the implementation. The string /compat/linux has to be
hardcoded in
Peter Jeremy wrote:
I'll support that. The example given in style(9):
a = b-c[0] + ~d == (e || f) || g h ? i : j 1;
should rate as an entry in the Obfuscated C competition rather than
an example of maintainable code.
As a matter of fact, what's the reasoning behind this
Bruce Evans wrote:
It would be nice if style(9) documented the options to give indent(1)
to match the `approved' layout convections. (This would reduce the
effort involved in importing large chunks of code).
This is impossible, since indent(1) is buggy and out of date with both
KNF and
Ok, people, heads up -- I'm about to commit a patch to /sys/i386
which changes the way FreeBSD uses the x86 LDT. Specifically,
I'm moving LUDATA_SEL from LDT entry 4 to 5 (Why 5? Why not?)
and re-using entry 4 as a call gate for SysV system calls made
by library stubs from Solaris 2.6 and
* From: John Polstra j...@polstra.com
* On 28-Jan-99 Bruce Evans wrote:
Hey John, are you sure your mailer is Y2K compliant?
Satoshi
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Some people when confronted by people wanting to have extra braces
say change style(9).
Well, here is my change..
I think theere is enough support for this that this should be discussed
seriously, and It's not like in the good old days, or
I'm not used to extra parenthesis are not going to be
Brian Somers wrote:
So there are now 2 possibilities for this problem:
a) I was out of sync :(
b) Someone fixed ppp
Last nights commit was for RADIUS support in ppp. There was another
latency problem that I fixed about a week ago - maybe that was it :-)
Yuck! (jumping in the air
At 10:13 28/01/99 , Mike Zanker wrote:
Thanks, this is the problem - I've only got I586_CPU in my config. I *knew*
I should have kept a GENERIC kernel around!
OK, I've been very, very silly and not kept a GENERIC kernel around and
cannot boot with my existing kernel. Is there some way of booting
On Thu, 28 Jan 1999, Mike Zanker wrote:
OK, I've been very, very silly and not kept a GENERIC kernel around and
cannot boot with my existing kernel. Is there some way of booting from
floppy (e.g. boot.flp from 3.0-RELEASE or 3.0-SNAP) and copying a GENERIC
kernel to my existing root
John Polstra j...@polstra.com wrote:
On 28-Jan-99 John Birrell wrote:
John Polstra wrote:
Hear ye, hear ye! Be it here noted and archived for all eternity that
on January 27, 1999 Pacific Time, John Polstra was, for one fleeting
moment, purer than Bruce! :-)
OK, so now we
I've just finished building my n'th release of -STABLE, and that dang boot
floppy is still too big. I know I came in on the trailing edge of the
discussion to change the whole boot thing, but after poking through a few
ideas, and testing them out, I came up with a few that might make for
a
On Thu, Jan 28, 1999 at 08:06:58PM +1100, Bruce Evans wrote:
Someday -C should avoid touching the file if possible, so that it
doesn't clobber the file's ctime and backups based on ctimes don't do
unnecessary work. This is possible if none of the attributes except
the file times would change,
On Wed, 27 Jan 1999, Garrett Wollman wrote:
On Wed, 27 Jan 1999 18:30:15 -0500 (EST), Robert Watson
rob...@cyrus.watson.org said:
It's not clear to me, when thinking of introducing a new file (say, for
auditing support :), what I should name it. Would it be kern_audit.c or
No. installworld more or less assumes single user.
This is really what I'm getting at. :-)
If installworld assumes single-user mode, why do we install -C
ld-elf.so.1 ? The first time I asked this question, I didn't mention
single-user mode and your answer was that it's to protect live
systems.
On Thu, 28 Jan 1999, Mike Zanker wrote:
Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I
attempted to boot into my 3.0-STABLE system. However, as soon as the kernel
starts to boot I get
panic: cpu class not configured
and the machine reboots (and so on...)
Is
Is there a way to view the contents of a text file (specifically,
/boot/loader.rc) with BTX? Now that there are all these nifty new modules,
my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way
I have my /boot/loader.rc setup is such that it unloads everythin
automatically
On Thu, 28 Jan 1999 19:56:37 +0900, Daniel C. Sobral d...@newsguy.com
said:
Peter Jeremy wrote:
I'll support that. The example given in style(9):
a = b-c[0] + ~d == (e || f) || g h ? i : j 1;
should rate as an entry in the Obfuscated C competition rather than
an example of
| :I think that style(9) should be modified to include
| :Parenthesis may be used to improve the readbility of complex
| :expressions even if not strictly required.
| :instead of the stupid phrase presently there.
| :also:
| :Braces around code blocks should be allowable even when not
* From: Luke l...@aus.org
* linux_lib port. [why does it install into / anyways]
You can put it anywhere and symlink to it, like sysinstall does now,
but it has to be called /compat (or some other well-known place)
because of the implementation. The string /compat/linux has to be
Mark Newton wrote:
Ok, people, heads up -- I'm about to commit a patch to /sys/i386
which changes the way FreeBSD uses the x86 LDT. Specifically,
I'm moving LUDATA_SEL from LDT entry 4 to 5 (Why 5? Why not?)
and re-using entry 4 as a call gate for SysV system calls made
by library stubs
Jaye Mathisen wrote:
This utility is too valuable for all the update not to at least have a
mention of it.
Thank you. :) The occasional compliment makes the hard work worthwhile.
At the very least, references should be made to it in /usr/src/Makefile as
part of the conversion
In article 199901280753.xaa98...@apollo.backplane.com,
Matthew Dillon dil...@apollo.backplane.com wrote:
Unfortunately, GCC isn't smart enough to match the function type
to the correct structure - it always stuffs it into the first structure.
Don't blame GCC. The C standard requires
:Anyway, GCC actually does have an extension that addresses this
:problem. See Labeled Elements in Initializers in the info pages.
:Note, this extension should NOT be used, in my opinion.
:
:John
:--
: John Polstra j...@polstra.com
: John D.
Hi,
I have finally corrected a long standing bug in the bt848 driver
with regard to selecting the SVIDEO input for true SVIDEO camera and for
the many normal cameras connected via the SVIDEO port (eg the bundled
hauppauge camera).
As a result some applications which select SVIDEO input sources
On Thu, 28 Jan 1999 05:48:31 +0200 (SAT), Robert Nordier
rnord...@nordier.com said:
| COMPATIBILITY
| The rm utility differs from historical implementations in that
| the -f option only masks attempts to remove non-existent
| files instead of masking a large variety of errors.
From: Wilko Bulte wi...@yedi.iaf.nl
Date: Wed, 27 Jan 1999 23:12:18 +0100 (CET)
Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
just a matter of taste or is there more to it? I for one don't see any
advantage in eth[0-9] style device naming.
It's a matter of whether
On Wed, 27 Jan 1999, Matthew Dillon wrote:
Could an Adaptec SCSI guru take a look at this code ? There's
probably some poor sob running EISA who's scratching his head right
now :-)
Hey!
Actually, my EISA box with a 1742 has been having weird lockups. Not sure
if that has
On Thu, 28 Jan 1999, Greg Lehey wrote:
On Thursday, 28 January 1999 at 20:39:03 +1100, Bruce Evans wrote:
See e.g. tcp_input.c ip_input.c and many network device drivers as
an example -- basically all places where, for efficiency reasons,
the code tries to expand in-line various block, the
Patrick Hartling wrote:
Is there a way to view the contents of a text file (specifically,
/boot/loader.rc) with BTX? Now that there are all these nifty new modules,
my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way
I have my /boot/loader.rc setup is such that it
Daniel C. Sobral d...@newsguy.com wrote:
} Patrick Hartling wrote:
}
} Is there a way to view the contents of a text file (specifically,
} /boot/loader.rc) with BTX? Now that there are all these nifty new modules,
} my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way
As sth...@nethelp.no wrote...
I agree.. and same thing goes for Ethernet drivers. I actually
like the way Linux always has eth0, eth1, ... (which we could
Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
just a matter of taste or is there more to it? I for
As Daniel O'Connor wrote...
On 27-Jan-99 Wilko Bulte wrote:
I agree.. and same thing goes for Ethernet drivers. I actually
like the way Linux always has eth0, eth1, ... (which we could
Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
just a matter of taste
As Jordan K. Hubbard wrote...
How Mr. ignoromous Nate could construe this to mean that I was trying
to brush something under the rug is beyond me. As I said to Julian,
I probably shouldn't have made the committ, but the fact is that I
not only left the module on my
On Thu, 28 Jan 1999, Julian Elischer wrote:
Some people when confronted by people wanting to have extra braces
say change style(9).
Amazingly there hasn't been a SINGLE comment!
(after a whole 8 hours!)
julian
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
Julian Elischer writes:
Some people when confronted by people wanting to have extra braces
say change style(9).
Well, here is my change..
You can count my vote.
I would also add a paragraph like this:
If possible code should complile cleanly with gcc's -Wall flag.
Note however that
Not true IMO. You still need to know what hardware you have before you
can build your own kernels etc etc.
Also the eth[0..x] thing means you can replace your ethernet card
with a new one of a different type without having to look through
your config code for references to ed0 or
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Ah, you mean like John McEnroe ? ;-)
Specifically NOT like John McEnroe. :-)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
subscribe
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
On Wed, 27 Jan 1999, Jordan K. Hubbard wrote:
Are there any plans to create another boot disk (cdrom.flp?), 2.88MB
in size especially for CD-ROM boots?
Yes.
Yummy. Reminds me of the atapi.flp fiasco a few years back. :-(
Doug White
Internet:
Luigi Rizzo lu...@labinfo.iet.unipi.it
not speaking about vinum, but to me, the indentation of 8 char and
line length of 80 chars are almost mutually exclusive.
See e.g. tcp_input.c ip_input.c and many network device drivers as
an example -- basically all places where, for efficiency reasons,
the
As David Wolfskill wrote...
From: Wilko Bulte wi...@yedi.iaf.nl
Date: Wed, 27 Jan 1999 23:12:18 +0100 (CET)
Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
just a matter of taste or is there more to it? I for one don't see any
advantage in eth[0-9] style device
Julian Elischer jul...@whistle.com wrote:
Well, here is my change..
I think it's a good move and I'll support it (FWIW).
@@ -256,13 +256,23 @@
.Ed
.Pp
Space after keywords (if, while, for, return, switch). No braces are
-used for control statements with zero or only a single statement.
+used
On Thu, 28 Jan 1999 sth...@nethelp.no wrote:
I agree.. and same thing goes for Ethernet drivers. I actually
like the way Linux always has eth0, eth1, ... (which we could
Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
just a matter of taste or is there
I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
(from the best that I can tell). Both are PCI.
I've attempted to use both cards in several PCI slots, under 2.2.8 and 3.0
boot floppies, and a 3.0-stable (updated 2 days ago). None of these
releases found either card
In libc_r, I don't think the code in uthread_kern.c's
_thread_kern_select() scales at all.
As the number of network connections (TCP) to my application grows, I
believe this routine takes longer and longer and my CPU goes to 100%
user space.
Something makes me believe that this routine has an
I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
(from the best that I can tell). Both are PCI.
They are supported in 4.0-CURRENT by the rl driver. I belive they are also
included in 3.0-STABLE, but I'm not sure if they are on the boot floppy.
And before using this
On Thu, 28 Jan 1999, Rod Taylor wrote:
I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
(from the best that I can tell). Both are PCI.
I've attempted to use both cards in several PCI slots, under 2.2.8 and 3.0
boot floppies, and a 3.0-stable (updated 2 days
1 - 100 of 163 matches
Mail list logo
