Subject: Linux-Development Digest #868
From: Digestifier <Linux-Development-Request@senator-bedfellow.MIT.EDU>
To: Linux-Development@senator-bedfellow.MIT.EDU
Reply-To: Linux-Development@senator-bedfellow.MIT.EDU
Date:     Wed, 29 Jun 94 04:13:04 EDT

Linux-Development Digest #868, Volume #1         Wed, 29 Jun 94 04:13:04 EDT

Contents:
  Limiting Telnet (Allan Alford)
  Re: Hard disks limited to 16 heads? (David Monro)
  Re: Patches for Linux port of db.1.73 (Berkeley db library) (Neal Becker)
  Is DAT surported on Linux? (DL83-08)
  1.1.23 floppy driver broken on my notebook (Andrew Gallatin)
  Re: Quirky idea: Remote V (Byron A Jeff)
  Re: Quirky idea: Remote Virtual Consoles (Byron A Jeff)
  Re: Novell NCP Documentation Available! (was Re: IPX Netware Protocol) (Barry Lynam)
  Re: Disk-compression for Linux (Eberhard Moenkeberg)
  Re: 1.1.23 floppy driver broken on my notebook (Klaus Schneider)
  Re: Linux ext2fs vs. ufs vs. presto was Re: Fast File System? (Vince Fleming)
  Kenrel hacking tips (maizeli@md2.huji.ac.il)
  Re: computer science (Daniel J. Carreira /ADVISOR Clay)
  Re: System lock ups: NCR 53c810 driver problem? (Lars Heinemann)
  Re: I've found a bug in tcsh (R. D. Thomas)

----------------------------------------------------------------------------

From: chiphead@actlab.rtf.utexas.edu (Allan Alford)
Crossposted-To: comp.unix.questions,fj.os.linux
Subject: Limiting Telnet
Date: 28 Jun 1994 21:32:01 GMT

I have the Slackware source code for telnet.

I need to create a limited version which allows
2 of my users (guest accounts) to ONLY telnet
to one other node on my net...

They shouldn't be able to use 'telnet <args>'
or 'telnet> open <args>' to get anywhere.

I have two choices:

1) Make one telnet for everyone, and scan for
user name...

2) MAke a separate guest-only telnet which returns
a simple script whenever destination is NOT the one
destination needed....

I think 2 will be easier.  I have a strong programming
background, but don't know C on UNIX yet.

Where do I start?

Open up main.c or telnet.c?

Which variable am I looking for to set destination
(both from unix prompt AND telnet prompt)...

ANY AND ALL HELP WILL BE APPRECIATED!  THANKS!

chiphead@actlab.rtf.utexas.edu























































------------------------------

From: davem@extro.ucc.su.OZ.AU (David Monro)
Subject: Re: Hard disks limited to 16 heads?
Date: Mon, 27 Jun 1994 05:46:57 GMT

onno@stack.urc.tue.nl (Onno Hovers) writes:

>Oystein H. Olsen (Biology) (oystein@bimcore.emory.edu) wrote:
>> I have a 540 Mb hard disk from Dell that is configured for 32 heads,
>> 524 cylinders, and 63 sectors. The kernel complains about using more
>> than 16 heads and cannot use the drive. I then reduced the heads to 16
>> and doubled the cylinders to 1028. Now, fdisk and several programs at 
>> boot complain about using more than 1024 cylinders. The warning says that
>> some program might crash. Fdisk also display odd boundary messages. Reducing
>> the cylinders to 942 and increasing sectors to 70 generates complaints about
>> using more than 63 sectors....

>> So, back to the initial problem, why does the kernel (hd.c) limit the number
>> of heads to 16?
>This is a limitaition of the BIOS. There is a standard called "enhanced IDE"
>that should solve those problems. I don't if there is support for this
>standard in linux. Anyway, you should try to format your harddisk under the
>following settings:
>  cylinders: 1024 
>  heads:     16
>  sectors:   63
>This should get you the maximum of space that's available. Only SCSI
>harddisks can have more space. 

Oops, I meant to post the mail I just sent. Oh well, here we go again.

