"Daniel C. Sobral" wrote:
> Nik Clayton wrote:
> >
> > Does FreeBSD support hardware crypto?
>
> It does.
>
> > There'll shortly be a story on /. about OpenBSD's hardware crypto support,
> > in the form of the HiFn 7751 chip. OpenBSD recommend buying them from
> > www.powercrypt.com.
Also, do
Alright, a couple things come to mind here.
1. Did you make the database? (# cap_mkdb /etc/login.conf)
2. Did you add the user to the class (# chfn user)
(and then put the class name in the class field)
3. If you did do that, login as the user (not su), and
type "limit" and give me an outpu
Mike Smith wrote:
> > So, I want to know how I can "automagically" set the device options,
> > every time a user kldload's the device driver.
>
> If you want to support this mode of operation, you really don't have a
> lot of options right now.
> Well, teaching kldload about module parameters wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hey out there!
This is my first time doing someting like an i am having problems
with one part. The session limit does not seem to be working. My
understanding was that this was a hard limit for the number of
simutanious logins a person may have. I cr
> So, I want to know how I can "automagically" set the device options,
> every time a user kldload's the device driver.
If you want to support this mode of operation, you really don't have a
lot of options right now. This is, in one fashion at least, my fault.
Sorry. 8(
I would be inclined,
We were unable to get a wi configured on 4.0 release yesterday but it may
be that we didn't have the time to check out the configuration fully.
Was never recognized on boot-up. We've got a few more to get configured
over the next week so we'll put your patch in and try again.
Jim Flowers <[E
On Thu, 13 Apr 2000, Murray Stokely wrote:
> I'm having trouble displaying the value of image_params->fname in
> this small snippet of code from imgact_elf.c. When the system execs
> an unbranded elf binary it doesn't tell you the name of the actual
> file that you tried to exec, which can be
> Two options.
>
> Once is that you can get hints, the other is that you can get
> environment variables. The third is to have sysctls, but those can't
> be set until after the driver has finished loading. Which one do you
> want me to talk about?
You forgot module arguments, which, along with
On Thu, Apr 13, 2000 at 05:11:44PM -0700, Ulf Zimmermann wrote:
> Finaly got my new desktop system for work in, but I am having problems
> that the probe at install hangs. Booting verbose, the last message
> I can get from scroll back in regards to ATA:
>
> ata0-master: success setting up UMDA4 m
Finaly got my new desktop system for work in, but I am having problems
that the probe at install hangs. Booting verbose, the last message
I can get from scroll back in regards to ATA:
ata0-master: success setting up UMDA4 mode on VIA chip
ad0: ATA-4 disk at ata0 as master
ad0: 19574MB (40088160
I have had some wi cards for a while, and while I have managed to get
an Airport to work (a friend helped me out), I believe that adding wi
to the list of bridge compatible interfaces may be helpful.
According to the documentation, the IBSS mode of the driver doesn't
work. That's too bad, as in
Warner,
> Two options.
>
> Once is that you can get hints, the other is that you can get
> environment variables. The third is to have sysctls, but those can't
> be set until after the driver has finished loading. Which one do you
> want me to talk about?
I'm sorry, but I don't know what "hin
Two options.
Once is that you can get hints, the other is that you can get
environment variables. The third is to have sysctls, but those can't
be set until after the driver has finished loading. Which one do you
want me to talk about?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
Now that my device driver basically works (I can successfully do pings
and ftp transfers through it) using default settings, I'd like to
start polishing it up a bit...
This is a driver for a DSL device (Lucent WildWire), and our driver
has lots of options because there are many "flavors" of DSL a
[EMAIL PROTECTED] said:
:- It took me an hour to figure this out today, and I'll be delighted if
:- it solves your problem. :-)
You da man!
Here is the change I made. Dear core team, please add to
errata! Thanks!
*** xdm-config.orig Thu Apr 13 16:37:35 2000
--- xdm-config Thu Apr 13 16:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Robert Withrow wrote:
>I asked about this in questions...
>
>It appears that authorization is broken in XDM in 4.0 REL. At least
>if I start XDM using the default everything, just the way I have
>for the la
On Wed, 12-Apr-2000 at 21:33:34 +0200, Wilko Bulte wrote:
> On Wed, Apr 12, 2000 at 03:02:10PM -0400, Sean O'Connell wrote:
> > Wilko Bulte stated:
> > > On Wed, Apr 12, 2000 at 10:38:04AM -0400, Vivek Khera wrote:
> > > > > "A" == Asmodai writes:
> > > >
> > > > >> I don't think this is a
Nik Clayton wrote:
>
> Does FreeBSD support hardware crypto?
It does.
> There'll shortly be a story on /. about OpenBSD's hardware crypto support,
> in the form of the HiFn 7751 chip. OpenBSD recommend buying them from
> www.powercrypt.com.
>
> If you go there you'll see that FreeBSD support
[EMAIL PROTECTED] said:
:- Do you have an up to date /etc?
Yes. This is a virgin installation of 4.0 REL.
bash-2.03$ uname -sr
FreeBSD 4.0-RELEASE
bash-2.03$ grep -A 6 XDM /etc/pam.conf
# XDM is difficult; it fails or moans unless there are modules for each
# of the four management groups; a
On Thu, 13 Apr 2000, Robert Withrow wrote:
> Any other ideas?
Do you have an up to date /etc?
/etc/pam.conf contains:
# XDM is difficult; it fails or moans unless there are modules for each
# of the four management groups; auth, account, session and password.
xdm authrequiredpa
I asked about this in questions...
It appears that authorization is broken in XDM in 4.0 REL. At least
if I start XDM using the default everything, just the way I have
for the last several releases, all attempts to log into the server
fail with authentication rejections.
The only suggestion on
Speaking of hardware support for compression...
I've been looking for hardware accelerated zlib for a while. I even
contacted the guys zlib developers and Hi/fn and came up with nothing.
Any suggestions?
Charles
-Original Message-
From: Len Conrad [mailto:[EMAIL PROTECTED]]
Sent: Thurs
I'm having trouble displaying the value of image_params->fname in
this small snippet of code from imgact_elf.c. When the system execs
an unbranded elf binary it doesn't tell you the name of the actual
file that you tried to exec, which can be very annoying when you run
an obfuscated shell-insta
Hi,
I semi-talked with Alfred Perlstein about this on IRC I keep getting a
return value of 14 (EINVAL) when I call copyin(). While issue may be my
fault, that is not the issue... the issue is that atleast in the main
page, it's undocumented. After randomly finding a man page in digital
unix
Hi
I'm trying to debug a kernel that is not crashing but hanging, with all
processes in 'inode' wchan. So I did a 'call panic()', and now I have
the crashdump, but is there a way to get to the data structures of the
kernel???
Mark
--
Nice testing in little China...
To Unsubscribe: send mail t
unsubscribe freebsd-hackers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Similarly, what about hardware compression support? Say in conjunction
with the LanMedia 1504P 4-port T1/E1 card?
Len
> > Does FreeBSD support hardware crypto?
>
>We've issued a device major number for nCipher's nFast PCI hardware
>cryptographic accelerator. I'd suggest contactin
On Thu, 13 Apr 2000 10:30:04 +0100, Nik Clayton wrote:
> Does FreeBSD support hardware crypto?
We've issued a device major number for nCipher's nFast PCI hardware
cryptographic accelerator. I'd suggest contacting the nCipher guy who
asked for the device major, John Hartley <[EMAIL PROTECTED]>
[ slashdot.org hat firmly on head, FU set to me ]
Does FreeBSD support hardware crypto?
There'll shortly be a story on /. about OpenBSD's hardware crypto support,
in the form of the HiFn 7751 chip. OpenBSD recommend buying them from
www.powercrypt.com.
If you go there you'll see that FreeBSD s
29 matches
Mail list logo
