> everything is working fine as it used to after installing current but i get this
>error message when ppp tries to connect
>
> "ppp[52]: tun0: Warning: deflink: /dev/cuaa1: Bad file descriptor" i'm not sure
>how to fix this any ideas ?
[.]
You'll need to explain a bit more, and maybe sh
Since sometime last month, rc5des failed to start from my rc.local. I did
a little investigation and it turned out that rc5des was started but later
terminated by a SIGHUP. During its brief lifetime, /dev/console was its
control terminal. Does anyone know what was going on?
-lq
To Unsubscribe:
everything is working fine as it used to after installing
current but i get this error message when ppp tries to connect
"ppp[52]: tun0: Warning: deflink: /dev/cuaa1: Bad file
descriptor" i'm not sure how to fix this any ideas
?
Months. :)
> Any idea of when 4.0-RELEASE will be out, in terms of months or years?
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
This is the output of my systat -vm 1 after the upgrade to gcc 2.95.2:
2 usersLoad 0.13 0.58 0.63 Wed Nov 17 19:11
Mem:KBREALVIRTUAL VN PAGER SWAP PAGER
Tot Share TotShareFree in out in out
Act
> > You mean along the lines of if_xx.ko? That might be an idea, apart
> > from the fact that then the module name does not correspond in any
> > way to the name used in the manpage.
>
> I'd love to see the various modules grouped logically. I'd vote in
> favor of usb_* in case it counts...
It
> > Yes. Boot system, kldload ums_mod, kldload umass_mod, plug in mouse and
> > Zip drive and off you go.
>
> I assume "_mod" stands for module. Would you consider dropping that from
> the name? Very view things in /modules have "_mod" in their names.
That was done because of some problem in c
In article <[EMAIL PROTECTED]>, Frank Mayhar
<[EMAIL PROTECTED]> wrote:
> Bob Bishop wrote:
>
> > BUT I have to say that on principle I'm with Rod on this one: EOF
> > != EOT and mixing them up is a recipe for (inter alia) finding you
> > can't read back dumps when you need them.
>
> Not to mentio
Julian Elischer wrote in list.freebsd-current:
> On Wed, 17 Nov 1999, Oliver Fromme wrote:
> > Adam Wight wrote in list.freebsd-current:
> > > x I like the -e option when I'm root and trying to debug things. I
> > > x think that peter's fix seems to be ideal. You can find out about your
since the environment is supposed to be part of the address space
it is ssupposed to be private..
On Wed, 17 Nov 1999, Oliver Fromme wrote:
> Adam Wight wrote in list.freebsd-current:
> > x I like the -e option when I'm root and trying to debug things. I
> > x think that peter's fix seems t
Adam Wight wrote in list.freebsd-current:
> x I like the -e option when I'm root and trying to debug things. I
> x think that peter's fix seems to be ideal. You can find out about your
> x own uid, but no one else's unless you are root.
>
> I agree, but anything that runs suid has to be
In message <02d801bf3132$71f6f8c0$[EMAIL PROTECTED]>, "David W. Chapman Jr.
" writes:
>Any idea of when 4.0-RELEASE will be out, in terms of months or years?
Feature freeze in this year. Release in Q1/2000.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]
On Wed, 17 Nov 1999, Daniel C. Sobral wrote:
> Doug Rabson wrote:
> >
> > > Well, I finally decided to try to get my sound card working again.
> > > It is not detected as a PNP device, but rather as a motherboard
> > > resource using PNPBIOS. It is supposed to be an ESS1869 and, indeed,
> > > I
Any idea of when 4.0-RELEASE will be out, in terms of months or years?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
The core team has discussed the issue of bumping the libstdc++
version numer because of the compiler upgrade:
Yes, we do have a rule saying ``only one bump per release'',
and that rules still stands. But no rule without exception:
Clearly what we're looking at here deserves a version number
b
-BEGIN PGP SIGNED MESSAGE-
In message <[EMAIL PROTECTED]> TrouBle writes:
: just a quick note, where do i find the information needed about the bind
: problem i face in 3.3-RELEASE if any ??
You can find it at the BIND web site.
FreeBSD has Bind 8.1.2.
- From the chart at
http
On Wed, 17 Nov 1999, Sheldon Hearn wrote:
> XFree86 makes it through the ports ``build'' target just fine. It
> breaks in ``install''. That's why I told Manfred I wasn't seeing the
> problem.
I'd imagine the confusion is caused by the install target (improperly)
building things. Yet another pr
-BEGIN PGP SIGNED MESSAGE-
In message <[EMAIL PROTECTED]> Ben Rosengart
writes:
: I'd be happier if you said the message was *from* the security officer. :-)
I am the security officer. :-) That's why I get the
secuirty-officer's mail :-). I've not verified the information by
inspecti
x I like the -e option when I'm root and trying to debug things. I
x think that peter's fix seems to be ideal. You can find out about your
x own uid, but no one else's unless you are root.
I agree, but anything that runs suid has to be excluded as well.
-Adam Wight
To Unsubscribe: send ma
On Wed, 17 Nov 1999, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Forrest Aldrich writes:
> : So wouldn't be the impact if a server was compromized in the absence
> : of an available fix :)
>
> A message to the security officer indicated that we don't have the
> root hole in -current or -
In message <[EMAIL PROTECTED]> Forrest Aldrich writes:
: So wouldn't be the impact if a server was compromized in the absence
: of an available fix :)
A message to the security officer indicated that we don't have the
root hole in -current or -stable, but are vulnerable to the DoS
attacks.
Warne
In message <[EMAIL PROTECTED]> Matthew Dillon writes:
: Why don't we get rid of the 'e' option to ps while we are at it
: considering how much of a security hole it is. I've never liked the
: 'e' option.
I like the -e option when I'm root and trying to debug things. I
think that pe
subscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Other folks may also have expressed similar sentiments, but I'll quote a
couple that I noted as I was blitzing through my >1900-message backlog
(after being in class all last week):
>Date: Wed, 10 Nov 1999 14:57:15 +0100 (CET)
>From: Oliver Fromme <[EMAIL PROTECTED]>
>Using command substitution
On Wed, 17 Nov 1999, Martin Cracauer wrote:
> I can now reproduce the problem. Please test the appended diff which
> should fix this problem while still working for the
> here-backquote-three-stage-pipeline case.
>
> My apology especially to Bruce, I managed to pass your test case by
> not copy/
[redirected to -CURRENT]
Repeat after me:
If I am running -CURRENT, I should be subscribed to -CURRENT, and
that's where I should send my messages about -CURRENT.
On Wednesday, 17 November 1999 at 9:53:19 -0500, Christopher Stein wrote:
>
> Could someone please tell me why bdevsw has disa
> Martin Cracauer writes:
>> Today I encountered again the problem when doing `man MIME::*' (you
>> have to install /usr/ports/mail/p5-MIME-Tools). Curiously, I have no
>> problem with `man \*'
>> Again reverting to eval.c r1.22 solve the problem.
> I can now reproduce the problem. Ple
In <[EMAIL PROTECTED]>, Jean-Marc Zucconi wrote:
> > Steve Price writes:
>
> > On Mon, 8 Nov 1999, Jean-Marc Zucconi wrote:
> > # > Jean-Marc Zucconi writes:
> > #
> > # > Try this in -current
> > # > $ cat some_file | head
> > #
> > # > I have to use ^C to regain control.
>
> Steve Price writes:
> On Mon, 8 Nov 1999, Jean-Marc Zucconi wrote:
> # > Jean-Marc Zucconi writes:
> #
> # > Try this in -current
> # > $ cat some_file | head
> #
> # > I have to use ^C to regain control.
> #
> # ... and reverting to rev. 1.22 of eval.c fixes the problem.
> > I'll be pulling the switch to use GCC 2.95.2 as the base compiler in
> > -CURRENT on Sunday evening (Freefall time).
>
> It seems that currently after introduction of 2.95.2 world could not be
> compiled with -jN option (complains about not being able to locate genrtl.h).
This patch make "ma
Doug Rabson wrote:
>
> > Well, I finally decided to try to get my sound card working again.
> > It is not detected as a PNP device, but rather as a motherboard
> > resource using PNPBIOS. It is supposed to be an ESS1869 and, indeed,
> > I use ESS drivers on Windows. But Compaq obviously decided t
On Mon, Nov 15, 1999 at 01:59:55PM -0500, spork wrote:
> I noticed that ipfilter is still gone... Was there any resolution here,
> or is ipfilter gone for good?
>
> All other concerns/features aside, I find the stateful inspection stuff
> much easier to setup than the ipfw filtering... I only t
32 matches
Mail list logo
