After a bit of work on TCP sequence numbers, and generating initial
sequence numbers which are difficult to predict, I have put some
code together, which I belive makes the way in which FreeBSD
generates initial send sequence numbers more secure.
Problems with our existing scheme are that we are u
Well, in my case, changing from 2MB to 8MB's knocked the rebuild time from
2:05 to 36 seconds, for appx 15000 records.
not enough memory to make a real difference that I can see, but it kept
the disk tps meter pegged at 118-120.
On Wed, 1 Sep 1999, Sheldon Hearn wrote:
>
>
> On Tue, 31 Aug 1
On Fri, 27 Aug 1999, Dennis wrote:
>
> It seems that an interface configured with an address, which is then
> deleted, and then set to a different address on the same network, the
> machine continues to use the original address although all evidence of it
> is gone.
>
> examples.
>
> ifconfi
On Tue, 31 Aug 1999 18:29:58 MST, Jaye Mathisen wrote:
> Got tired of the dinky cachesize for pwd_mkdb, especially since vipw
> doesn't take advantage of the -u or -s options.
Vipw doesn't take advantage of the -u option? I must have read through
the code too fast.
> Dramatically helps on tho
After a bit of work on TCP sequence numbers, and generating initial
sequence numbers which are difficult to predict, I have put some
code together, which I belive makes the way in which FreeBSD
generates initial send sequence numbers more secure.
Problems with our existing scheme are that we are
On Fri, 27 Aug 1999, Dennis wrote:
>
> It seems that an interface configured with an address, which is then
> deleted, and then set to a different address on the same network, the
> machine continues to use the original address although all evidence of it
> is gone.
>
> examples.
>
> ifconf
Mark Murray writes :
> > Speaking of ITAR, has anybody actually every approached FreeBSD to say
> > what we're doing is in violation of ITAR?
>
> IANAL, but IIRC, ITAR is dead; Wasssenaar is the bogeyman these days
> (at least outside the USA).
>
> The DoD, DoJ, DoE, DoC and watever other Do's yo
I am modifying the tulip device driver to support this xircom card. I have it
almost entirely working, *except* that it goes into infinite re-neogitiate
loops. The card probes correctly at bootup, but any attempt to change
information via ifconfig ("ifconfig de0 inet ..." and "ifconfig de0 up",
On Wed, 1 Sep 1999, Andy Farkas wrote:
> > I've got what I think is a working MCA shim for the 'BT' driver.
> >
>
> not quite...
>
> The io, irq and drq values are correct on both aha & bt...
>
> aha0 is still failing the INQUIRE command...
if (reply_len != reply_buf_size) {
Mark Murray writes :
> > Speaking of ITAR, has anybody actually every approached FreeBSD to say
> > what we're doing is in violation of ITAR?
>
> IANAL, but IIRC, ITAR is dead; Wasssenaar is the bogeyman these days
> (at least outside the USA).
>
> The DoD, DoJ, DoE, DoC and watever other Do's y
I am modifying the tulip device driver to support this xircom card. I have it
almost entirely working, *except* that it goes into infinite re-neogitiate
loops. The card probes correctly at bootup, but any attempt to change
information via ifconfig ("ifconfig de0 inet ..." and "ifconfig de0 up",
On Wed, 1 Sep 1999, Andy Farkas wrote:
> > I've got what I think is a working MCA shim for the 'BT' driver.
> >
>
> not quite...
>
> The io, irq and drq values are correct on both aha & bt...
>
> aha0 is still failing the INQUIRE command...
if (reply_len != reply_buf_size) {
On Wed, 1 Sep 1999, John Birrell wrote:
> On Tue, Aug 31, 1999 at 08:27:00AM -0700, Doug wrote:
> > John Birrell wrote:
> a patch to change one word in /usr/src/usr.bin/make/main.c?! Please take
> a few moments to have a look for "unknown" in that file. Sigh.
>
> If there is someone with a scratc
> I've got what I think is a working MCA shim for the 'BT' driver.
>
not quite...
The io, irq and drq values are correct on both aha & bt...
aha0 is still failing the INQUIRE command...
disk0s4a:> boot -v
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 199
Got tired of the dinky cachesize for pwd_mkdb, especially since vipw
doesn't take advantage of the -u or -s options.
So here a couple patches that make the cachesize tweakable from make.conf.
Dramatically helps on those 10-15k line password files.
I would appreciate it if somebody would at lea
On Wed, 1 Sep 1999, John Birrell wrote:
> On Tue, Aug 31, 1999 at 08:27:00AM -0700, Doug wrote:
> > John Birrell wrote:
> a patch to change one word in /usr/src/usr.bin/make/main.c?! Please take
> a few moments to have a look for "unknown" in that file. Sigh.
>
> If there is someone with a scrat
I've got what I think is a working MCA shim for the 'BT' driver.
I'd like someone with an MCA box and one of these cards to test it for me
as I have not yet found a card to. (Anyone want to give me one?)
Please see:
http://www.jurai.net/~winter/mca/README.bt
If you've not seen the MCA
> I've got what I think is a working MCA shim for the 'BT' driver.
>
not quite...
The io, irq and drq values are correct on both aha & bt...
aha0 is still failing the INQUIRE command...
disk0s4a:> boot -v
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 19
Got tired of the dinky cachesize for pwd_mkdb, especially since vipw
doesn't take advantage of the -u or -s options.
So here a couple patches that make the cachesize tweakable from make.conf.
Dramatically helps on those 10-15k line password files.
I would appreciate it if somebody would at le
I've got what I think is a working MCA shim for the 'BT' driver.
I'd like someone with an MCA box and one of these cards to test it for me
as I have not yet found a card to. (Anyone want to give me one?)
Please see:
http://www.jurai.net/~winter/mca/README.bt
If you've not seen the MCA
I've got what I think is a working MCA shim for the AHA driver.
I'd like someone with an MCA box and an aha-1640 to test it for me as my
1640 isn't here yet.
Please see:
http://www.jurai.net/~winter/mca/README.aha
If you've not seen the MCA bus code that this driver requires also see:
> In message <28661.936093...@critter.freebsd.dk> Poul-Henning Kamp writes:
> : >Hmph. I guess common sense wins over ITAR in this case. :)
> :
> : That's certainly an improvement in that particular battle :-)
>
> Speaking of ITAR, has anybody actually every approached FreeBSD to say
> what we'r
I've got what I think is a working MCA shim for the AHA driver.
I'd like someone with an MCA box and an aha-1640 to test it for me as my
1640 isn't here yet.
Please see:
http://www.jurai.net/~winter/mca/README.aha
If you've not seen the MCA bus code that this driver requires also see:
> In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
> : >Hmph. I guess common sense wins over ITAR in this case. :)
> :
> : That's certainly an improvement in that particular battle :-)
>
> Speaking of ITAR, has anybody actually every approached FreeBSD to say
> what we're doing is in vi
On Wed, 1 Sep 1999, John Birrell wrote:
> On Tue, Aug 31, 1999 at 08:27:00AM -0700, Doug wrote:
> > John Birrell wrote:
> > > The solution is to fix `make'. I could commit the fix, but I'm not
> > > in a position to build -stable just now. I'm not supposed to commit
> > > without testing. The fix
so where re you at the moment?
julian
On Wed, 1 Sep 1999 adr...@freebsd.org wrote:
> Comments welcome.
>
>
>
> Adrian
>
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
On Wed, 1 Sep 1999, John Birrell wrote:
> If there is someone with a scratch disk on which they can install 2.2.8
> (or 2.2.7 or 2.2.6) and do a `make aout-to-elf' and report the results,
> we could get this sorted out. I don't have the hardware to do that
> anymore. Any list-lurkers want to help
On Tue, Aug 31, 1999 at 08:27:00AM -0700, Doug wrote:
> John Birrell wrote:
> > The solution is to fix `make'. I could commit the fix, but I'm not
> > in a position to build -stable just now. I'm not supposed to commit
> > without testing. The fix looks straight forward though, so "it
> > should ju
On Wed, 1 Sep 1999, John Birrell wrote:
> On Tue, Aug 31, 1999 at 08:27:00AM -0700, Doug wrote:
> > John Birrell wrote:
> > > The solution is to fix `make'. I could commit the fix, but I'm not
> > > in a position to build -stable just now. I'm not supposed to commit
> > > without testing. The fix
so where re you at the moment?
julian
On Wed, 1 Sep 1999 [EMAIL PROTECTED] wrote:
> Comments welcome.
>
>
>
> Adrian
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Wed, 1 Sep 1999, John Birrell wrote:
> If there is someone with a scratch disk on which they can install 2.2.8
> (or 2.2.7 or 2.2.6) and do a `make aout-to-elf' and report the results,
> we could get this sorted out. I don't have the hardware to do that
> anymore. Any list-lurkers want to help
On Tue, Aug 31, 1999 at 08:27:00AM -0700, Doug wrote:
> John Birrell wrote:
> > The solution is to fix `make'. I could commit the fix, but I'm not
> > in a position to build -stable just now. I'm not supposed to commit
> > without testing. The fix looks straight forward though, so "it
> > should j
If you're cvsuping to -stable or -current, rebuild world and rebuild kernel.
Binary compatibility got broken somewhere in there..
Chuck Youse
Director of Engineering
CyberSites, Inc.
-Original Message-
From: owner-freebsd-hack...@freebsd.org
[mailto:owner-freebsd-hack...@freebsd.org]on B
If you're cvsuping to -stable or -current, rebuild world and rebuild kernel.
Binary compatibility got broken somewhere in there..
Chuck Youse
Director of Engineering
CyberSites, Inc.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Martin Borghoff
Sent:
On Tue, Aug 31, 1999 at 11:15:49AM +0100, Doug Rabson wrote:
[...]
> > Attached is a patch for GNU fileutils-4.0 that will make rm
> > yield when the workaround code catches a bad readdir().
>
> Are you using a FreeBSD port for GNU fileutils? If so, your patch should
> be directed to the port main
> Speaking of ITAR, has anybody actually every approached FreeBSD to say
> what we're doing is in violation of ITAR?
IANAL, but IIRC, ITAR is dead; Wasssenaar is the bogeyman these days
(at least outside the USA).
The DoD, DoJ, DoE, DoC and watever other Do's you guys have are all
passing the buc
In message <28661.936093...@critter.freebsd.dk> Poul-Henning Kamp writes:
: >Hmph. I guess common sense wins over ITAR in this case. :)
:
: That's certainly an improvement in that particular battle :-)
Speaking of ITAR, has anybody actually every approached FreeBSD to say
what we're doing is in
On Tue, Aug 31, 1999, Martin Borghoff wrote:
> Hai!,
>
> Is the add option in ipfw removed?
>
> if i do a simple thing like :
>
> ipfw add pass tcp from any to any setup
> ipfw: setsockopt(IP_FW_ADD): Invalid argument
>
> please give me some hints..
Have you either:
a.) Loaded /modules/ip
:Hello,
:
:I am using 3.2-Stable and I have a 9GB disk drive used as cache for
:squid proxy. I have changed the min free space with tunefs program to 0
:but now I have a problem. Even though I have 250MB free space on the
:file system, I get file system full error.
:
:usr/local/squid/cache/disk1:
On Tue, Aug 31, 1999 at 11:15:49AM +0100, Doug Rabson wrote:
[...]
> > Attached is a patch for GNU fileutils-4.0 that will make rm
> > yield when the workaround code catches a bad readdir().
>
> Are you using a FreeBSD port for GNU fileutils? If so, your patch should
> be directed to the port mai
Hai!,
Is the add option in ipfw removed?
if i do a simple thing like :
ipfw add pass tcp from any to any setup
ipfw: setsockopt(IP_FW_ADD): Invalid argument
please give me some hints..
Thanks in advance!.
- Martin -
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe fr
> Speaking of ITAR, has anybody actually every approached FreeBSD to say
> what we're doing is in violation of ITAR?
IANAL, but IIRC, ITAR is dead; Wasssenaar is the bogeyman these days
(at least outside the USA).
The DoD, DoJ, DoE, DoC and watever other Do's you guys have are all
passing the bu
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: >Hmph. I guess common sense wins over ITAR in this case. :)
:
: That's certainly an improvement in that particular battle :-)
Speaking of ITAR, has anybody actually every approached FreeBSD to say
what we're doing is in violation of ITA
Hello,
I am using 3.2-Stable and I have a 9GB disk drive used as cache for
squid proxy. I have changed the min free space with tunefs program to 0
but now I have a problem. Even though I have 250MB free space on the
file system, I get file system full error.
usr/local/squid/cache/disk1: write fai
On Tue, Aug 31, 1999, Martin Borghoff wrote:
> Hai!,
>
> Is the add option in ipfw removed?
>
> if i do a simple thing like :
>
> ipfw add pass tcp from any to any setup
> ipfw: setsockopt(IP_FW_ADD): Invalid argument
>
> please give me some hints..
Have you either:
a.) Loaded /modules/i
:Hello,
:
:I am using 3.2-Stable and I have a 9GB disk drive used as cache for
:squid proxy. I have changed the min free space with tunefs program to 0
:but now I have a problem. Even though I have 250MB free space on the
:file system, I get file system full error.
:
:usr/local/squid/cache/disk1:
On Tue, 31 Aug 1999, Matthew N. Dodd wrote:
>
> Did I maybe forget to mention adding the line to sys/i386/conf/files.i386?
>
> i386/mca/aha_mca.c optionalmca aha
>
yes.
> --
> | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
> | win...@jurai.net
On Tue, Aug 31, 1999, Doug Rabson wrote:
> On Mon, 30 Aug 1999, Andrew J. Korty wrote:
>
> > > I suppose there already was a rather lengthy discussion about a
> > > "user"-option
> > > .
> > > I hope this sysctl-thing will make it into the mount-manpage, because if
> > > not,
> > > it might turn
Hai!,
Is the add option in ipfw removed?
if i do a simple thing like :
ipfw add pass tcp from any to any setup
ipfw: setsockopt(IP_FW_ADD): Invalid argument
please give me some hints..
Thanks in advance!.
- Martin -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
On Wed, 1 Sep 1999, Andy Farkas wrote:
> Righty-o, I've finally got a kernel to boot on my MCA box! Yay!
>
> Its a rather large "Apricot FTs 486" with the Panther Rev F MB:
>
> http://www.mitsubishi-computers.com/insight/en/products/servers/fts/ftsmain.htm
Ah! This is good since it means that
Righty-o, I've finally got a kernel to boot on my MCA box! Yay!
Its a rather large "Apricot FTs 486" with the Panther Rev F MB:
http://www.mitsubishi-computers.com/insight/en/products/servers/fts/ftsmain.htm
It is currently running NT4 (SP5) with all the adapters in it recognised
and supported
Hello,
I am using 3.2-Stable and I have a 9GB disk drive used as cache for
squid proxy. I have changed the min free space with tunefs program to 0
but now I have a problem. Even though I have 250MB free space on the
file system, I get file system full error.
usr/local/squid/cache/disk1: write fa
On Tue, 31 Aug 1999, Matthew N. Dodd wrote:
>
> Did I maybe forget to mention adding the line to sys/i386/conf/files.i386?
>
> i386/mca/aha_mca.c optionalmca aha
>
yes.
> --
> | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
> | [EMAIL PROTECTE
On Tue, Aug 31, 1999, Doug Rabson wrote:
> On Mon, 30 Aug 1999, Andrew J. Korty wrote:
>
> > > I suppose there already was a rather lengthy discussion about a "user"-option
> > > .
> > > I hope this sysctl-thing will make it into the mount-manpage, because if not,
> > > it might turn out to be a
On Wed, 1 Sep 1999, Andy Farkas wrote:
> Righty-o, I've finally got a kernel to boot on my MCA box! Yay!
>
> Its a rather large "Apricot FTs 486" with the Panther Rev F MB:
>
> http://www.mitsubishi-computers.com/insight/en/products/servers/fts/ftsmain.htm
Ah! This is good since it means that
John Birrell wrote:
>
> On Mon, Aug 30, 1999 at 03:55:42PM -0700, Doug wrote:
> > > `make' has changed.
> >
> > Ok, that's the cause then, so what's the solution? :) And
> > meanwhile is it going to hurt anything if I put a suggestion on my 'make
> > upgrade' web page that users do 'make -DM
Righty-o, I've finally got a kernel to boot on my MCA box! Yay!
Its a rather large "Apricot FTs 486" with the Panther Rev F MB:
http://www.mitsubishi-computers.com/insight/en/products/servers/fts/ftsmain.htm
It is currently running NT4 (SP5) with all the adapters in it recognised
and supporte
John Birrell wrote:
>
> On Mon, Aug 30, 1999 at 03:55:42PM -0700, Doug wrote:
> > > `make' has changed.
> >
> > Ok, that's the cause then, so what's the solution? :) And
> > meanwhile is it going to hurt anything if I put a suggestion on my 'make
> > upgrade' web page that users do 'make -D
I developed boot loader, which is more powerful and looks better than
boot loader, which is usually installed with FreeBSD release. I used
it for a long time and decided to send it to FreeBSD.
I haven't own home page and can't give you URL where you can read
information about my boot loader. So, h
I developed boot loader, which is more powerful and looks better than
boot loader, which is usually installed with FreeBSD release. I used
it for a long time and decided to send it to FreeBSD.
I haven't own home page and can't give you URL where you can read
information about my boot loader. So,
On Mon, Aug 30, 1999 at 03:55:42PM -0700, Doug wrote:
> > `make' has changed.
>
> Ok, that's the cause then, so what's the solution? :) And
> meanwhile is it going to hurt anything if I put a suggestion on my 'make
> upgrade' web page that users do 'make -DMACHINE_ARCH=i386 upgrade' as a
> t
>Hmmm. That's a point. I was thinking primarily of the "segregate the
>crypto" issue, but you're right that this would also put us back to
>the "bad old days" where sys/ was broken across multiple directories.
>Hmph. I guess common sense wins over ITAR in this case. :)
Yes, this is ver
Doug Rabson wrote:
>
> On Mon, 30 Aug 1999, Francis Jordan wrote:
>
> > Do as NetBSD does to remain compatible? Or borrow a few thoughts from
> > Solaris, which also has 128 signals:
> >
> > typedef struct {/* signal set type */
> > unsigned long __sigbits[4];
> > } sig
On Mon, Aug 30, 1999 at 03:55:42PM -0700, Doug wrote:
> > `make' has changed.
>
> Ok, that's the cause then, so what's the solution? :) And
> meanwhile is it going to hurt anything if I put a suggestion on my 'make
> upgrade' web page that users do 'make -DMACHINE_ARCH=i386 upgrade' as a
>
>Hmmm. That's a point. I was thinking primarily of the "segregate the
>crypto" issue, but you're right that this would also put us back to
>the "bad old days" where sys/ was broken across multiple directories.
>Hmph. I guess common sense wins over ITAR in this case. :)
Yes, this is ve
* Jeroen Ruigrok/Asmodai (asmo...@wxs.nl) [990829 14:40]:
> They shouldn't.
>
> That's what we have /var for like you said.
OK, I totally agree that named should dump to /var/somegoodpath but this
I guess falls out of my own hacking limits. I think we need a desiscion
if to move named dumps from
Doug Rabson wrote:
>
> On Mon, 30 Aug 1999, Francis Jordan wrote:
>
> > Do as NetBSD does to remain compatible? Or borrow a few thoughts from
> > Solaris, which also has 128 signals:
> >
> > typedef struct {/* signal set type */
> > unsigned long __sigbits[4];
> > } si
* Jeroen Ruigrok/Asmodai ([EMAIL PROTECTED]) [990829 14:40]:
> They shouldn't.
>
> That's what we have /var for like you said.
OK, I totally agree that named should dump to /var/somegoodpath but this
I guess falls out of my own hacking limits. I think we need a desiscion
if to move named dumps f
On Mon, 30 Aug 1999, Francis Jordan wrote:
> Marcel Moolenaar wrote:
> >
> > [cc'd to David E. Cross (cro...@cs.rpi.edu) and James Raynard
> > (jrayn...@freebsd.org)]
> >
> > I'm thinking about extending the number of signals. I like your thoughts
> > and opinions.
> >
> > Basicly what I'm goin
On Mon, 30 Aug 1999, Andrew J. Korty wrote:
> > I suppose there already was a rather lengthy discussion about a
> > "user"-option
> > .
> > I hope this sysctl-thing will make it into the mount-manpage, because if
> > not,
> > it might turn out to be a really FAQ :)
> > --
> > Volker Stolz * st.
On Sun, 29 Aug 1999, Bjoern Fischer wrote:
> Hello Doug, hello Matthew, hello list members,
>
> there are some hints that readdir() in -STABLE has problems when
> used on NFSv3 (UDP; and TCP probably, too) mounted file systems.
> The reason may be the recovery code for stale READDIR cookies.
>
>
On Sat, 28 Aug 1999, Sergey Babkin wrote:
> Mark Ovens wrote:
> >
> > On Fri, Aug 27, 1999 at 08:45:31PM -0400, Sergey Babkin wrote:
>
> > >
> > > A funny thing is that Microsoft is porting essentially a
> > > 32-bit version of Windows to Merced. All the programs for
> > > Windows that want to u
In message <506.936093...@localhost>, "Jordan K. Hubbard" writes:
>Hmmm. That's a point. I was thinking primarily of the "segregate the
>crypto" issue, but you're right that this would also put us back to
>the "bad old days" where sys/ was broken across multiple directories.
>
>Hmph. I guess com
Hmmm. That's a point. I was thinking primarily of the "segregate the
crypto" issue, but you're right that this would also put us back to
the "bad old days" where sys/ was broken across multiple directories.
Hmph. I guess common sense wins over ITAR in this case. :)
- Jordan
> In message <1033
On Tue, 31 Aug 1999, Mark Murray wrote:
> > >I'll be very happy to work with you on this one.
> >
> > Does it make sense to make src/crypto/sys for kernel code?
> > (for IPsec we need crypto code *in kernel*).
>
> I wonder...
>
> There was a contrib/sys (where softupdates went), and tha
On Mon, 30 Aug 1999, Francis Jordan wrote:
> Marcel Moolenaar wrote:
> >
> > [cc'd to David E. Cross ([EMAIL PROTECTED]) and James Raynard
> > ([EMAIL PROTECTED])]
> >
> > I'm thinking about extending the number of signals. I like your thoughts
> > and opinions.
> >
> > Basicly what I'm going
On Mon, 30 Aug 1999, Andrew J. Korty wrote:
> > I suppose there already was a rather lengthy discussion about a "user"-option
> > .
> > I hope this sysctl-thing will make it into the mount-manpage, because if not,
> > it might turn out to be a really FAQ :)
> > --
> > Volker Stolz * [EMAIL PROTE
On Sun, 29 Aug 1999, Bjoern Fischer wrote:
> Hello Doug, hello Matthew, hello list members,
>
> there are some hints that readdir() in -STABLE has problems when
> used on NFSv3 (UDP; and TCP probably, too) mounted file systems.
> The reason may be the recovery code for stale READDIR cookies.
>
> FYI, There are crypto-related files in the following locations.
> I'll take a detailed look into both repositories...
Thanks! It makes the most sense to keep this exactly as it it, except
for the files in src/sys/netinet6/ which should move to src/sys/crypto/
if they have crypto in t
On Sat, 28 Aug 1999, Sergey Babkin wrote:
> Mark Ovens wrote:
> >
> > On Fri, Aug 27, 1999 at 08:45:31PM -0400, Sergey Babkin wrote:
>
> > >
> > > A funny thing is that Microsoft is porting essentially a
> > > 32-bit version of Windows to Merced. All the programs for
> > > Windows that want to
In message <506.936093482@localhost>, "Jordan K. Hubbard" writes:
>Hmmm. That's a point. I was thinking primarily of the "segregate the
>crypto" issue, but you're right that this would also put us back to
>the "bad old days" where sys/ was broken across multiple directories.
>
>Hmph. I guess co
Hmmm. That's a point. I was thinking primarily of the "segregate the
crypto" issue, but you're right that this would also put us back to
the "bad old days" where sys/ was broken across multiple directories.
Hmph. I guess common sense wins over ITAR in this case. :)
- Jordan
> In message <103
>>> Does it make sense to make src/crypto/sys for kernel code?
>>> (for IPsec we need crypto code *in kernel*).
>>I'd say it makes a lot of sense.
>Yes, but shouldn't it be src/sys/crypto if we want to have
>"kern-developer" still have a sensible meaning ? (and for
>all the other reasons
In message <10335.936082...@localhost>, "Jordan K. Hubbard" writes:
>> Does it make sense to make src/crypto/sys for kernel code?
>> (for IPsec we need crypto code *in kernel*).
>
>I'd say it makes a lot of sense.
Yes, but shouldn't it be src/sys/crypto if we want to have
"kern-develope
On Tue, 31 Aug 1999, Mark Murray wrote:
> > >I'll be very happy to work with you on this one.
> >
> > Does it make sense to make src/crypto/sys for kernel code?
> > (for IPsec we need crypto code *in kernel*).
>
> I wonder...
>
> There was a contrib/sys (where softupdates went), and th
On Mon, Aug 30, 1999 at 05:34:00PM -0700, Dima Dorfman wrote:
> hi, i was reading some of the mailing list archives to get an answer to
> 'why dont icmp echo requests get passed to the raw sockets', and now that
> i have the answer i was wondering... is there a way to tell the kernel NOT
> to proce
> FYI, There are crypto-related files in the following locations.
> I'll take a detailed look into both repositories...
Thanks! It makes the most sense to keep this exactly as it it, except
for the files in src/sys/netinet6/ which should move to src/sys/crypto/
if they have crypto in
On Tue, Aug 24, 1999 at 04:25:26PM -0400, John W. DeBoskey wrote:
>The subject says it all... We have some code that scans files
> backwards...
>
>In looking through /usr/src/sys/kern/vfs_syscalls.c I can't see
> where we do any validation on the resulting seek location... Do the
> appro
>>> Does it make sense to make src/crypto/sys for kernel code?
>>> (for IPsec we need crypto code *in kernel*).
>>I'd say it makes a lot of sense.
>Yes, but shouldn't it be src/sys/crypto if we want to have
>"kern-developer" still have a sensible meaning ? (and for
>all the other reason
In message <10335.936082907@localhost>, "Jordan K. Hubbard" writes:
>> Does it make sense to make src/crypto/sys for kernel code?
>> (for IPsec we need crypto code *in kernel*).
>
>I'd say it makes a lot of sense.
Yes, but shouldn't it be src/sys/crypto if we want to have
"kern-develop
bri...@wintelcom.net (Alfred Perlstein) writes:
> 1) file descriptor passing (described in Unix Network Programming Vol I)
Or just read recv(2), search for SCM_RIGHTS.
> 2) shared address fork (should be on http://lt.tar.com)
Or just read rfork(2), and you don't need to share the address space
On Mon, 30 Aug 1999 12:26:06 CST, Warner Losh wrote:
> : On LITTLE_ENDIAN machines?
>
> Endian shouldn't matter.
Yup, it was the kind of stupid comment someone who doesn't actually know
what's going on would make. ;-)
I hadn't cottoned on to the notion of using an array.
Thanks,
Sheldon.
T
On Mon, Aug 30, 1999 at 05:34:00PM -0700, Dima Dorfman wrote:
> hi, i was reading some of the mailing list archives to get an answer to
> 'why dont icmp echo requests get passed to the raw sockets', and now that
> i have the answer i was wondering... is there a way to tell the kernel NOT
> to proc
On Tue, Aug 24, 1999 at 04:25:26PM -0400, John W. DeBoskey wrote:
>The subject says it all... We have some code that scans files
> backwards...
>
>In looking through /usr/src/sys/kern/vfs_syscalls.c I can't see
> where we do any validation on the resulting seek location... Do the
> appr
> >I'll be very happy to work with you on this one.
>
> Does it make sense to make src/crypto/sys for kernel code?
> (for IPsec we need crypto code *in kernel*).
I wonder...
There was a contrib/sys (where softupdates went), and that got moved
to sys/contrib.
Perhaps something simila
> Does it make sense to make src/crypto/sys for kernel code?
> (for IPsec we need crypto code *in kernel*).
I'd say it makes a lot of sense.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
96 matches
Mail list logo
