add directory docs
This commit is contained in:
gohigh
70
docs/kgb/1st_mascot.txt
Normal file
70
docs/kgb/1st_mascot.txt
Normal file
@@ -0,0 +1,70 @@
|
||||
From: barrett@aminet.uucp (Keith Barrett)
|
||||
Subject: Linux T-Shirts: Mail me ideas
|
||||
Date: 24 Mar 93 13:52:45 GMT
|
||||
Reply-To: barrett%aminet.uucp@nuconvex.com
|
||||
|
||||
Linux: Because sources are fun
|
||||
Linux: Because a PC is a terrible thing to waste
|
||||
Linux: It's not just an OS, it's an adventure
|
||||
Linux: Why ask why?
|
||||
Linux: Because the 3267th U*IX system HAS to be good
|
||||
Linux: 2 user license? get out of my face.
|
||||
Linux: All this and sources too.
|
||||
Linux: Free? Sources? Posix? Pinch me, I'm dreaming.
|
||||
Linux: Now you can format a floppy AND do something else.
|
||||
Linux: You don't understand, do you?
|
||||
|
||||
I have a license for my car and dog, I DIDN'T want one for my
|
||||
*IX system.
|
||||
|
||||
Linux: Comercial software gone horribly wrong
|
||||
|
||||
|
||||
Top 11 reasons why I use Linux:
|
||||
|
||||
11. Can't claim it's "new and improved" because it hasn't been
|
||||
released yet.
|
||||
|
||||
10. Having source code helps justify getting larger disk drives.
|
||||
|
||||
9. Now that 3rd user can log into my system? Pinch me - I
|
||||
must be dreaming.
|
||||
|
||||
8. Sounds like a Peanuts character
|
||||
|
||||
7. A new release every 2 weeks really impresses the babes.
|
||||
(well; hacker babes anyway).
|
||||
|
||||
6. Now I can spend my money on food instead - or maybe a tape
|
||||
drive.
|
||||
|
||||
5. Who are you gonna trust? USL/Novel, SCO, OSF, or 1000+ socially
|
||||
impaired strangers scattered around the globe communicating
|
||||
solely by electronic mail?
|
||||
|
||||
4. Another excuse for a cool t-shirt!
|
||||
|
||||
3. I sleep better at nights knowing that the Amiga port won't
|
||||
strand millions of users who already have enough reasons
|
||||
to maime everyone at CBM.
|
||||
|
||||
2. Linux? I thought you said Lexus.
|
||||
|
||||
1. Sources? Free? - 'nuff said.
|
||||
|
||||
|
||||
|
||||
How about the Linux foundation invent an animal logo also?
|
||||
|
||||
|
||||
--
|
||||
-kgb
|
||||
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
UUCP: nuconvex.com!aminet!barrett Keep circulating the tapes - MST3k
|
||||
DDN: barrett%aminet.uucp@decwrl.dec.com // My life is my own - the prisoner
|
||||
Alternate: barrett@pamsrc.enet.dec.com \X/ Amiga 3000UX - The Next Generation
|
||||
================================================================================
|
||||
|
||||
|
||||
|
||||
79
docs/kgb/1st_posting.txt
Normal file
79
docs/kgb/1st_posting.txt
Normal file
@@ -0,0 +1,79 @@
|
||||
From: barrett@pamsrc.enet.dec.com (Keith Barrett)
|
||||
Subject: SCSI tape drive help
|
||||
Date: 22 Feb 93 21:19:09 GMT
|
||||
Reply-To: barrett@pamsrc.enet.dec.com
|
||||
|
||||
|
||||
I scanned this newsgroup, and while I found a few people asking the
|
||||
same questions I'm about to ask, there were no real answers (probably
|
||||
because most asked for email responses).
|
||||
|
||||
I want to get a SCSI tape drive (QIC-150 or QIC-250) that supports
|
||||
reading and writing 150 meg tapes. I will be exchanging between Linux
|
||||
and other UNIX workstations (the tapes are the 6150, 6250 kind, approximate
|
||||
dimentions are 4x6x1). It would be real nice if the same drive supported 250
|
||||
meg tapes also.
|
||||
|
||||
Cost must be <= about $800. ARCHIVE VIPERS tend to be very expensive.
|
||||
I've seen WANGTEK mentioned. Could anyone offer information, advice,
|
||||
suggestions, etc?
|
||||
|
||||
Also, I already have a CIPHER 150 meg SCSI tape drive. Could I get this
|
||||
to work with LINUX? DOS? If so, how?
|
||||
|
||||
I'd also like to ensure (as best as possible) that the drive also
|
||||
works with Windows-NT and DOS.
|
||||
|
||||
|
||||
Please email me at the address below. If I get enough information, I'll
|
||||
post a summary.
|
||||
|
||||
|
||||
I think we need a TAPE DRIVE FAQ. :-)
|
||||
|
||||
Thanks!!!
|
||||
|
||||
|
||||
Keith Barrett
|
||||
barrett@pamsrc.enet.dec.com
|
||||
|
||||
|
||||
P.S. The drive will be used on a modern ADAPTEC controller
|
||||
|
||||
|
||||
------------------------------
|
||||
|
||||
From: Theodore Ts'o <tytso@athena.mit.edu>
|
||||
Subject: Re: SCSI tape drive help
|
||||
Date: 23 Feb 1993 11:56:51 -0500
|
||||
Reply-To: tytso@athena.mit.edu
|
||||
|
||||
From: barrett@pamsrc.enet.dec.com (Keith Barrett)
|
||||
Date: 22 Feb 93 21:19:09 GMT
|
||||
|
||||
I want to get a SCSI tape drive (QIC-150 or QIC-250) that supports
|
||||
reading and writing 150 meg tapes. I will be exchanging between Linux
|
||||
and other UNIX workstations (the tapes are the 6150, 6250 kind, approximate
|
||||
dimentions are 4x6x1). It would be real nice if the same drive supported 250
|
||||
meg tapes also.
|
||||
|
||||
A drive which support QIC-150 tapes will also support the 6250 tapes ---
|
||||
the format is the same, just the tape is longer.
|
||||
|
||||
I've found refurbished, or new-but-taken-out-of-PS/2 Tandburg 3660 tape
|
||||
drives at PC computer trade shows for $150-$175. They're not "new", but
|
||||
most of them either haven't been used much if at all. The one catch is
|
||||
that your warranty is whatever the salvage dealer is willing to give
|
||||
you. I got a 60 day warranty with mine. It worked perfectly the first
|
||||
time I hooked it up to my Adaptec 1542B. (Ironic, isn't it? The
|
||||
controller ended up costing me more than the tape drive! :-)
|
||||
|
||||
These PC computer trade shows run approximately once a month in the
|
||||
Boston area, and there are usually several salvage dealers that show up
|
||||
at these shows. If you're in the Boston area, and you want to find out
|
||||
when the next one of these shows are; let me know. The next time I get
|
||||
a postcard from these folks, I'll send you email.....
|
||||
|
||||
- Ted
|
||||
|
||||
|
||||
114
docs/kgb/1st_time.txt
Normal file
114
docs/kgb/1st_time.txt
Normal file
@@ -0,0 +1,114 @@
|
||||
From: barrett@aminet.uucp (Keith Barrett)
|
||||
Subject: TAMU problems
|
||||
Date: 27 Mar 93 02:17:49 GMT
|
||||
Reply-To: barrett%aminet.uucp@nuconvex.com
|
||||
|
||||
|
||||
OK, I Finally got around to trying out Linux (TAMU).
|
||||
First, let me say that Linux looks GREAT! Can't believe it's free. Easy
|
||||
to use (well, as easy as any unix is). I'm excited by the possibilities.
|
||||
I LOVE the fact I can mount my msdos partition and xfer files, and X.
|
||||
Nice work!
|
||||
|
||||
However, I have MANY problems, some of them major. I realize I'm
|
||||
behind in release version, and I will try to upgrade asap, but I'd
|
||||
like to know if anyone has seen these, or if there are solutions.
|
||||
Some of these problems are bigtime show stoppers for me, as I require
|
||||
UUCP and bi-modem communications to work.
|
||||
|
||||
|
||||
Minor problems first --
|
||||
|
||||
1. Is there ANY way to change this tiny font being displayed? It's much
|
||||
too small.
|
||||
|
||||
|
||||
2. What's this "MINIX-fs magic match failure" message that appears on
|
||||
every startup? The whole system seems fine, including all 3 partitions
|
||||
and files systems. efsck doesn't clear it either. I suspect it's some
|
||||
dumb script trying to do something and getting a partition type wrong.
|
||||
I get a similar error if I use fsck instead of efsck.
|
||||
|
||||
|
||||
3. Are there any non-Xwindows programs to enable/disable audio CD's?
|
||||
|
||||
|
||||
4. No BRU. I like tar, but I wish I had both. I encounter systems that
|
||||
do have BRU and not TAR.
|
||||
|
||||
|
||||
5. To keep the system reliable (especially on a pwer failure reboot),
|
||||
I included an execution of efsck in my startup. Is there a way for
|
||||
rc.local to "determine" if this is needed rather than always
|
||||
doing it?
|
||||
|
||||
|
||||
6. I can't get XDM to work. It's flaky, and the few times I actually got
|
||||
the login screen to come up, it wouldn't take input.
|
||||
|
||||
|
||||
7. It took me a while to figure out that uucp and news didn't come with
|
||||
sample files for everything that's needed. "Dialers", "newsgroups",
|
||||
and a few others were missing. Also, there was no sample entry in
|
||||
Devices for an ACU.
|
||||
|
||||
I eventually resolved these.
|
||||
|
||||
|
||||
|
||||
OK, now on to the major things I REALLY could use help with. Right now,
|
||||
these stop me from using the system at all.
|
||||
|
||||
|
||||
8. I can't get mail to function correctly on the local system. I can
|
||||
send mail to myself, but when I send to a user that has forwarding
|
||||
on (in their mail file), the letter seems to vanish. If I set root
|
||||
up as forwarded and send mai lto it, the end-user (and root) can't
|
||||
receive it. When I send to an external site -- same thing.
|
||||
|
||||
I can't locate it anyway (files, queues, etc.), and can't find a
|
||||
log record of it's failure.
|
||||
|
||||
|
||||
9. mail is getting a dummy domain suffix from somewhere - I can't
|
||||
figure it out. It's something like "myorg.mydomain"
|
||||
|
||||
|
||||
10 If I set getty up on the serial port, and attempt to use kermit to
|
||||
make an outgoing interative connection, getty is still in the way
|
||||
and modem responses cause an inifinate "login" attempt loop.
|
||||
|
||||
Trying uugetty did the same thing (and curiously, uugetty doesn't
|
||||
support standard switches).
|
||||
|
||||
What do I do about this? How does one set up a bi-directional modem
|
||||
port? I though uugetty would be the way, but it doesn't even know
|
||||
"-r".
|
||||
|
||||
|
||||
11. There doesn't seem to be any flavor of a "mailsurr" on the system.
|
||||
Why? How does one set up a default and "SMARTER HOST" addressing?
|
||||
|
||||
|
||||
12. uucico and uuxqt core dump on me. I can't get them to run at all.
|
||||
I don't know what to do about this. Anyone else getting this?
|
||||
|
||||
|
||||
Is there anyway to still use VC's while X windows is up? It seems to
|
||||
be an exclusive choice.
|
||||
|
||||
|
||||
|
||||
Thanks! I hope there are answers.
|
||||
|
||||
|
||||
|
||||
Keith Barrett
|
||||
--
|
||||
-kgb
|
||||
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
UUCP: nuconvex.com!aminet!barrett Keep circulating the tapes - MST3k
|
||||
DDN: barrett%aminet.uucp@decwrl.dec.com // My life is my own - the prisoner
|
||||
Alternate: barrett@pamsrc.enet.dec.com \X/ Amiga 3000UX - The Next Generation
|
||||
==============================================================================
|
||||
262
docs/kgb/A20 - a pain from the past.htm
Normal file
262
docs/kgb/A20 - a pain from the past.htm
Normal file
@@ -0,0 +1,262 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<!-- saved from url=(0045)http://www.win.tue.nl/~aeb/linux/kbd/A20.html -->
|
||||
<HTML><HEAD><TITLE>A20 - a pain from the past</TITLE>
|
||||
<META http-equiv=Content-Type content="text/html; charset=gb2312">
|
||||
<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
|
||||
<BODY>
|
||||
<H1>A20 - a pain from the past</H1>Everybody hates the CapsLock key, but
|
||||
keyboard manufacturers continue producing keyboards with CapsLock - it could be
|
||||
that someone wants it.
|
||||
<P>With A20 it is similar but worse. Really nobody wants it, but it continues to
|
||||
haunt us.
|
||||
<P>
|
||||
<H2>History</H2>The 8088 in the original PC had only 20 address lines, good for
|
||||
1 MB. The maximum address FFFF:FFFF addresses 0x10ffef, and this would silently
|
||||
wrap to 0x0ffef. When the 286 (with 24 address lines) was introduced, it had a
|
||||
real mode that was intended to be 100% compatible with the 8088. However, it
|
||||
failed to do this address truncation (a bug), and people found that there
|
||||
existed programs that actually depended on this truncation. Trying to achieve
|
||||
perfect compatibility, IBM invented a switch to enable/disable the 0x100000
|
||||
address bit. Since the 8042 keyboard controller happened to have a spare pin,
|
||||
that was used to control the AND gate that disables this address bit. The signal
|
||||
is called A20, and if it is zero, bit 20 of all addresses is cleared.
|
||||
<H2>Present</H2>Why do we have to worry about this nonsense? Because by default
|
||||
the A20 address line is disabled at boot time, so the operating system has to
|
||||
find out how to enable it, and that may be nontrivial since the details depend
|
||||
on the chipset used.
|
||||
<H2>Classical A20 control, via the keyboard controller</H2>The output port of
|
||||
the keyboard controller has a number of functions. <BR>Bit 0 is used to reset
|
||||
the CPU (go to real mode) - a reset happens when bit 0 is 0. <BR>Bit 1 is used
|
||||
to control A20 - it is enabled when bit 1 is 1, disabled when bit 1 is 0.
|
||||
<BR>One sets the output port of the keyboard controller by first writing 0xd1 to
|
||||
port 0x64, and the the desired value of the output port to port 0x60. One
|
||||
usually sees the values 0xdd and 0xdf used to disable/enable A20. Thus: <PRE> call empty_8042
|
||||
mov al,#0xd1 ! command write
|
||||
out #0x64,al
|
||||
call empty_8042
|
||||
mov al,#0xdf ! A20 on
|
||||
out #0x60,al
|
||||
call empty_8042
|
||||
</PRE>where <TT>empty_8042</TT> has to wait for the kbd to finish handling
|
||||
input, say <PRE>empty_8042:
|
||||
call delay
|
||||
in al,#0x64
|
||||
test al,#2
|
||||
jnz empty_8042
|
||||
ret
|
||||
</PRE>
|
||||
<H3>Variation</H3>The HP Vectra accepts a shortcut, where writing 0xdd or 0xdf
|
||||
to port 0x64 will disable/enable A20. <PRE>! For the HP Vectra
|
||||
call empty_8042
|
||||
jnz err
|
||||
mov al,#0xdf
|
||||
out #0x64,al
|
||||
call empty_8042
|
||||
jnz err
|
||||
mov al,#0xdf ! Do it again
|
||||
out #0x64,al
|
||||
call empty_8042
|
||||
jnz err
|
||||
! Success
|
||||
</PRE>(HIMEM.SYS in DOS 5.0 incorrectly identifies some computers as HP Vectra -
|
||||
this may cause a hang at boot. Fixed in DOS5.0a.)
|
||||
<H2>A20 control via System Control Port A</H2>Some operating systems use the
|
||||
switching off and on of A20 as part of the standard procedure to switch between
|
||||
real (16-bit) and protected mode. Since the keyboard microcontroller is slow, it
|
||||
was desirable to avoid it, and a Fast Gate A20 Option was introduced, where I/O
|
||||
port 0x92 (System Control Port A) is used to handle A20, circumventing the
|
||||
keyboard controller.
|
||||
<P>Thus, MCA, EISA and other systems can also control A20 via port 0x92. This
|
||||
port has a number of functions, and the details depend on the manufacturer. Bits
|
||||
0,1,3,6,7 seem to have the same meaning everywhere this port is implemented.
|
||||
<BR>Bit 0 (w): writing 1 to this bit causes a fast reset (used to switch back to
|
||||
real mode; for MCA this took 13.4 ms). <BR>Bit 1 (rw): 0: disable A20, 1: enable
|
||||
A20. <BR>Bit 3 (rw?): 0/1: power-on password bytes (stored in CMOS bytes
|
||||
0x38-0x3f or 0x36-0x3f) accessible/inaccessible. This bit can be written to only
|
||||
when it is 0. <BR>Bits 6-7 (rw): 00: hard disk activity LED off, 01,10,11: hard
|
||||
disk activity LED on. <BR>Bits 2,4,5 are unused or have varying meanings. (On
|
||||
MCA bit 4 (r): 1: watchdog timeout occurred.)
|
||||
<P>
|
||||
<H3>Using 0x92 may be necessary</H3>Sometimes (especially on embedded systems)
|
||||
no keyboard controller is present, and it may be necessary to use 0x92. Often
|
||||
however, the chip will catch accesses to ports 0x64 and 0x60 and simulate the
|
||||
expected behaviour, also when no keyboard controller is present. Sometimes, this
|
||||
snooping behaviour must be enabled first.
|
||||
<H3>Using 0x92 may be dangerous</H3>Gianluca Anzolin
|
||||
<G.ANZOLIN@INWIND.IT>reports: I have an Olivetti M4 (P166) with TRIDENT 9660
|
||||
video card integrated on the mainboard. Linux boots well, but after LILO has
|
||||
loaded the kernel, the screen becomes black and remains black ever after.
|
||||
Removing <PRE> inb $0x92, %al #
|
||||
orb $02, %al # "fast A20" version
|
||||
outb %al, $0x92 # some chips have only this
|
||||
</PRE>from <TT>setup.S</TT> solved this. Apparently on his machine writing to
|
||||
some of these bits is dangerous and does something to the on-board video card
|
||||
(disable it? lspci shows it only when 0x92 is not touched). Similar things are
|
||||
reported by others:
|
||||
<BLOCKQUOTE><I>I am trying to install Linux on an old Olivetti pc M4 Modulo
|
||||
P75 but I am quickly stopped. I always got the same display problem very soon
|
||||
during the installation.The display is not updated anymore. The embedded
|
||||
display adapter is a "Trident 9xxx PCI".</I> </BLOCKQUOTE>and
|
||||
<BLOCKQUOTE><I>I have a strange problem with an old Olivetti M4 (pentium 75)
|
||||
machine. I buy for a very cheap price 5 of these, but when I boot the machine
|
||||
the screen goes blank. The (embedded on MoBo) video chip is a Trident
|
||||
TGUI9780.</I> </BLOCKQUOTE>
|
||||
<P>Petr Vandrovec <VANDROVE@VC.CVUT.CZ>suggests to do the write only when it is
|
||||
really necessary: <PRE> inb $0x92, %al #
|
||||
+ testb $02, %al
|
||||
+ jnz no92
|
||||
orb $02, %al # "fast A20" version
|
||||
outb %al, $0x92 # some chips have only this
|
||||
+no92:
|
||||
</PRE>Since bit 0 sometimes is write-only, and writing a one there causes a
|
||||
reset, it must be a good idea to add the line <PRE> andb $0xfe, %al
|
||||
</PRE>before the <TT>outb</TT>.
|
||||
<H3>Using only 0x92 may be dangerous</H3>Kai Germaschewski reports that he gets
|
||||
a spontaneous kernel reboot (on a Sony PCG-Z600NE) after suspend/resume when A20
|
||||
was enabled using 0x92 but not via the keyboard controller. Apparently state set
|
||||
via keyboard controller is correctly saved and restored, but state set via 0x92
|
||||
is not.
|
||||
<H3>Port 0x92 may have to be enabled</H3>Various SMSC super I/O chips will
|
||||
emulate the keyboard controller, but emulate port 0x92 only when that has been
|
||||
enabled.
|
||||
<H3>CMOS indicating the presence of a Fast A20 Gate</H3>Depending on the BIOS,
|
||||
the possibility of using a fast A20 switch may be visible in the CMOS. For
|
||||
example, some AMI BIOSes have in CMOS location 0x2d a byte with contents <PRE> System Operational Flags
|
||||
Bit 7 = 1: Weitek math coprocessor present
|
||||
Bit 6 = 1: Floppy drive seek at boot disabled
|
||||
Bit 5 = 1: System boot sequence A:,C: (otherwise C:,A:)
|
||||
Bit 4 = 1: System boot CPU speed high
|
||||
Bit 3 = 1: External cache enabled
|
||||
Bit 2 = 1: Internal cache enabled
|
||||
Bit 1 = 1: Fast gate A20 operation enabled
|
||||
Bit 0 = 1: Turbo switch function enabled
|
||||
</PRE>Of course, this does not help at all.
|
||||
<H3>FreeBSD</H3>FreeBSD does <PRE>/*
|
||||
* Gate A20 for high memory
|
||||
*/
|
||||
void
|
||||
gateA20(void)
|
||||
{
|
||||
#ifdef PC98
|
||||
outb(0xf2, 0x00);
|
||||
outb(0xf6, 0x02);
|
||||
#else
|
||||
#ifdef IBM_L40
|
||||
outb(0x92, 0x2);
|
||||
#else IBM_L40
|
||||
while (inb(K_STATUS) & K_IBUF_FUL);
|
||||
while (inb(K_STATUS) & K_OBUF_FUL)
|
||||
(void)inb(K_RDWR);
|
||||
|
||||
outb(K_CMD, KC_CMD_WOUT);
|
||||
while (inb(K_STATUS) & K_IBUF_FUL);
|
||||
outb(K_RDWR, KB_A20);
|
||||
while (inb(K_STATUS) & K_IBUF_FUL);
|
||||
#endif IBM_L40
|
||||
#endif
|
||||
}
|
||||
</PRE>that is, uses 0x92 only for a IBM_L40 (whatever that may be). The FreeBSD
|
||||
handbook describes PC98 as "an alternative development branch of PC hardware,
|
||||
popular in Japan" and "the NEC PC98 platform".
|
||||
<P>
|
||||
<H3>Minix and HIMEM.ASM</H3><A
|
||||
href="http://www.win.tue.nl/~aeb/linux/kbd/xfix-286mode2">Here</A> is a patch
|
||||
fragment for minix. It contains the interesting part <PRE>! movb al, #0xff ! Pulse output port
|
||||
! outb 0x64
|
||||
! call kb_wait ! Wait for the A20 line to settle down
|
||||
</PRE>from some old HIMEM.ASM source (that one still can find on the net). I
|
||||
have seen no other places where command 0xff is described as doing something
|
||||
useful.
|
||||
<H2>Access of 0xee</H2>On some systems reading ioport 0xee enables A20, and
|
||||
writing it disables A20. (Or, sometimes, this action only occurs when ioport
|
||||
0xee is enabled.) And similar things hold for ioport 0xef and reset (a write
|
||||
causes a reset).
|
||||
<P>The i386SL/i486SL documents say <PRE>The following ports are visible only when enabled,
|
||||
Any writes to these ports cause the action named.
|
||||
Name of Register Address Default Value Where placed Size
|
||||
FAST CPU RESET EFh N/A 82360SL 8
|
||||
FAST A20 GATE EEh N/A 82360SL 8
|
||||
</PRE>
|
||||
<P>The AMD Elan SC400 docs (<A
|
||||
href="http://www.amd.com/products/epd/processors/4.32bitcont/13.lan4xxfam/22.lansc400/a21032/21032.pdf">21032.pdf</A>)
|
||||
say:
|
||||
<BLOCKQUOTE><I>Register EEh can be used to cause the same type of masking of
|
||||
the CPU A20 signal that was historically performed by an external SCP (System
|
||||
Control Processor) in a PC/AT Compatible system, but much faster. This control
|
||||
defaults to not forcing the propagation of A20: Dummy Read = Returns FFh, and
|
||||
forces the A20 signal to propagate. Dummy Write = Deasserts the forcing of the
|
||||
propagation of the A20 signal via this particular control, data value written
|
||||
is N/A. For software compatibility and other reasons, there are several
|
||||
sources of GateA20 control. These controls are effectively ORed together with
|
||||
the output of the OR gate driving the Enhanced Am486 microprocessor A20M pin.
|
||||
Therefore, A20 will propagate if ANY of the independent sources are forcing
|
||||
A20 to propagate.</I> </BLOCKQUOTE>
|
||||
<H2>Other ports</H2>It is rumoured that systems exist that use bit 2 of ioport
|
||||
0x65 or bit 0 of ioport 0x1f8 for A20 control (0: disabled, 1: enabled). Don't
|
||||
know what systems that might be. The AT&T 6300+ needs a write of 0x90 to
|
||||
port 0x3f20 to enable (and a write of 0x0 to disable) A20.
|
||||
<H2>Disabling A20</H2>It may be necessary to do both the keyboard controller
|
||||
write and the 0x92 write (and the 0xee write) to disable A20.
|
||||
<H2>A20 and reset</H2>If (in protected mode) A20 is disabled, the odd megabytes
|
||||
are inaccessible. After a reset, execution begins at top-of-memory: 0xfffff0 on
|
||||
the 286 and 0xfffffff0 on 386 and later. With disabled A20 this becomes 0xeffff0
|
||||
or 0xffeffff0 and the machine will probably crash, having no memory mapped
|
||||
there.
|
||||
<H2>A20 and cache</H2>One tests A20 by writing something to an address with bit
|
||||
0x100000 set, and seeing whether the corresponding location in low memory
|
||||
changes. However, this plan may be thwarted by the cache that remembers the old
|
||||
value and doesn't know about A20.
|
||||
<P><A
|
||||
href="http://qdn.qnx.com/support/docs/neutrino_qrp/building/startup.html">Neutrino</A>
|
||||
describes the following function <TT>x86_enable_a20()</TT>:
|
||||
<BLOCKQUOTE><I>Enable address line A20, which is often disabled on many PCs on
|
||||
reset. It first checks if address line A20 is enabled and if so returns 0.
|
||||
Otherwise, it sets bit 0x02 in port 0x92, which is used by many systems as a
|
||||
fast A20 enable. It again checks to see if A20 is enabled and if so returns 0.
|
||||
Otherwise, it uses the keyboard microcontroller to enable A20 as defined by
|
||||
the old PC/AT standard. It again checks to see if A20 is enabled and if so
|
||||
returns 0. Otherwise, it returns -1. If cpu is a 486 or greater, it issues a
|
||||
<TT>wbinvd</TT> opcode to invalidate the cache when doing a read/write test of
|
||||
memory to see if A20 is enabled. In the rare case where setting bit 0x02 in
|
||||
port 0x92 may affect other hardware, you can skip this by setting
|
||||
<TT>only_keyboard</TT> to 1. In this case, it will attempt to use only the
|
||||
keyboard microcontroller.</I> </BLOCKQUOTE>hpa comments:
|
||||
<BLOCKQUOTE><I>As far as I know the only machines which have the cache problem
|
||||
are i386 boxen, but the i386 doesn't have WBINVD. The i486 has a pin on the
|
||||
CPU for A20, which takes effect inside the L1 cache, and so it shouldn't have
|
||||
any A20 cache issues.</I> </BLOCKQUOTE>
|
||||
<P>Jens Maurer <A
|
||||
href="http://www.cck.uni-kl.de/misc/tecra710/linux-problem">reported</A> in 1996
|
||||
on boot problems with a bzImage kernel:
|
||||
<BLOCKQUOTE><I>On the Toshiba laptop, the first two bytes at 0x100000 are
|
||||
incorrect and identical to those from address 0x000000 (which was an alias for
|
||||
0x100000 before the A20 gate enable). At a second read from 0x100000
|
||||
immediately afterwards, the correct memory content is returned. Asus P55TP5XE
|
||||
boards (Triton I chipset) show quite the same problem, but there, only the
|
||||
first byte is incorrect and booting bzImage kernels works fine. To me, this
|
||||
looks like some buffer or cache coherency problem although I think that caches
|
||||
are organized in at least 16 byte cache lines. ... This exact same problem
|
||||
reportedly also exists on Fujitsu 555T (report from Andrea Caltroni) laptop
|
||||
and Compudyne Pentium 60 (report from David Kerr) desktop computers.</I>
|
||||
</BLOCKQUOTE>He gives a patch, and adds "<I>Unfortunately, Philip Hands reports
|
||||
that the above patch makes some people with other non-laptop computers unable to
|
||||
boot.</I>"
|
||||
<P>Using zImage instead of bzImage avoids the problem (since zImage is not
|
||||
loaded high). Debian has distributed special Tecra boot floppies for a while.
|
||||
Later it was found out that these laptops just have an incredibly slow keyboard
|
||||
controller and that all is fine with a larger timeout.
|
||||
<H2>BIOS</H2>If it is difficult, maybe impossible, to write a routine that will
|
||||
enable A20 on all PCs, one might ask the BIOS to do so. Many recent BIOS
|
||||
versions implement INT15 AX=240x functions, as follows: <PRE>INT 15 AX=2400 disable A20
|
||||
INT 15 AX=2401 enable A20
|
||||
INT 15 AX=2402 query status A20
|
||||
INT 15 AX=2403 query A20 support (kbd or port 92)
|
||||
|
||||
Return:
|
||||
If successful: CF clear, AH = 00h
|
||||
On error: CF set, AH = status
|
||||
Status: 01h keyboard controller is in secure mode
|
||||
86h function not supported
|
||||
For AX=2402 the status (0: disabled, 1: enabled) is returned in AL
|
||||
For AX=2403 the status (bit 0: kbd, bit 1: port 92) is returned in BX
|
||||
</PRE></BODY></HTML>
|
||||
0
docs/kgb/RedHat_Intro.txt
Normal file
0
docs/kgb/RedHat_Intro.txt
Normal file
40805
docs/kgb/barrett2.txt
Normal file
40805
docs/kgb/barrett2.txt
Normal file
File diff suppressed because it is too large
Load Diff
57
docs/kgb/barrett3.txt
Normal file
57
docs/kgb/barrett3.txt
Normal file
@@ -0,0 +1,57 @@
|
||||
|
||||
From: barrett@pamsrc.enet.dec.com (Keith Barrett)
|
||||
Subject: Re: RFD: Bug Forms for Linux
|
||||
Reply-To: barrett@pamsrc.enet.dec.com
|
||||
Date: Tue, 27 Apr 1993 14:43:42 GMT
|
||||
|
||||
|
||||
I suggest creating a newsgroup dedicated to only bug reporting
|
||||
(comp.os.linux.bugs}. This was highly successful in the alt.sys.amiga.uucp
|
||||
groups. The advantages are obvious
|
||||
|
||||
Bugs and soluations are seen by everyone who needs to.
|
||||
|
||||
Newsgroup extraction can be automated; news posts could have a specific
|
||||
format.
|
||||
|
||||
Traffic is moved away from the main newsgroup
|
||||
|
||||
The newsgroup could be moderated if desired.
|
||||
|
||||
Inappropriate items, or items that are really FAQs are still visible.
|
||||
|
||||
--
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
Keep Circulating the tapes - MST3k. | barrett@pamsrc.enet.dec.com
|
||||
Linux = Likable Unix :-) |
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
------------------------------
|
||||
|
||||
From: sct@dcs.ed.ac.uk (Stephen Tweedie)
|
||||
Subject: Re: RFD: Bug Forms for Linux [comp.os.linux.bugs, anybody?]
|
||||
Date: 27 Apr 93 17:42:47 GMT
|
||||
|
||||
In article <1993Apr27.144342.22297@nntpd.lkg.dec.com>, barrett@pamsrc.enet.dec.com (Keith Barrett) writes:
|
||||
|
||||
> I suggest creating a newsgroup dedicated to only bug reporting
|
||||
> (comp.os.linux.bugs}. This was highly successful in the alt.sys.amiga.uucp
|
||||
> groups. The advantages are obvious
|
||||
|
||||
I would *strongly* second this motion.
|
||||
|
||||
Another (major) advantage to the new group - it would help to keep the
|
||||
volume on the Linux-activists mail channels under control, so that
|
||||
they could be more useful as channels for development discussion as
|
||||
originally intended, not as help forums as they currently seem to be
|
||||
heading.
|
||||
|
||||
Can anybody remember when the last split was voted? I think that the
|
||||
6-month limit between split votes is due to expire pretty soon.
|
||||
|
||||
Cheers,
|
||||
Stephen Tweedie.
|
||||
---
|
||||
Stephen Tweedie <sct@uk.ac.ed.dcs> (Internet: <sct@dcs.ed.ac.uk>)
|
||||
Department of Computer Science, Edinburgh University, Scotland.
|
||||
|
||||
38
docs/kgb/bryce.txt
Normal file
38
docs/kgb/bryce.txt
Normal file
@@ -0,0 +1,38 @@
|
||||
|
||||
From: p_copela@csd.uwe.ac.uk (Phil (SysAdmin Parallel Research))
|
||||
Subject: SLS 0.98 scsi+swap
|
||||
Date: 22 Oct 92 06:01:32 GMT
|
||||
Reply-To: p_copela@csd.bristol-poly.ac.uk
|
||||
|
||||
|
||||
Having downloaded the SLS release (0.98.1), I find that although I define
|
||||
/dev/sda4 of my scsi drive as a swap space and indead when the kernel boots
|
||||
I have the helpful message that the 8 Meg swap space is being added, I find
|
||||
that the 'free' command doesn't find the swap device at all 'free -s'
|
||||
returns 'swap: No swap device' and swapon -a reports that /dev/sda4 is
|
||||
already busy / mounted (presuably as a swap area)
|
||||
|
||||
Having read through the FAQ supplied in the release I found nothing to
|
||||
indicate any flags that might have been needed in /etc/fstab
|
||||
|
||||
/dev/sda4 none swap <???flags???>
|
||||
|
||||
I then thougt that this might be a case of recompile the kernel and run ps -U
|
||||
again but 25 min later and the same problem,.... the kernel reports that it is
|
||||
adding the swap space and free refuses to believe that I have, which is telling
|
||||
the truth?.
|
||||
|
||||
I was in the middle of downloading ps-0.98.tar.Z from sunsite when my network
|
||||
went down for nightly backups (pah) so I haven't recompiled the memory utils
|
||||
|
||||
does anyone spot where I've gone wrong?
|
||||
|
||||
Phil
|
||||
=--=
|
||||
|
||||
===============================================================================
|
||||
(c) 1992 Philip Copeland - alias 'Bryce' (SysAdmin)
|
||||
JANET : p_copela@uk.ac.bristol-poly.csd
|
||||
|
||||
"... I can resist anything but temptation..."
|
||||
===============================================================================
|
||||
1190
docs/kgb/bryce2.txt
Normal file
1190
docs/kgb/bryce2.txt
Normal file
File diff suppressed because it is too large
Load Diff
42
docs/kgb/cox1.txt
Normal file
42
docs/kgb/cox1.txt
Normal file
@@ -0,0 +1,42 @@
|
||||
|
||||
From: iiitac@cybaswan.UUCP (Alan Cox)
|
||||
Subject: Re: using ka9q
|
||||
Date: 17 Jul 92 14:43:05 GMT
|
||||
|
||||
|
||||
KA9Q uses a hosts.net file in its current directory for FTP and handles
|
||||
mail in a totally non-unix way. I've mailed the maintainer of the program
|
||||
with the changes to
|
||||
a) make finger work (executes a bsd finger program)
|
||||
b) fix incoming/outgoing email
|
||||
c) fix incoming telnet ( the telunix code)
|
||||
|
||||
I've not heard from him since so I don't know if they all got through. Im
|
||||
also going away for a bit so I won't be able to mail you the patches for
|
||||
a while.
|
||||
|
||||
Some pointers:
|
||||
smtp mail is almost right, just add a bit of code to check the
|
||||
username exists (with getpwnam()) and generate mailbox paths as /usr/mail/<id>
|
||||
with the right owner/groups and smtp works.
|
||||
|
||||
telunix has a set of problems. Firstly the program assumes sys5.2
|
||||
rather than posix and regards a -1 from a nonblocking read as an error.
|
||||
Add a check that makes error of -1 and errno=EAGAIN map to a 0 read and
|
||||
it will work for line mode.
|
||||
The second problem is a combination of errors in the telnet processor
|
||||
and options not sent. Make telnet.c simply ignore the WILL ECHO sequence
|
||||
and use sendmsg to send IAC DO ECHO IAC DONT SGA at the start of an incoming
|
||||
telnet to kick the machine into character mode.
|
||||
Although I tried setting the tty options to get the carriage return
|
||||
mapping to work I was forced to munge all cr/lf codes about to get
|
||||
returns to work properly.
|
||||
|
||||
Oh in addition it doesn't spawn logins like bsd telnetd instead you need
|
||||
to have them sitting on pty's read - just add /dev/ttyp0 /dev/ttyp1 and
|
||||
/dev/ttyp2 to your /etc/inittab
|
||||
|
||||
|
||||
|
||||
Alan Packet=[GW4PTS@GB7AKJ] Ampr=gw4pts@ozymandias.gw4pts.ampr.org
|
||||
Internet=iiitac@pyr.swan.ac.uk
|
||||
83
docs/kgb/cox2.txt
Normal file
83
docs/kgb/cox2.txt
Normal file
@@ -0,0 +1,83 @@
|
||||
|
||||
From: iiitac@cybaswan.UUCP (Alan Cox)
|
||||
Subject: Re: Single user boot mode
|
||||
Date: 4 Aug 92 15:56:04 GMT
|
||||
|
||||
|
||||
Linux already supports a single user boot mode. You stick the right
|
||||
statements EARLY into the rc file. Similarly linux runs beautifully
|
||||
without a monitor when you make tty1 a link to ttys1 (this ought to be
|
||||
documented somewhere really).
|
||||
|
||||
Alan
|
||||
|
||||
------------------------------
|
||||
|
||||
From: iiitac@cybaswan.UUCP (Alan Cox)
|
||||
Subject: Re: Ctrl-Alt-Del in linux, doesn't work.
|
||||
Date: 4 Aug 92 15:58:46 GMT
|
||||
|
||||
In article <3780@svin02.info.win.tue.nl> alph@win.tue.nl writes:
|
||||
>smace@nyx.cs.du.edu (Scott Mace) writes:
|
||||
>
|
||||
>]Ctrl-Alt-Del doesn't reboot my system. It disables the keyboard and
|
||||
>]locks everything up. I am running 0.96c patch level 2, and have AMI
|
||||
>]BIOS., 386DX-33, Adaptec AHA-1542B,...
|
||||
>
|
||||
>I have AMI-BIOS too, and I have the same problem...
|
||||
>occasionally...
|
||||
>
|
||||
>I tried Ctrl Alt Del and the computer hangs
|
||||
>I did a cold reboot, logged in, looked at some files, logged out,
|
||||
> tried Alt Ctrl Del and the computer rebooted.
|
||||
>
|
||||
|
||||
I too can vouch for this happening. I've been chasing it down and I
|
||||
don't think its entirely the BIOS. I've tried two very similar machines
|
||||
with AMI BIOS and AMD386 chips (33Mhz and 40Mhz). One one ctrl-alt-del
|
||||
is fine (the DX40), the 33Mhz 386 however locks up solid. Interestingly
|
||||
enough a ctrl-alt-del from windows 3 has the same effect.
|
||||
|
||||
I'm beginning to think its a chipset problem - unless you all happen
|
||||
to have a WD8013EB card in the machines which lock up ?
|
||||
|
||||
Alan
|
||||
|
||||
------------------------------
|
||||
|
||||
From: iiitac@cybaswan.UUCP (Alan Cox)
|
||||
Subject: Re: Is there a who command or a simple mail command around for linux?
|
||||
Date: 7 Aug 92 09:20:28 GMT
|
||||
|
||||
In article <713124194.F00100@remote.halcyon.com> Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin) writes:
|
||||
>
|
||||
> RB> Also, I have seen a "who" command in the stuff I have. Does such a
|
||||
>
|
||||
> RB> beast exist? Thanks.
|
||||
>
|
||||
|
||||
I've got a who I wrote ages ago its only short. I'll try and post it on monday
|
||||
if I remember. I've also got a passable port of bsd finger (without the
|
||||
tcp/ip bits and lastlogin).
|
||||
|
||||
Alan
|
||||
|
||||
------------------------------
|
||||
|
||||
|
||||
From: iiitac@cybaswan.UUCP (Alan Cox)
|
||||
Subject: Re: Is there a who command or a simple mail command around for linux?
|
||||
Date: 7 Aug 92 09:20:28 GMT
|
||||
|
||||
In article <713124194.F00100@remote.halcyon.com> Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin) writes:
|
||||
|
|
||||
| RB> Also, I have seen a "who" command in the stuff I have. Does such a
|
||||
|
|
||||
| RB> beast exist? Thanks.
|
||||
|
|
||||
|
||||
I've got a who I wrote ages ago its only short. I'll try and post it on monday
|
||||
if I remember. I've also got a passable port of bsd finger (without the
|
||||
tcp/ip bits and lastlogin).
|
||||
|
||||
Alan
|
||||
184
docs/kgb/cvs_client_info.txt
Normal file
184
docs/kgb/cvs_client_info.txt
Normal file
@@ -0,0 +1,184 @@
|
||||
=====================
|
||||
Basic CVS Client Info
|
||||
=====================
|
||||
|
||||
|
||||
Client usage
|
||||
|
||||
"client" basically means the `cvs` command or some wrapper
|
||||
for it.
|
||||
|
||||
|
||||
Basic concepts
|
||||
|
||||
Anything located in a subdirectory of a CVSROOT is considered
|
||||
a cvs module. In our server example, the "shell_scripts" is a module.
|
||||
cvs commands tend to deal with either a module at a time, or individual
|
||||
files.
|
||||
|
||||
Setting up a CVSROOT
|
||||
|
||||
examples:
|
||||
|
||||
export CVSROOT=/usr/local/cvsroot
|
||||
|
||||
export CVSROOT=:ext:foo@somehost.com:/usr/local/cvsroot
|
||||
|
||||
export CVSROOT=:pserver:bar@somewhere.net:/usr/local/cvsroot
|
||||
|
||||
|
||||
Logging into cvs
|
||||
|
||||
cvs login
|
||||
|
||||
then the appropriate passwd. This is really only needed for
|
||||
pserver methods.
|
||||
|
||||
Checking out a module
|
||||
|
||||
cvs checkout module_name
|
||||
|
||||
example:
|
||||
|
||||
for checking gimp out of gnome from scratch:
|
||||
|
||||
export CVSROOT=:pserver:anonymous@anoncvs.gnome.org:/cvs/gnome
|
||||
cvs login
|
||||
(hit return, there is no passwd)
|
||||
cvs -z3 checkout gimp
|
||||
(wait....)
|
||||
|
||||
Thats it.
|
||||
|
||||
The -z3 is a cvs option telling it to use compression level 3
|
||||
for files it transfers.
|
||||
|
||||
|
||||
Updating a module
|
||||
|
||||
We'll assume were using pserver type configuration from here
|
||||
on out.
|
||||
|
||||
cd dir/
|
||||
cvs -z3 update -Pd
|
||||
|
||||
(the -Pd isnt absoultly necessary, but what the heck).
|
||||
|
||||
Adding a file to the cvs repo
|
||||
|
||||
(create the new file)
|
||||
cvs add new_file
|
||||
cvs commit
|
||||
|
||||
This will add the new file to the repo.
|
||||
|
||||
|
||||
Committing changes
|
||||
|
||||
(change something with the files)
|
||||
cvs -z3 commit
|
||||
|
||||
(this will pop up a text editor. What this is for is
|
||||
for you to enter in some sort of meaningful messages about
|
||||
what changes you made)
|
||||
|
||||
Then it will commit those files to cvs.
|
||||
|
||||
If you get "uptodate" errors here, you will need to update
|
||||
your local tree first. See the section on updating.
|
||||
|
||||
|
||||
|
||||
Merge conflicts
|
||||
|
||||
Occasionally, if patch can figure how to handle the diffs between
|
||||
what you have locally, and whats in the repo, you will get merge
|
||||
conflicts when you update.
|
||||
|
||||
If you need to merge these by hand, the conflicts get marked in
|
||||
the file with
|
||||
|
||||
>>>>>>>>>>>>>>>
|
||||
Your stuff
|
||||
==============
|
||||
The stuff from the rep
|
||||
<<<<<<<<<<<<<<<<<<<<<
|
||||
|
||||
So you will need to figure out which one is correct, and
|
||||
then clean up all the ">>>>" and "======="'s
|
||||
|
||||
Or if you don't care about the conflicts, rm the file and update
|
||||
again.
|
||||
|
||||
|
||||
Removing a file from the repo
|
||||
|
||||
rm file_name
|
||||
cvs remove file_name
|
||||
cvs commit
|
||||
|
||||
Note that you have to remove the file locally first, then
|
||||
`cvs remove` it.
|
||||
|
||||
|
||||
Diffing what you have with the repo
|
||||
|
||||
Very often you will need to get a diff between what you
|
||||
have locally, and what is in the tree. You might need to
|
||||
do this to send a patch, or just to see what all you
|
||||
have changed.
|
||||
|
||||
cvs diff -u
|
||||
(for the whole module)
|
||||
|
||||
cvs diff -u filename
|
||||
(for a specific file)
|
||||
|
||||
the -u just tells it to used "unified" diff format, which
|
||||
tends to be a little easier to read.
|
||||
|
||||
|
||||
Thats about 99% of the commands you need to know to use cvs
|
||||
on a day to day basis. For keeping up with most projects
|
||||
that are cvs based, just login, checkout, and update are
|
||||
all you need. add, remove, diff, commit are about it
|
||||
for using a cvs tree. Of course, there are lots of
|
||||
other tricks involved.
|
||||
|
||||
|
||||
Different "Branches" and trees
|
||||
|
||||
Cvs has the ability to maintain different
|
||||
"branches" or forks or a code base, and keep them in
|
||||
the same cvs server. This is primarily used when
|
||||
someone is doing something that might break a program
|
||||
or otherwise would be best left out of the main or
|
||||
HEAD branch for a while.
|
||||
|
||||
To check out a non-HEAD (HEAD is the primary branch),
|
||||
you use the -r command line option to checkout,update, etc.
|
||||
|
||||
to check out the HOLLYWOOD version of gimp
|
||||
|
||||
cvs -z3 co -r HOLLYWOOD gimp
|
||||
|
||||
Once its checked out, it knows its HOLLYWOOD branch,
|
||||
so you don't need to use the -r option. However, if you wanted
|
||||
to go back to the main HEAD branch, you would have to
|
||||
specify that.
|
||||
|
||||
|
||||
Reverting or checking older versions
|
||||
|
||||
One of the primary advantages of revision control is
|
||||
the ability to go back to older revisions of modules or
|
||||
trees.
|
||||
|
||||
For example, if for some reason, you needed to get
|
||||
a version of a file from , 1, 1999.
|
||||
|
||||
cvs -z3 update -D "Nov 1 1999"
|
||||
|
||||
The date string is pretty flexible.
|
||||
|
||||
|
||||
85
docs/kgb/cvs_server_info.txt
Normal file
85
docs/kgb/cvs_server_info.txt
Normal file
@@ -0,0 +1,85 @@
|
||||
===========================
|
||||
CVS Server Setup
|
||||
==========================
|
||||
|
||||
|
||||
creating a local repository
|
||||
|
||||
export CVSROOT=/path/to/where/cvs/is
|
||||
cvs init
|
||||
|
||||
|
||||
Creating a module
|
||||
|
||||
cvs import -m "commit message here" path_to_module module_name start
|
||||
|
||||
ie, for a dir called shell_scripts
|
||||
|
||||
cd shell_scripts
|
||||
cvs import -m "importing shell scripts" shell_scripts shell_scripts start
|
||||
|
||||
|
||||
Checking out that module to work on it.
|
||||
|
||||
If you are importing something that already exists, you probably
|
||||
want to import it, then check it out again. This will check out the
|
||||
source with all the appropriate control files and whatnot. So, make sure
|
||||
you cp/mv the original before you check it out again.
|
||||
|
||||
mv shell_scripts shell_scripts.orig
|
||||
cvs checkout shell_scripts
|
||||
|
||||
This will checkout (download) all the files currently
|
||||
in that module of cvs.
|
||||
|
||||
Whee!
|
||||
|
||||
|
||||
|
||||
Remote server setup
|
||||
|
||||
There are two basic methods, rsh/ssh, and pserver. For most
|
||||
Open Source projects, pserver seems pretty popular, but for cases
|
||||
where confidentially is needed, the ssh method is probably preferred.
|
||||
|
||||
rsh/ssh
|
||||
|
||||
The advantage here is the possibility to use ssh, and the
|
||||
the lack of a need to run a cvs server constantly.
|
||||
|
||||
The only trick is that the client needs to exist on the server,
|
||||
and be able to login it normally. This is the primary disadvantage to this
|
||||
setup.
|
||||
|
||||
|
||||
pserver
|
||||
|
||||
Pserver setup uses a different passwd file than standard logins,
|
||||
so it is possible to give people login access to a cvs server without
|
||||
any shell or login privilege.
|
||||
|
||||
The hard part is you create the repo, then add any user entries
|
||||
to $CVSROOT/CVSROOT/passwd in the form:
|
||||
|
||||
username:passwd_string:user_to_run_as
|
||||
|
||||
passwd_string is the crypt()'ed passwd, not the plain text passwd.
|
||||
|
||||
an easy way to do this is:
|
||||
|
||||
perl -e "print crypt('passwd','a_salt_string');"
|
||||
|
||||
|
||||
Probably want to create a user for cvs particularly.
|
||||
|
||||
You also need to add the cvs pserver line to /etc/inetd.conf:
|
||||
|
||||
2401 stream tcp nowait cvs /usr/bin/cvs cvs --allow-root=/path/to/cvsroot pserver
|
||||
|
||||
Generally want to setup a cvs user, and a chroot environment for running
|
||||
cvs in. Start with the one for FTP, and work from there.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
114
docs/kgb/history.htm
Normal file
114
docs/kgb/history.htm
Normal file
@@ -0,0 +1,114 @@
|
||||
<html>
|
||||
<head>
|
||||
<title>Keith Barrett Home Page</title>
|
||||
</head>
|
||||
<body bgcolor=white>
|
||||
<h1>LINUX HISTORY</h1>
|
||||
Here are some early document events in the history of Linux.
|
||||
At some point, I may construct
|
||||
a timeline of the significant events (I have newsgroup discussions
|
||||
and announcements of many events).
|
||||
<h2>Linux 1991</h2>
|
||||
Linux was a fairly active entity on the internet in 1991, when
|
||||
most of the activities revolved around kernel and file systems. Back then,
|
||||
there was no WWW -- users interacted via the Linux newsgroup (which
|
||||
had no spamming and little flames back then), and email. Binaries (especially the
|
||||
kernel) were so small that they were sometimes posted directly to the
|
||||
newsgroup as UUENCODE files. Here is an archive of the Linux newsgroup from 1991.
|
||||
You will notice
|
||||
that Linus was very interactive, as well as Ted Ts'o (I believe he was
|
||||
the person who created this archive file).
|
||||
<br>
|
||||
<p>
|
||||
<a href="linux-activists91.txt">1991 Linux Activists</a>
|
||||
|
||||
<h2>Linux 1992</h2>
|
||||
<p>
|
||||
Here is an archive capture of the newsgroup from 1992.
|
||||
<br><p>
|
||||
<a href="linux-activists92.txt">1992 Linux Activists</a>
|
||||
<br><p>
|
||||
Also in 1992, a publishing company named JANA was the first to create
|
||||
CD-ROM captures of the mit and newsgroup archives and sell them. These
|
||||
were labeled "Expo Edition CD-ROM NEWS" (when they had a label). It is
|
||||
from these CDs that I have extracted these archive files.
|
||||
|
||||
<h1>Personal Linux Histories</h1>
|
||||
Here are most likely the first postings of some well known (to me) people in
|
||||
the Linux community. The people are listed roughtly in the order that they
|
||||
began to appear on the network. By March 1993, all of these people were frequent posters
|
||||
to the newsgroups and there are a large number within the archives. One of the
|
||||
more entertaining things to look for is the old tag lines in their signatures and
|
||||
their old email addresses.
|
||||
|
||||
<p>
|
||||
<h2>Linus</h2>
|
||||
<a href="linus.txt">This 11/6/91 posting</a> is the first I have from
|
||||
Linus. Obviously these aren't his first, but it must be darn close.
|
||||
|
||||
<p>
|
||||
<h2>Ted 'Tim' Ts'o</h2>
|
||||
Ted is probably the oldest poster next to Linus. His
|
||||
postings go all the way back to the first 1991 postings I have in the archive. <a href="ted.txt">This 11/7/91 entry</a>
|
||||
is his first posting claiming that he just heard about Linux and is creating the Linux 0.10 archives on tsx-11.mit.edu.
|
||||
|
||||
<p>
|
||||
<h2>Alan Cox</h2>
|
||||
<a href="cox1.txt">THIS</a> this is the first post I have by Alan, made
|
||||
on 7/17/92. <a href="cox2.txt">HERE</a> are a few more.
|
||||
|
||||
<p>
|
||||
<h2>Bryce Copland</h2>
|
||||
<a href="bryce.txt">HERE</a> is Bryce's first newsgroup posting from 10/2/92, and
|
||||
possible his first use of Linux, Bryce was
|
||||
also handling the Network FAQ (which was his <a href="bryce2.txt">2nd posting</a>).
|
||||
|
||||
<p>
|
||||
<h2>Stephen Tweedie</h2>
|
||||
Stephen was a very frequent poster.
|
||||
<a href="tweedie0.txt">This 10/12/92 entry</a> is the first postings I
|
||||
have on record from Stephen. <a href="tweedie2.txt">HERE</a> are a few more. He
|
||||
was hacking everything! He and I had several interactions on the newsgroup.
|
||||
|
||||
<p>
|
||||
<h2>Erik Troan</h2>
|
||||
<a href="troan.txt">
|
||||
This 2/8/93 posting</a> is the earliest post from Erik I could find (it's followed
|
||||
by an interesting post from Linus).
|
||||
His <a href="troan2.txt">next postings</a> were later that same month, and
|
||||
contain a reponse from Ted. <a href="troan3.txt">Other early posts</a> also included his
|
||||
mentioning that this new thing called Windows NT will be coming out soon
|
||||
(PROVING that Linux is older than NT), and his responding to the suggested creation
|
||||
of the first Linux magazine. There's also an interaction between Erik and Ted in there.
|
||||
|
||||
<p>
|
||||
<a name="kgb">
|
||||
<h2>Keith Barrett</h2>
|
||||
I personally became involved in studying Linux in late 1992,
|
||||
and eventually took the
|
||||
plunge installing TAMU on <a href="1st_time.txt">March 27, 1993</a>.
|
||||
The kernel release was .99pl3 in the popular distributions SLS 1.01 and TAMU.
|
||||
Slackware was also out, but SLS was still more popular. The .99pl5 kernel was
|
||||
just about making the rounds I believe.
|
||||
<br><p>
|
||||
<a href="barrett2.txt">HERE</a> are some of my posts concerning problems when I
|
||||
quickly switched to the SLS release,
|
||||
<a href="1st_posting.txt">HERE</a> is my first posting to the newsgroup, and
|
||||
interestingly the
|
||||
first person to respond to my post was Ted Ts'o. I was asking about SCSI tape
|
||||
drives and eventually did some driver testing and got listed in the
|
||||
SLS and Slackware "Hardware Compatibility" document.
|
||||
<br><p>
|
||||
<a href="barrett3.txt">HERE</a> is posting where I suggested a breakup of the
|
||||
Linux newsgroups, immediately followed by Stephen Tweedie proclaiming his support.
|
||||
<br><p>
|
||||
I also was THE FIRST PERSON to suggest that Linux have a mascot!. Look at the end of
|
||||
<a href="1st_mascot.txt"> this posting.</a> Where's my royalities?
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
309
docs/kgb/linus.txt
Normal file
309
docs/kgb/linus.txt
Normal file
@@ -0,0 +1,309 @@
|
||||
Subject: Trying to answer ...
|
||||
Date: Wed, 6 Nov 1991 13:58:52 +0200
|
||||
From: Linus Benedict Torvalds <torvalds@cc.helsinki.fi>
|
||||
To: Linux-activists@joker.cs.hut.fi
|
||||
|
||||
Well, it seems people are starting to get some things working, and my
|
||||
mailbox has certainly been busy.
|
||||
|
||||
> Does linux work on a SX?
|
||||
|
||||
Yes. I've personally tried it, and there were no problems. It seems
|
||||
linux works on all members of the [3|4]86-family. Knock wood.
|
||||
|
||||
> How do the mtools programs work?
|
||||
|
||||
Urg. I fu**ed up. As has been pointed out, it is much easier to use tar
|
||||
on a disk-image. Stupid of me not to think of that, even though that's
|
||||
what tar is for. Even so, I should at least have done some kind of
|
||||
readme for the mtools files.
|
||||
|
||||
If you want to read files from the DOS-partition, the mtools programs
|
||||
should work. They need some setting up: you need to tell them what
|
||||
devices A,B and C are. This is done by making the appropriate links to
|
||||
/dev/dosX (X=A,B,C). A and B are assumed to be floppies or small
|
||||
harddisk partitions, ie a 12-bit FAT. C is assumed to have a 16-bit fat.
|
||||
To read a 1.44M dos-floppy in A:
|
||||
|
||||
mknod /dev/dosA b 2 28 # tell linux that A is 1.44Mb floppy
|
||||
mdir A:
|
||||
etc.
|
||||
|
||||
To read your DOS-partition (16-bit FAT):
|
||||
|
||||
mknod /dev/dosC b 3 1 # 1 partition on 1 drive: don't use 0
|
||||
mdir C: # as that's the whole disk, not one prt
|
||||
|
||||
12-bit harddisk partition:
|
||||
|
||||
mknod /dev/dosB b 3 1
|
||||
mdir B:
|
||||
|
||||
Note that if you have a small partition, you probably have a 12-bit fat
|
||||
on your harddisk as well, and you should use A or B for it, not C.
|
||||
If you don't know what type of FAT you have, try with both B or C.
|
||||
Note that A/B/C has no relation to the MS-DOS devices, even though
|
||||
that's the normal way of setting it up.
|
||||
|
||||
> Somebody had trouble, didn't even get a "partition table ok" with his
|
||||
> IDE drive.
|
||||
|
||||
There /should/ be no trouble with IDE drives, so hopefully that isn't
|
||||
the problem. One possibility is that everything works, but the
|
||||
video-card isn't a colour-VGA. If you are using a mono-mode, the screen
|
||||
map is elsewhere (I think, I'm not really used to the IBM video modes),
|
||||
and linux happily writes to the wrong location. Thus the only thing you
|
||||
see is "Loading system ...", which is written with BIOS-routines.
|
||||
|
||||
If this is indeed the problem, you should be able to test it by booting
|
||||
up, putting in the root diskette, and pressing ENTER. Hopefully the
|
||||
drive will run for a while, and then stop. Try doing something blindly
|
||||
(write ls /mtools<enter>), and see if the floppy reacts. If the only
|
||||
trouble is the video card, this will be corrected in the next version.
|
||||
|
||||
If it isn't the video, things are worse. Could the person please mail me
|
||||
with more info (BIOS, type of computer etc)?
|
||||
|
||||
> nic.funet.fi is unavailable. What can I do?
|
||||
|
||||
As you probably have noticed, there is now another site available that
|
||||
carries it. See my .plan if you missed the message. nic will give you
|
||||
the files eventually, but there has indeed been something wrong with it.
|
||||
|
||||
> problems with gcc-1.37.1. Gives divide error (with the gnulib
|
||||
> routine). Could the 16-bit object files be posted?
|
||||
|
||||
Arghhh. I haven't tested the gnulib routines (as gcc-1.40 never wants
|
||||
the divide/mutliply routines), so they might be buggy. Silly me. I'll
|
||||
certainly post the 16-bit object files (they are only a couple of
|
||||
hundred bytes anyway), and anybody should be able to get linux
|
||||
recompiled within linux (after some makefile-editing, so that make
|
||||
doesn't try to recompile the bootblock etc).
|
||||
|
||||
> ESDI drives, shoelace, DLD?
|
||||
|
||||
These I know nothing about. ESDI drives should work ok, but ...
|
||||
Shoelace? Anybody? I don't know how it works, though I use it for minix.
|
||||
About DLD's: if somebody comes up with a clever way of implementing it
|
||||
all cleanly, and can explain it to me, I could certainly look into it.
|
||||
Even better would be if somebody else wrote it from scratch :-).
|
||||
|
||||
Linus (torvalds@kruuna.helsinki.fi)
|
||||
--[0003]--
|
||||
|
||||
[0004] tytso@ATHENA.MIT.EDU Linux_Activists 11/07/91 14:22 (83 lines)
|
||||
Subject: 16-bit binaries
|
||||
Date: Wed, 6 Nov 1991 17:58:43 +0200
|
||||
From: Linus Benedict Torvalds <torvalds@cc.helsinki.fi>
|
||||
To: Linux-activists@joker.cs.hut.fi
|
||||
|
||||
Ok, here's the 16-bit binaries of the bootsector and setup. They are 544
|
||||
and 340 bytes respectively, but taring made them somewhat bigger (8192).
|
||||
I decided to send them as a tar archive, as that increases the ways you
|
||||
can import them to linux.
|
||||
|
||||
In order to use them, you have to edit the Linux makefile a bit: remove
|
||||
(or comment) the lines that have the 16 bit dependencies on them (I'd
|
||||
also suggest you change 'clean' so that it won't remove these binaries),
|
||||
and install these binaries in the boot-directory. The bootblock is
|
||||
compiled to load 196kB of the system (currently only 110kB is used), so
|
||||
there is some room to grow before a new bootblock is needed. This of
|
||||
course means that the load-time is slightly longer than necessary, but
|
||||
it's still quite fast.
|
||||
|
||||
Also, as somebody commented, 'cp Image /dev/PS0' won't work with older
|
||||
versions of GNU cp. Frankly I don't know if the version of cp that linux
|
||||
uses is corrected, but a 'cat Image > /dev/PS0' or 'dd bs=8192 if=Image
|
||||
of=/dev/PS0' should work (change /dev/PS0 to match your bootfloppy, of
|
||||
course).
|
||||
|
||||
Additionally, I'd like to know if the floppy-driver works for 2 (or
|
||||
more) drives? Nobody has commented on that yet. Do a sync before you try
|
||||
it though (just in case...).
|
||||
|
||||
Linus (torvalds@kruuna.helsinki.fi)
|
||||
|
||||
------- uuencoded compressed tar-file starts here ----------------------
|
||||
begin 644 bin16.tar.Z
|
||||
M'YV08MZ\H3.GS!@Z !(J7,BPH<.'$"-*G$@1 (B+-VK4 &%1Q@T:,6)P!.%Q
|
||||
M!HV-%B^J!!$#!@T8%VNTM %#AHR6-%32K&FQHL^?0(,*'4JTJ-&C2),J7<IT
|
||||
M8H !$ AP5"C@9P"&N( =<(0-%P!(CH#E A @A;T4_^:54H<A(21&R+B&=02-
|
||||
M%X!_NA+FJKH+@ !<! 0TFS!'05X 7@$,7F=.%F( " ;7 N BD0,@ ;R"!49K
|
||||
M (Q_S2#D:KOK (!>0C('F!#:*X2PZ&8 0(>,<BA^ 7HDK(/!Q2(/F'$A$#!H
|
||||
MWP,Z"W!Q(+Y/ IT!Z?K]<S$*M[J$(" 58,@(6*I_#^KXB[&MNVX@<@(,<Q$*
|
||||
M\PH#F0 D"A8L7(( V>8DH',@!K 4V 2#3@+HU"!?, / 1]D.!F!6AP2X7/7>
|
||||
M)@#40< _!G0"P"@4^C=*?/7=M\P<LG2WW6O D)>.*?] ,4444BQB@8:+.!!?
|
||||
M$(A4(R.%B%CC6"#BD$6+8!/(48 666R!Q3")'388DDJFL\P_4N@BSP"P .".
|
||||
M%L,DU( "3+P1!AEIN'$&"'/D,0<=9;0!@@MP?OEE4W36:>>="1DP0!6JX.GG
|
||||
MGX &*NB@A!9JZ*&"%D1''7 @ZBAV&&DTDD<@B=31#2:AM-)*-< $P@RN52#
|
||||
M#"_-<(-*-<P0@PP]/>KJJ[#&*FNL3T4UE457^92K0IIQU=EGH25B04*T(-),
|
||||
M!:-4E1A7Q=A 0&9?A?4+( #D @$ \Y"R+#;-8@#M9K] 4NVUV7I5@2R!#&8D
|
||||
M(/P,0 <$O0(3[KB/8:N*/HGQ$]:)ND%"AP-<H6766("HE0XZ_^"2'5</!.!!
|
||||
M! $T;,$% :#S!0"P1&,.&>A@@?$WYH"!3A081V .".L D+(YH*2<,BP@F!."
|
||||
MRQBC8$XH-,-"@,PY"W!SS@'PK#( /P\-RS]"KQQ*A T#,]UD V=,CEDH")
|
||||
M'?9TZ= _IB6D"3!W=0V )& [A$ ^ B2P4)%')KEDDPD]Z;:45%J)I99<>@FF
|
||||
MF&2:B:::;+H)IPMR*C#KX8@GKOCBC#?N^..01R[YY)17;OGE=H919AD 4 "
|
||||
M 0DM0 L \A#!@!M(0!'&&R\P488:"!D1D&AUT8 $Z:E7N89K,]1QQL C ''
|
||||
MZ0 LP T !!"3.V1KA"$'[&N\X89"AA?/#EE\C-$Y\L^K$08 :2"4$ ,*F6/&
|
||||
M]@6X44<;;:0! !G? \" YP& ,P+JD-$1_1K1OPZ #&, GOQ00#H5L"IUKX-#
|
||||
MF5[7!@!(SP[CXP%97&&@U-&!#FEH@_3*,#TXP(%S\F,"\B"@@^T9@ UIJ /_
|
||||
M@"<^!H A(2AX ?X0H(;VK=!_' ! \8G/GTH889S<%X8W(!!-B0D 1Z3'R=(
|
||||
M1XTAS/!U=I!>"N>0$ <HA &L()T :&#"-]@A#'-HWD(88)< ., )VR/ &5YW
|
||||
M.C2L 80,@ 99Y'"#&;(I#:_;'/ZJQP!R^ 4!1)@A&A*X.O_)CUKRPP?R=*&]
|
||||
MU(5A#6D(HO/<)S]*>(E\[SN#'0OB0=;%CP&H\!)'!,"+[Z5.#H3TY/@2TP N
|
||||
M$D 2VTF=&M!0!CFTH0YN "$!C."E0!*-!28,(!M0.+TC>(D*9 &"#;9W #H0
|
||||
MDPP<5$@#T$ 64D!AAG; HP?KX#\T:-!+?$B(($KH2#=\< X;3,@Q0N$E1HSP
|
||||
M!.A[71WD +QCB,)+2Q2 )]; S#F\[I'1DV:6!D (*<QP#6QHTYKHF1 "H%&'
|
||||
MQ$">!CR7NC6]00[0'*8#ZZ ]'6(#>8C( A AR08XI%.'U-3A]0!@"1_8,0RL
|
||||
MH\-)"6!0 %@Q(?KH C/;0(='JK**UPH %:Q@0C74 0VN^QXR;4H"TMD">*EK
|
||||
M ^O*$#OI >!: Z@B#LC"#*A"Y@U2)68T=5@V!R !>::8GN<,@(9')A4 S*AB
|
||||
M$E7!!6:&H0[9S.7TJFA$ AA@"3,<X@738%+W>8X 50PG >CP &:J 0X)C1TE
|
||||
M;2HN +BA"8+,PQ?EH$>;BM"FI$@(-XQHP3G@T0X<W*L#8%!%KP1 !"1+W1U@
|
||||
MQX:%"I %[-I7 = #2W,$ [1(V+SII<&/8#0 <<3*N?6&L8\7/![E'3 ]0)
|
||||
MC[-Z[@"US>!;$])8OW @#G:\J!OH^08JVA01W#VL'SXPPS;D$8.Y;"@('T!
|
||||
M4N+AH,UCE ))&[6F27 _+BO[M(0O3"6B9G<%>'M?H ^-. 1A0G93M->* !H
|
||||
M+&"&:E"#:<OPQ>G- ;+<;10 /' 5SQ7 >=D$WO.X2RT"+!%];<A#'E8LOJ99
|
||||
MD@!@Z$!@X; H+QZX:6UI6BB%&H'V<G)U\47>7A_@6DT0=:U?C"GP!/B N I
|
||||
M!U:,ZBV1JE< &-&\#P"'7[2AA]\ZCW^=?< +FP8/TB'!H-=]0YDVN->K*H01
|
||||
MA7#L&R3[S81 @'ZX.,1O-8C'(>JR#GYN*BD)8<*V1K*M (#@5;<J %DTHKW.
|
||||
M>Z_[L.KGSY+ATJE;0QW2T.%HID$,"H' "^LGB(.V-0P]]1YWCW=5\5E"7*EK
|
||||
MJQR,VF7D[<'/Z 6 /MR9ZS(4FG_?X_15E^CB1P#Q#=!$)2[]?-^K9HD L(B/
|
||||
M!7^7U[%"@+57!1L!()#GM:Z.GOZ3X%6I,4<1;EL.&-2<6@$@80B@XX^M/J6Q
|
||||
MPVAH -"RHQ!09(6=O58W$)B;WSL? ") /@(@@MB04<.>PQ#6[]4R#PF) $=P
|
||||
M3-&(UP&F;)#I7@E@B(QS,0#J\,03J8K!YADQJ!D_JU^],,,WK"&(KXN=G^VR
|
||||
M\+H" !F-A$PV:[F^1YHPXXTR([529X<V&+Q-93 B',:0T@@P.@"00.8IR]33
|
||||
MU7VO466+ ":0YX>21_4,]'0#4HVX<$Q*("$!<(6@93D'27)VKP/(,^;VSO>^
|
||||
G^_WO@ ^\X =/^,(;_O"(3[SB%\_XQCO^\9"/O.0G3_G*6_[RF%<<
|
||||
|
||||
end
|
||||
--[0004]--
|
||||
|
||||
[0005] tytso@ATHENA.MIT.EDU Linux_Activists 11/07/91 14:22 (127 lines)
|
||||
Subject: Devices
|
||||
Date: Wed, 6 Nov 1991 19:15:45 +0200
|
||||
From: Linus Benedict Torvalds <torvalds@cc.helsinki.fi>
|
||||
To: Linux-activists@joker.cs.hut.fi
|
||||
|
||||
Before the actual article: a quick question. Are any of you using DOS
|
||||
version 5.0 ? If I've understood correctly, 5.0 changes the disk-layout
|
||||
rather heavily. I doubt mtools can handle the new DOS partitions, and
|
||||
possibly even the partition table has changed. Again, I'd be interested
|
||||
to know if everything works fine with DOS 5.0.
|
||||
|
||||
Mika Matti Jalava: "device numbers" (Nov 6, 18:08):
|
||||
> Hi!
|
||||
>
|
||||
> Would it be possible to post some kind of a table of valid device
|
||||
> numbers? [ for people not having minix ]
|
||||
|
||||
Ok. Here is a short table:
|
||||
|
||||
|
||||
Memory devices: Major = 1 (characted devices)
|
||||
minor
|
||||
0 /dev/ram - not implemented (never will be, I think: minix special)
|
||||
1 /dev/mem - not implemented (easy, seldom used)
|
||||
2 /dev/kmem - not implemented (easy, but I haven't done it)
|
||||
3 /dev/null
|
||||
4 /dev/port (implemented, but untested - don't play with it)
|
||||
|
||||
example: "mknod /dev/null c 1 3"
|
||||
|
||||
|
||||
Floppy disks: Major = 2 (block devices)
|
||||
|
||||
minor = drive + 4*type, drive = 0,1,2,3 for A,B,C or D-diskette
|
||||
|
||||
type 1: 360kB floppy in 360kB drive (5.25")
|
||||
2: 1.2M floppy in 1.2M drive (5.25")
|
||||
3: 360kB floppy in 720kB/1.44Mb drive (3.5")
|
||||
4: 720kB floppy in 720kB/1.44Mb drive (3.5")
|
||||
5: 360kB floppy in 1.2M drive (5.25")
|
||||
6: 720kB floppy in 1.2M drive (5.25")
|
||||
7: 1.44M floppy in 1.44M drive (3.5")
|
||||
|
||||
Thus minor nr for a 1.44Mb floppy in B is: 1 + 4*7 = 29, and to read an
|
||||
old 360kB floppy in a 1.2M A-drive you need to use minor= 0 + 4*5 = 20.
|
||||
|
||||
Example: "mknod /dev/PS0 b 2 28" (b for block: 2 for floppy, 28 for 1.44
|
||||
in A)
|
||||
|
||||
|
||||
Hard disks: Major = 3 (block devices)
|
||||
minor
|
||||
0 /dev/hd0 - The whole hd0, including partition table sectors etc.
|
||||
1 /dev/hd1 - first partition on hd0
|
||||
...
|
||||
4 /dev/hd4 - fourth partition on hd0
|
||||
5 /dev/hd5 - The whole hd1, again including partition table info
|
||||
6 /dev/hd6 - first partition on hd1
|
||||
...
|
||||
9 /dev/hd9 - fourth partition on hd1
|
||||
|
||||
NOTE! Be /very/ careful with /dev/hd0 and /dev/hd5 - you seldom need
|
||||
them, and if you write to them you can destroy the partition tables:
|
||||
something you probably don't want.
|
||||
The only things that use /dev/hd0 are things like "fdisk" etc.
|
||||
|
||||
NOTE 2!! The names for hd's are the same as under minix, but I think
|
||||
minix orders the partitions in some way (so that the partition numbers
|
||||
will be in the same order as the partitions are physically on the disk).
|
||||
Linux doesn't order anything: it has the partitions in the same order as
|
||||
in the partition table (ie /dev/hd1 might be physically after /dev/hd2).
|
||||
|
||||
NOTE 3!! Somebody wrote he trashed his DOS-partition with mtools. Are
|
||||
you sure you didn't do a "mkfs /dev/hdX" with the demo-minix, where the
|
||||
X was a DOS-partition and not an empty one? One way to be sure to trash
|
||||
a DOS-partition is to overwrite it with a minix filesystem. Not that
|
||||
I'm sure that mtools works (/I/ didn't write it :-), just wondering...
|
||||
|
||||
|
||||
Tty's: Major = 4 (character devices)
|
||||
minor
|
||||
0 /dev/tty0 - console
|
||||
1 /dev/tty1 - serial 1
|
||||
2 /dev/tty2 - serial 2
|
||||
|
||||
Example: "mknod /dev/tty2 c 4 2"
|
||||
|
||||
|
||||
Personal tty: Major = 5 (character device)
|
||||
|
||||
minor: 0 /dev/tty - "linked" to the tty that your process has got:
|
||||
normally /dev/tty0 in linux (until someone makes a init/login).
|
||||
|
||||
Example: "mknod /dev/tty c 5 0"
|
||||
|
||||
|
||||
> I think I'll have to try a couple of old MFM disks, as my ESDI does
|
||||
> not seem to like Linux. The test that someone suggested,
|
||||
> cat </dev/hd1>/dev/null probably did not do what it should have done,
|
||||
> it just hung the machine.
|
||||
|
||||
Don't be so sure: using direct reads/writes on a device is rather slow,
|
||||
and on a bigger partition (>10M) this can take some time even for a
|
||||
harddisk. I've never tried to optimize direct devices for performance.
|
||||
If you can get out from the "cat" with ^C, it probably works. If ^C
|
||||
doesn't kill it, ESDI drives probably won't work.
|
||||
|
||||
Another way to test the drive would be to write "cat /dev/hd1". This
|
||||
prints anything it reads onto the screen: if nothing appears, linux is
|
||||
unable to read the drive. Use ^C to break when you have got enough.
|
||||
Again, if ^C won't work, the drive is unsupported. (note: pressing ^C
|
||||
repeadetly may kill the shell, as it will catch only the first one).
|
||||
|
||||
Note to everybody: currently I have these debug-statements in the
|
||||
kernel, so that when you try to read past the end of a partition or
|
||||
diskette you will get "xxx I/O error". This is normal (but reading
|
||||
beyond the end of the disk may not be :-).
|
||||
|
||||
> BTW, Is it possible to use a secondary HD controller? If not, will it
|
||||
> be some day?
|
||||
|
||||
Not currently, and as I haven't got a second controller... It should be
|
||||
relatively easy to add a driver for it: copy the code from hd.c to
|
||||
hd2.c, change the MAJOR_NR to 6 (or something), and change all the IO
|
||||
port addresses. That /might/ do it (VERY simplified explanation). I
|
||||
won't be able to do it - no way to debug the thing.
|
||||
|
||||
Linus
|
||||
22
docs/kgb/ted.txt
Normal file
22
docs/kgb/ted.txt
Normal file
@@ -0,0 +1,22 @@
|
||||
[0006] tytso@ATHENA.MIT.EDU Linux_Activists 11/07/91 14:27 (20 lines)
|
||||
Subject: Re: nic.funet.fi unreachable
|
||||
From: tytso@Athena.MIT.EDU (Theodore Ts'o)
|
||||
To: linux-activists@joker.cs.hut.fi
|
||||
|
||||
A quick scan using Archie shows that none of the FTP sites for Linux
|
||||
that it knows about are on the U.S. side of the Atlantic. In the hopes
|
||||
of reducing inter-atlantic traffic and reducing the load on
|
||||
nic.funet.fi, I've made Linux-0.10 available for anonymous FTP on
|
||||
TSX-11.MIT.EDU (18.172.1.2). I will make an attempt to keeps things
|
||||
reasonably current.
|
||||
|
||||
I've just recently heard about Linux from the Hurd mailing list, and
|
||||
from looking at the source code it looks very, very exciting. I haven't
|
||||
managed to install it on my hard disk yet (it looks like I'll need to
|
||||
blow away OS/2 in order to reclaim one of the four primary partitions
|
||||
--- shucks), but just from looking at the source code there are a bunch
|
||||
of things which look like interesting projects --- like supporting DOS
|
||||
extended partitions and multiple threads per task. Now, all I need to
|
||||
do is find some time to do some playing.... :-)
|
||||
|
||||
- Ted
|
||||
34
docs/kgb/ted2.txt
Normal file
34
docs/kgb/ted2.txt
Normal file
@@ -0,0 +1,34 @@
|
||||
|
||||
|
||||
From: Theodore Ts'o <tytso@athena.mit.edu>
|
||||
Subject: Re: SCSI tape drive help
|
||||
Date: 23 Feb 1993 11:56:51 -0500
|
||||
Reply-To: tytso@athena.mit.edu
|
||||
|
||||
From: barrett@pamsrc.enet.dec.com (Keith Barrett)
|
||||
Date: 22 Feb 93 21:19:09 GMT
|
||||
|
||||
I want to get a SCSI tape drive (QIC-150 or QIC-250) that supports
|
||||
reading and writing 150 meg tapes. I will be exchanging between Linux
|
||||
and other UNIX workstations (the tapes are the 6150, 6250 kind, approximate
|
||||
dimentions are 4x6x1). It would be real nice if the same drive supported 250
|
||||
meg tapes also.
|
||||
|
||||
A drive which support QIC-150 tapes will also support the 6250 tapes ---
|
||||
the format is the same, just the tape is longer.
|
||||
've found refurbished, or new-but-taken-out-of-PS/2 Tandburg 3660 tape
|
||||
drives at PC computer trade shows for $150-$175. They're not "new", but
|
||||
most of them either haven't been used much if at all. The one catch is
|
||||
that your warranty is whatever the salvage dealer is willing to give
|
||||
you. I got a 60 day warranty with mine. It worked perfectly the first
|
||||
time I hooked it up to my Adaptec 1542B. (Ironic, isn't it? The
|
||||
controller ended up costing me more than the tape drive! :-)
|
||||
|
||||
These PC computer trade shows run approximately once a month in the
|
||||
Boston area, and there are usually several salvage dealers that show up
|
||||
at these shows. If you're in the Boston area, and you want to find out
|
||||
when the next one of these shows are; let me know. The next time I get
|
||||
a postcard from these folks, I'll send you email.....
|
||||
|
||||
- Ted
|
||||
|
||||
59
docs/kgb/troan.txt
Normal file
59
docs/kgb/troan.txt
Normal file
@@ -0,0 +1,59 @@
|
||||
1993
|
||||
|
||||
-- February 8 Erik Troan ``This is a list (and short
|
||||
description) of all of the stuff
|
||||
that's been moved out of pub/Linux/Incoming on sunsite.unc.edu
|
||||
in the past 10 days. If the description is wrong, please let me
|
||||
(ewt@sunsite.unc.edu) know asap as this is the same description that
|
||||
goes in the INDEX file.
|
||||
I'm going to try to get these things out weekly to semi-weekly, but
|
||||
sunsite is a mess, so it may take me a while to get on a regular schedule.
|
||||
|
||||
/pub/linux/apps/m4-103A.taz
|
||||
General purpose macro language/preprocessor
|
||||
|
||||
/pub/linux/kernel/misc-patches/snd-driv-0.5.tar.Z
|
||||
Sound card driver
|
||||
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
|
||||
32bottom
|
||||
``He's done it again -- doesn't he ever rest''?Anonymous linux kernel
|
||||
hacker
|
||||
|
||||
|
||||
|
||||
-- February 9 Linus sez:
|
||||
``Only complete newbies don't know what this is all about, but I'd better
|
||||
tell you anyway: patchlevel 5 of the 0.99 kernel is now available on
|
||||
nic.funet.fi (pub/OS/Linux/PEOPLE/Linus) as both context diffs against
|
||||
pl4 and complete source code. I'm not even going to speculate on 1.0
|
||||
right now.
|
||||
|
||||
The pl5 diffs are about 90kB compressed: the major changes are to the
|
||||
tcp/ip code and the serial driver, while there are various minor fixes
|
||||
strewn around the system:
|
||||
|
||||
- serial lines/tty changes (tytso & Fred v Kempen)
|
||||
- NFS bugfixes (Rick Sladkey)
|
||||
- tcp/ip (Ross Biro)
|
||||
- coprocessor handling changes (me)
|
||||
- harddisk driver error handling (Mika Liljeberg)
|
||||
- various minor patches (me and others)
|
||||
|
||||
Serial lines now implement non-blocking opens correctly and support
|
||||
dial-out lines (same minor, major .eq 5). I changed the default startup
|
||||
mode to be CLOCAL so that people won't get confused by the modem line
|
||||
code when not using dial-in.
|
||||
|
||||
Another interesting change is the 387 error-coupling tests at bootup:
|
||||
the code to check if the intel-recommended exception 16 error reporting
|
||||
is present is non-obvious. If you have had problems with coprocessor
|
||||
error handling, or have a non-intel coprocessor, I'd suggest you test
|
||||
this out: I'd like to hear about problems/successes.
|
||||
PS. If you tested out the latest ALPHA-diffs (the ones that already
|
||||
changed the kernel version to pl5), the changes to the final pl5 were
|
||||
only cosmetic.
|
||||
153
docs/kgb/troan2.txt
Normal file
153
docs/kgb/troan2.txt
Normal file
@@ -0,0 +1,153 @@
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: Where's the driver for NE2000 cards?
|
||||
Date: Fri, 19 Feb 93 19:47:00 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
In article <1993Feb19.124841.27310@donau.et.tudelft.nl>,
|
||||
wolff@liberator.et.tudelft.nl (Rogier Wolff) writes:
|
||||
|>
|
||||
|> I have a PC with an NE2000 card in it. I found on a hardware-compatibility-
|
||||
|> list that this card should be supported, but my kernel reports that it can't
|
||||
|> find an 8013 card, and I can't find any references to NE2000 in the kernel.
|
||||
|> I also searched at tsx11 for a NE2000 patch, but couldn't find any.
|
||||
|>
|
||||
|
||||
Try looking on sunsite.unc.edu in /pub/Linux/system/Network. IF
|
||||
you poke around down there you should be able to find it. Alternatively,
|
||||
get the INDEX.whole or 00-find.linux and grep for 2000.
|
||||
|
||||
Sorry this isn't a better reference, but I'm at work and can't get to sunsite
|
||||
from here :-(
|
||||
|
||||
Erik
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
"Playing strip poker with exhibitionists kind of takes the challenge out of it"
|
||||
|
||||
Erik Troan = ewtroan@vnet.ibm.com, ewtroan@eos.ncsu.edu,
|
||||
ewt@sunsite.unc.edu (internet)
|
||||
= ewtroan@raleigh.ibm.com (ibm ip/net), T/L 444-7435 (ibm tele/net)
|
||||
|
||||
|
||||
------------------------------
|
||||
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: seyon?
|
||||
Date: Mon, 22 Feb 93 14:02:39 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
|> I have seen references made to seyon for Linux on here.. But I
|
||||
|> can't seem to find it anywhere! Where is it? Thanks...
|
||||
|
||||
Try sunsite.unc.edu:/pub/Linux/X11/xapps
|
||||
|
||||
Erik
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
"Playing strip poker with exhibitionists kind of takes the challenge out of it"
|
||||
|
||||
Erik Troan = ewtroan@vnet.ibm.com, ewtroan@eos.ncsu.edu,
|
||||
ewt@sunsite.unc.edu (internet)
|
||||
= ewtroan@raleigh.ibm.com (ibm ip/net), T/L 444-7435 (ibm tele/net)
|
||||
|
||||
------------------------------
|
||||
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: rzsz && kermit
|
||||
Date: Mon, 22 Feb 93 14:14:01 GMT
|
||||
Reply-To: ewtroan@vnet.ibm.com
|
||||
|
||||
|
||||
|> > I saw mention in here recently about using rz from kermit
|
||||
|> > under Linux. The suggestion was to start the transfer on the
|
||||
|> > remote and then to return to kermit and issue the command
|
||||
|> > 'run rz </dev/modem >/dev/modem'.
|
||||
|>
|
||||
|> I believe you are referring to a response from me to someone. I forgot that
|
||||
|> rzsz now checks to see if it is being invoked to run on /dev/tty. If not it
|
||||
|> exits with an error message. A number of people have published patches to
|
||||
|> make newer versions of rzsz to work using stdin and stdout. I believe I
|
||||
|> have seen patches on sunsite. Check with the Seyon stuff. I have kept
|
||||
|> using a very old version of rzsz that does not contain the restrictive
|
||||
|> copyright.
|
||||
|>
|
||||
|
||||
I just compiled rzsz9202 from sunsite.unc.edu:/pub/Linux/apps/comm, and
|
||||
got it to work fine by changing a line that read 'open("/dev/tty" ...' to
|
||||
open /dev/ttys1 instead (the line should be in rbsb.c, but I'd grep
|
||||
all of the c stuff for /dev/tty to be sure). Now I can just ctrl-z out
|
||||
of kermit and type "rz" and everything's happy as a clam.
|
||||
|
||||
Btw, there are some rzsz patches in /pub/Linux/apps/comm, but I haven't
|
||||
looked to see what they patch. Those may be the same ones referred to
|
||||
above.
|
||||
|
||||
Erik
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
"Playing strip poker with exhibitionists kind of takes the challenge out of it"
|
||||
|
||||
Erik Troan = ewtroan@vnet.ibm.com, ewtroan@eos.ncsu.edu,
|
||||
ewt@sunsite.unc.edu (internet)
|
||||
= ewtroan@raleigh.ibm.com (ibm ip/net), T/L 444-7435 (ibm tele/net)
|
||||
|
||||
------------------------------
|
||||
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: Where's SPICE?
|
||||
Date: Fri, 26 Feb 93 16:01:31 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
|> Here's where you can find SPICE patches for Linux, along with some
|
||||
|> documentation:
|
||||
|>
|
||||
|> sunsite.unc.edu(152.2.22.81):/pub/Linux/Incoming/spice.kit.T.Z
|
||||
|>
|
||||
|> I haven't tried it yet. I found this information in a recent post to
|
||||
|> this newsgroup. I will forward a copy of the post via email for those
|
||||
|> who request it. Please ask for ~misc/SPICE (by way of reminding me).
|
||||
|>
|
||||
|
||||
Look at sunsite.unc.edu:/pub/Linux/apps/math. It should be in there. If
|
||||
not, grep 00-find.Linux for "spice".
|
||||
|
||||
Erik
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
"Playing strip poker with exhibitionists kind of takes the challenge out of it"
|
||||
|
||||
Erik Troan = ewtroan@vnet.ibm.com, ewtroan@eos.ncsu.edu,
|
||||
ewt@sunsite.unc.edu (internet)
|
||||
= ewtroan@raleigh.ibm.com (ibm ip/net), T/L 444-7435 (ibm tele/net)
|
||||
|
||||
------------------------------
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: GIF-Previewer wanted
|
||||
Date: Fri, 26 Feb 93 16:07:28 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
|> I need a previewer for GIF-Files. I could start and write one using
|
||||
|> the VGALIB-routines but it would save lot of work if someone
|
||||
|> allready has a previewer.
|
||||
|>
|
||||
|
||||
First of all, yes there is one. Secondly, sunsite.unc.edu has it. I just
|
||||
don't remember quite where it is (as I downloaded it last night though, I
|
||||
probably should). Look in /pub/Linux/apps/graphics or /pub/Linux/graphics.
|
||||
If that doesn't help, grep for "pbm" in 00-find.Linux - the viewer is one
|
||||
directory underneath pbm. If you still can't find it, send a note to me
|
||||
at ewt@sunsite.unc.edu and I'll find it for you.
|
||||
|
||||
Sorry for not being more specific,
|
||||
|
||||
Erik
|
||||
|
||||
479
docs/kgb/troan3.txt
Normal file
479
docs/kgb/troan3.txt
Normal file
@@ -0,0 +1,479 @@
|
||||
|
||||
From: ewtroan@watson.ibm.com (Erik Troan)
|
||||
Subject: Re: Linux Journal -- magazine
|
||||
Date: Wed, 21 Apr 1993 14:12:03 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
In article <C5pr9t.3Kp@fin.uucp>, chip@fin.uucp (Chip Salzenberg) writes:
|
||||
|> According to linux@fylz.com (Linux Journal):
|
||||
|> >Why does the Linux community need a magazine? The publisher of a
|
||||
|> >technical magazine I was talking to put it this way: "No successful
|
||||
|> >movement has ever made it without a journal reporting on its progress."
|
||||
|>
|
||||
|> Ha! We don't need no steenkin' journal. We have Usenet.
|
||||
|> --
|
||||
|> Chip Salzenberg, at home <chip@fin.uucp> or <tscs!fin!chip>
|
||||
|
||||
But! Other's do need a nice clean journal. They don't have Usenet.
|
||||
|
||||
The whole world isn't on internet. Any effort that can be made that doesn't
|
||||
cost ME or YOU anything is a good idea. Don't discourage anyone from
|
||||
spreading the word about linux. Think about all of those poor lost souls
|
||||
who still see "C>" when they turn on their machines.
|
||||
|
||||
Sad, isn't it?
|
||||
|
||||
Erik
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
When I was in school, I cheated on my metaphysics exam: I looked into
|
||||
the soul of the boy sitting next to me.
|
||||
-- Woody Allen
|
||||
Erik Troan = ewt@sunsite.unc.edu, ewtroan@vnet.ibm.com
|
||||
|
||||
|
||||
------------------------------
|
||||
|
||||
From: ewtroan@watson.ibm.com (Erik Troan)
|
||||
Subject: Re: 16550 uarts and .99pl8
|
||||
Date: Wed, 21 Apr 1993 14:22:30 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
In article <1993Apr20.114346.781@ositos.UUCP>, cmf@ositos.UUCP (Carl
|
||||
Fongheiser) writes:
|
||||
|> In article <1993Apr19.081303.15747@cs.tulane.edu>
|
||||
butler@cs.tulane.edu (Larry Butler) writes:
|
||||
|> >Is anyone having problems with patchlevel 8 and 16550 uarts? Ever since I
|
||||
|> >changed from pl 6 to pl 8 I have been having problrms with characters
|
||||
|> >repeating. It's a little hard to explain. I clipped a couple of lines from
|
||||
|> >kermit while logged in to a remote system:
|
||||
|>
|
||||
|> I'm seeing the exact same thing with my Boca 4-port card. Kind of annoying
|
||||
|> when I'm using the modem to fetch stock quotes :-(
|
||||
|>
|
||||
|> Carl Fongheiser
|
||||
|> ositos!cmf@vpnet.chi.il.us
|
||||
|
||||
I'm having that problem too! I've been running pl 7 before I bought
|
||||
my no-name 16550C card, and have reapeating characters intermittantly.
|
||||
|
||||
Erik
|
||||
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
When I was in school, I cheated on my metaphysics exam: I looked into
|
||||
the soul of the boy sitting next to me.
|
||||
-- Woody Allen
|
||||
Erik Troan = ewt@sunsite.unc.edu, ewtroan@vnet.ibm.com
|
||||
|
||||
------------------------------
|
||||
|
||||
From: ewtroan@watson.ibm.com (Erik Troan)
|
||||
Subject: Windows NT Announcement
|
||||
Date: Wed, 21 Apr 1993 16:45:15 GMT
|
||||
Reply-To: ewt@sunsite.unc.edu
|
||||
|
||||
Just wanted to make sure everyone heard about Bill Gates latest announcement
|
||||
concerning Windows NT. Apparently it won't ship before August 1st, will
|
||||
nedd at least 16mb of RAM (more for servers), and will be priced around
|
||||
$500 for the non-server version. He even said that if you don't know why
|
||||
you want NT, you probably don't want NT.
|
||||
|
||||
Thank you Linus for saving us all from this. My 4 MB 25 MHz 386 has never
|
||||
seemed so lively.
|
||||
|
||||
Erik
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
When I was in school, I cheated on my metaphysics exam: I looked into
|
||||
the soul of the boy sitting next to me.
|
||||
-- Woody Allen
|
||||
Erik Troan = ewt@sunsite.unc.edu, ewtroan@vnet.ibm.com
|
||||
|
||||
|
||||
------------------------------
|
||||
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: Linux FTP mail server?
|
||||
Date: Fri, 23 Apr 1993 18:08:18 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
In article <802@wpsun4.UUCP>, jayk@wpsun4.UUCP (Jay Kint) writes:
|
||||
|> Is there one, and how does one use it? More precisely, is it fairly
|
||||
standard
|
||||
|> and what is the address one sends a help to. As well, perhaps someone knows
|
||||
|> if the uunet has a FTP mail server. I have access to the archives on UUNET
|
||||
|> and they contain the Linux stuff.
|
||||
|>
|
||||
|> Thanx for any information.
|
||||
|>
|
||||
|> Jay
|
||||
|> wpsun4!jayk@uunet.uu.net
|
||||
|>
|
||||
|
||||
sunsite.unc.edu has a mailserver of its very own. To use it, send mail to
|
||||
"ftpmail@sunsite.unc.edu" and it'll tell you how.
|
||||
|
||||
In response to your next question, I'm pretty sure that sunsite does indeed
|
||||
have every tcp bell and ip whistle that exists. jem likes to play :-)
|
||||
|
||||
Let me know if you have any problems,
|
||||
|
||||
Erik
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
When I was in school, I cheated on my metaphysics exam: I looked into
|
||||
the soul of the boy sitting next to me.
|
||||
-- Woody Allen
|
||||
Erik Troan = ewt@sunsite.unc.edu, ewtroan@vnet.ibm.com
|
||||
|
||||
------------------------------
|
||||
|
||||
From: pdh@netcom.com (P D H)
|
||||
Crossposted-To: comp.os.os2.programmer,comp.os.coherent,comp.os.mach,comp.os.minix,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development
|
||||
Subject: Re: QIC NEWS vol.1 Special Edition #1
|
||||
Date: 23 Apr 93 05:49:01 GMT
|
||||
|
||||
jmonroy@netcom.com (Jesus Monroy Jr) posts:
|
||||
|
||||
> -I tried to convince them to reconsider the issue of that cost vs.
|
||||
> -the profit of selling more drives. At least 2 people I talked
|
||||
> -to said they would bring it up when the chance arrived. I talked
|
||||
> -to them in terms of the LINUX system market potentials. I can't
|
||||
> -see how they can ignore the OS/2 market.
|
||||
>
|
||||
> We sell the .. for OS/2.
|
||||
> :: [deleted] ::
|
||||
|
||||
Now LINUX, please. I've already abandoned OS/2, having found that it is
|
||||
not (yet) a true 32-bit protected mode system (I know, 32-bits apps, but
|
||||
that is not what I am taking about).
|
||||
|
||||
> ->You can get all the specs you need from the QIC committee.
|
||||
> :: [deleted] ::
|
||||
> :: [see QIC NEWS vol.1 no.1] ::
|
||||
|
||||
Not true. This is apparently the specs that CMS wants you to think you
|
||||
need. The "need" in this case seems to be that on the part of CMS; THEY
|
||||
need for us porgrammers to go hide somewhere and quit trying to make
|
||||
better software. Every time I hear that from them, it makes me SICK!
|
||||
I have the QIC specs. Ain't in there.
|
||||
|
||||
|
||||
> This goes back to the amount of support we can provide. The
|
||||
> software and communications are not as simple as they may appear.
|
||||
> The specs are also long and terse.
|
||||
|
||||
Please don't baby me. Some of us a very good programmers that can
|
||||
understand complex subjects, and even understand hardware. So they
|
||||
are long and terse. That's only a sign of poor documentation anyway.
|
||||
I know the parallel port problem is not simple. It is difficult in
|
||||
part because the original design didn't expect it to be used for this.
|
||||
But then we can find tons of really bad designs in the PC architecture
|
||||
that people found working solutions around.
|
||||
|
||||
|
||||
> Our software group is quite active. They have to support new
|
||||
> hardware as it comes out while doing new software development.
|
||||
|
||||
All the more reason to open the specs. Third party software developers
|
||||
might well surprise you in how innovative they can be.
|
||||
|
||||
|
||||
I believe a possible solution here is for the QIC group to adopt a
|
||||
standard for operating over the parallel interface. This standard
|
||||
really should be one that is very universal. It should not be
|
||||
specific to tape backup units, but rather, it should be one that
|
||||
will allow software on the PC, and hardware on the other side of
|
||||
the interface that plugs into the PC, to have a reliable and simple
|
||||
communications path. Then on top of that (an interface circuit and
|
||||
a driver on the PC) you can put any kind of connection application
|
||||
you want, like a backup tape.
|
||||
|
||||
Then another standard should exist for how to command a tape backup
|
||||
unit through the above reliable simple raw data path. It should be
|
||||
workable as a modular standard, usable for tapes supporting any of
|
||||
the other QIC recording formats and data formats.
|
||||
--
|
||||
| Phil Howard, pdh@netcom.com, KA9WGN Spell protection? "1(911)A1" |
|
||||
| Right wing conservative capitalists are out to separate you from your MONEY |
|
||||
| Left wing liberal do gooders are out to separate you from EVERYTHING ELSE!! |
|
||||
+-----------------------------------------------------------------------------+
|
||||
|
||||
------------------------------
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: some general questions about linux
|
||||
Date: Fri, 23 Apr 1993 18:21:39 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
In article <lee.735583373@ceg.uiuc.edu>, lee@ceg.uiuc.edu (Chris Lee) writes:
|
||||
|> I've seen linux run on a PC, and am convinced that it's the ONLY
|
||||
|> REAL OS for PCs. I have a few general questions about linux before
|
||||
|> I make the jump.
|
||||
|>
|
||||
|> 1. How reliable is the filesystem? Do fsck and friends repair
|
||||
|> most (if not all) of the file system damage?
|
||||
|>
|
||||
|
||||
Very. I've been running the ext fs for months w/o a problem. I've heard
|
||||
ext2 and xiafs are fine too. Minix is extremely reliable as well, but
|
||||
fairly braindead.
|
||||
|
||||
|> 2. Will disk utilities like Norton Speed Disk corrupt the linux
|
||||
|> partition if run? I assume you don't really need to run a
|
||||
|> defrag program if it has a real file system.
|
||||
|>
|
||||
|
||||
It will kill the parition is no time flat. Of course, I'd be suprised
|
||||
if you could ever convince one to run on a non-dos parition anyway. If
|
||||
you do manage to somehow, report it to the company who made it
|
||||
immediately. It really should no better.
|
||||
|
||||
Many good fs do need de-fragmentors. Linux has one, and it's on
|
||||
sunsite (and I'm sure it's on other places as well).
|
||||
|
||||
|> 3. Being UN*X, I assume if you boot linux, you have to go thru
|
||||
|> the shutdown procedure. But, being dual-bootable with DOS,
|
||||
|> can you just turn the machine off if you booted DOS instead of
|
||||
|> linux? Will this damage the linux partition?
|
||||
|
||||
If you're running dos, you can just turn it off. No problems.
|
||||
|
||||
|>
|
||||
|> 4. I've seen a DOS partition mounted on linux. How accessible
|
||||
|> is the linux partition to DOS? Do you have to go thru the
|
||||
|> floppy to do that?
|
||||
|
||||
Not very accessible at all. The best way of moving a linux file to
|
||||
dos is to boot linux and "cp file /dos". Shutdown, and then boot dos.
|
||||
It'll be there when you get there.
|
||||
|
||||
|>
|
||||
|> 5. How much disk space is required for the OS, GCC, and TeX
|
||||
|> with none of the networking stuff (this is probably a FAQ)?
|
||||
|> I figure I don't really need ftp, rlogin, and telnet for
|
||||
|> a home machine.
|
||||
|
||||
I don't know - 30 meg maybe. Somewhere around there anyway. Note that
|
||||
if you do the installation by hand it'll be significantly smaller then
|
||||
the equivalent SLS installation (as SLS is VERY complete).
|
||||
|
||||
|>
|
||||
|> 6. How are printers accessed? Is it thru the parallel port or
|
||||
|> the serial port? Also, are drivers and filters available for
|
||||
|> various printers?
|
||||
|>
|
||||
|
||||
Parallel or Serial. Standard lp commands are available. The only drivers
|
||||
you should beed are for printing graphics, and TeX .dvi convertors can
|
||||
do some of it, and GhostScript can probably do the rest.
|
||||
|
||||
|> 7. What comm programs are available? Currently I just use the
|
||||
|> terminal program that came with Windows3.1 (*gag*).
|
||||
|
||||
Kermit (my favorite), Minicom, pcomm. You didn't mention X anywhere
|
||||
in this, so I'll assume you don't want to run X ones (though the comm
|
||||
progs for X are supposed to be much better)
|
||||
|
||||
|>
|
||||
|> 8. What video cards are supported? The one I saw was on a
|
||||
|> Diamond Speedstar. Does it support ATI cards? Also, I read
|
||||
|> that EISA and MCA support is not there. What about local
|
||||
|> bus video (this is probably a FAQ)?
|
||||
|>
|
||||
|
||||
MCA doesn't work. At all. Don't try it. EISA and local bus should though.
|
||||
For non-X stuff, and standard VGA card should work fine. If you don't want
|
||||
graphics at all, any EGA/VGA/MDA card works.
|
||||
|
||||
Erik
|
||||
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
When I was in school, I cheated on my metaphysics exam: I looked into
|
||||
the soul of the boy sitting next to me.
|
||||
-- Woody Allen
|
||||
Erik Troan = ewt@sunsite.unc.edu, ewtroan@vnet.ibm.com
|
||||
|
||||
------------------------------
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: 16550 uarts and .99pl8
|
||||
Date: Mon, 26 Apr 1993 13:36:44 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
In article <C5yv07.Eny@world.std.com>, nigel@world.std.com (Nigel R
|
||||
Gamble) writes:
|
||||
|> I don't have any problems with 0.99pl8 and my 16550A. But I recently
|
||||
|> read over in comp.sys.ibm.pc.hardware that the difference between a
|
||||
|> 16550 and a 16550A is that the 16550 has a bug in the FIFO which can
|
||||
|> cause repeated characters. So the question is: has anyone who knows
|
||||
|> that they have a 16550A (and not a plain 16550) seen this repeated
|
||||
|> character problem?
|
||||
|>
|
||||
|> --
|
||||
|> Nigel Gamble gamble!nigel@uunet.uu.net
|
||||
|> Boca Raton, FL, USA. uunet!gamble!nigel
|
||||
|
||||
I'm having this problem. Looking at the chip tells me its a 16550C, and
|
||||
the kernel tells me its a 16550A at bootup.
|
||||
|
||||
Erik
|
||||
|
||||
------------------------------
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: nothing lets me mount proc fs :(
|
||||
Date: Mon, 26 Apr 1993 13:43:34 GMT
|
||||
Reply-To: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
|
||||
|
||||
In article <C62MB3.Ep@r-node.hub.org>, marc@r-node.hub.org (Marc G
|
||||
Fournier) writes:
|
||||
|> Hi folks...
|
||||
|>
|
||||
|> how do I get mount to let me mount a proc fs so that I can use
|
||||
|> procps? I've tried useing the default mount that comes with the SLS
|
||||
|> dist, but it gives me a mount: error #####...I've tried downloading
|
||||
|> and compiling the mount-0.99.6.tar.z package, but it tells me that my
|
||||
|> kernel doesn't have proc fs enabled...which it most certainly does (I
|
||||
|> compiled it a second time, just in case I did make that mistake)
|
||||
|>
|
||||
|> what am I missing, please?
|
||||
|>
|
||||
|> thanks...
|
||||
|>
|
||||
|> marc
|
||||
|>
|
||||
|
||||
Try this
|
||||
|
||||
# su
|
||||
# mkdir /proc
|
||||
# mount -proc /proc /proc
|
||||
|
||||
I'd guess you're missing the mkdir part.
|
||||
|
||||
Erik
|
||||
|
||||
---------------------
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Subject: Re: [Q] Where can I find SCCS for linux
|
||||
Date: Mon, 26 Apr 1993 13:52:10 GMT
|
||||
Reply-To: ewt@sunsite.unc.edu
|
||||
|
||||
|
||||
In article <1993Apr26.040302.28468@samba.oit.unc.edu>,
|
||||
jem@sunSITE.unc.edu (Jonathan Magid) writes:
|
||||
|> In article <C5xJIv.5Dy@sci.kun.nl> wimjan@sci.kun.nl (Wim-Jan
|
||||
Hilgenbos) writes:
|
||||
|> >Hi,
|
||||
|> >
|
||||
|> >If I remember correctly I read 2 month ago something about SCCS
|
||||
|> >ported to linux. Recently we started to use it at university so
|
||||
|> >I like to have it for my linux system at home. I let archie search
|
||||
|> >for it, but all it came up with were BSD-sources. So I'm wondering
|
||||
|> >Is there a SCCS for linux? IF so where? If not so, can I use the
|
||||
|> >BSD source?
|
||||
|>
|
||||
|> sccs is available on sunsite.unc.edu in
|
||||
|> /pub/Linux/development/ver_cont/sccs.tar.Z.
|
||||
|>
|
||||
|> enjoy,
|
||||
|> jem.
|
||||
|>
|
||||
|>
|
||||
|
||||
Incredible. I just removed sccs from sunsite, get to work, fire up my
|
||||
newsreader for the first time since Friday, and there is a nice long thread
|
||||
on SCCS.
|
||||
|
||||
A note from a concerned citizen prompted me to take a look at the sccs
|
||||
distribution on sunsite (which was where jem said above). The source code
|
||||
has *no* copyright information, even though one file (sccs.c) that I looked
|
||||
at had an RCS tag indicating it was from UCB 4.2. As I have never seen
|
||||
and legitimate bsd source code without a copyright notice, this made me a
|
||||
little nervous.
|
||||
|
||||
Then I looked at the README, which said this as a port of sccs to linux
|
||||
be PALMC (People Against Large Multinational Corporations), and the
|
||||
port was done by "Bart", who apparently has no e-mail address.
|
||||
|
||||
Finally, I looked at the Makefile, which mentioned System III, but also
|
||||
had no copyright.
|
||||
|
||||
These observations and my own knowledge that SCCS was oringally written
|
||||
at AT&T and was thus owned by them prompted my to remove sccs from sunsite's
|
||||
archives this morning. If anyone has
|
||||
|
||||
a) A freely available version of sccs or
|
||||
b) Knowledge as to where this one came from
|
||||
|
||||
Please let me know so I can resolve that problem. Until I get more information,
|
||||
sccs will no longer be available on sunsite.
|
||||
|
||||
Please direct all replies and flames to email at ewt@sunsite.unc.edu.
|
||||
|
||||
Erik
|
||||
|
||||
PS: To all potential uploaders of (C) stuff: While I support linux as strongly
|
||||
as you do, I cannot allow non freely-distributable software on sunsite.
|
||||
Please don't bother uploading it, as you are oonly making my life more
|
||||
difficult and c.o.l. more noisy.
|
||||
|
||||
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
|
||||
When I was in school, I cheated on my metaphysics exam: I looked into
|
||||
the soul of the boy sitting next to me.
|
||||
-- Woody Allen
|
||||
Erik Troan = ewt@sunsite.unc.edu, ewtroan@vnet.ibm.com
|
||||
|
||||
|
||||
------------------------------
|
||||
|
||||
From: Theodore Ts'o <tytso@athena.mit.edu>
|
||||
Subject: Re: 16550 uarts and .99pl8
|
||||
Date: 26 Apr 1993 22:57:46 -0400
|
||||
Reply-To: tytso@athena.mit.edu
|
||||
|
||||
From: ewtroan@ewt.raleigh.ibm.com (Erik Troan)
|
||||
Date: Mon, 26 Apr 1993 13:36:44 GMT
|
||||
|
||||
I'm having this problem. Looking at the chip tells me its a 16550C, and
|
||||
the kernel tells me its a 16550A at bootup.
|
||||
|
||||
Don't worry about it. There are no real functional differences between
|
||||
the NS16550A, the NS16550AF, the PC16550, and the PC16550C --- indeed, I
|
||||
don't believe there is a software method for distinguishing between
|
||||
them. The only real thing that is at all important is distinguishing
|
||||
between these three cases:
|
||||
|
||||
*) NS8250 UART's (don't have a scratch register, don't have FIFO)
|
||||
*) NS16450/NS16550 UART's (don't have a FIFO -- or a working FIFO)
|
||||
*) NS16550A/NS16550AF,PC16550,PC16550C (has a working FIFO).
|
||||
|
||||
And all Linux cares about is whether or not the chip has a working FIFO
|
||||
or not --- if it does, it will print that it has a 16550A; otherwise, it
|
||||
will print that it has detected a 16550 or a 16450.
|
||||
|
||||
Note: there are actually very few NS16550's out there --- they were only
|
||||
produced for a few months before National Semiconductor realized there
|
||||
was a bug in a chip, and quickly fixed it. Most of them are in the
|
||||
first generation PS/2's, which means most Linuxer's probably won't run
|
||||
into them.
|
||||
|
||||
One thing that is confusing is that there are other chip manufacturers
|
||||
other than National Semiconductor making 16550A compatible UART's. So
|
||||
just because the chip says "16550" doesn't necessarily mean that you
|
||||
can't use its FIFO's --- take a look at what the kernel says. If the
|
||||
kernel detects a 16550A, you can probably trust its FIFO's.
|
||||
|
||||
- Ted
|
||||
|
||||
57
docs/kgb/tweedie0.txt
Normal file
57
docs/kgb/tweedie0.txt
Normal file
@@ -0,0 +1,57 @@
|
||||
|
||||
From: sct@dcs.ed.ac.uk (Stephen Tweedie)
|
||||
Subject: Re: Magic match failed!
|
||||
Date: 16 Oct 92 16:50:10 GMT
|
||||
|
||||
In article <Bw2xC1.4t5@comp.vuw.ac.nz>, Bill.Viggers@comp.vuw.ac.nz (Bill Viggers) writes:
|
||||
|
||||
> Nntp-Posting-Host: debretts.comp.vuw.ac.nz
|
||||
|
||||
> I tried using the SLS release 0.98 for the first time last night.
|
||||
> Placing the a1 disk in the drive, all proceded fine. However after
|
||||
> it said 'place root disk in the drive' things began to fail rather
|
||||
> badly. I placed the disk a2 (as this is the other rawrite'ed disk I
|
||||
> assume this is the root disk) in the drive and got a message 'magic
|
||||
> match failed', along with:
|
||||
|
||||
> magic match failed (a second time)
|
||||
> [cms-dos FS rel. alpha 8, FAT 12, check=n, conv=b]
|
||||
> [no=cxf9, cs=1, #f=2, fs=1, f1=7, ds=15, de=224, data=29, se=2400,es=0]
|
||||
> no bmap support
|
||||
|
||||
> What have I done wrong? And is it likely to be related to
|
||||
> installing a new HD on my machine?
|
||||
|
||||
> Bill
|
||||
|
||||
The "magic match failed" message is issued by the kernel when it tries
|
||||
to mount a file system and cannot find the correct header information
|
||||
for that file system on the block device.
|
||||
|
||||
When Linux mounts the root partition, it tries to look for all the
|
||||
different possible file system types on the partition in the order
|
||||
minix, extfs, dosfs. It does this by trying to mount the different
|
||||
types in that order, until one of the mounts succeeds. The messages
|
||||
you describe means that linux has mounted a DOS filing system as root
|
||||
--- the two magic match failures mean that linux has failed to find a
|
||||
minix or an extfs file system, and the rest of the blurb is the
|
||||
standard information printed out whenever linux mounts a dos file
|
||||
system.
|
||||
|
||||
I'm not familiar with SLS --- I started out with mcc-interim --- but I
|
||||
suspect that your rawritten disk should NOT have a dos file system on
|
||||
it; mounting a dos file system as root is legal, but probably not what
|
||||
was intended. Rawrite should be able to create a valid minix disk,
|
||||
completely overwriting the dos information formatted onto it by the
|
||||
dos format command. Your best bet might be to download the a2 disk
|
||||
again. Then again, I might be talking garbage... Your mileage may
|
||||
vary.
|
||||
|
||||
Good luck anyway - Who said Linux was the best thing since sliced
|
||||
bread? Sliced bread doesn't even come close!
|
||||
|
||||
Cheers,
|
||||
Stephen Tweedie.
|
||||
---
|
||||
Stephen Tweedie <sct@uk.ac.ed.dcs> (Internet: <sct@dcs.ed.ac.uk>)
|
||||
Department of Computer Science, Edinburgh University, Scotland.
|
||||
77
docs/kgb/tweedie2.txt
Normal file
77
docs/kgb/tweedie2.txt
Normal file
@@ -0,0 +1,77 @@
|
||||
|
||||
From: sct@dcs.ed.ac.uk (Stephen Tweedie)
|
||||
Subject: Re: [Q] xdm on SLS 098 doesn't work, startx does! Why?
|
||||
Date: 2 Nov 92 14:25:57 GMT
|
||||
|
||||
In article <1992Oct28.051339.7168@utstat.uucp>, rafal@utstat.uucp (Rafal Kustra (summer student)) writes:
|
||||
|
||||
> In article <coizi01.720209558@convex> coizi01@convex.zdv.uni-tuebingen.de (N. Zimmermann) writes:
|
||||
>>I have installed Linux on my 486 DX and ET4000 sucessfully. Just a
|
||||
>>few deltails won't fit in my SLS 098 distribution: X works well when
|
||||
>>started from "startx", it hangs, when started with xdm in rc. The
|
||||
>>startup screen appears, the login window comes up, but no keyboard
|
||||
>>input is possible, just bell rings when hitting any keys and I have
|
||||
>>to press CTRL ALT DEL!
|
||||
|
||||
> Ok, I had problems with xdm under Xfree86, although it worked under
|
||||
> x11v1.1. First of all, it seems, that you have getty going. You have
|
||||
> to comment out all getty's on virtual consoles in /etc/inittab (all
|
||||
> the ones on tty#). Then in rc, on the last line put: echo starting
|
||||
> xdm ... /bin/doshell /dev/tty1 /usr/X386/bin/xdm
|
||||
|
||||
That should work, but if it doesn't, you're stuck unable to get a
|
||||
virtual console. I run xdm from the inittab on /dev/tty1, and run a
|
||||
normal getty on /dev/tty2, so that if X fails I can always fall back
|
||||
to a console login. From my /etc/inittab...
|
||||
|
||||
tty1:xterm:/bin/doshell /dev/tty1 /usr/X386/bin/xdm
|
||||
tty2:console:/bin/getty 19200 tty2
|
||||
ttys1:bbcb32:/etc/getty -m 19200,9600 ttys1
|
||||
|
||||
Cheers,
|
||||
Stephen Tweedie.
|
||||
|
||||
PS. Is this in the FAQ yet?
|
||||
---
|
||||
Stephen Tweedie <sct@uk.ac.ed.dcs> (Internet: <sct@dcs.ed.ac.uk>)
|
||||
Department of Computer Science, Edinburgh University, Scotland.
|
||||
|
||||
------------------------------
|
||||
|
||||
From: sct@dcs.ed.ac.uk (Stephen Tweedie)
|
||||
Subject: Re: Bugs in LINUX tar (?)
|
||||
Date: 5 Nov 92 17:28:37 GMT
|
||||
|
||||
In article <Bx8G3M.DBE@news.cso.uiuc.edu>, jy10033@ehsn11.cen.uiuc.edu (Joshua M Yelon) writes:
|
||||
|
||||
> Last night I switched from minix FS to ext FS. Here are the steps I
|
||||
> went through:
|
||||
|
||||
> * tarred my whole filesystem using gnu tar, split tarfile onto
|
||||
> floppies. * reformatted hard disk using mkefs. * reloaded software
|
||||
> from floppy using the tar on the 0.98 rootdisk.
|
||||
|
||||
> Much to my chagrin, though, the tar on the root floppy didn't seem
|
||||
> to quite understand the tarfile format: it loaded the files up ok,
|
||||
> and got all the chmod bits right, but got most of the file
|
||||
> ownerships wrong! Needless to say, this took a long time to fix.
|
||||
|
||||
> It may be important that I use UID's greater than 1000... although
|
||||
> I can't see why that would be a problem, it IS unusual.
|
||||
|
||||
First of all, you should be using the -p (set permissions) option to
|
||||
tar; although if you say the mode bits are correct, you're probably
|
||||
doing this anyway.
|
||||
|
||||
The problem with ownership is that when you boot from the root floppy,
|
||||
you are no longer using the passwd and group files from your tarred
|
||||
root partition. So, all those users and groups who should own the
|
||||
files you are restoring simply don't exist at the time of the restore.
|
||||
You should copy the original /etc/passwd and /etc/group files into
|
||||
/etc on the root floppy before extracting the tar archive.
|
||||
|
||||
Cheers,
|
||||
Stephen Tweedie.
|
||||
---
|
||||
Stephen Tweedie <sct@uk.ac.ed.dcs> (Internet: <sct@dcs.ed.ac.uk>)
|
||||
Department of Computer Science, Edinburgh University, Scotland.
|
||||
Reference in New Issue
Block a user