Re: OT: Wheeeeee! New PSpice Benchmarks

From: Ken Smith (kensmith_at_green.rahul.net)
Date: 08/31/04 

Date: Tue, 31 Aug 2004 02:31:52 +0000 (UTC)

In article <pan.2004.08.31.01.40.36.401923@att.bizzzz>,
keith <krw@att.bizzzz> wrote:
[...]
>I have OrCad 9.x, but I never considered trying it at home (no license).

I don't off the top remember which version mine is. Its really stone age.
At work they paid for the upgrades etc. Personally I could see paying any
thing for the small improvements so I never upgraded.

>I'm quite used to "man" pages, having done Unixisms for some time. Though
>I do find "man" pages rather terse and slightly better than useless if you
>don't know what they're saying. For instance I've been trying to get my
>USB flash-drive running under Linux. Cool, I can follow directions in the
>"man fstab" page, except that it doesn't tell me what all that crap is!
>I finally (with major help from the web) got it working, but it was ugly,
>and still have "issues" (my mount point tends to disappear). Grrr.

I didn't say or wish to imply that the man pages were very helpful. Their
existance is the indicator I was suggesting.

>...as reference. I remember the IBM JCL manuals were chock-full of
>information, if you know what they were saying. reference <> help.

I /*EOD ed all my knowledge about JCL years ago.

>I've installed SuSE at least a half-dozen times. I added a DATA drive and
>it crashed the installation on the pATA drive (it got sooo confused). I
>then tried installing on tha SATA drive a few times, good idea! (the
>drivers don't work!).

My machine is "bog standard" so the install went fine. True the SuSE help
folks. I'd be interested to know if they are helpful.

>> BTW: You can do darn near anything in a Bash script.
>
>Oh, my! Another issue! I followed the instructions (albeit from a RH
>user) on how to do a BASH script for the above flash-drive. No joy in
>Mudville[*] tonight. ...and mud-season is supposed to end by May

99 times out of 100 what they told you is more complex than what you need.
Its sort of like making chile. If a batch comes out extra good, chances
are you left out something.

Once you figure out the weird way things work, it starts to sort of make
sense.

When you know what needs doing:

You put the script into /etc/init.d, and a link to it in one of the rc#.d
sub-directories. The script has to be made so it can be run using chmod.

To figure things out, I commonly make the script in my no-privelaged
~/script directory. This way I limit the amount of damage I can do.

Googling on things sometimes finds good examples.

>[*] If it doesn't stop raining I'll have to throw the computers out as
>anchors. A friend has already lost his
>basement/foundation/furnace/water-heater to floods (though his *flood*
>insurance company calls a foot-wall of water running t'wards the house
>and through the basement "sepage").

If you house is wrecked by the water damage, hire a company to knock it
down and haul it away, then report it stolen. Chances are you have theft
insurance :>.

Are you in the south east? Sounds bad. 

-- 
--
kensmith@rahul.net   forging knowledge