On Thu Apr 17 08:54:02 EDT 2014, aris...@ar.aichi-u.ac.jp wrote:
> Hello,
>
> I found this mail today. sorry.
>
> > Just not to overwrite newer files
>
> cpdir does behave this way.
mkfs already does this. :-)
- erik
Hello,
I found this mail today. sorry.
> Just not to overwrite newer files
cpdir does behave this way.
2009/07/20 18:32、c...@gli.cas.cz のメール：
> hi,
>
> i'm quite happy with the 'cpdir' by Kenji Arisawa (thanks, Kenji!) on
> sources/contrib/arisawa.
> However, your scripty seems fine, too.
btw, shouldn't mkfs use allproto by default like mk9660 does
or am I just missing something?
On Mon, Jul 20, 2009 at 6:55 AM, Charles Forsyth wrote:
>>Before I say anythign daft, what's '+'? It does not appear to be special on
>>my system.
>
> it's interpreted by mkfs in its proto file to mean al
On Mon, Jul 20, 2009 at 6:56 PM, erik quanstrom wrote:
> i know you can do it with du, but it seems a bit "cat -n"ish to me.
> for comparison:
This was why I wrote 'walk' a few years ago; du is the disk usage
tool, not a general file walker.
- Dan C.
minooka; time rc -c 'du -a . | wc'
> On Mon, Jul 20, 2009 at 2:41 PM, erik quanstrom wrote:
> > on coraid's worm, a find on main takes not too long:
> >
> > minooka; cd /n/ila
> > minooka; time rc -c 'find . | wc'
> > 356164 356164 13987863
> > 1.24u 1.38s 6.65r rc -c find . | wc
>
> The
On Mon, Jul 20, 2009 at 2:41 PM, erik quanstrom wrote:
> on coraid's worm, a find on main takes not too long:
>
> minooka; cd /n/ila
> minooka; time rc -c 'find . | wc'
> 356164 356164 13987863
> 1.24u 1.38s 6.65r rc -c find . | wc
The FAQ also mentions:
du -a . | grep foo
Just out of c
>
> I think the latter approach would produce a more usable, less frustrating
> filesystem than the former.
>
plan 9 seems to me to be firmly in the fs rather than
the database camp.
before i moved to plan 9, i thought that locate was a
very cool tool. things had gotten mighty hard to find
in
I've been thinking for a while that I don't quite like directories, as
organizing metadata. Too restrictive: you can only really choose one place,
to find something you already have to know where to look (or search through
everything), and if you choose long, comprehensible names, your unique set
On Mon, 20 Jul 2009 11:19:16 -0400
Dan Cross wrote:
> On Mon, Jul 20, 2009 at 11:02 AM, Ethan
> Grammatikidis wrote:
> > Sorry if that was a bit harsh, but I've had far too much 'advice' to 'just
> > do this easy little thing'... Computers are supposed to supplement the
> > brain, to help, not
On Mon, Jul 20, 2009 at 11:02 AM, Ethan
Grammatikidis wrote:
> Sorry if that was a bit harsh, but I've had far too much 'advice' to 'just do
> this easy little thing'... Computers are supposed to supplement the brain, to
> help, not require more (and in some cases quite impossible) work. To file
> Sure. Let me get a modest little cybernetic interface to one of those
> temporal vision thingummabobs they have these days and I'll call you right
> back.
>
> Sorry if that was a bit harsh, but I've had far too much 'advice' to 'just do
> this easy little thing'... Computers are supposed to s
On Mon, 20 Jul 2009 15:00:43 +0100
"Steve Simon" wrote:
> > ...c-stoff/t-stoff powered rocket...
>
>
> I watched OU programs as a child too :-)
>
I didn't, my parents would never have a TV. ::) I got that from a book, The
World's Worst Aircraft.
> I suggest you consider why you are moving d
> ...c-stoff/t-stoff powered rocket...
I watched OU programs as a child too :-)
I suggest you consider why you are moving directories about, I have just got
out of the habit.
If I get a tar or a zip which contains dome data I need I just mount it with
fs/tarfs or fs/zipfs and look inside. If I
On Mon, 20 Jul 2009 07:50:08 -0400
erik quanstrom wrote:
> > & [what] does mkext stand for), and
>
> make extract, i assume.
>
> >
> > file /bin/mkfs
> > /bin/mkfs: cannot open: '/bin/mkfs' file does not exist
> >
> > Dude, like, huh?
>
> you must have missed the first few lines of
> & [what] does mkext stand for), and
make extract, i assume.
>
> file /bin/mkfs
> /bin/mkfs: cannot open: '/bin/mkfs' file does not exist
>
> Dude, like, huh?
you must have missed the first few lines of the man page
disk/mkfs [-aprvxU] [-d root] [-n name] [-s source] [
On Mon, 20 Jul 2009 10:55:21 +0100
Charles Forsyth wrote:
> >Before I say anythign daft, what's '+'? It does not appear to be special on
> >my system.
>
> it's interpreted by mkfs in its proto file to mean all the substructure of a
> directory.
> see mkfs(8).
>
Thanks. I looked over the man
On Mon, 20 Jul 2009 11:32:11 +0200
wrote:
> hi,
>
> i'm quite happy with the 'cpdir' by Kenji Arisawa (thanks, Kenji!) on
> sources/contrib/arisawa.
> However, your scripty seems fine, too. Could we add a switch to conform with
> gnu's cp -au? Just not to overwrite newer files. I don't know th
hi,
i'm quite happy with the 'cpdir' by Kenji Arisawa (thanks, Kenji!) on
sources/contrib/arisawa.
However, your scripty seems fine, too. Could we add a switch to conform with
gnu's cp -au? Just not to overwrite newer files. I don't know there is an
option there in 'tar' (I can't see in in tar
>Before I say anythign daft, what's '+'? It does not appear to be special on my
>system.
it's interpreted by mkfs in its proto file to mean all the substructure of a
directory.
see mkfs(8).
On Sun, 19 Jul 2009 14:05:04 -0400
erik quanstrom wrote:
> On Sun Jul 19 12:26:24 EDT 2009, eeke...@fastmail.fm wrote:
> > I was never satisfied with dircp. It's practice of copying the contents
> > of one directory into another seemed limiting at best, obstructive at
> > worst. The recursive cop
<{echo +}
works just fine.
On Sun, Jul 19, 2009 at 8:16 PM, Richard Miller<9f...@hamnavoe.com> wrote:
>> i keep /tmp/allproto around with the contents of '+'.
>
> There's also one in /sys/lib/sysconfig/proto/allproto,
> but that takes longer to type.
>
>
>
> i keep /tmp/allproto around with the contents of '+'.
There's also one in /sys/lib/sysconfig/proto/allproto,
but that takes longer to type.
On Sun Jul 19 12:26:24 EDT 2009, eeke...@fastmail.fm wrote:
> I was never satisfied with dircp. It's practice of copying the contents
> of one directory into another seemed limiting at best, obstructive at
> worst. The recursive copy options of Gnu cp seemed much more elegant(!),
> preserving the u
I was never satisfied with dircp. It's practice of copying the contents
of one directory into another seemed limiting at best, obstructive at
worst. The recursive copy options of Gnu cp seemed much more elegant(!),
preserving the usual option syntax of cp and merely extending it slightly
to include
24 matches
Mail list logo
