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

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

R-i-g-h-t -- that's the ticket - Thanks again, for the explanation too.
I had played around with it and found when in any of the the VT/VCs
(ctrl+alt+F1[2,3,4,5,6]), that it works when 'logged in' (perhaps only
when as root, but I forgot to try usermode too) -- I was also hoping I
could take a screenshot of those screens, but it doesn't seem to work
like that (i.e.; Capture using PrintScrn in VC, then use Alt+F7 to come
out of VC, and paste into App).

I normally use cut-and-paste in X, but it's cutting/pasting text. I don't
know if I ever had print-screen working.

Needless to say - just capturing the Text in some way would be very
useful to me (i.e.; some sort of Logfile, or even copy and paste. I
don't n-e-e-d to screen capture per se.

If you are having trouble during boot, move the original scripts TEMPORARILY
to some different name - such as 'mv /etc/rc.d/rc.S /etc/rc.d/rc.S.original'
and the copy the original back ('cp /etc/rc.d/rc.S.original /etc/rc.d/rc.S')
and then use your editor to make changes on this copy. Once you have made
the change, do a 'diff' to verify that only the changes you desire were made.
The syntax is 'diff /etc/rc.d/rc.S.original /etc/rc.d/rc.S'. The reason for
doing it this way is that if things go to he!! in a handbasket, you need only
copy the original back, and all is (more or less) forgiven. Using the 'diff'
detects the strangest errors, like some user friendly editor that helps you
by inserting newlines at around 70-odd characters (which breaks the scripts
quite well), as well as the usual fumble-fingering.

I guess perhaps it's not set in syslogd (or whatever daemon), but
perhaps it's 'modifying one of the Shell scripts found in /etc/init.d,
such as 'sysklogd'(?)

syslogd or klogd or sysklogd - they only put stuff into places you designate
when they receive it. If the original application isn't sending the stuff to
the logging daemon, there is nothing the daemon can do on it's own.

-- or an entry one would place in /etc/inittab(?).

I'd be hesitant to do so, but if you know what you are doing this is a
possible answer. Can you see me not recommending this?

Ah...nice;
I've not heard of that yet - but I am s-l-ow-l-y making my way through
that ABS guide you pointed me to. I want to be sure and check into all
aspects as I move through it.

I think I told you - Rome wasn't built in a day. Neither do you learn shell
scripting overnight. One step at a time.

but nowhere do you see stderr being redirected
(other than to /dev/null on occasion).

...and I guess stderr is the one I need to look more into (not so used
to that one).

I don't have a Debian script handy to use as an example, but let's say that
it looks something like

foo -bar -baz
echo 'foo started'

To get a stderr output ASSUMING THE FILE SYSTEM IS MOUNTED 'r/w' BY THIS
POINT, you might try

echo 'trying to start foo' >> /tmp/some.file.name
foo -bar -baz 2>>/tmp/some.file.name
echo 'foo started'

The '2>>/tmp/some.file.name' appends stderr to that file FOR THIS PARTICULAR
COMMAND ONLY.

Right - and IIRC, one diff between them is the way the Startup scripts
(BSD's SysV type for some) and the how the diff runlevels
operate/interact, and with what networking (or multi-user
functionality) is available at each runlevel, and at which runlevel the
GUI (if needed) is first available.

BSD vs SysV is complex, but it's relatively obvious when you look at
/etc/inittab. The _results_ are about the same - but it's how do you get
from "A" to "B". Which runlevel to use is also usually indicated in the
/etc/inittab file.

You know - I should burn another Knoppix LiveCD and try to get this
older P166 going to do just this - I recall seeing all sorts of packet
sniffing tools (airsnort, snort, tcpdump, etc) in the knoppix menus
once booted up into the GUI (they are likely there/available in text
mode as well). But getting the P166 going only requires a NIC, and then
I'll also have another box, from which to access each from the other.

Now we're thinking. Minor problem is knowing how to interconnect things - a
hub or a switch (the switch would have to be in promiscuous mode to see
packets on other ports), but yeah!

For a curiosity - when you first boot into windoze after Linux, and the
card isn't finding the DHCP server, what does (I think the command is)
'ipconfig /all' - no, wait you said win98 - try winipcfg and the more button,
show with respect to the hardware address? Compare that to when it's working.
Is windoze able to talk to the network card? A symptom in Linux is that the
MAC address is all zeros when it can't talk to the card.

Oh - check this thread out

Newsgroups: alt.os.linux.mandriva
Subject: Re: Netbios Packets

Yeah, I've got the thread on my server - looks like "Whiskers" is handling
things. You wrote:

]You may want to consider removing the ZeroConf package (if it exists on
]Mandriva - I'm using Debian Sarge)

I'm trying to remember which file Mandr* uses for this - I don't use that
distribution, and most people posting fixes on it are talking about using
some distribution specific configuration tool. I'd grep for 'ZEROCONF' in
/etc/sysconfig/network and the files in/etc/sysconfig/network-scripts/.

I see the extension 'SomeFile.tar.gz' all the time (I need to do more
'man' digging) ;-) and I've recently been hitting the 'man gzip' (and
many others pages) to try and figure "HOWTO" just to *View* (which
means 1st decompressing, I suppose) all the various *.gz archived files
in /var/log ....within the _Terminal_ while in a Console - not the
pretty GUI.