This isn't actually true - on my system the bios will let me put anything
I want for heads, cylinders, sectors. So I use 1048 cylinders, 16 heads
and 63 sec/track. I get warnings from fdisk for 2 reasons:

1) The number of cylinders is > 1024
2) The end of the last partition is at physical cylinder 24 according to
the partition table (this is because 1048 missin the high bit comes out
as 24).

I have yet to see a problem with this setup though, and I've been using
the drive pretty solidly for the last 6 months. (Except that now the
drive is on a secondary controller, so the bios doesn't know about it
anymore).

There are a couple of caveats, though -
1) Dos may scream. It will certainly scream if you try and create a dos
        partition which includes the last 24 cylinders.
2) Make sure the partition wich holds the boot kernel image is completely
        within the first 1024 cylinders, otherwise the bios may not be
        be able to load the kernel!
3) There are apparenly some bioses out there that won't let you tell them
        that there are 1048 cylinders, and will attempt to force the
        32 heads config on you. This is bad news. Chris Metcalf may know
        more than I do about that situation (metcalf@catfish.LCS.MIT.EDU).
        Unfortunately I have lost his posting and mail on the issue.

Good luck,
        David Monro


>> Oystein Haug Olsen
>> oolsen@biology.emory.edu

>Regards,

>--
>------------------------------------------------------------------------------
>    /-------/       / | Onno Hovers [IRCNICK=arrow]
>   /       /-------/  | 2nd Year student Physics  
>  /       /-------/   | email:  onno@stack.urc.tue.nl
> /-------/       /    | tel. :  013-676622
> Ask for OHware (TM)  | addr.:  Wandelboslaan 105, 5042 PC Tilburg, Nederland 
>------------------------------------------------------------------------------
>All animals are equal, but some animals are more equal than others--G.Orwell  

------------------------------

From: neal@ctd.comsat.com (Neal Becker)
Subject: Re: Patches for Linux port of db.1.73 (Berkeley db library)
Date: 27 Jun 1994 20:20:18 GMT

I just grabbed db.1.79 from Berkeley, and I see linux is already
there.  I haven't tried it yet though.

------------------------------

From: s21008@cc.ntnu.edu.tw (DL83-08)
Subject: Is DAT surported on Linux?
Date: Tue, 28 Jun 1994 16:00:00 GMT

I have a DAT with a tar file, which I would like to transfer to floppies. My
friend has a WangDAT, so I figured I could use the Slackware install
floppies which contain tar on the root floppy, and just tar -M it onto
floppies. Problem is, how do I access the DAT (SCSI 2GB 1/4" WangDAT). Is
there another way of doing this, perhaps? Anyone with experience?

--

 /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
%v  Curtis Dean Smith                      Internet: s21008@cc.ntnu.edu.tw   |
0j  Institute of Chinese Language & Literature                               |
?3  National Taiwan Normal University            Bitnet: NTNUS239@TWNMOE10   |
 \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

------------------------------

From: gallatin@duke.edu (Andrew Gallatin)
Subject: 1.1.23 floppy driver broken on my notebook
Date: 28 Jun 1994 16:39:49 GMT

I just built & installed 1.1.23 and noticed that the floppy driver is
broken.

Symptoms: Doing an 'mdir a:' or a 'mount -t msdos /dev/fd0H1440 /mnt'
or even a dd on /dev/fd0 will all result in the process spinning both
the hard & floppy drives, & the machine almost hanging.  By almost, I
mean the process is in a D wait, the drives are spinning, and it takes
a few minutes to get any kind of response from the machine.  Shutdown
fails.

The machine is an Acom VESA-4000 Notebook.  Its got a single 3.5"
floppy.  The Bios tells me:

486DX266 Modular BIOS V3.20-00mD 
Copyright(c)1984-1990 Award Software Inc."
Notebook

I still had the 1.1.11 source tree sitting around, and simply compiled
in the floppy.c file & that seems to have fixed things.

Drew

##############################################################################
#               Andrew Gallatin, System Administrator                        #
#           Institute of Statistics and Decision Sciences                    #
#         Box 90251, Duke University, Durham, NC 27708-0251                  #
#                   email:  gallatin@isds.duke.edu                           #
##############################################################################

------------------------------

From: byron@gemini.cc.gatech.edu (Byron A Jeff)
Subject: Re: Quirky idea: Remote V
Date: 28 Jun 1994 21:03:37 GMT

In article <1.9832.2382.0N27D264@dscmail.com>,
John Will <john.will@dscmail.com> wrote:
>BR>I meant for it to support multiple VC's. In fact if it worked properly
>BR>it would look and act exactly like the Linux console.
>
>Sounds like SCREEN...

OK. I'll buy that. Screen is a start. However Screen runs on the server.
Since we're talking about PC's with local processing I'd want much of the
app to run on the RVC. In addition I want the same keys, mouse, and graphics
that I get with the real console.

Nothing already does what I want. Some are closer than others though.

BAJ
-- 
Another random extraction from the mental bit stream of...
Byron A. Jeff - PhD student operating in parallel - And Using Linux!
Georgia Tech, Atlanta GA 30332   Internet: byron@cc.gatech.edu

------------------------------

From: byron@gemini.cc.gatech.edu (Byron A Jeff)
Subject: Re: Quirky idea: Remote Virtual Consoles
Date: 28 Jun 1994 21:07:29 GMT

In article <WSLEE.94Jun27164514@almond-frost.ai.mit.edu>,
Whay S. Lee <wslee@ai.mit.edu> wrote:
>
>In article <2ula4n$m0c@netaxs.com> sto2@netaxs.com (Brian Stoler) writes:
>>
>       Can't you already do that by:
>
>            1. hook up the low-end machine to the linux 
>              box via a serial port
>           2. run "iscreen" or "pcucp"

1) Graphics?
2) Same keybinding as the keyboard attached to the Linux box?
3) Mouse/selection support?

