Re: How to use RSA with USA_RESIDENT=NO?
In message [EMAIL PROTECTED] Jun Kuriyama writes: : After installworld, I can not use ssh with RSA. Does someone know how : to fix this problem? You may need to load the random device, or put it in your kernel. Its name recently changed, so maybe that is what is causing you problems. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux Emulation ETTW?
In message [EMAIL PROTECTED] Jordan Hubbard writes: : By ETTW i mean estimated time to work :D : : It works right now and has for the last week. If you get out of date : with your modules, on the other hand, you're shooting your own feet off. And the move to the new layout may be shooting you without your knowledge. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to use RSA with USA_RESIDENT=NO?
Jun Kuriyama wrote: After installworld, I can not use ssh with RSA. Does someone know how to fix this problem? - % ssh white ssh: no RSA support in libssl and libcrypto. See ssl(8). Disabling protocol version 1 DH_generate_key % This is going to sound weird, but did you rebuild the kernel? I'm *sure* I had my system at one point such that ssh worked with the new kernel but not with the old one. I'm not sure why, perhaps I was dreaming. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Load avg. bottoms out at 1.00
Anyone else seeing this? I just cvsup'd my kernel sources/remade my kernel an hour ago, and I'm still seeing this problem. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Load avg. bottoms out at 1.00
On Thu, Sep 14, 2000 at 02:46:30AM -0400, Donn Miller wrote: Anyone else seeing this? I just cvsup'd my kernel sources/remade my kernel an hour ago, and I'm still seeing this problem. See http://people.freebsd.org/~jasone/smp/ under known issues: Idle processor time is charged to the idle processes. 5 September 2000 Unresolved. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
miniperl not found error?
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/perl/perl Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) /usr/obj/disk2/usr.src/gnu/usr.bin/perl/perl/../miniperl/miniperl: not found *** Error code 127 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error su-2.02# To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 message
Re: Fdescfs updates--coming to a devfs near you!
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 would do the trick. G'luck, Peter -- .sith ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FW: (KAME-snap 3318) Panic on current (12 Sept)
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 tunnel connection everything works fine till
2:00 am when the daily script runs OR if I run the daily script
by hand ... I generated the following dump and backtrace ...
It seems to crash in a makedev routine using FOREACH list macro's.
The problem doesn't seem to be with the list or the makedev function
in kern_conf.c. It seems to me that something in the kernel
corrupts the static list dev_hash when using the IPSec code.
Summary - when ising IPSec ... machine panics during daily
script execution.
If you need more info from the dumps, just ask !
Reinier
- gdb bt follows qith a few prints -
(kgdb)
#5 0xc0283d53 in trap (frame={tf_fs = 16, tf_es = -65520, tf_ds = -904265712,
tf_edi = 196611, tf_esi = 197379, tf_ebp = -904254412,
tf_isp = -90425, tf_ebx = 5, tf_edx = 2, tf_ecx = -1057628672,
tf_eax = 197374, tf_trapno = 12, tf_err = 0, tf_eip = -1072335336,
tf_cs = 8, tf_eflags = 66050, tf_esp = 197379, tf_ss = -905316928})
at ../../i386/i386/trap.c:436
436 (void) trap_pfault(frame, FALSE, eva);
(kgdb)
#6 0xc0157618 in makedev (x=3, y=196611) at ../../kern/kern_conf.c:232
232 LIST_FOREACH(si, dev_hash[hash], si_hash) {
(kgdb) li
227
228 if (x == umajor(NOUDEV) y == uminor(NOUDEV))
229 Debugger("makedev of NOUDEV");
230 udev = (x 8) | y;
231 hash = udev % DEVT_HASH;
232 LIST_FOREACH(si, dev_hash[hash], si_hash) {
233 if (si-si_udev == udev)
234 return (si);
235 }
236 si = allocdev();
(kgdb) p hash
$1 = 5
(kgdb) p dev_hash[hash]
$2 = {lh_first = 0x2}
(kgdb) p dev_hash[1]
$3 = {lh_first = 0xc0fb7980}
(kgdb) p dev_hash[2]
$4 = {lh_first = 0xc0fb7900}
(kgdb) p dev_hash[3]
$5 = {lh_first = 0xc0fb9d80}
(kgdb) p dev_hash[4]
$6 = {lh_first = 0x200} - OOPS !!
(kgdb) p dev_hash[5]
$7 = {lh_first = 0x2} - OOPS - the one we use ...
(kgdb) p dev_hash[6]
$8 = {lh_first = 0xc0fb5980}
(kgdb)
-- panic message --
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x1e
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0157618
stack pointer = 0x10:0xca1a2c28
frame pointer = 0x10:0xca1a2c34
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1910 (find)
trap number = 12
panic: page fault
syncing disks... 31 31 8 8 3 3
done
Uptime: 11h37m7s
###
# #
# R.N. Bezuidenhout NetSeq Firewall #
# [EMAIL PROTECTED] http://www.nanoteq.co.za#
# #
###
--
Date: 14-Sep-00
Time: 11:43:22
This message was sent by XFMail
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 something into it -
passing /dev/fd/0 as a filename to process would do the trick.
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...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: VMWare on -current, how fast should I expect it to be?
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 when Win98 was probing for devices. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: call for testers: init securelevel patch
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) return EPERM; -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: miniperl not found error?
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 have I missed somewhere along the line. Building of perl in the normal way (not using makeworld) has been broken for a while. You have to use "make build-tools" instead of just "make depend; make" in the top-level perl directory at certain times when the build-tools are out of date (in particular, when they don't exist). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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/stdin is better? It seems to be that saying "/dev/stdin" when
you mean stdin is better than saying "-" and hoping the application
handles that correctly. Of course many programs will read stdin by
default, and write stdout by default, but that doesn't help when you
want to read more than one file, one of which is stdin.
If anything I would propose we ditch it...
And break loads of scripts at the same time?
--
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 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 I would really love if we implemented "|.*" to mean
"do an popen(3)" instead.
But of course, this is bikeshed material...
If anything I would propose we ditch it...
And break loads of scripts at the same time?
I would argue that the programs and the scripts that call them are
already broken, but hey...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
No Subject
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 break security on loads of cgi-scripts while we're at it? Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
[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 PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Die über 350 besten Marketing-Praxis-Checklisten ...
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 zwei Tagen Vorschläge für ein erfolgreiches Internetmarketing vorlegen. Und dies natürlich neben dem üblichen Alltagsgeschäft! Kein Problem mit unseren Marketing-Praxis-Checklisten. Sie sorgen dafür, dass Sie bei Ihrer täglichen Arbeit entlastet werden und steigern den Erfolg Ihrer Marketingaktivitäten. Die Checklisten sind für Fr. 145.00/Stück erhältlich und damit bereits nach der ersten Anwendung amortisiert! Schauen Sie bei uns rein und überzeugen Sie sich von den Vorteilen des Marketing-Checklisten-Managers, als Handbuch oder CD-Rom erhältlich: http://www.stsmarketing.ch Wir freuen uns auf Ihren Besuch. Gruss Stefan Schmidlin Eid. dipl. Marketingleiter P.S.: Lassen Sie sich anhand von 5 kostenlosen Checklisten nach ihrer Wahl von der Qualität der Marketing-Checklisten-Sammlung überzeugen. This message was sent to you by Stefan Schmidlin, STS Marketing - Diese Nachricht wurde via MessageREACH versendet. Wenn Sie keine weiteren Emails von diesem Empfaenger wuenschen: 1. Klicken Sie auf Antworten. 2. Ersetzen Sie den Text in der Betreff-Zeile durch REMOVE. 3. Klicken Sie auf Senden. Sie werden ein letztes Mal eine Email mit einer Bestaetigung erhalten. - This message was sent using the MessageREACH Service. If you would prefer not to receive further messages from this sender: 1. Click on the Reply button. 2. Replace the Subject field with the word REMOVE. 3. Click the Send button. You will receive one additional e-mail message confirming your removal. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
[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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/proc /dev/std* [Was: Fdescfs updates--coming to a devfs near you!]
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" name is not very good idea. To say more, it breaks POSIX.
File names are a tratitional UNIX way to access character and block devices;
in System V you can access much more via file names, using streams.
Magic numbers are for MS DOS (remember COM1 and LPT1? :-)
I am not sure /proc/any number names are very useful, but
/dev/std{in|out|err} definitely are.
--
* *Konstantin Chuguev - Application Engineer
* * Francis House, 112 Hills Road
* Cambridge CB2 1PQ, United Kingdom
D A N T E WWW:http://www.dante.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 which has a legitimate need.
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).
Ugh. So what happens when you *really* want to read a filed called
"-"? Adding magic characters to low-level calls is a bad idea.
I believe /dev/fd originated in Unix v8 (or maybe plan 9) to provide a
uniform mechanism to get a class of process-internal objects where
they can be manipulated by shell scripts. If that's the case, it's
provenance is impeccable.
At the same time I would really love if we implemented "|.*" to mean
"do an popen(3)" instead.
Again, putting magic character recognition in a low-level call is a
bad idea. Worse yet, this kind of thing is really useful in shells
(which don't generally have the ability to manipulate fd's). Consider
trying to use that syntax in the shell?
Which is why modern shells that implement this kind of thing use a
different syntax. Of course, they depend on something like /dev/fd or
named pipes to provide this feature.
But of course, this is bikeshed material...
Most certainly. If you really want to make C programming look like
Perl programming, could you do it by adding new library calls, instead
of changing the semantics of existing ones?
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 the filename "-" unless it is special cased to mean stdin/stdout -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 requires
a filename as an argument. By handing it /dev/stdin, I can make it take
output as a part of a pipe. A _very_ useful little feature, IMNSHO.
As far as fdescfs, well, Unixware has something very like it, and I believe
that other commercial Unices do as well. I suspect that it's useful to
some, if not to all.
One thing about end users as opposed to engineers, they put this stuff to
uses that we can't even imagine. Never underestimate the sheer ingenuity
of a relatively naive user. :-)
--
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://store.exit.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Star Office and editor
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.bin: error in loading shared libraries: libvos1GCC.so: cannot open shared object file: No such file or directory I recall something about things running under the linux emulator *sometimes* treating references to / as references to /compat/linux. I'm thinking that this may be the problem, and it's not causing problems with -stable - yet. In particular, I'm wondering if the install file (an executable) is putting shared libraries in /tmp that executable it installs are then trying to find somewhere else - because of this path tweaking. I did try creating a /compat/linux/tmp that was a symlink to /tmp. I didn't fool with /compat/linux/usr/tmp, as it already existed. Anyone have any insight into this? Suggestions? Thanx, mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
On Thu, 14 Sep 2000 11:48:58 +0200, Poul-Henning Kamp [EMAIL PROTECTED] 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 this was the rationale for originally introducing
it.) It also helps when bogus programs refuse to read from the
standard input.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
cvsup3 now carries rsa_eay.c
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 freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 "-" instead of "/dev/stdin" but I
personally think it's the "-" hack to mean stdin/stdout which should be
abolished, not /dev/std{in,out,err}. No doubt others will disagree.
--
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
newbus docs
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 find it.
Was it my imagination?
(and if so, why isn't there one?)
--
__--_|\ 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 message
Re: Fdescfs updates--coming to a devfs near you!
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; imagine yourself trying to pipe something into it -
passing /dev/fd/0 as a filename to process would do the trick.
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.
How about the fact that the printing chapter in the Handbook uses /dev/fd/0
in its example of setting up a print filter using ghostscript since gs
doesn't read from stdin by default or use '-' for that purpose. Hmmm??
If anything I would propose we ditch it...
Tools, not policy, as you are so fond of saying.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 something which has a legitimate need.
How about the fact that the printing chapter in the Handbook uses /dev/fd/0
in its example of setting up a print filter using ghostscript since gs
doesn't read from stdin by default or use '-' for that purpose. Hmmm??
Actually, I think it should be the other way around: if anything should
go, it's the use of '-' in programs/scripts. The only advantage is that
it saves keystrokes.
I agree, /dev/std{in,out} is a very neat and elegant way of working with
stdin/out. If anything is the kludge, it's '-', and it's really vague as
to what it means. With /dev/std{in,out}, there's no doubt as to what's
going on with file ops. Plus, it's the unix way (tm) of doing
things. Almost all Unices have this, don't they? This means there's
likely to be some cross-platform shell scripts that use those things.
- Donn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
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 : :seems to suspend. : : Turns out this isn't the case. : : shutdown -p does not turn off the machine for me (Libretto 110ct). : : 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 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? Warner -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[CFR] KLDfy ip6_fw
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 PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
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 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? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
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, : : which changed in size just before the SMPng commit? : : 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. 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... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 think it is a reasonable feature to have. It probably won't
be useful all that often, but it could be very useful in some
situations. I know I've hit situations where I wished I could
do something like this, but I couldn't tell you an example
right this minute.
So, I wouldn't want to see fdesfs ditched, but on the other
hand I don't have any clue how to address the loose ends that
Chris mentioned in his initial message. :-)
---
Garance Alistair Drosehn = [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Institute
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
On Thu, 14 Sep 2000 13:46:44 -0600, Warner Losh [EMAIL PROTECTED] 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?=/etc/passwd
GROUP?= /etc/group
uidgid.h: ${PASSWD} ${GROUP}
perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \
$_[2], "\n");' ${PASSWD} ${.TARGET}
perl -ne 'split(/:/); print ("#define\tGID_", uc($_[0]), "\t", \
$_[2], "\n");' ${GROUP} ${.TARGET}
...add this to bsd.kmod.mk and include "uidgid.h" as necessary in
source files.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] Garrett Wollman writes:
: On Thu, 14 Sep 2000 13:46:44 -0600, Warner Losh [EMAIL PROTECTED] 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?= /etc/passwd
: GROUP?= /etc/group
:
: uidgid.h: ${PASSWD} ${GROUP}
: perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \
:$_[2], "\n");' ${PASSWD} ${.TARGET}
: perl -ne 'split(/:/); print ("#define\tGID_", uc($_[0]), "\t", \
:$_[2], "\n");' ${GROUP} ${.TARGET}
:
: ...add this to bsd.kmod.mk and include "uidgid.h" as necessary in
: source files.
Hmmm, I like it... But it does suffer from one problem that we
already have enough of in our tree. The build on one system, install
on another problem. It would be better than the current situtation.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
On Thu, 14 Sep 2000 16:42:00 -0400 (EDT), I wrote:
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 as well.
(Probably easier, actually, but I don't know AWK well enough to
actually implement it.)
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
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 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 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. 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... Yes, this is a bad thing, but it is the best compromise solution. You can either manually or with a future general devd(8) fix this. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
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 _/ _/_/_/"Modularity is not a hack."
_/ _/ _/-- D. J. Bernstein
_/ _/_/_/
_/ _/ _/_/
[EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: !.* [ was: Fdescfs updates--coming to a devfs near you! ]
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 I would really love if we implemented "|.*" to mean "do an popen(3)" instead. Isn't that potentially a huge security hole in every program that gets a filename from an external source? But of course, this is bikeshed material... If anything I would propose we ditch it... And break loads of scripts at the same time? I would argue that the programs and the scripts that call them are already broken, but hey... And I would argue that the fdescfs is cleaner than the '-' hack. (Which, by the way, should not be considered a filename hack so much as a command-line-parameter hack; since it was invented before there was a way to say 'use stdin/stdout' on the command-line... You could think of '/dev/stdin' as "'-' version 2") -Pat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
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 us enable that. It would remove the need to have setuid perl, for example. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newbus docs
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? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: page fault in sched_ithd
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
does anyone have any suggestions for a real fix?
The stray interrupt handler needs to have a thread, or stray interrupts
need to be handled as traps. Stray interrupts are more like NMIs than
normal interrupts, and NMIs are already (mis)handled as traps.
OK, but would you or anyone else object to the attached patch as a
temporary fix, at least? Page-faulting almost immediately is not
particularly good. The patch doesn't seem to have had any negative
effects so far.
Who are the main people responsible for the SMPng stuff anyway? jasone
and jhb seem to have been involved a bit, so I cc'd them as well.
--
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D
Index: ithread.c
===
RCS file: /usr/cvs/src/sys/i386/isa/ithread.c,v
retrieving revision 1.3
diff -u -r1.3 ithread.c
--- ithread.c 2000/09/13 18:33:23 1.3
+++ ithread.c 2000/09/14 22:06:44
@@ -95,6 +95,8 @@
SYSINIT(start_softintr, SI_SUB_SOFTINTR, SI_ORDER_FIRST, start_softintr, NULL)
+#defineMAX_STRAY_LOG 5
+
/*
* Schedule a heavyweight interrupt process. This function is called
* from the interrupt handlers Xintrnum.
@@ -103,6 +105,7 @@
sched_ithd(void *cookie)
{
int irq = (int) cookie; /* IRQ we're handling */
+ static int straycount[NHWI];/* count of stray IRQs */
struct ithd *ir = ithds[irq]; /* and the process that does it */
/* This used to be in icu_vector.s */
@@ -144,6 +147,21 @@
}
#endif
+ /* XXX: quick fix to avoid page fault until this is done properly. */
+ if (ir == NULL) {
+ if (irq NHWI) {
+ if (straycount[irq] MAX_STRAY_LOG) {
+ printf("stray irq %d\n", irq);
+ if (++straycount[irq] == MAX_STRAY_LOG)
+ printf("got %d stray irq %d's: "
+ "not logging anymore\n",
+ MAX_STRAY_LOG, irq);
+ }
+ return;
+ }
+ panic("sched_ithd: ithds[%d] == NULL", irq);
+ }
+
/*
* Set it_need so that if the thread is already running but close
* to done, it will do another go-round. Then get the sched lock
Re: newbus docs
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 actual documents. What kind of document do you want? I would imagine an overall architecture doc. Sort of like what Jordan just did for sysinst (e.g.). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: page fault in sched_ithd
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 "fixed" the problem for now, but does anyone have any suggestions for a real fix? The stray interrupt handler needs to have a thread, or stray interrupts need to be handled as traps. Stray interrupts are more like NMIs than normal interrupts, and NMIs are already (mis)handled as traps. OK, but would you or anyone else object to the attached patch as a temporary fix, at least? Page-faulting almost immediately is not particularly good. The patch doesn't seem to have had any negative effects so far. Who are the main people responsible for the SMPng stuff anyway? jasone and jhb seem to have been involved a bit, so I cc'd them as well. This looks good to me, let me through it my tree here and try it out. For SMPng stuff, probably just sending to the smp@ list should be sufficient. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newbus docs
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: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newbus docs
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 actual documents. What kind of document do you want? Probably something like this: http://people.freebsd.org/~asmodai/newbus-draft.txt or this: http://www.daemonnews.org/27/newbus-intro.html Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newbus docs
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 I totally sympathize with him. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mtree again
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_FOLLOW_LINKS = -L
to /etc/defaults/make.conf
--
Andrey A. Chernov
[EMAIL PROTECTED]
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: mtree again
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 ${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_FOLLOW_LINKS = -L
: to /etc/defaults/make.conf
This looks good to me.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Question
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?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Question
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
interfaces that aren't present yet decides that it needs to load the
relevant module, but it collides on loading. It's a bug, but basically
harmless.
Second, on both my sn card and my aue cards are installed I get:
WARNING: Driver mistake: repeat make_dev("bpf0")
You'll have to ask Poul about this; I think it has something to do with
moving devfs to /boot/devfs/devfs.ko.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: mtree again
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.orig Thu Jul 27 07:36:02 2000
+++ usr.sbin/mtree/mtree.c Fri Sep 15 04:00:46 2000
@@ -57,7 +57,7 @@
extern long int crc_total;
-int ftsoptions = FTS_LOGICAL;
+int ftsoptions = FTS_PHYSICAL;
int cflag, dflag, eflag, iflag, nflag, qflag, rflag, sflag, uflag, Uflag;
u_int keys;
char fullpath[MAXPATHLEN];
@@ -77,7 +77,7 @@
keys = KEYDEFAULT;
init_excludes();
- while ((ch = getopt(argc, argv, "cdef:iK:k:np:Prs:UuxX:")) != -1)
+ while ((ch = getopt(argc, argv, "cdef:iK:k:Lnp:qrs:UuxX:")) != -1)
switch((char)ch) {
case 'c':
cflag = 1;
@@ -106,6 +106,10 @@
if (*p != '\0')
keys |= parsekey(p, NULL);
break;
+ case 'L':
+ ftsoptions = ~FTS_PHYSICAL;
+ ftsoptions |= FTS_LOGICAL;
+ break;
case 'n':
nflag = 1;
break;
@@ -115,10 +119,6 @@
case 'q':
qflag = 1;
break;
- case 'P':
- ftsoptions ^= FTS_LOGICAL;
- ftsoptions |= FTS_PHYSICAL;
- break;
case 'r':
rflag = 1;
break;
@@ -170,7 +170,7 @@
usage()
{
(void)fprintf(stderr,
-"usage: mtree [-PUcdeinqrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]\n"
+"usage: mtree [-LUcdeinqrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]\n"
"\t[-X excludes]\n");
exit(1);
}
--- usr.sbin/mtree/mtree.8.orig Thu Jul 27 07:36:02 2000
+++ usr.sbin/mtree/mtree.8 Fri Sep 15 04:03:07 2000
@@ -40,7 +40,7 @@
.Nd map a directory hierarchy
.Sh SYNOPSIS
.Nm mtree
-.Op Fl PUcdeinqrux
+.Op Fl LUcdeinqrux
.Bk -words
.Op Fl f Ar spec
.Ek
@@ -70,9 +70,10 @@
.Pp
The options are as follows:
.Bl -tag -width flag
-.It Fl P
-Don't follow symbolic links in the file hierarchy, instead consider
-the symbolic link itself in any comparisons.
+.It Fl L
+Follow all symbolic links in the file hierarchy (by default
+.Nm
+considers the symbolic link itself).
.It Fl U
Modify the owner, group and permissions of existing files to match
the specification and create any missing directories or symbolic links.
--- etc/defaults/make.conf.orig Fri Sep 15 03:14:55 2000
+++ etc/defaults/make.conf Fri Sep 15 04:09:40 2000
@@ -43,6 +43,9 @@
# Compare before install
#INSTALL=install -C
#
+# Mtree will follow symlinks
+MTREE_FOLLOW_SYMLINKS= -L
+#
# To enable building enstalling suidperl with the setuid bit turned on
#ENABLE_SUIDPERL= true
#
--- etc/Makefile.orig Sat Sep 9 02:56:53 2000
+++ etc/MakefileFri Sep 15 04:06:36 2000
@@ -148,12 +148,12 @@
.endif
distrib-dirs:
- mtree -deU -f ${.CURDIR}/mtree/BSD.root.dist -p ${DESTDIR}/
- mtree -deU -f ${.CURDIR}/mtree/BSD.var.dist -p ${DESTDIR}/var
- mtree -deU -f ${.CURDIR}/mtree/BSD.usr.dist -p ${DESTDIR}/usr
- mtree -deU -f ${.CURDIR}/mtree/BSD.include.dist \
+ mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.root.dist -p
+${DESTDIR}/
+ mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.var.dist -p
+${DESTDIR}/var
+ mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.usr.dist -p
+${DESTDIR}/usr
+ mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.include.dist \
-p ${DESTDIR}/usr/include
- mtree -deU -f ${.CURDIR}/mtree/BSD.include.dist \
+ mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.include.dist \
-p ${DESTDIR}/usr/libdata/perl/5.6.0/mach
cd ${DESTDIR}/; rm -f ${DESTDIR}/sys; ln -s usr/src/sys sys
cd ${DESTDIR}/usr/share/locale; \
--- include/Makefile.orig Fri Sep 15 03:18:34 2000
+++ include/MakefileFri Sep 15 04:12:10 2000
@@ -103,7 +103,7 @@
rm -f ${DESTDIR}/usr/include/$i; \
fi
.endfor
- mtree -deU -f ${.CURDIR}/../etc/mtree/BSD.include.dist \
+ mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f
+${.CURDIR}/../etc/mtree/BSD.include.dist \
-p ${DESTDIR}/usr/include
.for i in ${LDIRS} ${LSUBDIRS}
cd ${.CURDIR}/../sys; \
--
Andrey A. Chernov
[EMAIL PROTECTED]
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
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 "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
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 the kernel core filename you want. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problems with aureal soundcard: kernel fault when playing mp3s
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. (http://www.cis.ohio-state.edu/~matey/au88x0/) so this might just be a problem with interactions between the linux .o files and kernel data structures. The soundcard worked fine using the linux drivers on a -current from August 14. I'm wondering if anything changed in the pcm code since then. That's what happened, as Peter noticed. The pcm interfaces did change. The following patch fixes the au88x0 driver for me. Thank you for the patch. I updated the stuff along with some documentation changes at http://www.cis.ohio-state.edu/~matey/au88x0/. Cheers, -Peter S. Housel- [EMAIL PROTECTED] http://members.home.com/housel/ -- lx To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No block devices (was: VMWare on -current, how fast should I expect it to be?)
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 is an example where they could presumably be useful. Doesn't Oracle run MUCH better when given raw block disk devices to store data on? Could this have lead to some of the poor performance Mike Smith was seeing when testing this summer? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No block devices (was: VMWare on -current, how fast should I expect it to be?)
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 decade. Could this have lead to some of the poor performance Mike Smith was seeing when testing this summer? No, we were layering over the filesystem, however filesystem load was insignificant. The Oracle performance issues are well known, and this isn't one of them. Thank you for clearing that up. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
: 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 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? Not a synchronization thing. I made sure of that. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
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 Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
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 the only place that you can get the error you reported. what does ls -l /dev/apm say? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
: 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. 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... Nope; no devfs, and the master.passwd is as close to standard as mergemaster can get. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