[compton ~]$ whatis mc
mc (1) - Visual shell for Unix-like systems
[compton ~]$

Handy little tool if it's installed. It allows you to look inside tarballs.
It's much nicer looking than just 'zless tarball.gz' or 'bzless tarball.bz2'.

I have no real problems viewing them in the Terminal, but when they're
HTML and Gzipped (or any other zip type like b2zip) I see all the HTML
code crap, as well as the relevant info.
No prob...I'll work it out.

'mc' is probably what you are looking for.

I need to drop down further, to the typical mainly *nix only apps, like
Lynx, Xfce, IceWM, emacs, mc, mutt, vim, etc...but this will take some
time to learn how to be productive using these mostly unfamiliar,
mostly keyboard only apps.

[compton ~]$ history | grep -c mc
13
[compton ~]$ ^mc^lynx
history | grep -c lynx
15
[compton ~]$ ^lynx^vi
history | grep -c vi
172
[compton ~]$

You could say I use those, though I use 'mail' rather than 'mutt', and vi
rather than emacs.

[compton ~]$ sed 's/^$/\%/' < rfcs/rfc-index.txt-06.10.06 | tr -d '\n' |
tr '%' '\n' | grep '^[0-9]' | tr -s ' ' | grep -v 'Not Issued' | sed
's/.*Status: //' | tr -d '\)' | sort | uniq -c | column

d-u-d-e....
I'll be studying the above for a few years ;-)
Showoff - and v-e-r-y called for ;-)

Like I say, it _looks_ complicated, but if you break it down into the
individual commands, it's really not doing rocket science.

the first sed turns all empty lines into a line
with a unique character, the first tr then deletes all newlines, while the
second translates that unique character into a newline (resulting in each
entry being on one long line).

again; d-u-d-e.... :-)

Part of the problem is thinking how can I get from here to there - not in one
mighty step, because that isn't very likely to work - but a step at a time
"If I do this, then I'll get that, and I can then do this other thing"...
But it all starts knowing what these individual simple commands can do, and
what your data looks like to start with. What did I use here; sed, tr, grep,
sort, and uniq (column is just to reduce the overall length of the printout).
Five commands reduced a list of

[compton ~]$ grep -c '^[0-9][0-9]*' rfcs/rfc-index.txt-06.10.06
4507
[compton ~]$ wc rfcs/rfc-index.txt-06.10.06
17024 93562 745982
[compton ~]$

4500 entries totalling 17000 lines and 3/4 megabytes to eight totals. This
certainly isn't something a beginner is going to do off the top of his/her
head, but something equally as bad was being done by those students at the end
of that 4 unit course (2 nights a week. 3 hours a night for 12 weeks), and the
first two or three weeks was getting the newbies so they could use a handful
of commands in vi and use /bin/mail. Don't think the class had any
prerequisites, but this was back in MS-DOS 4 and 5 or so. The class was called
"Introduction To Unix" and was taught at a community college.

I'll leave you be, for now -- I know I'll never let this thread die, if
I don't stop myself...

Well, it is drifting (quite far) off the original subject ;-)

Old guy
.