[24801] in Perl-Users-Digest
Perl-Users Digest, Issue: 6954 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Sep 3 09:11:18 2004
Date: Fri, 3 Sep 2004 06:10:13 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 3 Sep 2004 Volume: 10 Number: 6954
Today's topics:
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Scan Microsoft Office files <wfsp@removeyahoo.com>
Re: Simple question <tadmc@augustmail.com>
Re: Split by length <not_four@hotmail.com>
Re: Split by length (Anno Siegel)
Re: Split by length <tadmc@augustmail.com>
Re: Xah Lee's Unixism <roo@try-removing-this.darkboong.demon.co.uk>
Re: Xah Lee's Unixism jmfbahciv@aol.com
Re: Xah Lee's Unixism jmfbahciv@aol.com
Re: Xah Lee's Unixism jmfbahciv@aol.com
Re: Xah Lee's Unixism jmfbahciv@aol.com
Re: Xah Lee's Unixism jmfbahciv@aol.com
Re: Xah Lee's Unixism <espen@*do-not-spam-me*.vestre.net>
Re: Xah Lee's Unixism jmfbahciv@aol.com
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 03 Sep 2004 02:22:08 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <woOdnWbFs_Y9hqXcRVn-rg@august.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Fri, 3 Sep 2004 11:22:14 +0000 (UTC)
From: "wfsp" <wfsp@removeyahoo.com>
Subject: Re: Scan Microsoft Office files
Message-Id: <ch9k56$3am$1@titan.btinternet.com>
"Will Fawcett" <wfawcett@gmail.com> wrote in message
news:e08f2c58.0409022241.64e7898@posting.google.com...
>I am trying to put together a script that will allow me to scan
> Microsoft Office files and store "keywords" for those files so they
> are searchable by content not just title.
>
> If you open a word file with Perl and look at the actual source it is
> basically a text file with a bunch of bogus code. I was hoping someone
> here might have heard of a module out there that can step out the
> ambiguous code out and just store plain text words. Or is RegEx my
> only option?
>
> -Will
An example:
#!/bin/perl5
use strict;
use warnings;
use Win32::OLE;
my $w = Win32::OLE->GetActiveObject('Word.Application');
my $d = $w->ActiveDocument;
my $paras = $d->Paragraphs;
foreach my $para ( in $paras ) {
my $style = $para->Style->{ NameLocal };
my $text = $para->Range->{ text };
print "$style\t$text\n"
}
Assumes Word is open and a document is open. The vba help files have all the
methods/properties. A search on Win32::OLE will bring up many
tutorials/references.
------------------------------
Date: Fri, 3 Sep 2004 07:06:12 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Simple question
Message-Id: <slrncjgnhk.f1i.tadmc@magna.augustmail.com>
Zebee Johnstone <zebee@zip.com.au> wrote:
> and so when doing a pipe, the return value of open is perhaps not going
> to do what you expect.
This is a Frequently Asked Question.
perldoc -q pipe
Why doesn't open() return an error when a pipe open fails?
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 3 Sep 2004 15:48:27 +0800
From: "Fayland" <not_four@hotmail.com>
Subject: Re: Split by length
Message-Id: <ch97kc$r3c$1@news.yaako.com>
I read the perlfunc "split" again,and understand why the empty fields
produced.
Thanks.And I want to ask weather there is a way to skip the empty
fields(undef),how to write the regexp?
not /(.{1,2})/ but what?
"Tad McClellan" <tadmc@augustmail.com> дÈëÓʼþ
news:slrncjfutd.e25.tadmc@magna.augustmail.com...
> Fayland <not_four@hotmail.com> wrote:
>
>
> > $a = "avcdfadad";
>
>
> > It's weird
>
>
> No it isn't.
>
> If you had told us what you thought was weird, we could have perhaps
> explained it.
>
> At it is, it is doing exactly what is expected, so we cannot help
> repair whatever misunderstanding you have...
>
>
> > that I use "@a = split(/(.{1,2})/,$a);", it give me 10 elements
> > of array.
>
>
> You get 5 (empty) fields, and 5 separators, just what the function's
> docs say you should.
>
> That adds up to 10 (and I didn't even have to take off my shoes
> to calculate that :-)
>
>
> --
> Tad McClellan SGML consulting
> tadmc@augustmail.com Perl programming
> Fort Worth, Texas
------------------------------
Date: 3 Sep 2004 10:27:15 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Split by length
Message-Id: <ch9gu3$k73$1@mamenchi.zrz.TU-Berlin.DE>
Papago <me@myplace.com> wrote in comp.lang.perl.misc:
> Is there a single Perl command that will split a string into an array by
> number of characters? For example, if I had the string:
>
> $string = "monkey";
>
> I could specify a lenght, such as 2, and it would put every pair of 2
> characters into an array that looks something like this:
>
> $array[0] = "mo";
> $array[1] = "nk";
> $array[3] = "ey";
my @l = unpack '(a2)*', $string;
Anno
------------------------------
Date: Fri, 3 Sep 2004 07:10:38 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Split by length
Message-Id: <slrncjgnpu.f1i.tadmc@magna.augustmail.com>
Fayland <not_four@hotmail.com> wrote:
> "Tad McClellan" <tadmc@augustmail.com> дÈëÓʼþ
> news:slrncjfutd.e25.tadmc@magna.augustmail.com...
>> Fayland <not_four@hotmail.com> wrote:
>>
>>
>> > $a = "avcdfadad";
>> > that I use "@a = split(/(.{1,2})/,$a);", it give me 10 elements
>> > of array.
>>
>>
>> You get 5 (empty) fields, and 5 separators, just what the function's
>> docs say you should.
> I read the perlfunc "split" again,and understand why the empty fields
> produced.
> Thanks.And I want to ask weather there is a way to skip the empty
> fields(undef),
@a = grep length, split(/(.{1,2})/,$a);
but a m// in list context is Much Better for this task.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 03 Sep 2004 09:19:02 +0100
From: Rupert Pigott <roo@try-removing-this.darkboong.demon.co.uk>
Subject: Re: Xah Lee's Unixism
Message-Id: <1094199540.968446@teapot.planet.gong>
Patrick Scheible wrote:
[SNIP]
> Yes. NeXTStep didn't have a microkernel. The Mach kernel didn't get
> changed to a microkernel design until after NeXTStep split off from
> it.
Hmmm, you had better tell these folks they are wrong for starters :
http://www.macos.utah.edu/Documentation/MacOSXClasses/macosxone/unix.html
Do a google for NextStep and Microkernel, it appears to be a very
common understanding/myth...
Cheers,
Rupert
------------------------------
Date: Fri, 03 Sep 04 10:27:38 GMT
From: jmfbahciv@aol.com
Subject: Re: Xah Lee's Unixism
Message-Id: <413859f1$0$19713$61fed72c@news.rcn.com>
In article <10jepndi1en2id8@corp.supernews.com>,
SM Ryan <wyrmwif@tango-sierra-oscar-foxtrot-tango.fake.org> wrote:
># > Not exactly a typical editor function, agreed. I was feeling a little
># > whimsical at the time.
>#
># i once did a random email/usenet signature with zippy/yow ... but i
># added two other files to it ... and then i had to fix a feature in
># yow. yow uses a 16bit random number to index a yow file ... it was ok
># as long as your sayings file was less than 64kbytes. i had to modify
># yow to handle files larger than 64kbytes ... the "sayings" file used
># for 6670 separater pages was 167k bytes and the jargon file was 413k
># bytes ... while a current zippy yow file is 52,800 bytes.
>
>It's nice to know people still have time to work on
>really important things.
Before you choke on your stuffiness, you should know that
playing uncovered an ungodly number of bugs that would
have never been exercised doing computing that had been
approved by PHBs.
/BAH
Subtract a hundred and four for e-mail.
------------------------------
Date: Fri, 03 Sep 04 10:32:40 GMT
From: jmfbahciv@aol.com
Subject: Re: Xah Lee's Unixism
Message-Id: <41385b1e$0$19713$61fed72c@news.rcn.com>
In article <opsdpdzglzpqzri1@mjolner.upc.no>,
"John Thingstad" <john.thingstad@chello.no> wrote:
>On Thu, 02 Sep 2004 08:35:30 GMT, Brian Inglis
><Brian.Inglis@SystematicSW.Invalid> wrote:
>
>> On Tue, 31 Aug 2004 14:26:03 GMT in alt.folklore.computers, "John W.
>> Kennedy" <jwkenne@attglobal.net> wrote:
>>
>>> Andre Majorel wrote:
>>>> On 2004-08-31, Brian Inglis <Brian.Inglis@SystematicSW.Invalid> wrote:
>>>>
>>>>> On Tue, 31 Aug 2004 01:12:55 +0000 (UTC) in alt.folklore.computers,
>>>>> Andre Majorel <amajorel@teezer.fr> wrote:
>>>>>
>>>>>
>>>>>> On 2004-08-30, Antony Sequeira <usemyfullname@hotmail.com> wrote:
>>>>>
>>>>>>> Windows (MS) is not 'Unixism'?
>>>>>>
>>>>>> If by unixism, you mean any operating system that has a
>>>>>> hierarchical filesystem and byte stream files, yes. But that
>>>>>> would include quite a few other non-Unix operating systems,
>>>>>> including Mac OS 9, Prologue and probably everything else this
>>>>>> side of CP/M (DOS 1.x shall be deemed to be CP/M).
>>>>>
>>>>> DOS 2.x+ shall be deemed to be CP/M+!
>>>>
>>>>
>>>> Wasn't it in version 2 that they added directories and
>>>> Unix-style file handles ?
>>>
>>> Yes, and also a single-process pipe emulator. Ever since 2.0, MS has
>>> been trying to turn MS-DOS (later, Windows) into a Unix clone.
>>
>> MS has been borrowing code from Unix to create a real OS: TCP/IP;
>> NTFS<-ffs; memory mapped files<-mmap.
>> Shame they keep trying to add their own ideas in too: that must be
>> what causes the crashes!
>>
>
>You seeem misinformed.
>Microsoft swallowed up a team from DEC.
>The were developing a operating system called PRISM.
Which was Cutler's view of what VMS should be. Assuming
he hadn't change, this would not have delivered computing
system services to users.
>When the project was cancelled they quit DEC in protest.
>These peaple had more than a 100 years of experience in developing
>muliuser /
>mutitasking operating systems between them.
100 years total isn't much experience.
> .. The fact that the NT kernel is
>not
>entirely stable yet really shouldn't supprise anyone. Afterall Unix has
>messed with
>it's kernel for 30 years.
PRISM is as old as Unix...actually older.
<snip>
/BAH
Subtract a hundred and four for e-mail.
------------------------------
Date: Fri, 03 Sep 04 10:42:07 GMT
From: jmfbahciv@aol.com
Subject: Re: Xah Lee's Unixism
Message-Id: <41385d56$0$19713$61fed72c@news.rcn.com>
In article <opsdpprvxppqzri1@mjolner.upc.no>,
"John Thingstad" <john.thingstad@chello.no> wrote:
>On Thu, 2 Sep 2004 18:19:43 +0000 (UTC), Andre Majorel
><amajorel@teezer.fr> wrote:
>
>> On 2004-09-02, John Thingstad <john.thingstad@chello.no> wrote:
>>
>>> The fact that the NT kernel is not entirely stable yet really
>>> shouldn't supprise anyone. Afterall Unix has messed with it's
>>> kernel for 30 years.
>>
>> I feel compelled to point out that Linux achieved considerably
>> better stability after just a few years.
>>
>
>I feel compelled to replay that Linux is based on the Posix standard which
>is basically a recipie for writing unix. They did not write a new
>operating system. They implemented a tested and proven one.
So was Cutler's. He had his own ideas about what an OS should
do. None of them delievered efficient computing services that
the customer wanted.
/BAH
Subtract a hundred and four for e-mail.
------------------------------
Date: Fri, 03 Sep 04 10:47:32 GMT
From: jmfbahciv@aol.com
Subject: Re: Xah Lee's Unixism
Message-Id: <41385e9b$0$19713$61fed72c@news.rcn.com>
In article <opsdp4cjnapqzri1@mjolner.upc.no>,
"John Thingstad" <john.thingstad@chello.no> wrote:
>On Thu, 02 Sep 2004 16:13:20 -0700, Alan Balmer <albalmer@att.net> wrote:
>
>> On Fri, 03 Sep 2004 00:40:14 +0200, "John Thingstad"
>> <john.thingstad@chello.no> wrote:
>>
>>> well documented at the time. Linux Pauling started out with minix and
>>> then
>>> went on to make a (mostly) posix compliant unix.
>>
>> Linux Pauling? I know about Linus Torvalds and Linus Pauling . I don't
>> think the latter had much to do with Linux.
>>
>
>lol.. oops. No Pauling was a nobel prize winning chemist.
>No idea why that came out. (assosiative memory can be a bich)
>
The guys figured it out. You have an interested associative
memory :-).
/BAH
Subtract a hundred and four for e-mail.
------------------------------
Date: Fri, 03 Sep 04 10:51:21 GMT
From: jmfbahciv@aol.com
Subject: Re: Xah Lee's Unixism
Message-Id: <41385f7f$0$19713$61fed72c@news.rcn.com>
In article <41376DCA.B833324A@yahoo.com>,
CBFalconer <cbfalconer@yahoo.com> wrote:
>John Thingstad wrote:
>>
>.... snip ...
>>
>> These peaple had more than a 100 years of experience in
>> developing muliuser / mutitasking operating systems between
>> them. The fact that the NT kernel is not entirely stable yet
>> really shouldn't supprise anyone. Afterall Unix has messed
>> with it's kernel for 30 years. But the modular arcitecture
>> and the microkernel are new ideas in OS design and should in
>> time lead to a more extensible OS than unix.
>
>The original NT (3.0) was well designed, but slow on the hardware
>of the time. Then MS got to work increasing module connectivity
>and reducing reliability.
V3? I thought V4 was their last good one before they started to
put apps into execmode.
<snip>
/BAH
Subtract a hundred and four for e-mail.
------------------------------
Date: Fri, 03 Sep 2004 14:13:07 +0200
From: Espen Vestre <espen@*do-not-spam-me*.vestre.net>
Subject: Re: Xah Lee's Unixism
Message-Id: <kw1xhjczzg.fsf@merced.netfonds.no>
jmfbahciv@aol.com writes:
> V3? I thought V4 was their last good one before they started to
> put apps into execmode.
3.51 was the last good one.
--
(espen)
------------------------------
Date: Fri, 03 Sep 04 10:59:11 GMT
From: jmfbahciv@aol.com
Subject: Re: Xah Lee's Unixism
Message-Id: <41386155$0$19713$61fed72c@news.rcn.com>
In article <kg08hc.bgc1.ln@via.reistad.priv.no>,
Morten Reistad <firstname@lastname.pr1v.n0> wrote:
>In article <41376B82.C6A202FC@yahoo.com>,
>CBFalconer <cbfalconer@worldnet.att.net> wrote:
>>Peter Hansen wrote:
>>> Brian {Hamilton Kelly} wrote:
>>>> wyrmwif@tango-sierra-oscar-foxtrot-tango.fake.org "SM Ryan" wrote:
>>>
>>>>> There's a story about why railroad tracks are spaced the way they
are.
>>>>
>>>> Is this the one about two Roman horses' arses? If so, it also
accounts
>>>> for the physical dimensions of the Space Shuttle's boosters.
>>>
>>> A quick search using Google will show that while there is a
>>> certain amount of truth in the original story, most of the
>>> details are wrong, and the final bit about the booster rockets
>>> is unsubstantiated. But it's still a cute story.
>>
>>I know nothing about those stories, but it seems reasonable to me
>>that the boosters would have been designed to be transportable by
>>railroad, which ties their dimensions to track gauge.
>
>ISTR there was some tunnel NASA had to relate to if they wanted
>to move the goods from production to launch. But that may have been
>earlier products.
>
>But rail tunnels are also descended from the same asses, so to speak.
There was a city getting restored in Turkey that JMF and I visited;
I cannot remember its name other than it's in the New Testament
written by Paul. It was one of most fascinating places I'd ever
been other than aquariums and zoos. There are ruts in the
stone-block pavements caused by running carts to/from harbor/city.
We were told that these ruts were worn down by usage. I always
wanted to get a big stone and spend 5 min/day rubbing it to see
if the claim was true.
/BAH
Subtract a hundred and four for e-mail.
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 6954
***************************************
