Subject: Linux-Development Digest #861
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:     Sun, 26 Jun 94 22:13:06 EDT

Linux-Development Digest #861, Volume #1         Sun, 26 Jun 94 22:13:06 EDT

Contents:
  Re: ??? curses ??? (Zeyd M. Ben-Halim)
  Re: Where has Stephen Tweedie gone?? (Remy CARD)
  Re: NFS file locking: writing or porting 'lockd' (jdrumm on BIX)
  Re: Linux game development (Was Re: Why [DOS, W (Steffen W. Schilke)
  Re: DIP and 'hanging' IOCTL call: Help! (Christian Holtje)
  Re: svgalib and s3 (Felix v.Leitner)
  Re: DOSEMU and Novell (Rob Janssen)
  Re: Quirky idea: Remote Virtual Consoles (Rob Janssen)
  DIP and 'hanging' IOCTL call: Help! (fox@otago.ac.nz)
  Re: svgalib and s3 (Christian Holtje)
  Re: more breakage under 1.1.21 (rlogin xterms freeze up until being reset) (Hubert Weikert)
  IBM Token Ring skeleton driver available (Mark Swanson)
  Re: svgalib and s3 (Christian Holtje)
  Re: Runtime compilation and execution (Ken Pizzini)
  Re: IBM Token Ring skeleton driver available (Thomas Bogendoerfer)

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

From: zmbenhal@netcom.com (Zeyd M. Ben-Halim)
Subject: Re: ??? curses ???
Date: Fri, 24 Jun 1994 20:22:30 GMT

In article <1994Jun23.220838.1@orion.alaska.edu>,
 <atkkh@orion.alaska.edu> wrote:
>curses and ncurses, what are they? how do I use them?

The former is the original BSD library, the latter is a clone of SYSVR4
curses and offers many more functions. See the docs that come with ncurses
for more info.

Zeyd

-- 
---
Zeyd M. Ben-Halim       zmbenhal@netcom.com
10479 1/4 Santa Monica Blvd, LA, CA, 90025 (310) 470-0281

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

From: card@masi.ibp.fr (Remy CARD)
Subject: Re: Where has Stephen Tweedie gone??
Date: 26 Jun 1994 20:07:48 GMT

In article <RSANDERS.94Jun23000310@hrothgar.mindspring.com>,
Robert Sanders <rsanders@mindspring.com> wrote:
] I think his job's gotten extremely busy; at least that's the rumor.
] Also, Stephen spent a lot of time chasing and fixing a couple of
] long-lived subtle bugs in all the Linux filesystems, and that's
] exactly the sort of unrewarding work that will put someone off
] volunteer work for a while.

        I can't speak for Stephen but I think that he is overloaded with
work and could not work much on the Linux kernel during the last months.

] Stephen's a great guy, but he's not the only one of us who's capable
] of writing a compressed filesystem.  If you really want to see, and
] you're a competene programmer, here's your chance to learn a lot about
] kernel internals.

        You're right but any volunteer should check with Stephen by e-mail
to avoid duplicating efforts, just in case.

] Well, Remy Card recently said that as soon as he could get the code
] for anon. ftp, he'd work at porting it.  I think this may require some
] enhancements to Linux's VFS, among other things, so it's likely to be
] a big project; I'm sure Remy would appreciate some help.  As for when
] 4.4BSD will be available for anon. ftp, nobody seems to want to make
] it available because of the guaranteed ftp storm.  FreeBSD will
] probably have some of the 4.4BSD code incorporated soon (they have to
] because of the USL lawsuit), but there's no telling when.  Several
] months, at least.

        I already have LFS since it is now included in NetBSD current.
I have taken a look at the LFS code and porting it to Linux is far from
trivial.  Like FFS, LFS relies on the BSD VFS and buffer cache features
and there is a lot of work to do to make it fit in the Linux kernel.

        BTW, I have been overloaded with work too (actually, the whole
set of ext2fs programmers have been recently :-() and I won't be able to
work on it in the next weeks (next week is the Linux Conference in
Heidelberg and I had to work a lot to prepare the FS presentations).

        After I come back from Germany, I will look into LFS again and
I'll try to incorporate it in Linux.

]   -- Robert

                Remy

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

