> > Looks like I'm volunteering to write a manpage for the net.inet
> > sysctls - or does one exist? - I sure as hell can't find it!
>
> :-), you put your keyboard in it now!!!
Yup,
well I need the pointy hat too. A grep through the man tree shows
references to various sysctl MIBs hidden all ov
[Charset iso-8859-1 unsupported, filtering to ASCII...]
>
>
> >
> > This is an ACK. I like those names, the idea is okay given that
> > the documentation for it reflects what has been discussed here in
> > this thread so folks can understand this is a very simple security
> > measure.
> Hmm, d
>
> Geoff Rehmet writes:
> > > : Not that easily.. how are you going to make ipfw
> dynamically know
> > > : which ports have listeners and which don't?
> > >
> > > By filtering all RST packets?
> >
> > My view was that this is much simpler than filtering packets -
> > never generate the packe
>
> This is an ACK. I like those names, the idea is okay given that
> the documentation for it reflects what has been discussed here in
> this thread so folks can understand this is a very simple security
> measure.
Hmm, dumb question for the day - where are things like "log_in_vain"
documente
Geoff Rehmet writes:
> > : Not that easily.. how are you going to make ipfw dynamically know
> > : which ports have listeners and which don't?
> >
> > By filtering all RST packets?
>
> My view was that this is much simpler than filtering packets -
> never generate the packet. My guess is that i
> I kinda like the idea of a top-level compat category; it will keep the
> top level uncluttered when sysv and iBCS compatibility start requiring
> their own knobs, and if you put linux at the top level this will later
> be used as justification for putting all the other "compat" stuff up
> there
> In message <[EMAIL PROTECTED]> Archie Cobbs writes:
> : Not that easily.. how are you going to make ipfw dynamically know
> : which ports have listeners and which don't?
>
> By filtering all RST packets?
That would be closer than my set of rules, but has the undesired effect
of filtering what
> In message <[EMAIL PROTECTED]> Archie
> Cobbs writes:
> : Not that easily.. how are you going to make ipfw dynamically know
> : which ports have listeners and which don't?
>
> By filtering all RST packets?
My view was that this is much simpler than filtering packets -
never generate the packe
> There isn't any "int-cvs-cur", so are you referring to maybe the
> International Crypto Repository run by Mark Murray out of SA?
Yes, he is :-).
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current
> Rodney W. Grimes writes :
> > >
> >
> > Now what would a box with so much security concern such that
> > it needed this knob be doing running an ftp session though
> > your point is valid and acceptable for low security boxes. And
> > I can see the real benifit that having this knob for t
On 17-Aug-99 Warner Losh wrote:
> : Not that easily.. how are you going to make ipfw dynamically know
> : which ports have listeners and which don't?
> By filtering all RST packets?
The defeats the purpose of having the computer not generate them in the first
place.. Well not totally I suppose,
* Doug ([EMAIL PROTECTED]) [990817 03:40]:
> In case anyone cares I'd like to put in a vote for compat.linux.
>From the design standpoint this balances the needs of prominence and clean
>top level name space nicely.
Count me as another in favor of Mike's explanation.
Like Mike said, there
In message <[EMAIL PROTECTED]> Archie Cobbs writes:
: Not that easily.. how are you going to make ipfw dynamically know
: which ports have listeners and which don't?
By filtering all RST packets?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the bo
> Last CTM delta in
> ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur
> is 'int-cvs-cur.0114.gz' from May 15 1999.
>
> There definitely was commits in International depository
> after 'may 15'.
Send me the address you want them to go to and I'll add you.
In message <[EMAIL PROTECTED]> Geoff Rehmet
writes:
: In default configuration, everything would behave as per
: normal, and you would have to set a sysctl MIB before the
: behaviour that I have described is displayed.
:
: Can anyone think of any reason why this feature should
: not be implement
In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> In case anyone cares I'd like to put in a vote for compat.linux.
>> >From the design standpoint this balances the needs of prominence and clean
>> top level name space nicely.
>
>And in case it's not clear from the exposition in my messag
In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> I think that is too obscure considering the exposure this will get.
>
>What "exposure"? It's a backend to a tuning interface for our ABI
>compatibility...
We will be judged on how well we run linux more than many other sane
factors in the f
Rodney W. Grimes writes :
> >
>
> Now what would a box with so much security concern such that
> it needed this knob be doing running an ftp session though
> your point is valid and acceptable for low security boxes. And
> I can see the real benifit that having this knob for those boxes
> w
On Tue, Aug 17, 1999 at 12:13:33AM -0400, Chuck Robey wrote:
> On Tue, 17 Aug 1999 [EMAIL PROTECTED] wrote:
>
> > Last CTM delta in
> > ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur
> > is 'int-cvs-cur.0114.gz' from May 15 1999.
>
> There isn't any "int-cvs-cur
> Hi,
>
> My understanding on your problems is:
> 1. Standby by PM timer in BIOS setting fails with the system activity.
If by fails you mean enters standby mode, then yes the computer enters
standby mode while the system is active, after the period of time set in
the bios, as long as no keys hav
Ok I just tried some other mods... the first was to hard-wire disk0 to
be bios device 0x8b. no-go. The second was to patch to 'continue' if it
missed a probe, and to limit the probe to the first 0x10 entries... for
example: 0x00-0x0f and 0x80-0x8f.
How is it that the old boot code works? Wha
On Tue, 17 Aug 1999 [EMAIL PROTECTED] wrote:
> Last CTM delta in
> ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur
> is 'int-cvs-cur.0114.gz' from May 15 1999.
There isn't any "int-cvs-cur", so are you referring to maybe the
International Crypto Repository run
On 17-Aug-99 Rodney W. Grimes wrote:
> Would I use it in place of ipfw for what the original person asked
> about, no way, not in a million years. If I want a box secure it
> is going to have ipfw or ipfilter rules down to the last detail.
> Why, well, it would prevent some junior admin from
>
> On 17-Aug-99 Rodney W. Grimes wrote:
> > I kinda like the idea of this, but can't that really just
> > be done easily with a few ipfw rules, the last two being
> > the important ones:
> >
> > for port in "22 53" ; do
> > ipfw add allow udp from any to ${myip} ${port}
> > ipf
I modified the biosdisk.c code as follows
(first part of function)
for (unit=0;unitbi_bios_dev)
break;
if ((unit == nbdinfo ) && (nbdinfo < MAXBDDEV) ) {
unit=initial_bootinfo->bi_bios_dev;
bdinfo[nbdinfo].bd_unit=unit;
bdinfo[nbdinfo].bd_flags=(unit <
> The 200-220 periodic files under daily expect that the directory
> /var/backups exist when they run to back up various files. If you
> delete this directory, the "cp" commands will error.
>
> There seems to be two ways to fix the files.
>
> 1. Add a "if [ ! -d $bak ] ; then exit fi" to t
On 17-Aug-99 Rodney W. Grimes wrote:
> I kinda like the idea of this, but can't that really just
> be done easily with a few ipfw rules, the last two being
> the important ones:
>
> for port in "22 53" ; do
> ipfw add allow udp from any to ${myip} ${port}
> ipfw add allow udp fr
> Brian W. Buchanan writes:
> > > > Can anyone think of any reason why this feature should
> > > > not be implemented?
> > >
> > > I like that idea... net.inet.{tcp,udp}.drop_in_vain ?
> >
> > Why do we need a sysctl knob for this when it can be easily accomplished
> > with IPFW?
>
> Not that e
> Geoff Rehmet writes:
> > After the discussions regarding the "log_in_vain"
> > sysctls, I was thinking about a feature I would
> > like to implement:
> >
> > Instead of sending a RST (for TCP) or Port Unreachable
> > (for UDP) where the box is not listening on a socket,
> > I would like to impl
> 1. Add a "if [ ! -d $bak ] ; then exit fi" to the top
> of the files, or
> 2. Add a "mkdir -p $bak" to the top.
>
> Do others consider this an error, and if so which is the preferred fix?
Both. (2) followed by (1), possible logging a warning.
--
-- David([EMAIL PROT
Last CTM delta in
ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur
is 'int-cvs-cur.0114.gz' from May 15 1999.
There definitely was commits in International depository
after 'may 15'.
N.Dudorov
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
The 200-220 periodic files under daily expect that the directory
/var/backups exist when they run to back up various files. If you
delete this directory, the "cp" commands will error.
There seems to be two ways to fix the files.
1. Add a "if [ ! -d $bak ] ; then exit fi" to the top
Brian W. Buchanan writes:
> > > Can anyone think of any reason why this feature should
> > > not be implemented?
> >
> > I like that idea... net.inet.{tcp,udp}.drop_in_vain ?
>
> Why do we need a sysctl knob for this when it can be easily accomplished
> with IPFW?
Not that easily.. how are you
On Mon, 16 Aug 1999, Archie Cobbs wrote:
> Geoff Rehmet writes:
> > After the discussions regarding the "log_in_vain"
> > sysctls, I was thinking about a feature I would
> > like to implement:
> >
> > Instead of sending a RST (for TCP) or Port Unreachable
> > (for UDP) where the box is not liste
Geoff Rehmet writes:
> After the discussions regarding the "log_in_vain"
> sysctls, I was thinking about a feature I would
> like to implement:
>
> Instead of sending a RST (for TCP) or Port Unreachable
> (for UDP) where the box is not listening on a socket,
> I would like to implement a sysctl,
Brian F. Feldman scribbled this message on Aug 16:
> > be used as justification for putting all the other "compat" stuff up
> > there too. I think it's a slippery slope.
>
> much as possible. Just like the ports, it makes things easier on
> everyone if we use lower-case (compat.linux, compat.ibc
Mike Smith scribbled this message on Aug 16:
> >From the perspective of an integrated namespace, we've already made the
> wrong moves insofar as vm.* should be kern.vm.*, vfs.* should be
> kern.vfs.*, etc. Either the entire kernel namespace should have a
> presumed leading kern. (and the exist
On Mon, 16 Aug 1999, Mike Smith wrote:
> > In case anyone cares I'd like to put in a vote for compat.linux.
> > >From the design standpoint this balances the needs of prominence and clean
> > top level name space nicely.
>
> And in case it's not clear from the exposition in my message to Po
> have quite a few Plextor cd recorders so I am wondering if
> anyone has any experience with Plextor cd recorders...
Excellent experience. I have both their 4x and 8x [SCSI] burners.
If you check the various CDROM burner FAQs around, you will also find
that Plextors perform better than others
I agree with this as well.
> > "Linux compatibility"
> > "Linux ABI support"
> > "Linux binary compatibility"
>
> The suggested "linux mode", has a nice non-technical simple ring to it.
> If we called it this, the non-educated might not come away with the wrong
> idea. Management(tm) may not un
> "Linux compatibility"
> "Linux ABI support"
> "Linux binary compatibility"
The suggested "linux mode", has a nice non-technical simple ring to it.
If we called it this, the non-educated might not come away with the wrong
idea. Management(tm) may not understand "ABI" and the exact use of
"binar
> In case anyone cares I'd like to put in a vote for compat.linux.
> >From the design standpoint this balances the needs of prominence and clean
> top level name space nicely.
And in case it's not clear from the exposition in my message to Poul, I
would find this most agreeable too.
--
In case anyone cares I'd like to put in a vote for compat.linux.
>From the design standpoint this balances the needs of prominence and clean
top level name space nicely.
Doug
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Sigh.. OK, whatever Brian, it's clear that I can't communicate
with you and any future correspondence between us will be by
way of your mentor, Mike Smith. You had I have had our last
public exchange since you're now in my killfile.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Oh Guys,
I simply am trying to get information on which cd-recorder works
well on FreeBSD. It will help to avoid confusion and postings if
there was a cd-record handbook section explaining all the gory
details.
Peace
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail t
According to Mark Jaffe:
> > CVS is issuing an "out of memory" message on attempting to checkin a
> > 12MB file. What can I do? There is 300M of swap on the machine, it is
> > running FreeBSD 2.2.8, and CVS says:
> > "Concurrent Versions System (CVS) 1.9.26 (client/server)"
> >
> > I'll post this
On Mon, 16 Aug 1999, Jordan K. Hubbard wrote:
> I kinda like the idea of a top-level compat category; it will keep the
> top level uncluttered when sysv and iBCS compatibility start requiring
> their own knobs, and if you put linux at the top level this will later
> be used as justification for p
On Mon, 16 Aug 1999, Jordan K. Hubbard wrote:
> > Wormcontrol uses WORM ioctls, handled by both of the ATAPI drivers.
>
> Utterly irrelevant, not that you seem to let it stop you.
You bringing up worm(4) was entirely irrelevant. You implied that wormcontrol
does not work because the worm old-SC
> > Given that "ABI" is a bit obscure, kern.compat is the only sensible
> > choice.
>
> One one hand you're right (it is a compatibility stub) but OTOH it is also
> a kernel module... ;-)
>
> Perhaps modules like this will want to have their stuff in BOTH places,
> i.e. in kernel.compat and in
Is there an easy way to copy^h^h^h^h make backups from an atapi-cd-reader
to a scsi-cd-writer using cd-writer?
Leif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 16 Aug 1999, Mike Smith wrote:
> > > Yes, this is very true. But I think we are fooling ourselves if we
> > > believe linux emulation will not become 'standard' in the near future.
> > > Then we'll kick ourselves for giving the sysctl's convoluted names :-)
> >
> > Yeah...
> >Given that "ABI" is a bit obscure, kern.compat is the only sensible
> >choice.
>
> I think that is too obscure considering the exposure this will get.
What "exposure"? It's a backend to a tuning interface for our ABI
compatibility...
> It doesn't really matter much what we feel about it,
> Okay, I will bite.
>
> What would you call the linux emulator to convey the proper
> meaning to the suits types?
You don't. You say "FreeBSD has Linux binary compatibility", or
"FreeBSD will run (most) Linux applications out of the box".
--
\\ The mind's the standard \\ Mike Smith
I kinda like the idea of a top-level compat category; it will keep the
top level uncluttered when sysv and iBCS compatibility start requiring
their own knobs, and if you put linux at the top level this will later
be used as justification for putting all the other "compat" stuff up
there too. I th
Mike Smith wrote:
> > > Yes, this is very true. But I think we are fooling ourselves if we
> > > believe linux emulation will not become 'standard' in the near future.
> > > Then we'll kick ourselves for giving the sysctl's convoluted names :-)
> >
> > Yeah... Then, the next in line
In my case, you should always assume SCSI unless expressly indicated
otherwise. I hate ATAPI devices, no insult to Soren's fine work
intended. :)
- Jordan
>
> I take it that the absence of the interface means your cd-recoder uses scsi.
>
> Tnks A Lot!
>
>
> > > So can we have the manufactur
In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> > Yes, this is very true. But I think we are fooling ourselves if we
>> > believe linux emulation will not become 'standard' in the near future.
>> > Then we'll kick ourselves for giving the sysctl's convoluted names :-)
>>
>> Ye
> > Yes, this is very true. But I think we are fooling ourselves if we
> > believe linux emulation will not become 'standard' in the near future.
> > Then we'll kick ourselves for giving the sysctl's convoluted names :-)
>
> Yeah... Then, the next in line after "linux" are: ibcs2 an
Others have pretty much already listed my preferences:
"Linux compatibility"
"Linux ABI support"
"Linux binary compatibility"
or any of the other obvious permutations thereof...
- Jordan
> Okay, I will bite.
>
> What would you call the linux emulator to convey the proper
> meaning to the suit
I take it that the absence of the interface means your cd-recoder uses scsi.
Tnks A Lot!
> > So can we have the manufacture and model of your cd-recorder ? 8)
>
> Yes, it's a "Smart and Friendly" (gah!) "Rocket Recorder" - it does
> 8X CDR, 6X CDRW and 24X CD. I like it. :)
>
> - Jordan
--
Alec Wolman <[EMAIL PROTECTED]> wrote:
>The version of tar that comes with freebsd (v1.11.2 with local
>freebsd modifications) has a bug: if you attempt to copy large
>files (> 2GB) it will silently truncate the large file.
...
>There is a new version of gnu tar (v1.13) that has support for
>large
> Wormcontrol uses WORM ioctls, handled by both of the ATAPI drivers.
Utterly irrelevant, not that you seem to let it stop you.
> But ATA and wcd are both not CAM. dd works just fine. You can solve data
See above. dd's unsuitableness for writing CDs has nothing whatsoever
to do with CAM.
> Yo
> So can we have the manufacture and model of your cd-recorder ? 8)
Yes, it's a "Smart and Friendly" (gah!) "Rocket Recorder" - it does
8X CDR, 6X CDRW and 24X CD. I like it. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the messa
> I looked at the implementation of fast-read, and it doesn't look
> too hard to adapt to the new version of tar. I could create
> patches if there is interest
There is. Upgrading tar is something I've been wanting to do for over a
year. Anything to speed me along would be helpful.
--
--
Okay, I will bite.
What would you call the linux emulator to convey the proper
meaning to the suits types?
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
OK, here I am once more, after yet another reboot :)
Now I'm running an unpatched -current from last week. It behaves
almost the same, except for the delay in 'zzz'.
That is, the system will go in suspend mode (albeit without spinning
down the disks immediately) after a BIOS timeout or power-but
Followup: I decided to upgrade my P2B BIOS version. I had 1005, went
to 1010. This made a difference!
Now suspend works. However still the disks keep spinning until they
reach their BIOS timeout. In Linux & Windows, there is some hook when
going to suspend mode that spins down the (IDE) disks. Th
>> "MI" == Mitsuru IWASAKI <[EMAIL PROTECTED]> writes:
MI> Hi,
MI> I got ASUS P2B M/B & ATX case and assembled new box yesterday. With
MI> my patch, new box successfully transit into suspend state. There is
MI> no sounds from CPU fun, chassis fun and IDE HDD spin (powered down b
The version of tar that comes with freebsd (v1.11.2 with local
freebsd modifications) has a bug: if you attempt to copy large
files (> 2GB) it will silently truncate the large file.
To reproduce this bug, simply use
tar cf - | (cd ; tar xvpf -)
where is a directory that contains a large file
Well, okay.
They are sort of hiding the fact that they are using FreeBSD and
you will have to ask them why is FreeBSD is not more prominently
advertised. Not too long ago I read a review on various
internet appliances and Whistle listed their OS as BSD/UNIX.
On the other hand, Juniper does have
On Mon, 16 Aug 1999, Amancio Hasty wrote:
> And whats Whistle market capitilization since becoming part of IBM ? 8)
Sure, but the last time I heard a Whistle radio comercial, I heard no
mention of FreeBSD. Last time I saw a mention of RedHat, it sure as hell
included a mention of Linux.
- alex
On Mon, 16 Aug 1999, Tom Bartol wrote:
>
> I absolutely agree with Jordan on this point. I'm having an increasingly
> hard time keeping our lab running FreeBSD over Linux due to pressure from
> higher-ups who aren't in the technical trenches with me and who don't
> understand the very good te
Matthew Dillon wrote:
> :Well, it's also a module, so perhaps we should create the whole subtree
> :for modules (as was already discussed several times..)
>
> Yes, this is very true. But I think we are fooling ourselves if we
> believe linux emulation will not become 'standard' in the n
Tom Bartol <[EMAIL PROTECTED]> wrote:
> In a previous e-mail on this or a related thread I saw the term:
>
> "Linux image activator"
>
> or something close to this pass by. I think this term gave me a much
> closer feeling to what I imagine is really going on the the "linuxulator"
> than the term
And whats Whistle market capitilization since becoming part of IBM ? 8)
>
>
> On Mon, 16 Aug 1999, Tom Bartol wrote:
>
> >
> > I absolutely agree with Jordan on this point. I'm having an increasingly
> > hard time keeping our lab running FreeBSD over Linux due to pressure from
> > higher-up
I absolutely agree with Jordan on this point. I'm having an increasingly
hard time keeping our lab running FreeBSD over Linux due to pressure from
higher-ups who aren't in the technical trenches with me and who don't
understand the very good technical reasons I have for running FreeBSD
here. On
On Mon, 16 Aug 1999, Jordan K. Hubbard wrote:
> > Mkisofs is good for creating an ISO 9660 file systems. Wormcontrol and
> > dd are a good combination for writing them.
>
> This would be true if the worm driver wasn't actually dead. You
> should at least check on these things before publically
Cool,
So can we have the manufacture and model of your cd-recorder ? 8)
Browsing a little over at http://www.buy.com and noticed that they
have quite a few Plextor cd recorders so I am wondering if
anyone has any experience with Plextor cd recorders...
Tnks!
--
Amancio Hasty
[EMAI
All of this would be true if your personal definition of "emulator"
were the prevailing one, but that is unfortunately just not the
case. :)
When the average computing public thinks of an "emulator", they think
of something like MAME or the SNES emulator. Even the more
compute-minded folks tend
Hi,
My understanding on your problems is:
1. Standby by PM timer in BIOS setting fails with the system activity.
2. No new process can be started after resume.
Is it correct?
1. My laptops also fails if the console or window is updating by the
output from running commands. But standby on oth
> Mkisofs is good for creating an ISO 9660 file systems. Wormcontrol and
> dd are a good combination for writing them.
This would be true if the worm driver wasn't actually dead. You
should at least check on these things before publically recommending
obsolete mechanisms. :)
In the world of CAM
Mark Jaffe wrote:
>
> Jordan,
>
> CVS is issuing an "out of memory" message on attempting to checkin a
> 12MB file. What can I do? There is 300M of swap on the machine, it is
> running FreeBSD 2.2.8, and CVS says:
> "Concurrent Versions System (CVS) 1.9.26 (client/server)"
>
> I'll post this to
Cool,
I forgot to ask about heat generation. My 10k rpm scsi disks are external
due to that they like to run hot so my cd recorder most likely will also
be external.
Tnks for the info on the Yamaha!
Cheers
> On Mon, 16 Aug 1999, Amancio Hasty wrote:
>
> >
> > Sorry about that . T
Hi,
I got ASUS P2B M/B & ATX case and assembled new box yesterday. With
my patch, new box successfully transit into suspend state. There is
no sounds from CPU fun, chassis fun and IDE HDD spin (powered down by
BIOS setting, Power management setup -> PM Timers -> HDD Power Down:
1 Min.). The
:
:Yeah... Then, the next in line after "linux" are: ibcs2 and svr4 and
:whatever comes next. Can you live with them as main sysctl categories?
:
:Andrzej Bialecki
I think Solaris has a chance, but I doubt any other traditional vendor
UNIXes do. So it comes down to Solaris and Linux for
On Mon, 16 Aug 1999, Matthew Dillon wrote:
>
> :
> :On Sun, 15 Aug 1999, Matthew Dillon wrote:
> :
> :> :>2) under "kern.emu.linux"
> :> :>3) under "linux"
> :> :
> :> :I vote for 3.
> :> :
> :> :--
> :> :Poul-Henning Kamp FreeBSD coreteam member
> :> :[EMAIL PROTECTED]
:
:On Sun, 15 Aug 1999, Matthew Dillon wrote:
:
:> :>2) under "kern.emu.linux"
:> :>3) under "linux"
:> :
:> :I vote for 3.
:> :
:> :--
:> :Poul-Henning Kamp FreeBSD coreteam member
:> :[EMAIL PROTECTED] "Real hackers run -current on their laptop."
:> :FreeBSD -- It will
On Sun, 15 Aug 1999, Matthew Dillon wrote:
> :>2) under "kern.emu.linux"
> :>3) under "linux"
> :
> :I vote for 3.
> :
> :--
> :Poul-Henning Kamp FreeBSD coreteam member
> :[EMAIL PROTECTED] "Real hackers run -current on their laptop."
> :FreeBSD -- It will take a long t
$B=i$a$^$7$F!"%$%*%s%IBg3X$NGp:j!!M5;R$H?=$7$^$9!#(B
$B%$%*%s%IBg3X!!L>M@Gn;N!!?dA&0Q0w2q@_N)$N$*CN$i$;$,$"$j(B
$B$^$7$F!"%a!<%k$rCW$7$^$7$?!#(B
$B$3$NEY!"(BIOND University$B!J%O%o%$=#G'2D!"(BWAUC$B2CLA!K$G$O!"(B
$BF|K\$N3F3&$K$*$$$FB?Bg$J$kM@Gn;N9f$rM@Gn;N?dA&0Q0wBP>](B
$B!!#
Brian F. Feldman writes:
> On Sun, 15 Aug 1999, Warner Losh wrote:
>
> > In message <[EMAIL PROTECTED]> "Brian F.
>Feldman" writes:
> > : I suppose, but wouldn't the proper place be under machdep? I agree that
> > : a linux top-level MIB would be easiest to remember.
> >
> > Linux isn'
On Mon, 16 Aug 1999, Amancio Hasty wrote:
>
> Sorry about that . The emphasis is more on the hardware and second is the
> software -- I usually get around problems with the software.
I have a Yamaha 4416 (or something close to that) which has worked attached
to every machine I have tried. (F
hi, there!
On Sun, 15 Aug 1999, Amancio Hasty wrote:
> Any one care to recommend a CD writer for FreeBSD-current since thats
> typically what I run over here.
I use Sony CDU948S-RP more than year. works like a charm
If cd-recorder is not MMC-compatible check that cdrdao supports it
directly (So
Current CPU detection routine sometimes fails to detect IBM
BlueLightning CPU. The problem is caused by failure of Cyrix/IBM CPU
detection in sys/i386/i386/locore.s. Our Cyrix/IBM CPU detection code
is different from that in Cyrix's BIOS writer's guide because latter
code cannot distinguish Nex
I think that emulation usually denotes simulation so I would find another term
or invent one to describe the linux emulation layer.
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : We're staying away from the term "emulation" because it's being
> : associated with things like the abominable 'lxrun' and virtual-machine
> : emulators like VMware.
>
> Also, there is a perception that "emulation" is s
After the discussions regarding the "log_in_vain"
sysctls, I was thinking about a feature I would
like to implement:
Instead of sending a RST (for TCP) or Port Unreachable
(for UDP) where the box is not listening on a socket,
I would like to implement a sysctl, which disables the
sending of the R
96 matches
Mail list logo
