Current as of yesterday afternoon hangs trying to boot on my box with an
OPTi931 soundcard installed. It prints the probe, and then hangs. With
boot -v, the messages are
pcm0: OPTi931 at port 0x5
34-0x537,0x380-0x38b,0x220-0x22f,0xe0c-0xe0f irq 5 drq 0,1 on isa0
mss_init: opti_offset=2
I'm using -current from 3.0 w/out big problems over last years.
But after last 3 make world man breaks: trying _ANY_ man give
me an empty page but under .../man/man*/*.gz sources are good.
Only formatted-compressed pages are wrong.
Even the command:
# gzip -cd /usr/share/man/man1/man.1.gz |
On Fri, Apr 20, 2001 at 03:14:10PM -0700, Mike Smith wrote:
#
# Folks,
#
# although there was much rejoicing, I think there's no need for a
# new option to cp. Just use the toolbox, it's not too hard:
#
# (cat bigfilelist; echo destdir) | xargs cp
#
# Or even
#
# echo destdir
Date: Sat, 21 Apr 2001 14:12:59 +0200 (CEST)
From: Riccardo Torrini [EMAIL PROTECTED]
I'm using -current from 3.0 w/out big problems over last years.
But after last 3 make world man breaks: trying _ANY_ man give
me an empty page but under .../man/man*/*.gz sources are good.
Only
On Fri, Apr 20, 2001 at 07:26:18PM -0700, Rodney W. Grimes wrote:
(cat bigfilelist; echo destdir) | xargs cp
I like this version of the patch!! It's much much cleaner than
hacking up cp or xargs, it even follows the unix principle of
using simple tools and glueing them
As you requested, you have been unsubscribed from 'fwd-newswire'.
---
Return-Path: [EMAIL PROTECTED] ()
Received: from nova.sparklist.com ([207.250.144.28]) by nova.sparklist.com with SMTP
(SparkLIST.com WIN32 version 4.1); Sat, 21 Apr 2001 08:37:20 -0500
From: [EMAIL PROTECTED] ()
To:
On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote:
How do you do this in a script:
cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/.
for i in `find /path/to/source -type f`; do
cp $i /path/to/dest/
done
What's all the fuss about?
Ciao,
Sheldon.
To Unsubscribe:
Jens Schweikhardt [EMAIL PROTECTED] wrote:
You mean if bigfilelist list exceeds the -n limit of xargs (default 5000)?
Yes, you'll be surprised then. It was a bit of POLA violation for me when I
found xargs would by default use 5000 arg chunks and not all in one go.
I'd rather get rid of
Hi folks,
After downgrading to RELENG_4 for a while to prove to my team mates
that 3 months of pain were the result of hardware instability and not
features of HEAD, I'm ready to get back on the wagon.
I didn't follow the FILE size change debarcle, because I assumed that
the problem would be
Sheldon Hearn [EMAIL PROTECTED] wrote:
On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote:
How do you do this in a script:
cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/.
for i in `find /path/to/source -type f`; do
cp $i /path/to/dest/
done
That can
On 21-Apr-2001 Sheldon Hearn wrote:
On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote:
How do you do this in a script:
cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/.
for i in `find /path/to/source -type f`; do
cp $i /path/to/dest/
done
What's all the
Date: Sat, 21 Apr 2001 16:49:24 +0200
From: Sheldon Hearn [EMAIL PROTECTED]
After downgrading to RELENG_4 for a while to prove to my team mates
that 3 months of pain were the result of hardware instability and not
features of HEAD, I'm ready to get back on the wagon.
I didn't follow the FILE
Your comments have nothing to do with the issue at hand. Just wrap the
first argument to cp in double-quotes, i.e.
cp "$i"
The point is, why bastardize tools to cope with areas beyond their
focus and well within the focus of other tools?
Ciao,
Sheldon.
Sorry for butting in.
Sheldon Hearn [EMAIL PROTECTED] wrote:
On Sat, 21 Apr 2001 16:51:24 +0200, Oliver Fromme wrote:
That can overflow your shell's command line limit (at the
"for" command). True, our /bin/sh doesn't has such a
limit, AFAIK, but there _are_ shells that do).
That's actually my point.
On Sat, 21 Apr 2001 17:27:04 +0200, Oliver Fromme wrote:
Not all users use /bin/sh. Scripts needn't be written
in /bin/sh, and xargs can be used interactively, too (I
use it a lot). Just because _our_ xargs works fine with
_our_ /bin/sh doesn't mean there is no problem.
So we have two
As you requested, you have been unsubscribed from 'fwd-newswire'.
---
Return-Path: [EMAIL PROTECTED]
Received: from mailhost.sparknet.net ([207.67.22.123]) by nova.sparklist.com with SMTP
(SparkLIST.com WIN32 version 4.1); Sat, 21 Apr 2001 11:01:40 -0500
Received: from don-oakes.sparklist.com
Hi,
This is probably the wrong list, but I have no idea where
else to ask, and -current is also affected, so ...
I'm wondering why /bin/df is set-gid to the operator group
by default. I have tried to remove the s bit, and it is
still working fine. Looking at the source code didn't give
me a
On 21-Apr-01 David W. Chapman Jr. wrote:
I just tried to do an installkernel on a new kernel I built and I got the
same error except the last line changed to
stopped atffs_dirpref+0x210movzbl0(%ECX,%EAX,1),%EAX
Do I have any hope at recovering from this or should I start
On Sat, 21 Apr 2001, Oliver Fromme wrote:
I'm wondering why /bin/df is set-gid to the operator group
by default.
It's to df filesystems that aren't mounted. Try "df /dev/ad0s1a" (or
whatever) as user nobody with chmod 555 /bin/df.
-Paul.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Paul Herman [EMAIL PROTECTED] wrote:
On Sat, 21 Apr 2001, Oliver Fromme wrote:
I'm wondering why /bin/df is set-gid to the operator group
by default.
It's to df filesystems that aren't mounted. Try "df /dev/ad0s1a" (or
whatever) as user nobody with chmod 555 /bin/df.
Ah, thanks
On Sat, 21 Apr 2001, Oliver Fromme wrote:
Paul Herman [EMAIL PROTECTED] wrote:
On Sat, 21 Apr 2001, Oliver Fromme wrote:
I'm wondering why /bin/df is set-gid to the operator group
by default.
It's to df filesystems that aren't mounted. Try "df /dev/ad0s1a" (or
whatever) as
From: Oliver Fromme [EMAIL PROTECTED]
Subject: Re: cp -d dir patch for review (or 'xargs'?)
Date: Sat, 21 Apr 2001 17:27:04 +0200 (CEST)
Not all users use /bin/sh. Scripts needn't be written
in /bin/sh ...
Actually, just to jump in and correct this, scripts *should* be
written in /bin/sh.
Sorry to follow up on my own mail...
On Sat, 21 Apr 2001, Paul Herman wrote:
This brings up a slightly related question: Now that block
devices have been abolished, wouldn't it be a good idea to get rid
of the quick mount(2)/umount(2) of /tmp/df.XX to stat the file
system?
I see now
You need to rebuild fsck and install it and fsck your filesystems. This is the
dirpref changes biting you. Warner, we probably need an entry in UPDATING for
the dirpref changes that warn people to build and install a new fsck before
booting a dirpref kernel.
Er. This really isn't very
On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote:
How do you do this in a script:
cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/.
for i in `find /path/to/source -type f`; do
cp $i /path/to/dest/
done
What's all the fuss about?
Have you tried that for
On Sat, 21 Apr 2001, Paul Herman wrote:
This brings up a slightly related question: Now that "cooked" block
devices have been abolished, wouldn't it be a good idea to get rid of
the quick mount(2)/umount(2) of /tmp/df.XX to stat the file
system? Something like the following patch.
No.
Jordan Hubbard [EMAIL PROTECTED] wrote:
From: Oliver Fromme [EMAIL PROTECTED]
Not all users use /bin/sh. Scripts needn't be written
in /bin/sh ...
Actually, just to jump in and correct this, scripts *should* be
written in /bin/sh.
It depends.
I often happen to write zsh scripts,
And to come back on topic: Portable scripts also should
_not_ assume that there are no limits on the length of
shell commands. On the other hand, portable scripts can
legitimately assume that xargs supports -i and -I, which
ours doesn't.
Agreed on both counts. I guess we should fix that.
On Sat, 21 Apr 2001, Brian Somers wrote:
On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote:
How do you do this in a script:
cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/.
for i in `find /path/to/source -type f`; do
cp $i /path/to/dest/
done
Jordan Hubbard [EMAIL PROTECTED] writes:
And to come back on topic: Portable scripts also should
_not_ assume that there are no limits on the length of
shell commands. On the other hand, portable scripts can
legitimately assume that xargs supports -i and -I, which
ours doesn't.
On Sat, Apr 21, 2001 at 05:34:31PM +0200, Sheldon Hearn wrote:
So we have two problems:
1) Calling cp(1) repetitively is inefficient.
2) The argument list is too big for cp(1).
Extending cp(1) will not solve (2). Extending xargs(1) will solve both.
So why is an extension to cp(1)
Brian Dean [EMAIL PROTECTED] wrote:
But extending cp does solve the problem.
Only for cp. It wouldn't solve the problem for mv, ln and
a bunch of other tools. Fixing it at _one_ place in xargs
would solve all of that without touching a dozen tools.
[...]
This makes cp work with xargs;
So we have two problems:
1) Calling cp(1) repetitively is inefficient.
2) The argument list is too big for cp(1).
Extending cp(1) will not solve (2). Extending xargs(1) will solve both.
So why is an extension to cp(1) being proposed?
I wasn't proposing that cp should be changed - I
Dima Dorfman [EMAIL PROTECTED] wrote:
I don't have a copy of SuSv2 or anything else that defines -I and -i,
http://www.secnetix.de/~olli/susv2/xcu/xargs.html
but from what I can gather, -i is the same as "-I {}" and -I allows
things like this:
Not exactly. The difference is that the
I looked at your patches and immediately thought ``these patches
can't be right'' as I was expecting it to deal with things such as
xargs -I [] echo args are [], duplicated are []
I'm also dubious about the patches working for large volumes on
standard input. At this point I scrapped the
Putting that option into cp seems rather GNUish to me, but
not very UNIXish. :-)
Yes. I think most people agree that changing cp is not good.
Just my 2 Euro cents.
Regards
Oliver
--
Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 Mnchen
Any opinions expressed in
Dima Dorfman [EMAIL PROTECTED] wrote:
I don't have a copy of SuSv2 or anything else that defines -I and -i,
http://www.secnetix.de/~olli/susv2/xcu/xargs.html
but from what I can gather, -i is the same as "-I {}" and -I allows
things like this:
Not exactly. The difference is
On 21-Apr-01 Mike Smith wrote:
You need to rebuild fsck and install it and fsck your filesystems. This is
the
dirpref changes biting you. Warner, we probably need an entry in UPDATING
for
the dirpref changes that warn people to build and install a new fsck before
booting a dirpref
Brian Somers [EMAIL PROTECTED] writes:
I looked at your patches and immediately thought ``these patches
can't be right'' as I was expecting it to deal with things such as
xargs -I [] echo args are [], duplicated are []
It deals with it. It conveniently ignores the second '[]' :-).
On Sat, Apr 21, 2001 at 04:49:24PM +0200, Sheldon Hearn wrote:
Is this still true?
I don't believe so; I updated from 4.3-RC to 5.0-CURRENT on this
machine and didn't have to do anything special (except set NOMAN,
because I was being studly and updating using 'make all' instead of
'make
On Sun, 22 Apr 2001, Bruce Evans wrote:
In FreeBSD, mount privilege is controlled by the vfs.usermount
sysctl (default: off), so df must still be setgid operator to work
on devices.
The mount() method is better because can work on work on all types
of filesystems that the kernel
41 matches
Mail list logo
