Linux-Misc Digest #838, Volume #23 Mon, 13 Mar 00 16:13:05 EST
Contents:
Kernel Compile Documentation ("David ..")
Re: Red Hat install problem (Chris Lowth)
Re: Telnet to Unix box ("G. Roderick Singleton")
Uses for /dev/zero ("M. Leo Cooper")
Re: Uses for /dev/zero (Lew Pitcher)
ppp many RX errors, lots of stalling (John Noble)
Re: Two Scsi Cards, which is which? (Joseph R. Erlewein)
the command "rz" ([EMAIL PROTECTED])
Re: video player (Robie Basak)
----------------------------------------------------------------------------
From: "David .." <[EMAIL PROTECTED]>
Subject: Kernel Compile Documentation
Date: Mon, 13 Mar 2000 14:01:25 -0600
This is a multi-part message in MIME format.
==============90A0A7BB658B6C268376B32C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
The attached HTML file, documents my kernel compile of the 2.2.14-5.0
kernel. I have tried to keep it short but this is a little different
than compiling just the normal sources. If you find an error in it
please let me know so that I can make corrections to it. I believe it is
accurate though I sometimes make an error along the way. If you find it
helpful please let me know.
--
Due to extreme SPAM abuse! Remove z's and x's from above to reply.
Thnak the spammer's A..holes that they are. Still can't reach me?
Then your address range is already blocked due to previous spam.
Sorry! I hate spam!!
==============90A0A7BB658B6C268376B32C
Content-Type: text/html; charset=us-ascii;
name="kernel.compile.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="kernel.compile.html"
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Mozilla/4.72 [en] (X11; U; Linux 2.2.14 i686)
[Netscape]">
</head>
<body text="#000000" bgcolor="#CCCCCC" link="#0000EE" vlink="#551A8B" alink="#FF0000">
<font color="#990000"><font size=+4>Compiling a new Kernel using SRPMS</font></font>
<br><font size=-2>author: David Barnett</font>
<br><font size=-2>Date written: 3/13/2000</font>
<p> Download the kernel.src.rpm. While downloading the kernel you
can make a boot disk and rescue disk just in case you need it later. To
make a boot disk insert a blank floppy and give the command:
<p> mkbootdisk --device /dev/fd0
x.x.xx
# x.x.xx is kernel version.
<p>To make a rescue disk you need a blank floppy and to give the command:
<p>fdformat /dev/fd0H1440 # formats
disk
<br>cd /boot
<br>cp vmlinuz
/dev/fd0
# copies the kernel (vmlinuz) to floppy
<p>rdev # This shows the
kernels root device such as "/dev/hda5"
<br>rdev /dev/fd0 /dev/hdaXX
#where hdaXX is the correct root device.
<br>rdev -R /dev/fd0 1
# This makes the root device read only
<p>To test the new disk simply put the disk in A: and reboot.
<br>Once you have a working boot disk and rescue disk then you are ready
to continue with the compile.
<p>Install the src.rpm package with the command:
<p> rpm -i kernel-x.x.xx.src.rpm
# x.x.xx is version number
<p>This will install the kernel sources into the /usr/src/redhat/SOURCES
directory.
<p>At this point you need to:
<p> cd /usr/src/redhat/SPECS/
<br> rpm -bp
kernel-x.x.xx.spec
# be sure to use correct spec file name
<p> This will untar the source and install all the patches that are
provided with the src.rpm and place the un-tared directory in
/usr/src/redhat/BUILD/linux.
<p><font color="#990000">DO NOT attempt to reboot your system from this
point until the compile and install is complete.</font>
<p>Now you need to remove the old kernel version sources.
<p> cd /usr/src/
<br> rm -rf linux
#this removes the symbolic link directory
<br> rm -rf linux-x.x.xx # This removes the old kernel
sources where x.x.xx is the version number.
<p> Note: It is possible to leave the old version sources as long
as they are in their own /usr/src/directory with the correct version number
included in the directory name. ie.. linux-x.x.xx where
x.x.xx is correct version. If you choose to save the old version you must
still remove the /usr/src/linux symbolic linked directory.
<p>The next step is to remove the old kernel.
<p> cd /boot/
<br> rm -rf vmlinuz
<br> rm -rf vmlinuz-x.x.xx
# x.x.xx is version number.
<br> rm -rf System.map
<br> rm -rf System.map-x.x.xx # x.x.xx is
version number
<p>Note: You must remove the vmlinuz and System.map files. How ever
it is possible to leave the old version of vmlinuz-x.x.xx and
System.map-x.x.xx
where x.x.xx is correct version, as long as they have the correct
version number included in the file name.
<p>These will be replaced with the new kernel when you are done.
<p>Now give the command.
<p> cd
# back to root and give the command:
<p> ls /lib/modules/
<p>This will show what kernel version of modules you have. These can be
removed with the command:
<p> rm -rf /lib/modules/x.x.xx # where x.x.xx
is the old kernel version.
<p>This will remove the old version modules. Again if you want to keep
the old version be sure to name them correctly.
<p>At this point you need to copy the sources into /usr/src/ with the command:
<p> cp /usr/src/redhat/BUILD/linux
/usr/src/linux-x.x.xx
# where x.x.xx is the new kernel version
<br> chown -R 0.0
/usr/src/linux-x.x.xx/
# This sets owner & group to root.
<br> cd /usr/src/
<br> ln -s /usr/src/linux-x.x.xx
linux
# this creates symbolically linked linux directory.
<p> cd /usr/include
<br> rm -rf asm linux scsi
<br> ln -s /usr/src/linux/include/asm-i386 asm
<br> ln -s /usr/src/linux/include/linux linux
<br> ln -s /usr/src/linux/include/scsi scsi
<p> At this point you need to add any other patches not included
with the src.rpm that you want or need. After you get through installing
any additional patches. Now is the time to make any tweaks to the Makefile
or any other changes you wish to make to the source prior to the compile.
<p>To get started give the commands:
<p> cd /usr/src/linux/
<br> make mrproper
<p> make config, make menuconfig, make xconfig # choose
your weapon, only one is needed.
<p>Choose to load one of the .config files that were included in the src.rpm
and are located in the /usr/src/redhat/SOURCES directory. Choose the one
for your system.
<p> Make the needed selection changes for your specific system. Choose
carefully or you can have problems and have to recompile from the scratch.
When done be sure to save your changes. I also save to an alternate file
so that if I have to recompile for any reason I don't have to go back through
the whole config file to add or remove just one choice.
<p>So now that you have your config picked out it is time to give some
more commands. Starting with:
<p> make dep; make clean; make bzImage
<p>These 3 can all be included in one command as long as they are separated
by a ; (semicolon).
<p> This may take from a few minutes, several hours, or days depending
on your system. Be patient. Get some coffee, or maybe even some sleep if
it is a slower system. When the compiling is done you need to make
and install any modules that you need with the command:
<br>This step is not needed if you have compiled all modules into a monolithic
kernel.
<p> make modules
<br> make modules_install
<p> Once you get to this point it is just a matter of installing
the kernel. In order to do this you will need to give the following commands.
<p> cp /usr/src/linux/arch/i386/boot/bzImage
/boot/vmlinuz-x.x.xx
# where x.x.xx is kernel version.
<br> cp /usr/src/linux/System.map
/boot/System.map-x.x.xx
# x.x.xx is kernel version.
<p> cd /boot/
<br> ln -fs vmlinuz-x.x.xx vmlinuz
<br> ln -fs System.map-x.x.xx System.map
<br> rm -f module-info
<br> rm -f initrd-x.x.xx.img
<p> vi /etc/lilo.conf
<br> and remove the "initrd=/boot/initrd-x.x.xx.img"
line.
<br> and change the image=/boot/vmlinuz-x.x.xx to point the
correct version of your new kernel.
<br> Your /etc/lilo.conf would look similar to this for a dual boot
system with linux being the default OS:
<p> boot=/dev/hda
<br> map=/boot/map
<br> install=/boot/boot.b
<br> prompt
<br> timeout=50
<br> default=linux
<p> image=/boot/vmlinuz-2.2.13
<br> label=linux
<br> read-only
<br> root=/dev/hda5
<p> other=/dev/hda1
<br> label=dos
<p>Be sure to use the correct kernel version when making changes to your
/etc/lilo.conf file.
<br>Once you get these changes made then you need to install the new lilo
with:
<p> /sbin/lilo -v
<p> Also since you have compiled the modules into the kernel then
you no longer neeed the conf.modules file since it only is used to load
the modules needed at boot time.
<p> rm -f /etc/conf.modules
<p> From here you should be ready to reboot. Watch to see if you get
any error messages during the boot about modules. If you do then you probably
need to edit /etc/rc.d/rc.sysinit
<p> Comment out these lines starting around line 264 in the rc.sysinit
file (vi +264 /etc/rc.d/rc.sysinit):
<p> if [ -L /lib/modules/default ]; then
<br>INITLOG_ARGS= action "Finding module dependencies" depmod -a default
<br> else
<br> INITLOG_ARGS= action "Finding module dependencies" depmod -a
<br> fi
<br> fi
<br>
<p> If you have compiled a kernel with no loadable modules
then you may need to also comment the following line out.
<p> Comment out the line around line 252 in the rc.sysinit file (vi
+252 /etc/rc.d/rc.sysinit):
<p> if [ -x /sbin/depmod -a -n "$USEMODULES" ]; then
<br>
<p>If you have it working properly without a bunch of error messages then
you can update the devices with:
<p> cd /dev
<br> ./MAKEDEV update
<p>And if you use a few modules in your new kernel then you can do a:
<p> /sbin/depmod -a
<br>
<p>Best of luck with your new system.
</body>
</html>
==============90A0A7BB658B6C268376B32C==
------------------------------
From: Chris Lowth <[EMAIL PROTECTED]>
Subject: Re: Red Hat install problem
Date: Mon, 13 Mar 2000 15:47:51 +0000
I suspect you have confused it about which partition is root
(etc). Could you list the answers you give to the install screens - paying
particular attention to the partitioning of the drives, making file
systems, etc - anything hard disk related. Ideally - let's see the lot!
This *should* be a trivial one.
Chris.
On Sun, 12 Mar 2000, John Zumsteg wrote:
> I cannot get Red Hat 6.0 to install and boot. I've installed trying the
> standard workstation and server selections, as well as several different
> custom configurations. The install goes fine, but when I boot, it does a
> bunch of stuff, then the following:
>
> INIT: version 2.74 booting
> INIT: No inittab file found (although the install shows inittab being
> copied)
>
> Enter runlevel: (I enter 1)
> INIT: Entering runlevel 1
> INIT: No more processes left in the runlevel
>
> At which point, the machine is completely locked up; nothing works.
> This occurs whether I boot from the harddrive, or from a rescue disk or
> from a boot floppy.
> I have installed from this CDROM to another machine, without difficulty.
>
> The machine is:
> P2 - 266mhz
> 64mb RAM
> 4.3GB Seagate ultra-wide SCSI
> Adaptec AHA 2940 SCSI card
>
> As I said, this is a consistent result, over probably 8-10 installs now.
> Any help will be greatly appreciated.
>
> John
>
--
>From Chris Lowth
---
My Real e-mail address is (roughly):
chris
<AT> lowth
<DOT> com
(Silly over-parnoid anti-spam measure)
------------------------------
From: "G. Roderick Singleton" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux,comp.os.linux.networking
Subject: Re: Telnet to Unix box
Date: Mon, 13 Mar 2000 20:34:05 GMT
Floyd Davidson wrote:
>
> "G. Roderick Singleton" <[EMAIL PROTECTED]> wrote:
> >Floyd Davidson wrote:
> >>
> >> [EMAIL PROTECTED] (Herb Stein) wrote:
> >> >Now wait a minute Floyd. I do not actually use Linux in the
> >> >windowing environment, but my Unix recollection is that an
> >> >rlogin or telnet window can easily be VT100 compatible. It has
> >> >been a while but it works like that from another non-windows
> >> >system.
> >>
> >> Why would it? It's invoked from a command line, so you
> >> necessarily are already using either a terminal or a terminal
> >> emulator of some kind. All it does is pass the TERM variable to
> >> the environment at the remote host so that it knows what kind of
> >> a terminal is being used.
> >
> >If you have set it. Otherwise ... It is the user's responsibilty
>
> It passes it, period, whether you have set it or not. Whether
> it is properly defined is the issue. Setting TERM to "vt220",
> for example, only makes sense when the user's terminal is in
> fact emulating a vt220. It makes no sense at all when the local
> terminal is a linux console, xterm or other non-vt220 terminal.
>
But you can control this locally whether or not $TERM is passed.
You can define the emulation prior to using telnet or other remote
access tool so as to produce minimum pain. i.e. you have a remote
login thus you should know and understand the requirements for
your use. If you don't shame on you.
> >to define his environment. Often the sysadmin will provide
> >a 'canned' envrinoment for naive users but the user is still
> >responsible for ensuring that his environment provides useful
> >information to remote systems. So how does a user ensure his
> >environment is reasonable? By using one of the methods discussed.
>
> The methods discussed are all reasonable, but setting it to
> various *wrong* terminal types is not reasonable. That was the
> point.
>
Of course. Wrong is wrong. And why would a user in his right mind want
to do this? <shake head>
> >> Try setting your TERM variable to some wierdly named vt100 type,
> >> say for example a DT80. Telnet to some distant host and see
> >> what the TERM variable has been set to! (You might want to
> >> leave it set to a DT80, it might be a better description of the
> >> terminal attributes than is a vt100 description!)
> >>
> >
> >Telnet does not really care about $TERM. (see telnet(1)) so I don't see
> >the point of your arguement. If, on the other hand, we talk about rlogin
>
> See telnet(1):
>
> ENVIRONMENT
> Telnet uses at least the HOME, SHELL, DISPLAY, and TERM
> environment variables. Other environment variables may
> be propagated to the other side via the TELNET ENVIRON
> option.
>
Hmm. Mine does not and passes only DISPLAY and PRINTER by default. You
can, of course, define these and others in .telnetrc
> >and family, then we can discuss environment
> >definitions such as TERM. Why? Because the rlogin family does
> >pass along the user's environment.
>
> See rlogin(1):
>
> ENVIRONMENT
> The following environment variable is utilized by rlogin:
>
> TERM Determines the user's terminal type.
>
> As regards the TERM variable, rlogin and telnet are *identical*
> in that the value of the current environment on the local host
> is passed to the remote host and will be set when logging in.
>
What's your point. I agree that ALL member of the rlogin family
happily try to pass the user's environment.
> > This might affect use of
> >screen-oriented tools like vi if the passed $TERM is not recognized.
>
> It is not a "might affect" situation. It *definitely* will affect.
>
Depends on the user. vi(1) will work in line mode in 'dumb' mode
if it can't resolve the terminal emulation.
> > The
> >solution use tset or other method to synchronize
> >definitions so that tools will behave in an expected manner. i.e.
> >providing a bad definition is probably a more silly thing to do
> >than to let the connection take care of itself.
>
> Ahem... my point was that setting it to a *valid* terminal
> rather than aribtrarily selecting among various *invalid*
> terminals is indeed the correct solution. Whether it is done
> with tset or other means, if the TERM variable at the remote
> host is set to vt220 when in fact the terminal is a linux
> console, _it_won't_work_properly.
>
> It appears that many people are not fully aware of what the use
> of tset is, or what the effect of setting the TERM variable is.
> The TERM variable does NOT change the way a terminal responds to
> control sequences. It merely tells the various programs _what_
> the proper sequences are for a given terminal. It makes no sense
> to send vt220 sequences to a linux console... The tset program
> will also "initialize" a terminal and the driver attached to it.
> Hence it can send customized commands to a terminal to change
> modes, for example. But clearly it cannot change a linux
> console into a vt220 emulator.
>
If you are accessing a system and require use of a linux console or any
linux specific emulaltion, it is your responsibily to ensure
you have those requirements met on the remote system. Get the
sysadmin to add them or do it locally in your home directory.
> >> Hmmm... if your are really brave, try it from a shell inside GNU
> >> Emacs, where "emacs" is the terminal type. Or at least that is
> >> what it will be unless the init files for your shell on the
> >> distant host reset it.
> >
> >And in other tools or from the commandline.
>
> Can you expand on that comment, I don't quite understand what you mean
> to say there either.
>
> Floyd
>
> --
> Floyd L. Davidson [EMAIL PROTECTED]
> Ukpeagvik (Barrow, Alaska)
You may change your environment at will. You do not need emacs.
--
________________________________________________________________________________
G. Roderick Singleton, <[EMAIL PROTECTED]> PATH tech,
71 Underhill Drive, Unit 159, Toronto, ON M3A 2J8
Voice : 416-452-4583 Fax: 416-452-0036 Toll Free: 1-888-354-PATH
________________________________________________________________________________
*** Notice To Bulk Emailers: Attention! Pursuant to US Code, Title 47,
Chapter 5, Subchapter II, 227, any & all unsolicited commercial e-mail
sent to this address is subject to a download and archival fee in the
amount of the $1500 US and copies will be forwarded to domain
administrators. Emailing denotes acceptance of said terms!
------------------------------
From: "M. Leo Cooper" <[EMAIL PROTECTED]>
Subject: Uses for /dev/zero
Date: Mon, 13 Mar 2000 13:52:00 -0700
The /dev/zero pseudo-file is somewhat similar to /dev/null, but rather than
being a "black hole" like the latter actually does contain nulls. It's a bit
difficult to access or read the file unless you use something like 'od' or, I
guess, a hex editor...
What I'm wondering is whether there are any real-life uses for /dev/zero. Does
the OS or the kernel use it? Can anyone recall seeing /dev/zero in a script or
program?
There are quite a number of well-known uses for /dev/null, such as linking it
to the cookies file*, but no uses I know of for /dev/zero. What justifies its
existence?
*If a web server tries to read a cookies file symbolically linked to
/dev/null, it finds an empty file. I wonder what would happen with a cookies
file linked to /dev/zero. Very possibly the server would hang, since doing a
'cat' on it hangs.
------------------------------
From: [EMAIL PROTECTED] (Lew Pitcher)
Subject: Re: Uses for /dev/zero
Reply-To: [EMAIL PROTECTED]
Date: Mon, 13 Mar 2000 20:48:22 GMT
On Mon, 13 Mar 2000 13:52:00 -0700, "M. Leo Cooper"
<[EMAIL PROTECTED]> wrote:
>The /dev/zero pseudo-file is somewhat similar to /dev/null, but rather than
>being a "black hole" like the latter actually does contain nulls. It's a bit
>difficult to access or read the file unless you use something like 'od' or, I
>guess, a hex editor...
>
>What I'm wondering is whether there are any real-life uses for /dev/zero. Does
>the OS or the kernel use it? Can anyone recall seeing /dev/zero in a script or
>program?
Yes. The HOWTO that describes setting up swap files and partitions
mentions using /dev/zero to initialize a swap file before an addswap
command.
>There are quite a number of well-known uses for /dev/null, such as linking it
>to the cookies file*, but no uses I know of for /dev/zero. What justifies its
>existence?
The need for a lot of binary zeros?
Like in clearing swap files, and security wiping partitions and files.
>*If a web server tries to read a cookies file symbolically linked to
>/dev/null, it finds an empty file. I wonder what would happen with a cookies
>file linked to /dev/zero. Very possibly the server would hang, since doing a
>'cat' on it hangs.
>
>
Lew Pitcher
System Consultant
Toronto Dominion Financial Group
([EMAIL PROTECTED])
(Opinions expressed are my own, not my employer's.)
------------------------------
From: John Noble <[EMAIL PROTECTED]>
Subject: ppp many RX errors, lots of stalling
Date: Mon, 13 Mar 2000 20:30:20 GMT
Hi everyone,
I'm having some ppp / (modem?) trouble with my RedHat 6.1 system.
kernel: 2.2.12-20
pppd: 2.3.10, using kpp
modem: external, USRobtics 56k faxmodem.
When I'm surfing via netscape, I get many stalls and very erratic download
throughput (i.e. one second it's 4.4k/sec the next is 320 bytes / sec).
This happens all the time, not just when downloading something big. It
makes surfing quite painful and sloooow. In general, about 1/3 of my RX
packets have errors according to ifconfig:
ppp0 Link encap:Point-to-Point Protocol
inet addr:63.225.123.122 P-t-P:63.225.123.254
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:306 errors:86 dropped:0 overruns:0 frame:86
TX packets:313 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
sometimes it's higher. Is this a high error rate for received packets, or
about normal for ppp?
Using the "record" option for pppd to record all ppp traffic I found that
all the errors are FCS (frame check sequence) errors. From pppdump on the
pppd "record" output at the end of a packet:
70 61 6e 20 73 74 79 6c 65 3d 22 63 6f 6c 6f 72 pan style="color
3a 20 23 66 66 63 63 30 30 22 3e 43 4e 45 54 3c : #ffcc00">CNET<
2f 73 70 61 6e 3e 3c 2f 66 6f 6e 74 3e 3c /span></font><
BAD FCS: (residue = 2635)
This seems to happen on larger packets.
Could this be the cause of my stalling and erratic throughput?
Why might I be getting these errors? (I don't think it's a noisy line
becasue things work much better under Win98)
According to the ppp docs:
"During the initial connection sequence, you may see one or more
messages which indicate "bad fcs". This refers to a checksum error in
a received PPP frame, and usually occurs at the start of a session
when the peer system is sending some "text" messages, such as "hello
this is the XYZ company". Messages of "bad fcs" once the link is
established and the routes have been added are not normal and indicate
transmission errors or noise on the telephone line."
I've read through lots of other posts and tried different init strings to
the modem, and numerous pppd options. I've tried: novj, asyncmap 0,
asyncmap a0000, different sizes of mtr and mru. I'm using hardware flow
control (at least I've told pppd to do so and use &K3 to my modem).
Here's the ppp connect sequence form /var/log/messages:
Mar 11 16:26:44 localhost pppd[2865]: pppd 2.3.10 started by root, uid 0
Mar 11 16:26:44 localhost kernel: ppp_ioctl: set dbg flags to 10000
Mar 11 16:26:44 localhost kernel: ppp_ioctl: set flags to 10000
Mar 11 16:26:44 localhost pppd[2865]: Using interface ppp0
Mar 11 16:26:44 localhost pppd[2865]: Connect: ppp0 <--> /dev/pts/2
Mar 11 16:26:44 localhost kernel: ppp_tty_ioctl: set xasyncmap
Mar 11 16:26:44 localhost kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Mar 11 16:26:44 localhost kernel: ppp_ioctl: set flags to 10000
Mar 11 16:26:44 localhost kernel: ppp_ioctl: set mru to 5dc
Mar 11 16:26:44 localhost kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Mar 11 16:26:47 localhost kernel: ppp_tty_ioctl: set xmit asyncmap a0000
Mar 11 16:26:47 localhost kernel: ppp_ioctl: set flags to f010003
Mar 11 16:26:47 localhost kernel: ppp_ioctl: set mru to 5dc
Mar 11 16:26:47 localhost kernel: ppp_tty_ioctl: set rcv asyncmap a0000
Mar 11 16:26:47 localhost kernel: ppp_ioctl: set flags to f010043
Mar 11 16:26:47 localhost kernel: PPP BSD Compression module registered
Mar 11 16:26:48 localhost kernel: ppp_ioctl: set flags to f01004b
Mar 11 16:26:48 localhost pppd[2865]: local IP address 63.225.123.122
Mar 11 16:26:48 localhost pppd[2865]: remote IP address 63.225.123.254
Mar 11 16:26:48 localhost modprobe: no dependency information for module:
"/dev/ttyS0"
Mar 11 16:26:48 localhost modprobe: can't locate module ppp-compress-1
Mar 11 16:26:49 localhost kernel: ppp_ioctl: set flags to f0100cb
Current /etc/ppp/options file:
lock
kdebug 1
debug
record ppp.out
crtscts
asyncmap a0000
novj
FYI, output from setserial -a /dev/modem:
/dev/modem, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000, closing_wait2: infinte
Flags: spd_vhi skip_test
Not sure if this is a modem or ppp problem. Any clues? Anyone have any
ideas what may be giving me trouble?
I'd be very grateful for any input. And willing to try more debugging
activities.
Thanks
-John
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: [EMAIL PROTECTED] (Joseph R. Erlewein)
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: Two Scsi Cards, which is which?
Date: 13 Mar 2000 20:54:28 GMT
Reply-To: [EMAIL PROTECTED]
I have 2 scsi cards in my machine.
One is differential, with the root filesystem on it, and the other is
standard scsi-II. My problem is that when I connect my zip drive, my root
drive changes from /dev/sda2 to /dev/sdb2. Then I can't boot at all.
The diff card with my root partition keeps showing up as scsi adaptor 1
and the adaptec card (normal card with zip drive) shows up as adaptor
0. If I could get the adaptors to switch positions, I'd be all set, I
think,. since the drive would then always be /dev/sda and not get bumped,
instead the other drives would be bumped.
To do this, I first tried changing PCI slots. This changed the sequence in
which they initialized at boot time, but they still show up with the same
scsi0 and 1 adaptors under linux. Next, I tried recompiling the kernel so
the adapted card is modular and the other one is static, in hopes the
static card would get priority. Neither worked.
Any other ideas how I could get linux to flip-flop the scsi adaptor IDs of
the cards?
--
=================================================================
Joseph R. Erlewein, N8OUZ -- http://www.qsl.net/n8ouz
The Houghton/Hancock area Gas Price Phenomena - Documented!!
Now Available at: http://go.to/upgas
Proud Member HCCA, Hancock Chapter
=================================================================
------------------------------
From: [EMAIL PROTECTED]
Subject: the command "rz"
Date: Mon, 13 Mar 2000 20:53:46 GMT
does anyone know a/t about the command "rz"?
i get the feeling that it's not a very used command. it's used to
transfer files from one machine to another(irrelevant of the operating
system being run on that machine)over a modem. i need info on zmodem,
on how rz is implemented between the machines, how the command is typed
in, what sort of program calls it, or a/t else.
thanks for your tiem and help.
[EMAIL PROTECTED]
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED] (Robie Basak)
Subject: Re: video player
Reply-To: [EMAIL PROTECTED]
Date: 14 Mar 2000 05:09:03 GMT
On Mon, 13 Mar 2000 16:46:43 -0500, [EMAIL PROTECTED] wrote:
>Hello
>
>I didn't find any good video player. Do you know
>a good one which plays all kind of avi, mov, mpeg ?
>
>Thanks.
>
>Sacha
xanim
--
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
