okI give up!
I've been getting this error for ages when doing a
'make depend' on the current tree and up to now
I've just done a 'make -k' to get it to work.
Whats the final solution so I don't have to do this?
What stupid thing have I missed somewhere along the line.
===> gnu/usr.bin/per
I've never thought of a use for fdescfs...
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000
---> X_.---._/ presently in: Perth
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote:
> I've never thought of a use for fdescfs...
Well.. just a trivial example - imagine a program which takes a filename
as an argument; imagine yourself trying to pipe something into it -
passing /dev/fd/0 as a filename to process wou
Hi ...
I'm running a current machine of 12 Sept although this problem
also occured on a current of a few days earlier ...
This only happens when using the IPv6 IPSec code during the day,
it is readily reproduceable.
If during the day I load the racoon daemon and load keys and
establish a IPSec
In message <[EMAIL PROTECTED]>, Peter Pentchev writes
:
>On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote:
>> I've never thought of a use for fdescfs...
>
>Well.. just a trivial example - imagine a program which takes a filename
>as an argument; imagine yourself trying to pipe somet
On Wed, Sep 13, 2000 at 10:48:20AM -0400, Brian A. Seklecki - Stargate Industries, LLC
- NOC wrote:
> You're running vmware sucsessfully in --current?
Yes. -current from August 18th, and I'm running the vmware2-2.0.2.621 port.
Installing Win98 took about 4 hours though -- most of that was wh
Leif Neland wrote:
> How is that done?
> Will gdb not attach to init, or will init not let gdb attach?
The kernel won't let GDB attach. Look at the code for ptrace()...
/* can't trace init when securelevel > 0 */
if (securelevel > 0 && p->p_pid == 1)
On Thu, 14 Sep 2000, Joel M. Baldwin wrote:
> okI give up!
>
> I've been getting this error for ages when doing a
> 'make depend' on the current tree and up to now
> I've just done a 'make -k' to get it to work.
>
> Whats the final solution so I don't have to do this?
>
> What stupid thing
Poul-Henning Kamp wrote:
> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> is bogus. It looks like something which happened "because we can" more
> than something which has a legitimate need.
You think adding a hack to every program to support "-" to mean
stdout/std
In message <[EMAIL PROTECTED]>, Ben Smithurs
t writes:
>Poul-Henning Kamp wrote:
>
>> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
>> is bogus. It looks like something which happened "because we can" more
>> than something which has a legitimate need.
>
>You think ad
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Sep 14, 2000 at 02:37:06PM +0200, Poul-Henning Kamp wrote:
[snip]
> The majority of these programs could be handled by adding knowledge
> of "-" as a magic filename to fopen(3).
>
> At the same time I would really love if we implemented "|.*" to mean
> "do an popen(3)" instead.
Heh, and
[EMAIL PROTECTED] said:
:- The majority of these programs could be handled by adding knowledge of
:- "-" as a magic filename to fopen(3).
Suppose I *want* a filename called "-"? My tough luck, huh?
I *like* /dev/stdin. It's orthogonal!
--
Robert Withrow -- (+1 978 288 8256)
[EMAIL PROTECTE
Title:
Mehr Effizienz
und Erfolg mit den besten Marketing-Praxis-Checklisten
Liebe Marketingverantwortliche
Stellen Sie sich vor, Sie müssten bis morgen um 10.00 Uhr ein
erfolgsversprechendes Messekonzept präsentieren.
Oder kreative Ideen für die nächste Direct-Mail-Aktion und bis
in
zw
> [EMAIL PROTECTED] said:
> :- The majority of these programs could be handled by adding knowledge of
> :- "-" as a magic filename to fopen(3).
>
> Suppose I *want* a filename called "-"? My tough luck, huh?
Could you settle for "./-"?
> Robert Withrow -- (+1 978 288 8256)
> [EMAIL PROTECTED]
Johnny Eriksson wrote:
> > [EMAIL PROTECTED] said:
> > :- The majority of these programs could be handled by adding knowledge of
> > :- "-" as a magic filename to fopen(3).
> >
> > Suppose I *want* a filename called "-"? My tough luck, huh?
>
> Could you settle for "./-"?
>
I think any "magic"
Poul-Henning Kamp writes:
> In message <[EMAIL PROTECTED]>, Ben Smithurs
> t writes:
> >Poul-Henning Kamp wrote:
> >
> >> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> >> is bogus. It looks like something which happened "because we can" more
> >> than something whic
In message <[EMAIL PROTECTED]>, Robert Withro
w writes:
>
>[EMAIL PROTECTED] said:
>:- The majority of these programs could be handled by adding knowledge of
>:- "-" as a magic filename to fopen(3).
>
>Suppose I *want* a filename called "-"? My tough luck, huh?
./-
Very few programs understand
Poul-Henning Kamp wrote:
> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> is bogus. It looks like something which happened "because we can" more
> than something which has a legitimate need.
I strongly disagree. I actually have a script that I use daily which requi
I just realized this may be a difference due to a between -current and
-stable, so I've moved discussion to -current to check. Apologies if
this was the wrong thing to do.
On Wed, 13 Sep 2000, Mike Meyer wrote:
> It then fails to install for me with the error messages:
>
> /tmp/sv001.tmp/setup.b
< said:
> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> is bogus. It looks like something which happened "because we can" more
> than something which has a legitimate need.
It's required if we ever get around to supporting secure set-id shell
scripts. (I think th
MIT's Technology Licensing Office has given me the OK to distribute
rsa_eay.c, so it will now be available from cvsup3.freebsd.org (aka
freebsd.lcs.mit.edu).
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O Siem / The fires of f
Garrett Wollman wrote:
> [/dev/stdin] also helps when bogus programs refuse to read from the
> standard input.
Or if you want to read more than one file, one of which is standard input.
e.g.
gzip -dc oldlogs.*.gz | cat /dev/stdin todays-log | log-analyzer ...
Of course that will work with "-"
Well, it's time I learned about the rather cryptic newbus stuff...
So where are the best docs to read on it.?
Ones that give an overview?
"UTSL" and "See man 9 {cryptic function name}" are not the
answers I'm looking for...
Someone once mentionned an actual
document but I've been unable to
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Peter Pentchev writes
> :
> >On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote:
> >> I've never thought of a use for fdescfs...
> >
> >Well.. just a trivial example - imagine a program which takes a filename
> >as an argument
On Thu, 14 Sep 2000, John Baldwin wrote:
> Poul-Henning Kamp wrote:
> > In message <[EMAIL PROTECTED]>, Peter Pentchev writes
> >
> > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> > is bogus. It looks like something which happened "because we can" more
> > than so
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Mark Murray writes:
> : > In message <[EMAIL PROTECTED]> Warner Losh wri
> : tes:
> : > : 2) APM is now broken. It worked after the ACPI integration,
> : > :but after the SMPNG stuff neither apm -z nor the BIOS keys
> : > :
Hi,
I made KLD module of ip6_fw. Please review it.
http://www.imasy.or.jp/~ume/ipv6/FreeBSD/ip6_fw-kld-5C.diff for 5-CURRENT
http://www.imasy.or.jp/~ume/ipv6/FreeBSD/ip6_fw-kld-41R.diff for 4.1-RELEASE
Thanks,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECT
In message <[EMAIL PROTECTED]> John Baldwin writes:
: It may be a kernel/world sync problem. Although I don't know why the ioctl
: argument would suddenly become invalid. Maybe it passes in a struct ucred,
: which changed in size just before the SMPng commit?
I don't know either. However, it m
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> John Baldwin writes:
> : It may be a kernel/world sync problem. Although I don't know why the ioctl
> : argument would suddenly become invalid. Maybe it passes in a struct ucred,
> : which changed in size just before the SMPng commit?
>
> I do
In message <[EMAIL PROTECTED]> John Baldwin writes:
: Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> John Baldwin writes:
: > : It may be a kernel/world sync problem. Although I don't know why the ioctl
: > : argument would suddenly become invalid. Maybe it passes in a struct ucred,
: > :
At 11:48 AM +0200 9/14/00, Poul-Henning Kamp wrote:
>I must admit that I think in general that /dev/std{in,out,err}
>and /dev/fd is bogus. It looks like something which happened
>"because we can" more than something which has a legitimate need.
>
>If anything I would propose we ditch it...
I thi
< said:
> Hmmm, they look good to me. Maybe Mark's system doesn't have group
> operator at gid 5. That's one bad thing about the new DEVFS: it
> appears to enshrine things like this in the kernel...
It would only take a small amount of Makefile magic to fix
this... something like:
PASSWD?=
In message <[EMAIL PROTECTED]> Garrett Wollman writes:
: < said:
: > Hmmm, they look good to me. Maybe Mark's system doesn't have group
: > operator at gid 5. That's one bad thing about the new DEVFS: it
: > appears to enshrine things like this in the kernel...
:
: It would only take a small am
< It would only take a small amount of Makefile magic to fix
> this... something like:
> perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \
>$_[2], "\n");' ${PASSWD} >${.TARGET}
Oh, I forgot to point out -- this would be easy to do in AWK a
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> John Baldwin writes:
>: Warner Losh wrote:
>: > In message <[EMAIL PROTECTED]> John Baldwin writes:
>: > : It may be a kernel/world sync problem. Although I don't know why the ioctl
>: > : argument would suddenly
On Thu, Sep 14, 2000 at 04:53:54PM -0400, Garrett Wollman wrote:
> (Probably easier, actually, but I don't know AWK well enough to
> actually implement it.)
awk -F: '$0 ~/^(#|$)/ {next}
{print "#define\tUID_" toupper($1) "\t" $3}' ${PASSWD} > ${.TARGET}
--
Jos Backus _/ _/_
On 14-Sep-00 at 05:37, Poul-Henning Kamp ([EMAIL PROTECTED]) wrote:
> >You think adding a hack to every program to support "-" to mean
> >stdout/stdin is better?
>
> The majority of these programs could be handled by adding knowledge
> of "-" as a magic filename to fopen(3).
>
> At the same time
In message <[EMAIL PROTECTED]> Garrett Wollman writes:
: It's required if we ever get around to supporting secure set-id shell
: scripts. (I think this was the rationale for originally introducing
: it.) It also helps when bogus programs refuse to read from the
: standard input.
I'd like to see
In message <[EMAIL PROTECTED]> Julian Elischer writes:
: Someone once mentionned an actual
: document but I've been unable to find it.
: Was it my imagination?
: (and if so, why isn't there one?)
What do you mean actual document? man pages are actual documents.
What kind of document do you want?
Bruce Evans wrote:
> On Sat, 9 Sep 2000, Ben Smithurst wrote:
>
>> After poking around a bit with remote GDB, this seems to be caused by a
>> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM.
>>
>> The attached rather crude patch has "fixed" the problem for now, but
>> doe
On Thu, 14 Sep 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Julian Elischer writes:
> : Someone once mentionned an actual
> : document but I've been unable to find it.
> : Was it my imagination?
> : (and if so, why isn't there one?)
>
> What do you mean actual document? man pages a
Ben Smithurst wrote:
> Bruce Evans wrote:
>
> > On Sat, 9 Sep 2000, Ben Smithurst wrote:
> >
> >> After poking around a bit with remote GDB, this seems to be caused by a
> >> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM.
> >>
> >> The attached rather crude patch has "f
In message <[EMAIL PROTECTED]> Matthew Jacob
writes:
: I would imagine an overall architecture doc. Sort of like what
: Jordan just did for sysinst (e.g.).
Then he should ask for an architecture doc rather than being so snippy
and snide about "actual documentation."
Warner
To Unsubscribe: sen
On Thu, 14 Sep 2000, Warner Losh wrote:
>In message <[EMAIL PROTECTED]> Julian Elischer writes:
>: Someone once mentionned an actual
>: document but I've been unable to find it.
>: Was it my imagination?
>: (and if so, why isn't there one?)
>
>What do you mean actual document? man pages are actu
> In message <[EMAIL PROTECTED]> Matthew Jacob
>writes:
> : I would imagine an overall architecture doc. Sort of like what
> : Jordan just did for sysinst (e.g.).
>
> Then he should ask for an architecture doc rather than being so snippy
> and snide about "actual documentation."
Probably, but
Is there any progress in mtree fixing process?
I think there is acceptable solution, in following steps:
1) Return mtree defaults.
2) Add -L
3) Add ${MTREE_FOLLOW_LINKS} to mtree calls (which expands to nothing in
old systems, so we not broke anything in the transition process)
4) Add
MTREE_FOLL
In message <[EMAIL PROTECTED]> "Andrey A. Chernov" writes:
: Is there any progress in mtree fixing process?
It hasn't been high on my list. I'd be happy to review patches,
however.
: I think there is acceptable solution, in following steps:
:
: 1) Return mtree defaults.
: 2) Add -L
: 3) Add ${
I have two questions. Recently, I started seeing the message:
module sn already present!
when dhclient runs on my sn device. What causes this?
Second, on both my sn card and my aue cards are installed I get:
WARNING: Driver mistake: repeat make_dev("bpf0")
What do these mean?
>
> I have two questions. Recently, I started seeing the message:
> module sn already present!
> when dhclient runs on my sn device. What causes this?
It's caused by the 'sn' driver's module being called 'sn' rather than
'if_sn'. The code in ifconfig that tries to autoload modules for
On Thu, Sep 14, 2000 at 05:41:46PM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> "Andrey A. Chernov" writes:
> : Is there any progress in mtree fixing process?
>
> It hasn't been high on my list. I'd be happy to review patches,
> however.
Here it is:
--- usr.sbin/mtree/mtree.c.ori
On Tue, Sep 12, 2000 at 06:28:05PM -0700, Kris Kennaway wrote:
> > I'm also not sure where the rumors about a FreeBSD 4.1.5 got started
> > since I'd certainly never planned on such a thing, that, I think,
4.1.1 rather than 4.1.5 please.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
On Tue, Sep 12, 2000 at 06:11:20PM +0200, Niels Chr. Bank-Pedersen wrote:
> Hmm, how about those of us doing buildworlds/buildkernels on
> one (nfs)server for subsequent installworlds/installkernels
> on multiple other machines?
Use the `make reinstall' target with KERNEL_KO set to the name of th
On Tue, Sep 05, 2000 at 08:30:48AM -0700, Peter S. Housel wrote:
> > [Alexander, I'm Cc:ing you on this just in case you have heard of
> > anyone else having similar problems with Aureal cards with recent
> > -currents]
Sorry, I couldn't respond any earlier. I was out of business for a
while.
>
Greg Lehey wrote:
>
> FWIW, I was never happy with the removal of block devices either. I
> was shouted down with "can you point to any one use they are?", to
> which I replied "just because I don't know of one doesn't mean there
> isn't one, or that there will never be one in the future". This
Mike Smith wrote:
>
> >
> > Doesn't Oracle run MUCH better when given raw block disk devices to store
> > data on?
>
> Oracle wants to cache it's own data, it doesn't want the buffer cache
> behind it.
Yes, now it's all coming back. It's amazing how much you can forget in
the space of a decad
> > : zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument"
> >
> > I noticed this with the first SMPNG kernel I tried. The newer one
> > this problem disappeared. Don't know why it would matter, but I may
> > have missed a commit while in new mexico.
>
> It may be a kernel/world s
> I don't know either. However, it might be because of permission
> problems. It will return EINVAL when it can't open the apm file for
> write. Maybe a devfs related issue?
I don't have devfs on this system yet.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscr
In message <[EMAIL PROTECTED]> Mark Murray writes:
: > I don't know either. However, it might be because of permission
: > problems. It will return EINVAL when it can't open the apm file for
: > write. Maybe a devfs related issue?
:
: I don't have devfs on this system yet.
Odd that. That's t
> : > I don't know either. However, it might be because of permission
> : > problems. It will return EINVAL when it can't open the apm file for
> : > write. Maybe a devfs related issue?
> :
> : Hmm, it may not be using the right perms during make_dev perhaps.
>
> Hmmm, they look good to me.
Some time ago somebody tried to fix "\ No newline at end of file" bug in diff
and seems that he had not reached the target - the diff is still broked,
however in a slightly different way (tested both with 4-stable and 5-current).
See:
http://people.freebsd.org/~sobomax/config.h.orig
http://peopl
> In message <[EMAIL PROTECTED]> Mark Murray writ
es:
> : > I don't know either. However, it might be because of permission
> : > problems. It will return EINVAL when it can't open the apm file for
> : > write. Maybe a devfs related issue?
> :
> : I don't have devfs on this system yet.
>
> Od
62 matches
Mail list logo