From: jdrumm@BIX.com (jdrumm on BIX)
Subject: Re: NFS file locking: writing or porting 'lockd'
Date: 24 Jun 94 22:37:50 GMT

sims@usa.acsys.com (dave sims) writes:

>Hi again.  We have a few Linux boxes here at work connected by a
>network running NFS.  We need to lock and unlock NFS mounted files.
>Unfortunately, the lock daemon 'lockd' that resides on Suns doesn't
>exist on Linux.

>Anyone else interested in writing 'lockd' for Linux?  Since my
>employer is interested in it, I could be available to work on it full
>time.  Any other suggestions?

help\
I'm in the same situation, and am very interested
in any solution(s) you come up with.  If you want
any help porting, contact me via e-mail.  

Joe
jdrumm@bix.com

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

From: sws@tora.RoBIN.de (Steffen W. Schilke)
Subject: Re: Linux game development (Was Re: Why [DOS, W
Date: Sun, 26 Jun 1994 15:24:07 GMT

David Luyer (luyer@tartarus.uwa.edu.au) wrote:
: James Ojaste (jojaste@undergrad.math.uwaterloo.ca) wrote:
: : In article <2skp6o$r1@styx.uwa.edu.au>, I wrote:
: : >[my pointless ramblings deleted] ... Linux requires
: : >minimum 4meg (don't say 2meg,I've tried it) of memory for itself.

: : OK.  I won't mention that our CSC (Computer Science Club) has a 386
: : (donated in parts), with 2M ram, 52M hard disk, running Linux, and
: : playing samples over a DAC whenever a door is closed, or the lights are
: : turned on.  2M is fine for this purpose - but Linux doesn't require more.

Someone has read the Hitchhikers Guide to often ? ;-)

--
[Standard Disclaimer] in addition I would like to speak with my lawyer ....
S. Schilke; PoBox 1213; 61102 Bad Vilbel; Germany  a.k.a  sws@tora.RoBIN.de
                  Sokonoke Sokonoke tora-sama ga touru
$@%9%F%U%'%s(J  $@CN2H!Z%7%k%1![(J  $@$=$3$N$1$=$3$N$18WMM$,DL$k(J
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

From: choltje@ux1.cso.uiuc.edu (Christian Holtje)
Subject: Re: DIP and 'hanging' IOCTL call: Help!
Date: 26 Jun 1994 22:28:28 GMT

fox@otago.ac.nz writes:

>Hay all,

>for the last 6 weeks I have been trying to get DIP-3.3.7b-uri to work.
>I have now upgraded to Kernel 1.1.21, and Dip-3.3.7b-uri.

[stuff about wierd dip bug where script commands work if entered manually
 but not when using it as a script]

>Is there anybody out there who can shine a light on this weird problem????

>HELP!

>Bart Kindt, Dunedin, New Zealand

I used to have these problems a lot. I think it was the version of dip I
was using. Since I'm not very good at C I asked about (this was in the
.99.7 days) it and someone sent me a binary. I've been using it ever since.
I had (just today) put up a nice little package with my version of dip and
route, but if this doesn't help any post again. Maybe someone can help.
As for the ioctl call, I'm not sure, but I think that that is the part
of the program where is just sits and becomes a daemon...but I'm not sure.
Also, with the newer kernels(at least 1.1.2[0-1]) there is something wierd
done to slip. But I'm using 1.1.22 with no problems...

The slip package is:
slipstuff.tgz on sunsite....Today it is in /pub/Linux/Incoming....
tomorrow? Who knows.

        -Doc
-- 
    ---     ---     ---   -      -  -  -   ---  -----  docwhat@uiuc.edu
   +   -  +    -  +      +      +  -  +  -   +   -    CS major at Illinois
  *   +  *    +  *      *  +   *  +*+*  +*+*+   *    --- finger me at ---
 ****     ***     ***   **  **   *  *  *   *   *    choltje@ux1.cso.uiuc.edu

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

