> style(9) is not KNF, and never was intended to be. It's a FreeBSD style
> guide that bears similarity to KNF because that's what it used as a
> starting point.
I think we can safely presume that Bruce has been overruled on this
one. If the collective definition is different than his, and it se
> > Driver is readonly, specialy developed for freebsd,
> > supports most of NTFS's features.
> > Source is at http://iclub.nsu.ru/~semen/ntfs/
>
> Sounds like a good idea. Do you have a reviewer?
I'm looking at it now for 4.0-C.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To
"John W. DeBoskey" wrote in message ID
<199901271433.jaa75...@bb01f39.unx.sas.com>:
>A note of thanks to Jordan and everyone else who's been working
> on the new 4.0 code... We have our first complete processing of
> cd /usr/src && make world && cd release && make release.
Unfortunately the AX
I saw it several times with very recent -current
--
Andrey A. Chernov
a...@null.net
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Hello!
Where I can find snapshot for -stable & -current? I've tried
current.freebsd.org, but 'cd /pub/FreeBSD' says 'Permission denied'.
And there is nothing at
ftp://ftp.freebsd.org/pub/FreeBSD/release/snapshots/i386
-
Russell L. Carter wrote:
> Come on John, this has *meaning*. For or against -Wall
> *stands* for something! We have constitutional procedures
> to solve this thing!
The "constitutional procedures" just stomp on things because the
few who complain the loudest drown out those who silently or
not
Matthew Dillon once stated:
=The changes seem pretty reasonable, to me. I don't see why you are
=so rabid about not allowing a few extra braces for clarity. It
=would make the code more readable.
Somehow, this just reminded me of the US Communication Decency Act,
where indecency was d
On Thursday, 28 January 1999 at 21:43:41 -0800, Julian Elischer wrote:
>
>
> On Fri, 29 Jan 1999, Greg Lehey wrote:
>
>> On Friday, 29 January 1999 at 16:26:53 +1100, John Birrell wrote:
>>
>> I'm sure they might. But they'd be wrong. I do believe that
>> maintaining a coherent style is a Good Th
On Fri, 29 Jan 1999, Greg Lehey wrote:
> On Friday, 29 January 1999 at 16:26:53 +1100, John Birrell wrote:
>
> I'm sure they might. But they'd be wrong. I do believe that
> maintaining a coherent style is a Good Thing. I just dislike the
> particular style, but since it doesn't significantly
On Thu, Jan 28, 1999 at 09:39:36PM -0700, Nate Williams wrote:
> > Encouraging unreadable code is something I find highly questionable.
>
> I find the KNF style highly readable. As a matter of fact, I find the
> extra parentheses *often* to be a bunch of noise.
>
> And, as Bruce implied, if you
The changes seem pretty reasonable, to me. I don't see why you are
so rabid about not allowing a few extra braces for clarity. It would
make the code more readable.
Besides, a great deal of the preexisting code already uses braces
even in single statement if()'s... and a g
[...]
%We spend so much of our time looking up our own collective asses searching
%for the meaning of life that it is no wonder FreeBSD doesn't feel like it
%has a clear direction for the future. All people seem to want to do is
%stomp on others who try to contribute something.
Come on John, thi
On Friday, 29 January 1999 at 16:26:53 +1100, John Birrell wrote:
> Greg Lehey wrote:
>> I don't think they're a good idea. Sure, I don't like style(9), but
>> if we're going to overhaul it, we should do it properly. Given the
>> diversity of opinion expressed every time anybody has tried the
>>
Greg Lehey wrote:
> I don't think they're a good idea. Sure, I don't like style(9), but
> if we're going to overhaul it, we should do it properly. Given the
> diversity of opinion expressed every time anybody has tried the
> smallest change, I don't see that happening, so why don't we just
> forg
Somebody just drew my attention to /usr/src/Makefile:
# Unless -DNOAOUT is specified, a `make world' with OBJFORMAT=elf will
# update the legacy support for aout. This includes all libraries, ld.so
# and boot objects. This part of build should be regarded as
# deprecated and you should _not_ expec
On Thursday, 28 January 1999 at 19:41:29 -0800, Julian Elischer wrote:
>
> On Fri, 29 Jan 1999, Bruce Evans wrote:
>> style(9) is supposed to document KNF. It is not supposed to document
>> best coding practices, julian's preferences or bde's preferences.
>
> KNF is not a static thing that cannot
Christopher Masto once stated:
=suggestions, they should be useful suggestions. "Parenthesis are
=allowed to make your code easier to read, even if not strictly
=required by the compiler" is a much more useful suggestion than what
=is currently there.
Some safeguard should be put to prevent fall
Daniel C. Sobral wrote:
> Mike Smith wrote:
> > boot0 is the module that gives you the F? prompt
>
> What F? prompt???
The boot manager menu, for example
F1 FreeBSD
F2 UNIX
F5 Drive 1
Default: F1
> > boot1 is invisible, it just loads boot2
> > boot2 spins the | to begin
> : Any other strategy will, eventually, have you
> : charging around the crowd, waving your golf club and slobbering
> : maniacally - not really the kind of public image you want to be
> : cultivating here. :-)
>
> Given that there is a good potential to introduce bugs, the age old
> "have anothe
> The apparent infallability of code and historical documents anyone
> tries to update suggests that the Pope was involved with CSRG.
No, but in general the combined experience of the CSRG folks is greater
than most of the programmers here.
> Encouraging unreadable code is something I find highly
In message <19990128230223.a1...@netmonger.net> Christopher Masto writes:
: Encouraging unreadable code is something I find highly questionable.
Sadly, unreadable is in the eyes of the beholder. Code style is a
highly religious and contentious issue...
Warner
To Unsubscribe: send mail to major
> The resounding responce SO FAR (except for you) has been either
> "I don't really care about those changes" or "YES please!"
I've heard 3 'yes' votes, and I've abstained from commenting at this
time because I got beat up last time I mentioned something.
Nate
To Unsubscribe: send mail to majo
In message
Julian
Elischer writes:
: so far you are the first and only objector..
: which makes you outnumbered by 10 to 1 on email counts..
Unless things have changed a lot, bde counts 50x most people. This
isn't a democracy.
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "uns
Rod Taylor writes:
> 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 t
In message <83910.917513...@zippy.cdrom.com> "Jordan K. Hubbard" writes:
: Any other strategy will, eventually, have you
: charging around the crowd, waving your golf club and slobbering
: maniacally - not really the kind of public image you want to be
: cultivating here. :-)
I'm sure there are ma
On Friday, 29 January 1999 at 7:54:18 +1100, Peter Jeremy wrote:
> Luigi Rizzo
>> 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 --
On Fri, Jan 29, 1999 at 02:26:51PM +1100, Bruce Evans wrote:
> >My mail system appears to have accidentally deleted your excellent and
> >well-considered reasons for not allowing style(9) to say "it's OK to
> >use extra braces or parenthesis when it makes your code more
> >comprehensible".
>
> Per
Bruce Evans wrote:
[..]
> >Perhaps you could repeat it?
>
> style(9) is supposed to document KNF. It is not supposed to document
> best coding practices, julian's preferences or bde's preferences.
style(9) is not KNF, and never was intended to be. It's a FreeBSD style
guide that bears similarit
+[ Julian Elischer ]-
|
| On Fri, 29 Jan 1999, Bruce Evans wrote:
| > style(9) is supposed to document KNF. It is not supposed to document
| > best coding practices, julian's preferences or bde's preferences.
|
| KNF is not a static thing that cann
On Fri, 29 Jan 1999, Bruce Evans wrote:
> style(9) is supposed to document KNF. It is not supposed to document
> best coding practices, julian's preferences or bde's preferences.
KNF is not a static thing that cannot be changed.
KNF is in effect whatever is written in style(9).
In case I hadn't
Mike Smith wrote:
>
> Ugh. No. BTX is the kernel that boot2 and the loader use.
Well, that much I knew... It's just that I took to calling boot2 as
"btx"... :-)
> boot0 is the module that gives you the F? prompt
What F? prompt???
> boot1 is invisible, it just loads boot2
> boot2 spins the |
>> Of course I object.
>
>My mail system appears to have accidentally deleted your excellent and
>well-considered reasons for not allowing style(9) to say "it's OK to
>use extra braces or parenthesis when it makes your code more
>comprehensible".
Perhaps it is in some of your backups from 5 years
On Thu, 28 Jan 1999, John Polstra wrote:
> In article ,
> Julian Elischer wrote:
> > so far you are the first and only objector..
> > which makes you outnumbered by 10 to 1 on email counts..
>
> Uh, votes last longer than 8 hours around here. You should give
> people 3 days minimum to respon
+[ Julian Elischer ]-
| yeah but not a SINGLE person has said to not commit the patch to style(9)
| so I'm going to do it later tonight..
| (It doesn't make extra braces MANDATORY but it does ALLOW them.)
|
| julian
| (if this doesn't bring some NEYs
In article ,
Julian Elischer wrote:
> so far you are the first and only objector..
> which makes you outnumbered by 10 to 1 on email counts..
Uh, votes last longer than 8 hours around here. You should give
people 3 days minimum to respond. We don't all have pagers hooked
up to our mail systems
On Wed, 27 Jan 1999, IdiotSwitch Editor wrote:
> I can't code, so I wouldn't know how to implement these. Or even if it's
> possible.
>
> Parallel device loading. I know that freebsd's boot sequence can continue
> loading new devices while waiting for other devices to respond with irq's
> and
I can't code, so I wouldn't know how to implement these. Or even if it's
possible.
Parallel device loading. I know that freebsd's boot sequence can continue
loading new devices while waiting for other devices to respond with irq's
and whatnot. However, could this be taken a step further and hav
so far you are the first and only objector..
which makes you outnumbered by 10 to 1 on email counts..
On Fri, 29 Jan 1999, Bruce Evans wrote:
> >yeah but not a SINGLE person has said to not commit the patch to style(9)
>
> Of course I object.
>
> >so I'm going to do it later tonight..
>
> If
On Fri, Jan 29, 1999 at 01:25:07PM +1100, Bruce Evans wrote:
> >yeah but not a SINGLE person has said to not commit the patch to style(9)
>
> Of course I object.
My mail system appears to have accidentally deleted your excellent and
well-considered reasons for not allowing style(9) to say "it's O
>yeah but not a SINGLE person has said to not commit the patch to style(9)
Of course I object.
>so I'm going to do it later tonight..
If you commit it, then I will back it out.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the messag
:that day on, I never put assignments in conditionals with an explicit
:boolean test, aka if ((a = b) != 0) { ... }.
Oops, I meant 'without an explicit boolean test'.
-Matt
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscrib
yeah but not a SINGLE person has said to not commit the patch to style(9)
so I'm going to do it later tonight..
(It doesn't make extra braces MANDATORY but it does ALLOW them.)
julian
(if this doesn't bring some NEYs I'll be amazed..)
On Thu, 28 Jan 1999, Mike Smith wrote:
> > Beyond that it
> Beyond that it's pretty much just &/| and &&/|| precedences. I personally
> *never* liked the fact that C gave & and | ( and && and || ) differentl
> precedences. IMHO, the arithmatic-vs-shift parenthesization is something
> I've *always* done myself, so I don't mind those warni
:Yes, that's true... but on balance I (personally) find it's worth
:the tradeoff.
:
:On the other hand, I can't stand the GNU coding style..
:
:-Archie
:
:___
:Archie Cobbs * Whistle Communications, Inc. * http://www.whi
:>
:> More then judicious use -- inlines are an incredible advantage. Most
:> people don't realize that GCC will optimize constant arguments through
:> an inline call. Try this:
:>
:> static __inline
Yah, and if it's static it will not even output code for fubar.
I've neve
Matthew Dillon wrote:
> :Luigi Rizzo
> :>not speaking about vinum, but to me, the indentation of 8 char and
> :...
> :
> :According to most of the coding standards I've read, readability
> :(and hence maintainability) come before efficiency. That said, I
> :agree that efficiency _is_ an issue wit
Nate Williams writes:
> > I hope that wording is sufficiently unoffensive to the -Wall haters.
>
> '-Wall haters'. That almost sounds like 'Wall-flowers' or something. :)
:-)
> Agreed, but that's not the only reason I dislike '-Wall'. The other
> reason is that some of the warnings enabled in
>
> Are there any disagrees with an idea to commit a NTFS
> driver into current:
>
> I can commit/maintain driver mentioned at
> http://www.freebsd.org/projects/
>
> Driver is readonly, specialy developed for freebsd,
> supports most of NTFS's features.
> Source is at http://iclub.nsu.ru/~semen
> > 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
:Luigi Rizzo
:>not speaking about vinum, but to me, the indentation of 8 char and
:...
:
:According to most of the coding standards I've read, readability
:(and hence maintainability) come before efficiency. That said, I
:agree that efficiency _is_ an issue within the kernel's critical
:paths (th
> 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 :-)
On 28-Jan-99 Ollivier Robert wrote:
> According to Luke:
>> This is 4.5b1 communicator, and locks up X often enough I dont use it.
>
> Beta versions of 4.5 were bad (in that case b2 was far worse than b1)
> whereas 4.5 release is more or less stable. (it still crashes from time to
> time but not
On 28-Jan-99 Ollivier Robert wrote:
> According to Luke:
>> linux_lib port. [why does it install into / anyways]
>
> The standard sysinstall has been making a link into /usr/compat for months
> if not years :-)
Some people haven't used sysinstall for years :>
E-Mail: Luke
Sent by XFMai
: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 ha
According to Luke:
> This is 4.5b1 communicator, and locks up X often enough I dont use it.
Beta versions of 4.5 were bad (in that case b2 was far worse than b1)
whereas 4.5 release is more or less stable. (it still crashes from time to
time but not that often).
--
Ollivier ROBERT -=- FreeBSD:
According to Luke:
> linux_lib port. [why does it install into / anyways]
The standard sysinstall has been making a link into /usr/compat for months
if not years :-)
revision 1.193
date: 1997/07/16 11:45:48; author: jkh; state: Exp; lines: +5 -1
ln /compat to /usr/
Would it be possible to add an exponential delay when connecting fails for
either reason?
I just received my specified phone-bill. It filled 42 pages, with hundreds
of calls with a duration of 17 seconds. (Because my modem needs to be
software-reset; I have mentioned this before).
Each call costs
On Thu, 28 Jan 1999, Kenneth D. Merry wrote:
> > Just symlink eth0 to which card you like, just as /dev/mixer happens to be
> > a symlink to /dev/mixer1 on my system.
>
> How are you going to do that, when network drivers don't have device nodes?
>
Minor point :-)
Sorry, I missed that.
Leif
> 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,
...
> You might be refering to the loader prompt, not the btx prompt. If
> you type something as soon as the first "|"
+[ Nate Williams ]-
| > | :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.
Wilko Bulte wrote:
> > Well, for one its sucks trying to get newbies to work out what their
> > network card is
> > called..
> Not true IMO. You still need to know what hardware you have before you can
> build your
> own kernels etc etc.
Yes, this is true, but when they have just installed then i
Hello,
I thought I would upgrade my system to the latest -current
(as of a few days ago) so I could try the LinuxThreads stuff out.
I was running a -current of around November last year. I had no
problems upgrading my ELF userland and the bootblocks (my old aout
kernel boots fine), but when I try
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.
...snip
> Tried to get help in #freebsd in efnet, but no-one had suggestions that
> helped me... (Thanks anyhow Xanne)
compile
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
> 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
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 n^
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 i
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
Julian Elischer 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 for control
As David Wolfskill wrote...
> >From: Wilko Bulte
> >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.
Luigi Rizzo
>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
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: dwh...@re
subscribe
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
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
> 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 o
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 tha
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 f
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
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 ma
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
"Daniel C. Sobral" 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
} > I have
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 i
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 b
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 anyth
>From: Wilko Bulte
>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 you want the n
< 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.
I went down to our reading room and examined 1003.2. It says quite
clea
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 an
: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. Polst
In article <199901280753.xaa98...@apollo.backplane.com>,
Matthew Dillon 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 it to behave the way i
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 p
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
> * From: Luke
>
> * 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
> hardc
> | :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 no
<
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 maintainable code.
> As a matter of fact, what's the rea
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 l
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...)
>> 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
On Wed, 27 Jan 1999, Garrett Wollman wrote:
> < 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 only auditing the basic I/
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 chan
1 - 100 of 163 matches
Mail list logo