No you can't already do it.

Let me try again. I want an application that runs on Sub Linux class PC's
that will give you a screen, keyboard, and mouse that looks and acts 
EXACTLY (no approimations allowed) like the screen, keyboard, and mouse
that's attached to the Linux box.

Also Ethernet is the only way to go here.

Later,

BAJ
-- 
Another random extraction from the mental bit stream of...
Byron A. Jeff - PhD student operating in parallel - And Using Linux!
Georgia Tech, Atlanta GA 30332   Internet: byron@cc.gatech.edu

------------------------------

From: lynam@qut.edu.au (Barry Lynam)
Subject: Re: Novell NCP Documentation Available! (was Re: IPX Netware Protocol)
Reply-To: B.Lynam@qut.edu.au
Date: Mon, 27 Jun 94 05:13:35 GMT

In article <1994Jun20.234835.23712@kf8nh.wariat.org>,
bsa@kf8nh.wariat.org (Brandon S. Allbery) writes:
|> In article <2u4tr4$3bq@magus.cs.utah.edu>, kruckenb@sal.cs.utah.edu
|> (Pete Kruckenberg) says:
|> +---------------
|> | By any chance, has anyone tried to implement NCP using the
|> information
|> | in Pawel Szczerbina's article in Dr. Dobbs on Novell's NCP
|> | ("Undocumented Corner: Novell's Netware Core Protocol", Dr. Dobbs,
|> +------------->8
|> 
|> Yes.  The information is reportedly buggy and incomplete, but I think
|> it's
|> being used as a starting point to "black-box" a working NCP layer.
|> 
|> ++Brandon
|> -- 
|> Brandon S. Allbery      kf8nh@kf8nh.ampr.org          bsa@kf8nh.wariat.org
|> Friends don't let friends load Windows NT.           Linux iBCS2 emulation

I also remember something about Lantastic being the same as Netware and
there are details of how it works. This was a few years ago and I may be
mistaken but it could be worth looking at.

barry

-- 
+------------------------------------------------------------------+
| Barry Lynam                           EMail:  B.Lynam@qut.edu.au |
| Communications - Network Services     Phone:  +61 7 864 2883     |
| Computing Services                    Fax:    +61 7 864 1343     |
| Queensland University of Technology   Postal: GPO Box 2434       |
| Brisbane AUSTRALIA                            Brisbane 4001      |
|                                               AUSTRALIA          |
|--"I may not agree with your argument, but I'll defend your ------|
+---right to express it"-------------------------------------------+


------------------------------

Date: Mon, 27 Jun 1994 00:35:35 +0200
From: Eberhard_Moenkeberg@p27.rollo.central.de (Eberhard Moenkeberg)
Subject: Re: Disk-compression for Linux


Hello R. Schalk and all others,

on 26.06.94 R. Schalk wrote to All in USENET.COMP.OS.LINUX.DEVELOPMENT:

RS> Something new:

No. It is not new.

RS> I really think that a compressed filesystem would speed-up a CD-ROM.
RS> On a bigger issue: wouldn't it be nice that iso9660 would be superceded
RS> by a compressed filesystem. This way it's cheaper getting faster access
RS> than buying double, triple or quadruple speed drives. This would be good
RS> for all systems. Maybe this way it's possible (with reosonable speed) to
RS> run Linux from CD-ROM. It would make it easier for people to try Linux
RS> for the first time.

Adam J. Richter has already managed this on his YGGDRASIL "plug & play Linux"
CD. And - for compatibiltity - he uses the "standard" gzip, so you can
have access to his files on any system!

But a second limiting factor with CDROMs is the positioning time.

Greetings ... Eberhard


------------------------------

From: uk0q@rzstud1.rz.uni-karlsruhe.de (Klaus Schneider)
Subject: Re: 1.1.23 floppy driver broken on my notebook
Date: 28 Jun 1994 17:15:48 GMT

Andrew Gallatin (gallatin@duke.edu) wrote:
: I just built & installed 1.1.23 and noticed that the floppy driver is
: broken.

Although I have different symptoms than Andrew mentioned, it seems the
floppy driver is broken in 1.1.23 for me, too.

I tried to build a new boot disk and after the floppy started working
I got messages like

        floppy I/O error
        dev 0200, sector 470
        Reset-floppy called

for every other sector.  I have tried this about 10 times, half of it
with older kernel versions I still have "in stock" and I was able to
built the bootdisk every time with older kernels and _never_ with
1.1.23 (all with the same disk).

Klaus
===============================================================================
Klaus Schneider                         Email: root@ks1i486.dialup.xlink.net
Student of Informatics                         uk0q@rzstud1.rz.uni-karlsruhe.de
University of Karlsruhe, Germany               klsc@delphi.com
===============================================================================


------------------------------

From: vince@vtci.com (Vince Fleming)
Crossposted-To: comp.sys.sun.admin
Subject: Re: Linux ext2fs vs. ufs vs. presto was Re: Fast File System?
Date: 28 Jun 1994 21:01:11 GMT

Callum Gibson (callum@frost.bain.oz.au) wrote:
: Nigel Gamble (nigel@gate.net) wrote:
: > If you are concerned about power failure, the way to survive with
: > no corruption and no performance hit is to use a UPS.  Why would you
: > want to put any performance hit in the filesystem when there is a
: > better way to address the power fail problem?

: Then you could do as our sys admin did and trip over the power cord between
: the ups and the computer. (sorry Glenn). :-)