From: leitner@cs.tu-berlin.de (Felix v.Leitner)
Subject: Re: svgalib and s3
Date: 26 Jun 1994 20:26:08 GMT

choltje@ux1.cso.uiuc.edu (Christian Holtje) writes:

>>Hi, I was wondering if anyone has patched the s3 code in svgalib
>>to work with an s3 805 card.  The source says it's only been used on
>>a 911 chip :(.  

>>It seems so close.... anyone have a pointer to docs on the 
>>s3 chips?

>Just as a two center. I'd really LOVE to either have svgalib support
>VESA (bleech) or S3....just so I can write some stuff for it...(anyone
>like Car Wars :)

I think the S3 is not the problem, the RAMDAC is.

BTW: Are you seriously about that VESA thingy ?  I hope you know that this
is impossible and really makes you look like either a clueless beginner or
a comedian ;)
Well, OK, not impossible. But nearly.

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

Crossposted-To: comp.os.linux.help
From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: DOSEMU and Novell
Reply-To: pe1chl@rabo.nl
Date: Sun, 26 Jun 1994 21:24:41 GMT

In <2uk02uINN1q2@xs4all.hacktic.nl> barryl@xs4all.hacktic.nl (barryl) writes:

>Maybe a little off topic, but it is not necessary to use 2 ethernet cards 
>: you can change the built-in node-address by changing the NET.CFG :

>link driver NE2000
>  NODE ADDRESS=123456789ABC

>Barry.

But that won't work from dosemu, and that was what we were talking about.
Off topic, indeed...

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: Quirky idea: Remote Virtual Consoles
Reply-To: pe1chl@rabo.nl
Date: Sun, 26 Jun 1994 21:26:24 GMT

In <2uk9vl$e20@solaria.cc.gatech.edu> byron@gemini.cc.gatech.edu (Byron A Jeff) writes:

>I've noticed that there are bunches of PC's that cannot run Linux.
>Mostly 286's and early 386's with insufficient memory.

>They don't have enough memory or horsepower to be used as remote X terminals.

>However I find that having a remote console for a Linux box an interesting
>idea.

>This idea came to mind primarily because of DOSEMU. One might say "Well you
>can just run DOS on the machine, or telnet to the Linux box". Well with the
>first you don't have access to the Linux filesystems (except via the public
>Domain NFS and/or Lanmanager clients) and you can't easily run multiple
>instances of applications. See I run DOSEMU remotely much of the time. The
>problem is that with terminals and X windows, key bindings prove to be
>difficult. However I've found that things go rather well when the remote
>terminal I use is the console of another Linux box. The Alt and function
>keys work as expected and it should be possible to get the same console-like
>display on a remote console as it is on the native one.


>So I was thinking if it were possible to write a application that acts as
>an additional virtual console for a Linux box that I could press the low
>memory, low CPU machines I have access to into service. 

>Any thoughts?

Yes, that is certainly possible.  In fact, this is how Linux started :-)

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

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

From: fox@otago.ac.nz
Subject: DIP and 'hanging' IOCTL call: Help!
Date: Sat, 25 Jun 1994 00:47:44 GMT

Hay all,

for the last 6 weeks I have been trying to get DIP-3.3.7b-uri to work.
I have now upgraded to Kernel 1.1.21, and Dip-3.3.7b-uri.

I can start dip from the command line, e.g. dip -t, entering the relevant
information, and all works Okay.
But when I try to use 'diplogin' (e.g. dip -i), the dip program reports all
IP stuff etc okay, and ever starts the SLIP, *but* it does not execute the
Route and Ifconfig commands. 
Hacking the source code, I discovered that dip calls a Kernel command:
'ioctl', to start the SLIP on the serial line, but it DOES NOT RETURN from
this call. It simply stays there, without any errors, but the dip program
DOES continue, and the SLIP is actually executed. If I enter the Route
and Ifconfig command manually, it works.

How is it possible that a call to IOCTL does not return at all?


The problem is in the file TTY.C, the function tty_set_disc:

