On Thu Apr 9 05:18:31 EDT 2009, bdhee...@gmail.com wrote:
Extraction of only a 180M archive knelled down a 1.8Ghz/P-M4/i686/1Gb
RAM/40GiB IDE HDD machine running vanilla Plan9 installed natively:
term% cat /dev/sdC0/ctl |grep dma
config 0040 capabilities 2F00 dma 00550020 dmactl 00550020
Extraction of only a 180M archive knelled down a 1.8Ghz/P-M4/i686/1Gb
RAM/40GiB IDE HDD machine running vanilla Plan9 installed natively:
term% cat /dev/sdC0/ctl |grep dma
config 0040 capabilities 2F00 dma 00550020 dmactl 00550020 rwm 8 rwmctl 0
term% time
Try env | wc -l in bash. Now tell me why that value is so big.
[r...@host ~]# env | wc -l
37
[r...@host ~]#
Is that very high? I don't even know if it is or how it would mean anything
bad (or good for that matter) assuming it were high. Not to mention, it's a
very bad metric.
On Thu Apr 9 10:48:08 EDT 2009, eris.discor...@gmail.com wrote:
Most of it in the 19 lines for one TERMCAP variable. Strictly a relic of
the past kept with all good intentions: backward compatibility, and heeding
[...]
Quite a considerable portion of UNIX-like systems, FreeBSD in this
On Thu Apr 9 13:19:11 EDT 2009, rminn...@gmail.com wrote:
www.pdl.cmu.edu/posix
statlite()
the statlite man page is itself lightweight, being available
on the web in pdf form.
- erik
On Thu, Apr 9, 2009 at 9:44 AM, Eris Discordia eris.discor...@gmail.com wrote:
Try env | wc -l in bash. Now tell me why that value is so big.
[r...@host ~]# env | wc -l
37
[r...@host ~]#
Is that very high? I don't even know if it is or how it would mean anything
bad (or good for
On Thu, Apr 9, 2009 at 1:25 PM, erik quanstrom quans...@quanstro.net wrote:
On Thu Apr 9 13:19:11 EDT 2009, rminn...@gmail.com wrote:
www.pdl.cmu.edu/posix
statlite()
the statlite man page is itself lightweight, being available
on the web in pdf form.
And MS doc! There's a common Unix-y
i propose an extension to HTTP (call it HTTPeeLite) which allows me to
specify in my request to that webpage the format in which i prefer to
receive the man page. a 'setup' exchange can be sent beforehand to
establish the available types of documentation (.doc, .pdf, .tex,
.rtf, etc).
On Thu Apr 9 13:44:50 EDT 2009, mirtchov...@gmail.com wrote:
i propose an extension to HTTP (call it HTTPeeLite) which allows me to
specify in my request to that webpage the format in which i prefer to
receive the man page. a 'setup' exchange can be sent beforehand to
establish the available
On Thu, Apr 9, 2009 at 1:25 PM, erik quanstrom quans...@quanstro.net wrote:
On Thu Apr 9 13:19:11 EDT 2009, rminn...@gmail.com wrote:
www.pdl.cmu.edu/posix
statlite()
the statlite man page is itself lightweight, being available
on the web in pdf form.
And MS doc! There's a
set | wc -l
8047
well.
certainly if you leave bash or even dash set as the shell,
a terminal or 9term window takes ages on ubuntu. set the shell to p9p rc,
9term starts straight away and you're a better person for it.
or you could refrain from making the web any worse by just
providing the document in ... oh, what's that archane format ...
right, html. if i recall correctly, it's the standard for web content.
in the immortal words of Colin Chapman: Complicate, then add weight.
On Thu, Apr 9, 2009 at 1:48 PM, erik quanstrom quans...@quanstro.net wrote:
On Thu Apr 9 13:44:50 EDT 2009, mirtchov...@gmail.com wrote:
i propose an extension to HTTP (call it HTTPeeLite) which allows me to
specify in my request to that webpage the format in which i prefer to
receive the man
from the man pages^W^Wpdf:
// FUTURE DIRECTIONS
//
// None.
we should be so lucky.
I'm messing around with /sys/src/9/port/sysproc.c and I may have
distorted it beyond recovery, but I have a feeling this problem isn't
of my own making.
I have:
; cat /bin/ll
#!/bin/ls -l
;
If I invoke ll
; ll
--rwxrwxr-x M 9 lucio lucio 13 Jan 31 09:30
See exec(2):
For a file beginning #!, the arguments passed to the program
(/bin/rc in the example above) will be the name of the file
being executed, any arguments on the #! line, the name of
the file again, and finally the second and subsequent argu-
See exec(2):
For a file beginning #!, the arguments passed to the program
(/bin/rc in the example above) will be the name of the file
being executed, any arguments on the #! line, the name of
the file again, and finally the second and subsequent argu-
andrey mirtchovski wrote:
i propose an extension to HTTP (call it HTTPeeLite) which allows me to
specify in my request to that webpage the format in which i prefer to
receive the man page. a 'setup' exchange can be sent beforehand to
establish the available types of documentation (.doc, .pdf,
On Thu, Apr 9, 2009 at 3:05 PM, maht mattmob...@proweb.co.uk wrote:
andrey mirtchovski wrote:
i propose an extension to HTTP (call it HTTPeeLite) which allows me to
specify in my request to that webpage the format in which i prefer to
receive the man page. a 'setup' exchange can be sent
2009/4/9 Richard Miller 9f...@hamnavoe.com:
set | wc -l
8047
well.
This is nearly as big as the shell itself in the (ahem) good old days.
term% tar tzvf interdata_v6.tar.gz bin/sh
--rwxr-xr-x 8316 Nov 13 15:48 1978 bin/sh
No, it's very likely bigger. wc -l is lines of course, and
Already part of HTTP
Accept: application/msword; q=1, application/pdf;
q=0.5,application/x-troff-ms; q=0.3
q is the level of preference, you'll get word docs first
Wow. Could it get any worse?
yes. just read a few lines further in the rfc and note that
there's also a level
No, it's very likely bigger. wc -l is lines of course, and I'm
guessing each line is more than 1 character. However,
$ set | wc -l
64
I don't quite get that locally.
It only starts to balloon once you begin customizing bash. I'm not
sure how rc handles functions, but the nice thing about
On Thu, Apr 9, 2009 at 3:22 PM, erik quanstrom quans...@quanstro.net wrote:
Already part of HTTP
Accept: application/msword; q=1, application/pdf;
q=0.5,application/x-troff-ms; q=0.3
q is the level of preference, you'll get word docs first
Wow. Could it get any worse?
yes.
No, it's very likely bigger. wc -l is lines of course
Silly me, I was (optimistically) confusing it with wc -c.
in the immortal words of Colin Chapman: Complicate, then add weight.
Is this sarcasm?
I remember the quote as: To add speed, add lightness
-Steve
I prefer the cadillac of shells (zsh) the vw bug (rc).
I like this.
$ echo $BASH_VERSION
4.0.10(2)-release
$ set|wc
72 1062107
if this is the criteria, plan 9 loses:
; printenv|wc
73 2102417
- erik
p.s.
; cat /bin/printenv
#!/bin/rc
rfork en
cd /env
for(i in *){
if(! test -s $i)
echo $i ^ '=()'
if
ps, the quote is Simplify, then add lightness
On Thu, Apr 9, 2009 at 3:30 PM, andrey mirtchovski
mirtchov...@gmail.com wrote:
Is this sarcasm?
yes, but not addressed towards Mr. Chapman, bless his cars. glad at
least one person caught that.
internet is bizarro world.
according to
according to wikiquote.org it is Simplicate, then add lightness.
yes, it's even better than how i remember it!
On Thu, 09 Apr 2009 15:31:35 MDT andrey mirtchovski mirtchov...@gmail.com
wrote:
ps, the quote is Simplify, then add lightness
Makes perfect sense for Chapman's purposes. Replace steel
with aluminium. Fiberglass instead of sheet metal and so on.
Unfortunately we don't have exact analogs in
Unfortunately we don't have exact analogs in s/w. We can
only simplicate; we can't add lightness!
but somehow we can add weight. can't we? bash is perceivably
heavier than rc, xml perceivably heavier than 9p... statlite()
perceivably heavier than stat() :)
we just don't quantify weight in
It only starts to balloon once you begin customizing bash.
Have you customized your bash by aliases as long as tens or hundreds of
lines? Now is it bash's fault you have defined an alias for something that
ought to be a script/program in its own right?
--On Thursday, April 09, 2009 3:34 PM
Makes perfect sense for Chapman's purposes. Replace steel
with aluminium. Fiberglass instead of sheet metal and so on.
Unfortunately we don't have exact analogs in s/w. We can
only simplicate; we can't add lightness!
read ken's code!
- erik
On Fri, Apr 10, 2009 at 12:06 AM, Bakul Shah bakul+pl...@bitblocks.com wrote:
Unfortunately we don't have exact analogs in s/w. We can
only simplicate; we can't add lightness!
In manufacturing, I'd suppose lighter materials are harder to make and
use, kind of like using low level languages for
this is the space-shuttle dichotomy. it's a false one. it's a
continuum. its ends are dangerous.
So somewhere in the middle is the golden mean? I have no objections to
that. *BSD systems very well represent a silver, if not a golden,
mean--just my idea, of course.
it is interesting to me
35 matches
Mail list logo
