Files
2024-02-19 00:25:02 -05:00

513 lines
20 KiB
Plaintext

From: Digestifier <Linux-Activists-Request@news-digests.mit.edu>
To: Linux-Activists@news-digests.mit.edu
Reply-To: Linux-Activists@news-digests.mit.edu
Date: Sat, 25 Jan 92 13:30:11 EST
Subject: Linux-Activists Digest #15
Linux-Activists Digest #15, Volume #1 Sat, 25 Jan 92 13:30:11 EST
Contents:
man pages (Ken Block)
Re: How to boot a PC from drive B: (Bruce H. McIntosh)
Re: New floppy driver (Bob Smith)
Re: Minor device numbers. (Jeffrey Comstock)
Re: linux/mm/memory.c (Linus Benedict Torvalds)
Re: using Linux and DOS (Robert Duncan)
Re: Some Questions ... (Robert Duncan)
FAQ information (Marc CORSINI)
Re: Found problem with executable shell scripts. (Bob Smith)
TAR to Multi-volumes (Mont Pierce)
Problem with Kermit (kevin dahlhaus)
Re: ARG (hard drive problems) (Doug Dougherty)
COM3,COM4 and "out of memory" during uncompress. (Usenet)
----------------------------------------------------------------------------
From: krb@kingfish.cis.ufl.edu (Ken Block)
Subject: man pages
Date: 25 Jan 92 04:40:51 GMT
Someone posted that their were man pages. Is this true?
Could someone post ftp sites. I know of
nic.funet.fi
tsx-11.mit.edu
tupac-amaru.informatik.rwth-aachen.de
------------------------------
From: bhm@reef.cis.ufl.edu (Bruce H. McIntosh)
Subject: Re: How to boot a PC from drive B:
Date: 25 Jan 92 05:00:59 GMT
If you're into hardware hacking, you can rig a pc to boot from drive B in a
kind of painless fashion. The pc world tells its A drives from its B drives
not by means of the drive select jumpers on the drives (in fact, some drives
no longer even *have* the jumpers, which is a sore blow to a cp/m wizard like
me :-) ) but by means of that infernal twist in the floppy drive cable. Both
floppies are jumped as DS1, and the twist in the cable lets the pc do drive
select and motor on at the same time. The cable goes
controller ---- drive B ---(twist)--- drive A
What you need to do is get a 4 pole double throw switch. Pick out the lines
in the ribbon cable (lines 10-16, I think) and carefully figure out which lines
have the signals and which are grounds (you don't need to switch the grounds).
*VERY* carefully separate these lines from the ribbon and splice the switch in,
wired up as a "reversing switch", something like this:
from controller 10 -------o o----- 10 to drive B ====x==== to drive A
X
16 -------o o----- 16
12 -------o o----- 12
X
14 -------o o----- 14
(back view of 4pdt switch)
Flipping the switch has the effect of adding another twist to the cable, which
will reverse the effect of the twist between the drives, making the former B
drive to now be the A drive, and vice verse.
WARNING: This technique *should* work, although now that I think about it,
it'll blow the mind of your AT's cmos setup; you'll likely have to run the
setup utility (hopefully, it's in rom) to inform the BIOS that the drives have
been flopped. If you are the least bit unsure about doing this mod, get a
new floppy drive cable and perform the modification on *it*. That way, if my
harebrained scheme doesn't work, you can have the original cable to fall back
on.
--
=============================================================================
----- -----
| * | Bruce H. McIntosh __o Now in stereo! | * |
| O | bhm@cis.ufl.edu \<, | O |
----- ______________________()/ ()____*****-_-_-__---*\___ -----
| |
| "Worthy is the Lamb, who was slain, to receive power and |
=== wealth and wisdom and strength and glory and praise!" - Rev 5:12 ===
=============================================================================
------------------------------
From: bob@snuffy.dracut.ma.us (Bob Smith)
Subject: Re: New floppy driver
Date: 25 Jan 92 04:47:42 GMT
In article <Jan.23.18.51.40.1992.27911@dumas.rutgers.edu> hedrick@dumas.rutgers.edu (Charles Hedrick) writes:
> >I uploaded the improved floppy driver to tsx-11.mit.edu, this allows you to
> >format floppies as well as greatly speeding up reads.
>
> As I've reported privately to him, I'm still having the system hang
> whenever I try to do backups to a floppy. It hangs somewhere in the
> first 3 disks, at various places. This is becoming critical, since
> I'm about to move to a larger disk drive, but have no way (short of
> kermitting them to a Sun over a modem) to back up the old disk before
> removing it. I've been looking into the problem myself, but I don't
> know enough about the PC hardware to have much chance of fixing it.
After installing the new floppy driver I have a different sort of
problem... The machine reboots when I try to write to a floppy !?!?
The machine is an Epson NB3s laptop... I haven't had enough time
yet to see if I could figure out why, just reporting the symptoms...
--
\ Bob Smith \ mx: bob@snuffy.dracut.ma.us
\ 835 Mammoth Rd. \ uucp: ...{ulowell|wang|wybbs}!snuffy!bob
\ Dracut, MA. 01826 \ office && voice mail: +1 508 670-6712
------------------------------
From: jrc@brainiac.mn.org (Jeffrey Comstock)
Subject: Re: Minor device numbers.
Date: 24 Jan 92 22:03:44 GMT
In article <3883@umriscc.isc.umr.edu> bolsen@mcs213h.cs.umr.edu (Brian Olsen) writes:
>
>I've just installed mtools, but unfortunately at the moment I can only
>read high density floppies. From what I read in the 0.12 install
>documents, I believe I need to mknod my floppy devices differently.
>What are the minor device numbers for a 360k and a 720k drive?
>
>Any other advice would be appreciated.
>
>Thanks,
>Brian Olsen
The answer is R.T.F.M :-). This info is in docs/INSTALL-0.11 :
As with harddisk, floppies have device numbers, but this time major = 2
instead of 3. The minor number is not as easy: it's a composite that
tells which drive (A, B, C or D) and what type of drive (360kB, 1.2M,
1.44M etc). The formula is 'minor = type*4+nr', where nr is 0-3 for A-D,
and type is 2 for 1.2M disks, and 7 for 1.44M disks. There are other
types, but these should suffice for now.
Thus if you have a 1.2M A-drive, and want to call it "floppy0", you have
to tell linux so. This is done with the "mknod" command. mknod takes 4
paramters: the unix name of the device, a "b" or a "c" depending on
whether it's a Block of Character device, and the major and minor
numbers. Thus to make "floppy0" a 1.2M A-drive, you write:
mknod /dev/floppy0 b 2 8
b is for Block-device, the 2 is for floppy, and the 8 is 4*2+0, where
the 2 is 1.2M-drive and the 0 is drive A. Likewise to make a "floppy1"
device that is a 1.44M drive in B, you write:
mknod /dev/floppy1 b 2 29
where 29 = 4*7 + 1. There are a couple of standard names, for users
that are used to minix (major, minor in parentheses): /dev/PS0 is a
1.44M in A (2,28), /dev/PS1 a 1.44M in B (2,29), /dev/at0 is a 1.2M in A
(2,8), /dev/at1 is a 1.2M in B (2,9). Use mknod to make those that fit
your computer.
After you have made these special block devices, you can now read a
floppy under linux. The easiest way to import things into linux is by
writing a tar-file to a floppy with rawrite.exe, and then using:
--
Jeffrey R. Comstock
CW -. .-. ----- -..
INET uunet!jhereg.osa.com!/dev/null (EMAIL CURRENTLY BROKEN)
------------------------------
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Subject: Re: linux/mm/memory.c
Date: 25 Jan 92 10:54:53 GMT
In article <TYTSO.92Jan25002639@SOS.mit.edu> tytso@athena.mit.edu (Theodore Y. Ts'o) writes:
>
>Am I correct is suppose that a consequence of this is that every single
>dirty page of the parent has to be swapped in during a fork()? If so, I
>wonder what sort of hit you will take when something like GNU emacs
>fork()'s. (My GNU emacs on my Vax 3100 workstation is currently
>weighing in at 5.4 meg.)
Yes. This is bad, but not /that/ bad: linux only swaps /dirty/ pages: I
doubt the GNU emacs eceutable pages get dirtied, and are thus just
reloaded by the demand-loading mechanism (and nothing happens at the
fork()). But yes, when editing big files (where there are a lot of
dirty pages) will force a swap-in.
Swapping was added as a quick hack: it wasn't really meant to extend
virtual memory to really big values - more just to get gcc working on a
2M machine, and have that small extra memory when your executables don't
quite fit. More like a temporary "panic-memory": it linux swaps on a
more regular basis the algorithms should be changed to something better
as well, they are rudimentary right now..
Linus
------------------------------
From: duncan@ssdd475a.erim.org (Robert Duncan)
Subject: Re: using Linux and DOS
Date: 24 Jan 92 20:21:25 GMT
In article <1992Jan23.171127.16247@tc.cornell.edu> beers@theory.TC.Cornell.EDU (Jim Beers) writes:
> ...
> I would like to try Linux and would be willing to buy a second drive, 80
> Meg IDE drive, and use it as my second drive and dedicate it to linux.
> BUT, I would like to keep the original PC working as is.
> Is this possible? Can I start up with DOS and then switch over to linux?
This sounds very workable. You can leave your first hard drive alone if
you are willing to boot from a floppy disk when you wish to run Linux.
/dev/hd1 - /dev/hd4 are the partitions on the first hard drive, /dev/hd6 -
/dev/hd9 are on the 2nd. Make 2 or 3 partitions on the 2nd drive, one for
your main Linux area, one for a root Linux partition, and possibly one for
swap space. Then edit the boot image to use these areas and write it to a
floppy for booting. (please read the installation instructions first)
Boot without a floppy for MSDOS, with the floppy for Linux.
BTW, 80 meg of disk space should be fine, at least until somebody gets X11r5
ported...
--
p-----------------------------------------------------------------------------q
| Robert H. Duncan | |
| Environmental Research Institute of Michigan | |
| PO Box 134001 | |
| Ann Arbor, MI 48113-4001 | |
| (313)994-1200 ext.2880 | |
| Internet: duncan@erim.org | |
b-----------------------------------------------------------------------------d
------------------------------
From: duncan@ssdd475a.erim.org (Robert Duncan)
Subject: Re: Some Questions ...
Date: 24 Jan 92 20:34:09 GMT
In article <martin.696189581@menaik> martin@cs.UAlberta.CA (Tim Martin; FSO; Soil Sciences) writes:
> I got LINUX installed, and I got shoelace working, and I have a swap
> partition. GCC works, kermit works, uemacs works. Great Stuff!
> But now I have lots of "beginner" questions.
> ...
> Question #3: Patching is a new art, to me. If I do the fd patch and the lp
> patch and the login patch, can I be fairly confident the subsequent patches
> will work, and that the resultant binary will actually work? I guess this
> is a general Patch question: is patch fussy about the initial state of
> the code it is patching?
Patch is pretty smart about doing the patches, if the patches are what is
called 'context diffs' (cdiffs). For ordinary diffs, it is more difficult
to get them to work when the starting files are not as expected. Often this
means it is time to do hand editing.
The fd 'patch' is made of complete replacement and new files, you simply put
them in the right places and recompile. The lp patch uses ordinary diffs,
and at least on my system, required hand editing to work. (comment out 2
references to a non-existing include file and fix a makefile) I can't tell
you about the login patch, but I did the other two last night, and they
don't interfere with each other.
--
p-----------------------------------------------------------------------------q
| Robert H. Duncan | |
| Environmental Research Institute of Michigan | |
| PO Box 134001 | |
| Ann Arbor, MI 48113-4001 | |
| (313)994-1200 ext.2880 | |
| Internet: duncan@erim.org | |
b-----------------------------------------------------------------------------d
------------------------------
From: corsini@numero6.greco-prog.fr (Marc CORSINI)
Subject: FAQ information
Reply-To: corsini@labri.greco-prog.fr
Date: Sat, 25 Jan 1992 16:45:29 GMT
Hi Linuxers!
My site recieved alt.os.linux since yesterday and the messages are
dated from 19th Jan. :), so I follow the discussion on
alt.os.linux only via the digests (Hope this will end in 1 or 2 weeks).
I plan to post the FAQ at the end of the 1st week of each month in two
ways.
1) in Cdiff form (not before marsh 'cause the FAQ is not stable at all
and the Cdiff is twice bigger than the whole)
2) in whole form especially for new incomers.
And also the Cdiff updated, one or two weeks after each new version of
Linux is available.
Please suggest any change, rephrasing, deletions, new questions,
answers ...
Please include "FAQ" in the subject of messages sent to /me/ about
FAQ, not to the newsgroup since right now I get ONLY digests.
Please use corsini@labri.greco-prog.fr whatever will be the From part
of this message.
Thanks in advance,
Marc <corsini@labri.greco-prog.fr>
PS1:
Remind the vote in Feb. 18th for comp.os.linux
PS2:
At the moment the FAQ content looks like
I. LINUX GENERAL INFORMATION
II. LINUX USEFUL ADRESSES
III. INSTALLATION and SECURITY
IV. LINUX and DOS
V. SOME CLASSICAL PROBLEMS
VI. INSTALLATION HINTS
VII. FEATURES
------------------------------
From: bob@snuffy.dracut.ma.us (Bob Smith)
Subject: Re: Found problem with executable shell scripts.
Date: 25 Jan 92 15:07:59 GMT
In article <1992Jan25.050248.16436@cseg03.uark.edu> dws@cseg03.uark.edu (David W. Summers) writes:
>
> I found the work-around for problem that I was having. As you might recall,
> I tried to execute a shell script 'configure' and it had execute permissions
> and had:
>
> #!/bin/sh
>
> as the first line (a lot of you asked me to make sure about this).
>
> Well, BASH said 'file or directory not found' or something like that.
>
> Well, I found out that if I changed it to:
>
> #!/usr/bin/sh
>
> then it works fine! What seems to be happening is that BASH is NOT following
> symbolic links! I have /bin -> /usr/bin, with 'sh' in /usr/bin. With
> everything else I've tested, it follows the symbolic links, but apparently not
> on the above. Any ideas? Should I just grab the current version of BASH
> and re-compile? Is this a "feature" or a "bug"?
>
Bug or feature? I'm not sure, but the kind of behavior you're refering
to I can emulate with the Bourne shell in SunOS 3.5 ... So it must be
kinda normal ??!!?? :-)
--
\ Bob Smith \ mx: bob@snuffy.dracut.ma.us
\ 835 Mammoth Rd. \ uucp: ...{ulowell|wang|wybbs}!snuffy!bob
\ Dracut, MA. 01826 \ office && voice mail: +1 508 670-6712
------------------------------
From: mont@netcom.netcom.com (Mont Pierce)
Subject: TAR to Multi-volumes
Reply-To: mont@netcom.netcom.com (Mont Pierce)
Date: Sat, 25 Jan 1992 17:23:16 GMT
I use the tar that came with linux and have no problems backing up
to multiple volumes. You do have to specify the right options:
tar -ML 1440 -cvf /dev/fd0 [filenames]
-M = multiple volumes
-L = volume length is 1440 blocks
Type " tar + help" to get a full list of options. The "-b" option comment
is wrong though. It says "-b n block size is n*512 (defualt n=20)",
default n is really 2 not 20.
Only problem I've noticed is that if I use the "-z" option it doesn't
seem to save any data on the diskette. I've tested this by doing the
following:
tar -ML 1440 -zcvf tarfile [filenames]
When the tar command prompts for the next diskette I switched to another
window to look at the size of the "tarfile". The tar file was smaller
then 1474560 bytes. This indicates that tar reads the same amount of data
whether or not compressing the output. So using compress or not to do
backups to diskette doesn't matter. I had hoped that it would stuff more
data onto each diskette and thus use less diskettes. Oh well.
Mont@netcom.com
------------------------------
From: dahlhaus@news.cis.ohio-state.edu (kevin dahlhaus)
Subject: Problem with Kermit
Date: Sat, 25 Jan 1992 17:35:33 GMT
Since others have gotten kermit working, this is a problem
that probably stems from my lack of unix experience, but..
Linux returns the error: "Warning, Read access to lock directory denied."
When I try "set line /dev/tty65" to set the serial port. Any ideas
as to what I am doing wrong?
Thanks very much,
=======================================================================
Kevin P. Dahlhausen dahlhaus@cis.ohio-state.edu
TIS ap096@po.cwru.edu
------------------------------
From: valley@gsbsun.uchicago.edu (Doug Dougherty)
Crossposted-To: comp.binaries.ibm.pc.d
Subject: Re: ARG (hard drive problems)
Date: 25 Jan 92 17:59:26 GMT
mgjones@miavx1.acs.muohio.edu (Mike 'Felix' Jones) writes:
>BootAny is probably residing in the first 2 sectors of your harddrive
>where the partition information is. If you want to get rid of
>BootAny for good, and you don't need the information currently on the
>drive, you should low-level format the drive. That should remove any
>program anywhere on the drive. (see your drive manual or the supplier
>on how to low-level format it, or pick up one of the programs floating
>around that will do it for you).
As an aside, I often wonder what people with IDE drives do in these
situations. The ability to low-level format a drive is often a boon,
when you really want to start over from scratch. That's why my motto is
"MFM forever!".
But seriously, folks, there must be some kind of util that does
everything except the actual physical low-level formatting, for IDE
(& perhaps other non-formattable) drives.
--
- And many dragons - had felt the might - of the smite -
- of the righteous Sir Greenbaum. -
------------------------------
From: usenet@kth.se (Usenet)
Subject: COM3,COM4 and "out of memory" during uncompress.
Date: 25 Jan 92 17:51:49 GMT
I now got Linux running on my 386SX computer with 4 Mbyte memory, it seems
to work just fine.
However I have a couple of questions:
I have 3 serial ports on my computer (internal modem, mouse, and to another
computer) which I use when I am running MS-DOS on it (bad habit :-).
I dont't want to reconfiguring the hardware every time I want to use modem
etc in Linux. Does the driver supports COM3 and COM4 ? Or has one to change
the kernel ?
When I tried to uncompress a 500k file a got "out of memory" (or
something like that) message. is this normal ? I have no swap space.
Mattis Andersson
mattis@elixir.lne.kth.se
------------------------------
** FOR YOUR REFERENCE **
The service addresse, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: Linux-Activists-Request@NEWS-DIGESTS.MIT.EDU
You can send mail to the entire list (and alt.os.linux) via:
Internet: Linux-Activsts@NEWS-DIGESTS.MIT.EDU
Linux may be obtained via one of these FTP sites:
nic.funet.fi pub/OS/Linux
tsx-11.mit.edu pub/linux
tupac-amaru.informatik.rwth-aachen.de pub/msdos/replace
The current version of Linux is 0.12, released on Jan 14, 1992
End of Linux-Activsts Digest
******************************