tty_set_disc(int disc)
{
  if (disk == -1) disk = tty_sdisk;

  if (ioctl(tty_fd, TIOCSETD, &disc) < 0) {
  syslog(LOG_ERR ........
  fprintf(sterr, .................
  return(-errno);
  }
  printf("all ok!/n");
}

Not one of the above commands is executed, not the 'error' commands or the
'all ok' command. The system simply stays in ioctl. I am a Pascal programmer,
and have no experience with C, but this looks realy very strange to me!

I have been trying to get Uri to help, but he is to busy at the moment,
and thinks that I must be doing something wrong... But what?

I have tried Kernels 1.0.8, 1.1.19, 1.1.20, 1.1.21. No change.
I am using  AGETTY, bu have also tried GETTY, both supplied with Slackware.
No change.

Note that the above commans DO WORK if DIP is started in the -t mode!

Is there anybody out there who can shine a light on this weird problem????

HELP!

Bart Kindt, Dunedin, New Zealand


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

From: choltje@ux1.cso.uiuc.edu (Christian Holtje)
Subject: Re: svgalib and s3
Date: 26 Jun 1994 21:42:55 GMT

leitner@cs.tu-berlin.de (Felix v.Leitner) writes:

>choltje@ux1.cso.uiuc.edu (Christian Holtje) writes:
>>Just as a two center. I'd really LOVE to either have svgalib support
>>VESA (bleech) or S3....just so I can write some stuff for it...(anyone
>>like Car Wars :)

>I think the S3 is not the problem, the RAMDAC is.

>BTW: Are you seriously about that VESA thingy ?  I hope you know that this
>is impossible and really makes you look like either a clueless beginner or
>a comedian ;)
>Well, OK, not impossible. But nearly.

I'm new to graphics programing, but even if VESA is bleechy and slow and ugly,
it is more portable. Why would it be impossible? And yes, I'd prefer being
able to use the S3 chip. Why is the RAMDAC a problem? Isn't the code similar
to what is used in XFree?

        -(Not willing to rule out the possiblility of being clueless) Doc
-- 
    ---     ---     ---   -      -  -  -   ---  -----  docwhat@uiuc.edu
   +   -  +    -  +      +      +  -  +  -   +   -    CS major at Illinois
  *   +  *    +  *      *  +   *  +*+*  +*+*+   *    --- finger me at ---
 ****     ***     ***   **  **   *  *  *   *   *    choltje@ux1.cso.uiuc.edu

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

From: weikert@salyko.cube.net (Hubert Weikert)
Subject: Re: more breakage under 1.1.21 (rlogin xterms freeze up until being reset)
Date: 24 Jun 1994 16:13:30 GMT

Jonathan King (king@cogsci.ucsd.edu) wrote:
> to a remote host; also, he did a "make clean" when he compiled
> 1.1.21).  It's possible that 1.1.20 also would have done this, but

'make clean' isn't sufficient, .depend files are not removed.  You
should use 'make mrproper' to clean up all, especially if you step up to
a new patchlevel. 

Hubert

--
Hubert Weikert    DB1MQ    weikert@cube.net
CIS: 100034,374  weikert@muninn.sta.sub.org 


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

From: mswanson@borg.ott.ca (Mark Swanson)
Subject: IBM Token Ring skeleton driver available
Date: 24 Jun 1994 18:24:32 GMT

Awhile back - (long) I wrote an IBM Token Ring device
driver capable of working with ANY IBM token ring card 
MCA or otherwise (if Linux was going to work on MCA...)
The IBM Token Ring Technical Reference Manual is a frustrating nightmare
as an information source.  Most of the information is there.  And for any of
you who've written a driver, you know that most doesn't cut it.  Here's what you're
up against if you try this:

Cards WILL return undocumented values.
The manual gives you the ports to poke at, but doesn't tell you what has to be set
        up first.
Incomplete information.

