> > What is the plan (if any) for including crypto stuff in the kernel?
> > As time goes on this will be more and more needed, eg. for IPSec
> > and other VPN applications.
>
> The KAME/IPv6 guys have already brought this up; the agreement was
> that...
I just prepared IPsec related patches whic
> And I wonder if I can send the patches to lists to solicite
> comments.
Send them to me if you like :-)
> By the way, all crypto stuff are put under the sys/crypto dir
> in the patch. Should some of them put under sys/libkern instead?
No. Please leave them in sys/crypto/
M
--
Mark Murray
Jo
> > What is the plan (if any) for including crypto stuff in the kernel?
> > As time goes on this will be more and more needed, eg. for IPSec
> > and other VPN applications.
>
> The KAME/IPv6 guys have already brought this up; the agreement was
> that...
>
> > It would be nice if we had a /usr/sr
> > ...a sys/crypt/ directory should hold their DES code. :-)
>^
> Shouldn't this be crypto ? That is what I see if I look on internat
> in the /usr/local/etc/cvsup/sup directory.
So it should, and in the patch that I have, it is :-).
M
--
Mark Murray
Join the anti-SPAM movement:
I got a new machine (500 MHz PIII) with a 12 GB disk (nothing nowadays
though :-). There was already NT 4.0 installed and a 3.9 GB unitialized
partition left.
I booted the 3.3 CD, chose Custom and tried to create a FreeBSD
partition. 13200 blocks were left. I tried both, half of it and
the whole
I read some postings on the Linux-Archive, complaining the slowness in
looking up some big directory. Some claims that since the directory file
is typically small, advanced techniques such as B+ tree (and I add hash
method) are not necessary. We can simply pre-allocate the directory file
contig
On Fri, Dec 10, 1999 at 08:56:47AM -0500, Zhihui Zhang wrote:
> Can anyone give me an idea on how big a directory could be in some
> environment?
Our inn's /news/spool/control/cancel directory is almost 300k. If
we were a significantly larger news site we probably wouldn't be
running inn though.
On Fri, 10 Dec 1999, David Malone wrote:
> On Fri, Dec 10, 1999 at 08:56:47AM -0500, Zhihui Zhang wrote:
>
> > Can anyone give me an idea on how big a directory could be in some
> > environment?
>
> Our inn's /news/spool/control/cancel directory is almost 300k. If
> we were a significantly larg
reposting to the hackers
;-)
- Original Message -
From: Robert Gordon <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 09, 1999 1:56 PM
Subject: Clustered Read/writes and NFS..
> Hello,
>
> I'm attempting to understand if the NFS implementation takes
> advantage
Hello,
I originally posted this message to -questions mailing list, but it wasn't
probably the right place :-( So, if you read it few days ago, please silently
ignore ;-)
I use FreeBSD on my home PC and one server. I must say, that I am *very*
satisfied with it.
a) I am maintainer/author of F
:reposting to the hackers
:;-)
:- Original Message -
:From: Robert Gordon <[EMAIL PROTECTED]>
:To: <[EMAIL PROTECTED]>
:Sent: Thursday, December 09, 1999 1:56 PM
:Subject: Clustered Read/writes and NFS..
:
:
:> Hello,
:>
:> I'm attempting to understand if the NFS implementation takes
:(1) If the directory file is less than one page, there will be a waste of
:memory due to internal fragmentation. Why do not we set a limit, say one
:page, on when we start VMIO a directory?
It is true that when we use VMIO to back directories that a minimum of
one page of memory is use
On Fri, 10 Dec 1999, Martin Hinner wrote:
> I originally posted this message to -questions mailing list, but it wasn't
> probably the right place :-( So, if you read it few days ago, please silently
> ignore ;-)
>
> I use FreeBSD on my home PC and one server. I must say, that I am *very*
> sati
Pardon me if this was sent to the wrong list, but -hackers seemed as good
a place as any...
I'm running FreeBSD4.0, current as of 12/10/99 (today)...I just traded
with a friend and found myself with an SB AWE 64...while there are
instructions on getting this card working under 3.2, there are none
| US sites mirror their crypto from freebsd.org, international ones from the
| international repository. The preferred path is for code to be committed
| by international people to the international repository, since it can be
| imported from there back into the US - if we can avoid it we shouldn
On Fri, 10 Dec 1999, Dan Moschuk wrote:
> | our users (by geography) from accessing it. However at least in the case
> | of OpenSSL (which I'm planning to import into internat when I go home to
> | australia next week :-) the two will have to be divergent due to the
> | patent restrictions on RSA
:
:> :(3) Or maybe we can add a parameter to the filesytem, telling it to try to
:> :preallocate some contiguous disk space for all directory files. I guess
:> :that the cost per bit on disk is less than the cost per bit in memory.
:>
:> I believe the filesystem already does this.
:>
:
:The
> :(3) Or maybe we can add a parameter to the filesytem, telling it to try to
> :preallocate some contiguous disk space for all directory files. I guess
> :that the cost per bit on disk is less than the cost per bit in memory.
>
> I believe the filesystem already does this.
>
The FFS tries
try this:
device pcm0
device sbc0
IIRC pnp is standard in the latest -current, so if yours is more than a
few days old you may need controller pnp0 too.
If the above doesnt work, try options PNPBIOS.
And for further reference, the freebsd-multimedia list would be your best
bet.
| This was actually part of an unrelated point I was making - RSA will
| definitely not be going into the kernel anywhere at this point! In
| general, we want the two crypto repositories to stay in sync which
| generally means propagating from internat -> freefall, but we can't do it
| for RSA.
I am in the process of writing a device driver for the Turtle Beach Multisound
Monterey soundcard. At the moment I am statically compiling my code into the
kernel and it is somewhat operational. I have added conditional compilation
code to also compile as a kld module. My problem is that when I k
> This message was sent from Geocrawler.com by "Alex" <[EMAIL PROTECTED]>
> Be sure to reply to that address.
>
> Hello,
>
> I'm writting driver for PCI board.
> Is't possible to set interrupt handler for PCI
> device not in attach function? If yes, how?
> For ISA is possible to do by calling
> I got a new machine (500 MHz PIII) with a 12 GB disk (nothing nowadays
> though :-). There was already NT 4.0 installed and a 3.9 GB unitialized
> partition left.
>
> I booted the 3.3 CD, chose Custom and tried to create a FreeBSD
> partition. 13200 blocks were left. I tried both, half of it a
Greetings,
it appears that tail is not functioning properly with a file > 2 GB.
What can I do to tail such a file (actually to make it smaller than 2 GB) ?
Is there a large file capable tail for FreeBSD ?
I have also found that 'less' is unable to display that file, but more is.
:-/
Michael
>
> I am in the process of writing a device driver for the Turtle Beach Multisound
> Monterey soundcard. At the moment I am statically compiling my code into the
> kernel and it is somewhat operational. I have added conditional compilation
> code to also compile as a kld module. My problem is tha
- please only post to one list
- please do not post HTML messages to public mailing lists
> I'm using the parallel port to control some sort of a hardware (i2c).
You should probably use the i2cbb driver for this, as it can be easily
tweaked to do what you're trying to do here.
> For that I
26 matches
Mail list logo