Then you could kick youself and buy a system with an *internal* UPS. ;-}

[on a serious note, the larger AT&T/NCR have this as an option for that 
very reason]



------------------------------

Subject: Kenrel hacking tips
From: maizeli@md2.huji.ac.il
Date: 28 Jun 94 20:09:15 IST



I have been peeking into the linux kernel for a few days, and I find it
very interesting. I have good knowledge of 386 protected mode assembly and PC
hardware peripherels (been working with MS-DOS alot, and got to know it too
good inside, so I thought about switching to UNIX kernel hacking).

I had no trouble at all getting familier with the low-level stuff. However
other parts are a bit harder, especially becuase I simply do not know what the
code is SUPPOSED to do... Am looking for any tips where to find more
information about Linux's operation; what header files to read first, what
parts to ignore at first, etc...

And another thing, are the POSIX specificiations freely available, or if I pu
it another way, how can I get it?


Thanks in advance,

Yossi


------------------------------

From: rcs79343@cs.fit.edu (Daniel J. Carreira /ADVISOR Clay)
Subject: Re: computer science
Date: Tue, 28 Jun 1994 04:22:55 GMT

<every thing deleted>

As someone said the embedded environment may be the way to go that
way you can leverage you EE experience.  Also you might consider
getting some DSP expericnce / course work.  While finding DSP
work might be harder than general CS work it might pay better. I
see a lot of DSP work comming up..