The drivers I wrote link into the kernel (99.14 I think?).  Ifconfig tok0 142.212.48.58
etc.. works.. you can ifconfg tok0 down/up, etc.
After hacking away at it, the card initializes, but will NOT (@#%@#Darn it!) Join the
ring.  Perhaps you can get further than I.  Maybe I quit to early but didn't have the
time to hack away endlessly.  If you get it working, I'd be glad to help out through
the end of the project.

If you want my code, post or mail and I'll clean it up to 1.1.18 - if things haven't 
changed too much (cringe).
If I haven't responded in 1 day mail again as my silly pop reader (perl-pop1.0) started
tacking all incoming messages onto one big file lately.  Strange.
L8r.


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

From: choltje@ux1.cso.uiuc.edu (Christian Holtje)
Subject: Re: svgalib and s3
Date: 26 Jun 1994 19:24:13 GMT

cmay@titan.ucs.umass.edu (Christopher M. May) writes:

>Hi, I was wondering if anyone has patched the s3 code in svgalib
>to work with an s3 805 card.  The source says it's only been used on
>a 911 chip :(.  

>It seems so close.... anyone have a pointer to docs on the 
>s3 chips?

Just as a two center. I'd really LOVE to either have svgalib support
VESA (bleech) or S3....just so I can write some stuff for it...(anyone
like Car Wars :)

        -Doc
-- 
    ---     ---     ---   -      -  -  -   ---  -----  docwhat@uiuc.edu
   +   -  +    -  +      +      +  -  +  -   +   -    CS major at Illinois
  *   +  *    +  *      *  +   *  +*+*  +*+*+   *    --- finger me at ---
 ****     ***     ***   **  **   *  *  *   *   *    choltje@ux1.cso.uiuc.edu

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

From: ken@chinook.halcyon.com (Ken Pizzini)
Subject: Re: Runtime compilation and execution
Date: 25 Jun 1994 06:47:08 GMT

In article <2ucodf$r3i@mailer.fsu.edu>, Steven Hugg <hugg@xi.cs.fsu.edu> wrote:
>Now all I have to do is figure out how to get GDB to let me disassemble
>code in the data segment :)

(gdb) help disasssemble
Disassemble a specified section of memory.
Default is the function surrounding the pc of the selected frame.
With a single argument, the function surrounding that address is dumped.
Two arguments are taken as a range of memory to dump.

                --Ken Pizzini

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

From: tsbogend@bigbug.franken.de (Thomas Bogendoerfer)
Subject: Re: IBM Token Ring skeleton driver available
Date: 27 Jun 1994 00:15:20 +0200

mswanson@borg.ott.ca (Mark Swanson) writes:
>If you want my code, post or mail and I'll clean it up to 1.1.18 - if things haven't 
>changed too much (cringe).

I try to mail you, but mail bounced: 

|------------------------- Message log follows: -------------------------|
 no valid recipients were found for this message
|------------------------- Failed addresses follow: ---------------------|
 borg.ott.ca!mswanson ... unknown host
|------------------------- Message text follows: ------------------------|
Received: from hub-n by rachael.franken.de with uucp
        (Smail3.1.28.1 #3) id m0qHlpL-000mmlC; Sun, 26 Jun 94 06:28 MET DST
Received: from bigbug by hub-n.franken.de with uucp
        (Smail3.1.28.1 #9) id m0qHhdL-00045eC; Sun, 26 Jun 94 01:59 MET DST
Received: by bigbug.franken.de (Smail3.1.28.1 #6)
        id m0qHhIZ-000ExuC; Sun, 26 Jun 94 01:38 MET DST
Message-Id: <m0qHhIZ-000ExuC@bigbug.franken.de>
Date: Sun, 26 Jun 94 01:38 MET DST
From: tsbogend@bigbug.franken.de (Thomas Bogendoerfer)
To: mswanson@borg.ott.ca
Subject: Re: IBM Token Ring skeleton driver available
Newsgroups: comp.os.linux.development
References: <2uf8d0$aup@borg.ott.ca>

In comp.os.linux.development you write:
>If you want my code, post or mail and I'll clean it up to 1.1.18 - if things haven't 
>changed too much (cringe).

I'm very interested in your code, because at work we have many machines
with token-ring adapters and they all want to run linux:-). At the 
moment I try to port the mach token-ring driver to Linux. But your driver 
can save me a lot of time.

Bye, Thomas.


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


** 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
******************************
