Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having


Moe Trin wrote:

And this is different from the norm exactly how? ;-)

Not by much I suppose :-)
but I also really didn't start venturing into the realm until the late
90's, and then, it was a gift with ...yup; winblows installed.

You know? I never use/used a power strip in that manner (for *ATX*

That's true of many O/S that use a write cache. Unix has had this for
decades, as did Novell Netware and MacOS predating windoze. SGI had a
neat switch on their Challenger boxes in the early 1990s - you punched
the "power switch" on the front panel, and the O/S would cleanly terminate
any running apps, then flush the buffers, and finally unmount the disks
before turning off the power. There was also a hidden power switch at the
top right of the back panel, but this one killed power without doing
anything safe.

Cool...

0-88022-395-2 88-62746 First edition
1-56529-467-X 93-86245 Third Edition
0-7897-1636-4 98-84382 Tenth Edition
0-7897-2974-1 (2004) 15th Edition

Some of his stuff I take with a whole bag of salt,

I concur - there is _some_ info (here and there) in those publications
which is either lacking, or not *that* well informed. I used to be kind
of a bookworm myself, but lately I loathe the idea of having all these
technical text books laying around, taking up space, keeping the dust
off of 'em, etc, etc. I prefer the screen at this point, but you're
correct in that the wealth and depth of detailed info is more
comprehensively available...I'm not sure if it was the Inkjet whore
mongers which made me loathe 'paper' in it's entirety, or just not
having a comfortable reading area and workspace setup. Either way, I
love the installed man stuff, and the wealth of unix/linux info that
either gets installed (docs), or can be installed *locally*, for real
easy access. It's friggin great! (FOSS).

but I admit to using his
"swap the 79 cent crystal" improvement to an original PC-AT. It was working
at 8.5 MHz (rather than the stock 6 MHz) which pissed off my cube-mate who
had a real 8 MHz version with the anti-overclocking BIOS.

haha - Envy hath taken his soul ;-)
and Wow!, a Full 8.5 Megahertz? You must have been in heaven then...lol

For shell scripting, start with the Bash-Prog-Intro-HOWTO

-rw-rw-r-- 1 gferg ldp 31540 Jul 27 2000 Bash-Prog-Intro-HOWTO

Will do...thanks

then grab a copy of The Grendel's fabulous book "Advanced Bash Scripting
Guide" from the LDP (http://tldp.org/guides.html).

Done - Thanks a ton! I've already forgotten about all these
repositories overflowing with info.

I've lost track of how
many revisions it's gone through, but it's a _very_ polished book with lots
of examples. I also recommend setting down with a bucket of coffee and the
man pages, and trying to read through the boot scripts on your system. These
are generally written by someone who is _really_good_ at scripting, and is
_flaunting_ those skills.

I hear that - and have noticed that too...especially when I was
recently venturing into learning Python (real brief), since it's what
was already installed during installation of Debian Sarge - the docs
looked promising and the en.wikipedia.org article about it states how
it can be used, even though it's an OO language (which I generally
don't like b/c I don't like the idea of "objects"...you can thank
MScrud (ASPcrap) and JavaCrap and MacroMedia'sShock*** for that). I
started "looking" viewing the rcX.d DIR scripts ...and various other
ones (Perl) that are local, to get an idea of what's under-the-hood, as
I've noticed from reading UseNet posts, that this is the way to
'control' the system (from Startup items, to cron jobs, to runlevel
changes, etc)

Well, I know there is that difference in the missing hardware reset action,
but I think your 'second reboot and it works' might be that the first is
only partially fixing the problem, and the second reboot sees something it
recognizes and is able to correct/handle.

I think you are dead on - I'm thinking it shouldn't be broke to begin
with (so that it doesn't need any fixing that the 2nd reboot actually
fixes). IOW, perhaps the stupid Router using DHCP is the common element
throughout (for whatever reason it behaves this way, is beyond me), but
eventually I'll finally set Static IPs if not just to see the results,
but to also really delve further into my networking knowledge, so I can
be useful in a Network env.

It's a fairly powerful tool - but you do realize that O'Reilly was able to
find enough materials to get two full size books and a reference guide for
it (my wife cringes when I get _near_ a bookstore).

Effective awk Programming, 3rd Edition May 2001 $39.95
sed & awk, 2nd Edition Mar 1997 429 pgs $34.95
sed & awk Pocket Reference, 2nd Edition Jun 2002 $12.95

Excellent! - now I know what to look for - b/c as you know, many
publications(of all sorts) are a waste, and horrible.

except bzip2, but yeah it also handles regular files as well, which comes
in handy when searching through a directory that includes both types.

Gotcha...
BTW - should I be having a problem UnZipping ZIP files? I am though...
I d/l this ZIP file, and when I try to View it using 'Ark', it errors,
saying;
"The utility Zip is not in your PATH
please Install it, or contact the sys admin (myself ;-8)"

I understand the error message, so I entered
$PATH at the bash command in Konsole;
~$ $PATH
bash: /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games: No such
file or directory

Rather than muck with my Env var. and $PATH settings (since I've read
about dangerous things occuring if one adds ' .' to the default
PATH)...plus I have no idea "where" the actual executable resides that
I need to specify in the $PATH.

So like an idiot, a few days ago, when I had this issue, I did
something like this;
~$ apt-cache showpkg zip
~$ sudo apt-get install zip
Which now yields
Reading Package Lists... Done
Building Dependency Tree... Done
zip is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.

and which didn't help one bit anyway. I'm still stuck in this
muck-and-mire MS way of GUI thinking...ugh!


Fumble finger - try /usr/share/man/man1/

Not you -- Me!
Sorry, I _should've_ caught that typo - I know better than that
atleast.

What is my P-133... let's see, it's running a log server, print servers,
and backup network access box. It was running X - it still has FVWM2 on it
which is a fairly lightweight desktop.

Way Cool

I'm not into eye-candy, and mostly
use X to provide multiple xterms. X really doesn't belong on a server,
because X is a _user_ interface, and _users_ shouldn't be mucking about
the servers. It's astonishing how much memory and disk space X (and the
"popular" desktops) take.

I hear ya - If I had the knowledge to use the command line well enough,
I'd give up on the bloated Desktop Env/Apps, but it's unfortunately my
already 'learned' Micro*** way, that I need to Undo....:-(

yet I need to get it a NIC...there is an open PCI slot (as well as ISA
slots), but I think I need an earlier PCI type that isn't so easy to find
(New) nowadays...I'm sure I can find one, if only I can recall the
requirements

Possibly supply voltage. Look in Mueller's book.

ahhh.... yes - Duh! ;-0

I eventually plan on using it as either something headless (some sort
of Server) on the LAN

287028 Mar 31 2003 Remote-Serial-Console-HOWTO

Will do - thanks!

A wise person has two ways into a box - over the net, and through a console.
As this is to be headless, string a null modem cable to another system so it
can be used if networking goes weird.

Ok - I understand - thanks for that advice, and the pointers.

I've got six headless boxes here, and
use cascaded A/B/C/D switches to one system to allow direct access. Big clue
is to put Dymo (embossed) labels on the switches, and computers, and set the
prompts so that they include hostnames - it's embarrassing to halt a computer
then yank the power cord out of the wrong one.

Yeah - I always like labeling (color-coded too) for easy wiring up or
down specific components - I used this technique when managing my
band's PA gear, and even my own various Guitar setups...

Thanks Moe, for the enlightenment and conversation

Regards

.