just my $.02

--
D. Carreira           | The difference between a sufficiently advanced
rcs79343@.cs.fit.edu  | technology and magic is indistinguishable.
(407) 725-0251        | A.C. Clark -- Its magic. My Mom.


------------------------------

From: lars@fb17isun.uni-paderborn.de (Lars Heinemann)
Subject: Re: System lock ups: NCR 53c810 driver problem?
Date: 28 Jun 1994 19:58:45 +0200

Hello!

In <SO5PB9WF@gwdu03.gwdg.de> Lutz.Pressler@Unix.Med-Stat.GWDG.DE (Lutz Pressler) writes:

->Hello,

->first of all many thanks to Drew Eckhardt for writing the NCR PCI driver.
->I'm afraid I have to report some kind of (disturbing) bug though:
->with the NCR chip enabled and that driver, the system sometimes (quite
->often :() locks up totally. That does not happen with an Adaptec 1542B.

[stuff deleted]

->Symptoms:

->When working under X (haven't able to reproduce it without someone using
->X on console, it's started anyway (xdm), sometimes the system totally locks
->up: no keyboard reaction (incl. alt-cntrl-del) , no login via IP,
->mouse cursor is garbage.
->The only "cure" is pressing reset button or using power switch, hoping that
->the file systems are usable afterwards...
->That (mostly) happens when starting a program, sometimes that's the first
->xterm to start, sometimes it's under load >5 (gcc compiling kernel, 2 emacs
->running haoin, gnuchess playing machine-machine, etc... that was a test..)
->Because of the 32 MB RAM even in the latter situation swapspace (almost)
->wasn't touched.

I have the same problems with my Asus mainboard (486dx2/66).
The system locks up when starting first xterm or later running
commands like xv. Without X11 it works perfect (compiled emacs,
linux-kernel and both at same time, no problem).
So i'm now using my AHA1542b :(

Bye, Lars
-- 
    ____
   / / /_   Lars Heinemann              Tel.:   Q/F  049 05251 25647
  / /   /   lars@uni-paderborn.de       Adress: Geroldstr. 20   
 /_/_/_/    University Of Paderborn             33098 Paderborn, Germany

------------------------------

From: rdt@kaiwan.com (R. D. Thomas)
Subject: Re: I've found a bug in tcsh
Date: 27 Jun 1994 15:15:44 -0700

In article <2um060$lop@harbinger.cc.monash.edu.au>,
Stuart Cunningham <shcun1@aurora.cc.monash.edu.au> wrote:
>  I have a script which makes makefiles.  It occasionally appends a
>space, backslash, newline to the makefile so dependency lists can be
>split up over many lines.  It does this by the following csh command:
>       echo ' \' >>! $Makefile
>
>surprisingly, when I ran this script under linux's tcsh (from the
>slackware distribution), instead of appending " \", it appended a space
>then ASCII zero.  When I changed the line to:
>       echo ' \ ' >>! $Makefile
>the result was as expected (space, backslash, space). 
>  Has anyone noticed this before? Who should be notified about fixing
>it?
>
>  Stuart Cunningham

  This isn't a tcsh bug, Stuart.  In order to do what you wnat you really should
be using:
       echo ' \\' >>! $Makefile
Note the double backslash.

-- 
===========================================================================
                                                             rdt@kaiwan.com
===========================================================================

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: Linux-Development-Request@NEWS-DIGESTS.MIT.EDU

You can send mail to the entire list (and comp.os.linux.development) via:

    Internet: Linux-Development@NEWS-DIGESTS.MIT.EDU

Linux may be obtained via one of these FTP sites:
    nic.funet.fi				pub/OS/Linux
    tsx-11.mit.edu				pub/linux
    sunsite.unc.edu				pub/Linux

End of Linux-Development Digest
******************************
