> You are probably using a -CURRENT with a broken randomness
> device. For more information you can try and search the
> mailing list archives.
No - he has _no_ randomness device.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED
In article <[EMAIL PROTECTED]>,
Patrick Gardella <[EMAIL PROTECTED]> wrote:
> I've somehow been burned by the config changes when I build world
> yesterday. The build went fine, and then I followed the instructions
> on: http://people.freebsd.org/~imp/config-upd.html
>
> But when I rebooted, it
I've somehow been burned by the config changes when I build world
yesterday. The build went fine, and then I followed the instructions
on: http://people.freebsd.org/~imp/config-upd.html
But when I rebooted, it freezes right when I type "boot". Typing "boot
-v" does not reveal anything more.
Sam Xie wrote:
>
> Hi! All,
> I upgraded my OS to FreeBSD 5.0-CURRENT #20, everything seems fine except
> ssh. Every time if I try to ssh to another host, the system gives me an error
> message says,
> "ssh: no RSA support in libssl and libcrypto. See ssl(8).
> Disabling pr
Kris Kennaway wrote:
> On Tue, 11 Jul 2000, Ben Smithurst wrote:
>
>> 'pseudo-device stf' gives an error, stf lives in the gif driver, so this
>> is required really. Is that ok? Is there anyone at KAME I should send
>> this to as well?
>
> Um, "device stf" certainly does work.
Ah. I'm using
On Tue, 11 Jul 2000, Kris Kennaway wrote:
> Hmm, well it went away after a binutils recompile. So maybe I just still
> had the old version or something. *shrug*
Yes, I did:
> ld -V
GNU ld version 2.10-anoncvs-2512 (with BFD 2.10-anoncvs-2512)
Supported emulations:
elf_i386
> ld -V
On Tue, 11 Jul 2000, Kris Kennaway wrote:
> Since setting my malloc.conf flags to AJ I'm getting spontaneous sig10's
> in ld(1) - in fact I can't link anything with those flags set. Can anyone
> else confirm?
Hmm, well it went away after a binutils recompile. So maybe I just still
had the old ve
Since setting my malloc.conf flags to AJ I'm getting spontaneous sig10's
in ld(1) - in fact I can't link anything with those flags set. Can anyone
else confirm?
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>
To Unsubscribe:
Hi! All,
I upgraded my OS to FreeBSD 5.0-CURRENT #20, everything seems fine except
ssh. Every time if I try to ssh to another host, the system gives me an error
message says,
"ssh: no RSA support in libssl and libcrypto. See ssl(8).
Disabling protocol version 1
DH
> Dag-Erling Smorgrav <[EMAIL PROTECTED]> wrote:
> It seems that fetch(1) can not fetch any file. In this case, the
> downloaded(?) file size is zero.
DES> Make sure you have revision 1.2 (or newer) of src/usr.bin/fetch/fetch.c:
I cvsupped 20 minutes ago and remade libfetch and fetch. It
On Tue, 11 Jul 2000, Ben Smithurst wrote:
> I'd like to commit this:
>
> --- stf.4 2000/07/04 16:39:23 1.4
> +++ stf.4 2000/07/11 13:44:47
> @@ -36,7 +36,7 @@
> .Nd
> .Tn 6to4 tunnel interface
> .Sh SYNOPSIS
> -.Cd "pseudo-device stf"
> +.Cd "pseudo-device gif"
> .Sh DESCRIPT
On Tue, Jul 11, 2000 at 07:00:52PM +0200, Sheldon Hearn wrote:
>
>
> On Mon, 10 Jul 2000 11:14:16 MST, Eric Anholt wrote:
>
> > I am getting freezes on -current as of my last two updates, Jul. 9
> > and today, Jul. 10. My previous update was around Jun 14. I can
> > boot the kernel from th
I like to use:
tar cvpf /dev/ersa0 . >> /var/log/bu.log
so that it ejects the tape automatically after the archive is complete.
--
Cheers,
Mikel
+~+
| Optimized Computer Solutions, Inc
http://www.ocsny.com
| 39 W14th Street, S
The subject says it all.
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
orld'.
> Date Lines Make Time Lines/Minute
> - -
> 19991018 35281 6h40m16s 88.20
> 2401 39490 7h56m18s 82.96
> 2402 39427 7h28m41s 88.01
> 2412 39404 7h10m21s 91.64
> 2621 38679 7h20m20s 87.91
> 2630 39530 7h56m20
Yevmenkin, Maksim N, CSCIO writes:
> > Which changes in particular are you asking about?
>
> the attach/detach ``ng_ether'' nodes
I was planning on MFC'ing that soon.
-Archie
___
Archie Cobbs * Whistle Communications,
On Tue, Jul 11, 2000 at 14:50:08 -0500, Robert Small wrote:
> I'm running an adaptec controller (1542CF) with a Sony SDT-5000. I'm
> running:
>
> reeBSD (5.0-2511-CURRENT FreeBSD 5.0-2511-CURRENT #4: Thu Jul 6
> 20:31:41 CDT 2000)
>
> When I issue the command "camcontrol eject sa0" I re
> Which changes in particular are you asking about?
the attach/detach ``ng_ether'' nodes
thanks,
emax
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Yevmenkin, Maksim N, CSCIO writes:
> Does anybody knows when -current NETGRAPH changes
> will be back ported to 4.X branch (if they ever will)?
Which changes in particular are you asking about?
-Archie
___
Archie Cobbs *
If memory serves me right, "Robert Small" wrote:
> I'm running an adaptec controller (1542CF) with a Sony SDT-5000. I'm
> running:
>
> reeBSD (5.0-2511-CURRENT FreeBSD 5.0-2511-CURRENT #4: Thu Jul 6
> 20:31:41 CDT 2000)
>
> When I issue the command "camcontrol eject sa0" I receive:
>
>
I'm running an adaptec controller (1542CF) with a Sony SDT-5000. I'm
running:
reeBSD (5.0-2511-CURRENT FreeBSD 5.0-2511-CURRENT #4: Thu Jul 6
20:31:41 CDT 2000)
When I issue the command "camcontrol eject sa0" I receive:
Error received from stop unit command
When I issue the command "c
>I seem to see somewhat of a performance drop in the past week.
You should have read the commit messages :-)
I enabled malloc flags AJ by default, this has a performance
cost. It will be turned off for releases of course.
It has already exposed on bug (see peters commit).
You can disable it
>19991018 35281 6h40m16s 88.20
>2401 39490 7h56m18s 82.96
>2402 39427 7h28m41s 88.01
>2412 39404 7h10m21s 91.64
>2621 38679 7h20m20s 87.91
>2630 39530 7h56m20s 83.05
>2709 39679 8h40m28s 76.31
>2710 39568 9h13m46s 71.55
>2711 41178
7h56m18s 82.96
2402 39427 7h28m41s 88.01
2412 39404 7h10m21s 91.64
2621 38679 7h20m20s 87.91
2630 39530 7h56m20s 83.05
2709 39679 8h40m28s 76.31
2710 39568 9h13m46s 71.55
2711 41178 9h22m05s 73.27
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hajimu UMEMOTO wrote:
>> On Tue, 11 Jul 2000 14:56:35 +0100
>> Ben Smithurst <[EMAIL PROTECTED]> said:
>
> ben> 'pseudo-device stf' gives an error, stf lives in the gif driver, so this
> ben> is required really. Is that ok? Is there anyone at KAME I should send
> ben> this to as well?
In article <[EMAIL PROTECTED]>,
Alexander Leidinger <[EMAIL PROTECTED]> wrote:
> On 10 Jul, Will Andrews wrote:
>
> >> Only if ports-base isn't anymore in ports-all or my local CVS tree is
> >
> > ports-base was/has never [been] in ports-all, for some strange reason.
>
> Really?
[...]
> I read
On Mon, 10 Jul 2000 11:14:16 MST, Eric Anholt wrote:
> I am getting freezes on -current as of my last two updates, Jul. 9
> and today, Jul. 10. My previous update was around Jun 14. I can
> boot the kernel from the last update just fine, though ppp doesn't
> work due to net changes.
Just
On Fri, Jun 30, 2000 at 06:29:11AM -0700, Andrey A. Chernov wrote:
> On Wed, Jun 28, 2000 at 11:03:22PM -0700, Andrey A. Chernov wrote:
> > Fresh -current kernel with fresh -current bootblocks loaded ok but hangs in
> > boot (no diagnostics even printed, just silent hang with "/" on the screen).
Hello All,
Does anybody knows when -current NETGRAPH changes
will be back ported to 4.X branch (if they ever will)?
Thanks,
emax
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I'm using moused in conjunction with XFree86 4.0.1 and /dev/sysmouse.
Recently, my mouse pointer has been extremely jumpy in XFree86. I
think this is a syscons problem, as I have this problem with moused at
the console as well. Also, cursor movement is very jumpy.
--
- Donn
To Unsubscribe:
> On Tue, 11 Jul 2000 14:56:35 +0100
> Ben Smithurst <[EMAIL PROTECTED]> said:
ben> 'pseudo-device stf' gives an error, stf lives in the gif driver, so this
ben> is required really. Is that ok? Is there anyone at KAME I should send
ben> this to as well?
No. Before merging latest KAME,
I am getting freezes on -current as of my last two updates, Jul. 9
and today, Jul. 10. My previous update was around Jun 14. I can
boot the kernel from the last update just fine, though ppp doesn't
work due to net changes. (I'm stuck using the mac with a modem as a
natting router. ugh.) B
On Tue, Jul 11, 2000 at 15:28:45 +0100, David Malone wrote:
> I've just changed the daily security secipt to include the inode
> numbers of suid files. This means the first time you run the updated
> script you will see lots of files have "changed" - this is just
> the inclusion of the inode numbe
Sheldon Hearn wrote:
> On Tue, 11 Jul 2000 14:56:35 +0100, Ben Smithurst wrote:
>
>> 'pseudo-device stf' gives an error, stf lives in the gif driver, so this
>> is required really. Is that ok? Is there anyone at KAME I should send
>> this to as well?
>
> I'm interested to see how the KAME fol
Hi,
I've finally managed to capture a crashdump after a panic in sbdrop(). The
machine in question uses ppp/ipfw/natd to connect a small LAN to the
outside world via a DSL link. ppp started to misbehave: NS queries were
sent out but didn't come back (I had tcpdumps running on both tun0 and
ed1). I
If you dont use the loader, then the device.hints wont load and you wont
have a console for the kernel to print to. I had the same symptoms the
other day when I typo'ed the name of the device.hints file. Don't know
where your loader went but if I were you I'd try compiling it and sticking
it in
I've just changed the daily security secipt to include the inode
numbers of suid files. This means the first time you run the updated
script you will see lots of files have "changed" - this is just
the inclusion of the inode numbers in the listing.
I'd like to MFC this to 4.X in a few days, but I
On Mon, 10 Jul 2000, Mike Meyer wrote:
:Daniel C. Sobral writes:
:> Mike Meyer wrote:
:> The multiple levels are there to deal with changes in state. In BSD, for
:> instance, we have single user/multi-user. A number of other variations
:> can exist, both in heavy duty servers where you might want
On Tue, 11 Jul 2000 14:56:35 +0100, Ben Smithurst wrote:
> 'pseudo-device stf' gives an error, stf lives in the gif driver, so this
> is required really. Is that ok? Is there anyone at KAME I should send
> this to as well?
I'm interested to see how the KAME folks react to our chucking out th
Well, I fixed the problem with a serial console, and doing
cp /boot/loader.old /boot/loader
Has anyone else seen anything like this? Or is it flat-out pilot error?
Thanks,
==ml
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Kris Kennaway wrote:
> In this vein, I'd like to suggest a new "hands-off" policy of not
> committing gratuitous changes to KAME-derived code, including manpage
> changes, unless:
>
> a) The commit is required for operation on FreeBSD (in which case it's not
> really gratuitous)
I'd like to com
Before I start digging into this, I thought someone might have a lead
for me. The archives say nothing, although I'm not sure how to search
on something like this. ("Just Plain Weird" generates too many hits.)
I just upgraded to yesterday's -current from last week's -current.
via make buildworl
Hi,
I updated the patch for tcp_wrappers to support IPv6 scoped address.
It enables us to control link-local connections by interface like
this:
ALL : ALL@[fe80::%ed0]/10 : allow
ALL : ALL@[fe80::]/10 : deny
I'd like to commit it. Though, new IPv6 support code is running
withou
Jordan,
> I've looked at this driver and think it looks useful, though I'm a
> little concerned about the handling of bridge support. We don't
> really encourage users to edit module Makefiles just to enable a given
> feature in the compiled module
[...]
i think that whole ``#ifdef BRIDGE''
Hi,
I wrote IPv6 support code for FreeBSD installer. It was tested by
Japanese IPv6 guys and seems OK. So, I'd like to commit it. Could
someone please review it before commit?
There are the diff against 5.0-CURRENT and FD images built under
4.0-STABLE here:
http://www.imasy.or.jp/~um
On 10 Jul, Will Andrews wrote:
>> Only if ports-base isn't anymore in ports-all or my local CVS tree is
>
> ports-base was/has never [been] in ports-all, for some strange reason.
Really?
/usr/share/examples/cvsup/ports-supfile:
---snip---
## Ports Collection.
#
# The easiest way to get the por
On Mon, 10 Jul 2000, Nick Hibma wrote:
> The opt_ files can be generated by the makefiles, so there is no reason
> to remove those, see sys/modules/usb/Makefile
>
> SRCS = bus_if.h device_if.h usb_if.h usb_if.c \
>vnode_if.h \
>opt_usb.h \
>
"Daniel C. Sobral" <[EMAIL PROTECTED]> writes:
> Cyrille Lefevre wrote:
> >
> > HP-UX :
> >
> > /sbin/init.d/script start_msg|stop_msg|start|stop (FMPOV, there isn't not
> > enough possible choises, such as status, restart, config, command, etc.)
> > /sbin/rc[S0-5].d/[SK][0-9][0-9][0-9]script l
Cyrille Lefevre wrote:
>
> > http://www.freebsd.org/~dfr/devices.html
>
> off topic.
M... I must have copied the wrong link, then...
> > http://www.freebsd.org/~eivind/newrc.html
>
> well. what about a mix of the SystemV approach (ala HP-UX) and the IRIX one
> (using something like chconf
On Mon, 10 Jul 2000, Mikel wrote:
>
> Kelly Yancey wrote:
>
> >
> > How about rather then separate directories, you prefix the symlink names
> > with 'S' for startup scripts and 'K' (for "kill") for shutdown scripts. Then,
> > you rename rc.d to rc3.d...
>
> I like it. It's clean and simple,
50 matches
Mail list logo
