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



On 18 Jun 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<1150661543.975294.61580@xxxxxxxxxxxxxxxxxxxxxxxxxxx>, iforone wrote:

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.

If you think that Mueller is bad, you ought to see the mis-informed garbage
that some of the certification books contain.

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...

<turns, and looks at book cases>

I'm at home mind you, and this room has 108 running feet of book shelf space,
and this doesn't include the 16 books in front of me, between the two
monitors. Much (but not all) of that is technical books. My office at work
is almost as bad... or good depending on your interpretation.

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.

A comfortable chair is _very_ important.

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).

The _main_ advantage of on-line stuff is that it _can_ be a lot more up-to-date
than dead-trees. Trying to get a book written, published and distributed in
less than 6 months isn't easy. The other advantage of on-line verses dead-tree
is being able to search for keywords or phrases. I use 'zgrep' a _lot_ for
that purpose.

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

About two years ago I found a 12 MHz 286 with 1.5 Meg of RAM in the garage,
along with the two 5.25 inch floppies for MS-DOS 3.30. My NFS server with a
Gig of RAM and two 33 Gig drives boots faster.

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)

People seem to forget that /sbin/init is a text based setup, and the whole
world begins there, and goes outward via /etc/inittab. When the system won't
boot which means you don't have your favorite GUI admin tool...

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),

Normally, the way I'd investigate this is with a packet sniffer tee'd off
the system with problems.

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.

This may also help debug the problem. If you do set static values, and it
_still_ takes a second reboot to get the thing working, then we're back to
the idea of the card not being reset cleanly. Do you know off hand if there
is a "newer" windoze driver for the card?

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

Ora.com or oreilly.com - they have a very good reputation in books. In
that stack between the monitors, 10 of the 16 are O'Reillys.

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)"

[compton ~]$ which zip unzip
/usr/bin/zip
/usr/bin/unzip
[compton ~]$

This isn't a Debian box, but that should be similar. This is a separate
package from Gnu Zip

Description :
zip is a compression and file packaging utility for Unix, VMS, MSDOS,
OS/2, Windows NT, Minix, Atari and Macintosh. It is analogous to a
combination of the UNIX commands tar(1) and compress(1) and is
compatible with PKZIP (Phil Katz's ZIP for MSDOS systems).

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

Well, I suppose that is one way to do it, but what you wanted was

[compton ~]$ echo $PATH
/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/ibuprofin/bin
[compton ~]$

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)...

Yes, it's a bad idea, doubly so if ANYONE else can write to the directory
you are in.

plus I have no idea "where" the actual executable resides that
I need to specify in the $PATH.

[compton ~]$ whereis zip
zip: /usr/bin/zip /usr/share/man/man1/zip.1
[compton ~]$ whatis whereis
whereis (1) - locate the binary, source, and manual page files
for a command
[compton ~]$

'which' searches in your existing PATH. 'whereis' searches the system
directories . There is also a 'locate' command that looks in a database that
indexes all files on the system (more or less) that is normally created at
Oh-Dark-Thirty when no one is using the system because of heavy CPU load.

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.

Now, I'm not the Debian expert - I rarely use it any more, but man dpkg

dpkg -L | --listfiles package ...
List files installed to your system from package.

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....:-(

A lot depends on what you are trying to do with the system. I'm command
line, and always have been (Jeez, this article is already huge) but here
is three little hints:

[compton ~]$ ls `echo $PATH | tr ':' ' '` | egrep -vc '(:|^$)'
1317
[compton ~]$ echo $HISTSIZE
1000
[compton ~]$ history | sed 's/^......//' | tr '|' '\n' | sed 's/^ *//' | cut
-d' ' -f1 | sort -u | wc -l
90
[compton ~]$

Translation: There are 1317 commands in my PATH as a user (about 1600 as root).
My shell is set to remember the last 1000 times I hit the Enter key to run a
command. The line beginning with 'history' and ending with 'wc -l' is thus
considered 1 command, even though it has seven actual commands cascaded to
get the information I want. That command parses the preceding 1000 commands
and breaks them down into components, and counts how many different commands
I'm actually using... and 90 is a bit high - I normally see a range of 65 to
100 in the 21 different shells I have open on this desktop. Bottom line is
that you don't have to know a thousand or more commands. There are over 5000
man pages on this system. I rarely access even a tenth of those. Heck, /bin/ls
has over 45 options - I rarely use more than six. Get the idea?

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...

Years ago, I'm supposed to go do something to a workstation located in a
room with maybe nine others. I get there, and can't figure out which is
which because it's break time, and most of them are running a locked screen
saver. So I call the group administrator - "Which one is peachpit?". "That's
this one here". OK, so I go to another system, telnet in to peachpit, become
root, and start killing user processes so that I can shut the darn thing down.
Are you ahead of me yet? There's some poor user in the back of the room trying
desperately to figure out why every thing on her desktop is dying, and as
soon as she logs back in, things are dying again. For my part, I'm trying
to figure out what is respawning all these user processes... and the local
admin is telling the user to shut up because we're trying to figure out what
this problem is. Shortly after that, _EVERY_ system got Dymo labels on the
CPU and monitors.

Old guy
.


Quantcast