Subject: Linux-Development Digest #892
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, 6 Jul 94 09:13:16 EDT

Linux-Development Digest #892, Volume #1          Wed, 6 Jul 94 09:13:16 EDT

Contents:
  Re: TCP/IP networking for DOSEMU (Johannes Stille)
  Kernal for PowerPC (Walter Tautz)
  Encrypted drive? (Paul Gyugyi)
  Re: what is AF_MAX for Linux? (Alan Cox)
  Re: ARP broken ?! (Alan Cox)
  Dump command for Linux? (Kevin Martinez)
  Re: Graphics Terminals (Andrew R. Tefft)
  Re: Linux kernel programming book (aldy hernandez)
  Re: Encrypted drive? (Colin Plumb)
  FPException in _IO_dtoa ? Or is it me ? (Steffen Neumann)
  Adaptec 27xx/28xx SCSI Controllers (Michael Finken)
  Help needed compiling the kernel with c++ options (Mr DV Watkins)
  Re: Linux kernel programming book (Rob Janssen)
  Re: HD floppy with 1600 kB, why not? (Frank Lofaro)
  Re: TCP/IP networking for DOSEMU (Byron A Jeff)
  Where are kernel versions kept? (Pete Kruckenberg)

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

From: johannes@titan.westfalen.de (Johannes Stille)
Subject: Re: TCP/IP networking for DOSEMU
Date: Wed, 6 Jul 1994 00:43:25 GMT

In article <2vbm4g$fml@solaria.cc.gatech.edu> byron@gemini.cc.gatech.edu (Byron A Jeff) writes:
[...]
>My synopsis: Netware and TCP/IP can share a single NIC because they are 2 
>different protocols. However Linux TCP/IP and DOSEMU TCP/IP on the same NIC
>cannot use the same IP because it's impossible to tell to where packets to
>that IP must go (since they are now both using exactly the same protocol). So 

I completely agree with your analysis.

>to solve the problem:
>
>- create virtual NICs and a virtual network for the DOSEMU sessions.
>- have the Linux TCP/IP route code route packets from the real
>  net into the virtual net. 
>- The virtual NICs for DOSEMU would consist of a loopback interface for the 
>  lower half and a packet driver interface for the upper half. 

I wouldn't call them "loopback" interfaces, but the code would be about
as simple as the loopback code. I'd use a character device interface for
the connection to dosemu: If dosemu writes to the character device, the
Linux kernel gets the data as a network packet; if the Linux kernel
sends a packet to the "virtual NIC", dosemu can get the packet with
read().

>- So to both the real net and the Linux box, the DOSEMU side would
>  look like a separate network and each DOSEMU session would look like a new
>  machine on the DOSEMU network.
>- The DOSEMU packet driver will have a packet driver interface on the top end
>  for DOS TCP/IP/applications to connect to.
>- The bottom end of the packet driver will connect to the DOSEMU virutal NIC.

One wouldn't use a packet driver accessing virtual hardware, but another
DOSEMU integrated packet driver, i.e. the driver is running in native
mode as part of DOSEMU itself, not in virtual 8086 mode under control of
DOSEMU.

>This way only one packet driver for DOSEMU need be written: the driver for
>the virtual NIC. Linux takes care of the real NIC and routing to the virtual
>NICs.
>
>Question: routing works properly now right? What kernel/net package are
>required for correct routing?

Routing works properly since way before 1.0. You just need the
appropriate ifconfig and route programs for your kernel.

>Tell me what you think.

I think that there is hardly any need for a TCP/IP connection to DOSEMU.
Usually you can get TCP/IP software for Linux that is both cheaper and
better.
If I'm wrong, please tell me so. If there is suffcient need, I'd
probably write the drivers.

>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

        Johannes

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

From: wtautz@uoguelph.ca (Walter Tautz)
Subject: Kernal for PowerPC
Date: 5 Jul 1994 21:05:04 GMT

What is the current status for getting a native kernal for the PowerPC
line of microprocessors? How would I get involved in possibly contributing?
My experience is, alas, limited to a course I'm currently taking on the
Motorola 68000 line of CPU's -- chips whose architecture I find particularily
elegant versus, say the  8086, another processor with a 16-bit databus.

                                        Walter Tautz
                                        University of Guelph
                                        Ontario, Canada

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

From: pjg@tesla.esl.com (Paul Gyugyi)
Subject: Encrypted drive?
Date: 06 Jul 1994 01:12:51 GMT

Is there an encrypted file system, one where I could use the syntax

tranq> mount -o encryptedfs -passwd foobar /dev/sda /mnt/tmp

Or preferably have it prompt me for the password.  I have a
partition of misc. files that I leave unmounted so casual
users can't get at them.  I'd also like to keep
anyone from unplugging my scsi disk, taking it to another
linux box, and mounting it there.  I'm not looking for a
clipper chip or anything, ... heck, just Rot-13 would probably
be enough.  Can anyone point me to a relevant source file?
What else besides "mount" might need to be changed?

Thanks.
--
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
| Paul Gyugyi                      scrabble...click...snap...  |
| gyugyi@earthsea.stanford.edu     Paul_Gyugyi@smtp.esl.com    |
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=


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

From: iiitac@uk.ac.swan.pyr (Alan Cox)
Subject: Re: what is AF_MAX for Linux?
Date: Wed, 6 Jul 1994 08:22:52 GMT

In article <GTHAKER.94Jul5204138@polyphony.sw.stratus.com> gthaker@polyphony.sw.stratus.com (Gautam Thaker) writes:
>
>AF_MAX is 21 under SUN OS. I can't find this value defined to be
>any thing under Linux. What should it be? I have some code that
>uses this.
>
Current kernels now have this define to keep BSD style programs happy. The
value used is currently 8.

Alan


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

From: iiitac@uk.ac.swan.pyr (Alan Cox)
Subject: Re: ARP broken ?!
Date: Wed, 6 Jul 1994 08:24:26 GMT

In article <1994Jul1.092248.4210@dagoba.priconet.de> strauss@dagoba.priconet.de (Frank Strauss) writes:
>The simplest workaround is to set a static arp entry on the server by
>"arp -s client cl:ie:nt:hw:ad:dr". This works for me, though it's not
>the best way. Perhaps, we should take a look at the bootpd.

Yes bootpd has a bug, it fails to set the address family of the arp entry it
adds with SIOCSARP.

Alan


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

From: Kevin Martinez <lps@rahul.net>
Subject: Dump command for Linux?
Date: Wed, 6 Jul 1994 01:45:19 GMT

Is there any development going on for a dump command to dump raw devices 
in Linux?

It is handy for backups and duplicating filesystems.....

Thanks,

Kevin Martinez
lps@rahul.net
-- 
========================================================================
 Kevin Martinez    lps@rahul.net    Member of the Julie Kangas Fan Club
 Work: 1 800 50 SATAN                              Home: 1 510 676 1111
========================================================================

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

From: teffta@cs690-3.erie.ge.com (Andrew R. Tefft)
Subject: Re: Graphics Terminals
Date: Wed, 6 Jul 1994 02:04:52 GMT

This would be interesting and nice to have. Kind of a "transparent
window" in X which would show plain svga underneath.
-- 

Andy Tefft               - new, expanded .sig -     teffta@cs690-3.erie.ge.com

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

From: aldy@sauron.cc.andrews.edu (aldy hernandez)
Crossposted-To: comp.os.linux.misc
Subject: Re: Linux kernel programming book
Date: 5 Jul 1994 23:03:49 GMT

In article <2vbio1$9h4@hahn.informatik.hu-berlin.de>,
U.Kunitz <kunitz@informatik.hu-berlin.de> wrote:
>
>Language: _german_
>386 pages
^^^^^^^^^^
Hmmm. I got a good laugh out of that one.

Aldy

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

From: colin@nyx10.cs.du.edu (Colin Plumb)
Subject: Re: Encrypted drive?
Date: 6 Jul 1994 04:22:01 -0600

In article <PJG.94Jul5181251@tesla.esl.com>,
Paul Gyugyi <pjg@tesla.esl.com> wrote:
> I'm not looking for a
> clipper chip or anything, ... heck, just Rot-13 would probably
> be enough.  Can anyone point me to a relevant source file?
> What else besides "mount" might need to be changed?

*Ahem*.  Please be caureful implying that the Clipper ship is "good"
encryption.  The Skipjack algorithm may be, but the rest leaves
something to be desired.

Anyway, I don't have such a thing, but if anyone wants to write one
I can supply a lot of ideas and crypto code.  (Mostly based on the
design of Peter Gutmann's SFS for DOS.)
-- 
        -Colin

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

From: sneumann@TechFak.Uni-Bielefeld.DE (Steffen Neumann)
Subject: FPException in _IO_dtoa ? Or is it me ?
Date: Wed, 6 Jul 1994 10:35:30 GMT


Hi, my prob is a SIGFPE. I try to port a package for early vision emulation,
that consists amongst others of a command eve_gabor that has been compiled 
with a special library libeve.a that contains write_header1 and ffprintf.

We tried to call ffprintf with the same parameters as eve_gabor did,  and 
it worked. (no suprise, it looks correct....)

=====>  So: what might cause the error, what else do we have to check, 
and if we have to: how to step into sprintf() :-o ??

My config:
i486DX50, Slackware 1.2.0 thats gcc 2.5.8, libc 4.5.24 and Kernel 1.0.8
We had the same prob on a 386-40 with Math-Emulation
                 and on a 386-40 with Cyrix Coprocessor, both with Slack120
The whole things compiles with gcc without warning, only -Wall makes it 
complain about something like 'implicit returning int'
The whole package works well on several Sparc Stations and a HP700


O.K folks, here is the subroutine, located within libeve.a:

ffprintf(fd,i)  /* output floating point arg */

int fd;
float i;

{
        char s[50]="";

        sprintf(s,"%e\n",i);
        write(fd,s,strlen(s));
}

...and here is the session with xxgdb we have just done:

(xxgdb) info stack
#0  ffprintf (fd=1, i=-0.5) at wsubs.c:64
#1  0x3967 in fwrite_header1 (fd=1, hd=0xbffff9cc) at write_header1.c:42
#2  0x38ba in write_header1 (hd=0xbffff9cc) at write_header1.c:20
#3  0x561 in main (argc=9, argv=0xbffffa98) at eve_gabor.c:126

(xxgdb) info locals
fd = 1
i = -0.5
s = '\000' <repeats 49 times>
(xxgdb) step
[tcsetpgrp failed in terminal_inferior: Not a typewriter]

Program received signal SIGFPE, Arithmetic exception.
0x95b1 in _IO_dtoa ()


By the way: one *very* mysterious thing we have already disabled,
perhaps they are interconnected:
First s was declared like that: char s[50]; the function was called with 
ffprintf (1, hd->xo) (hd->xo = -0.5), but inside ffprintf() 
xxgdb told us i=6.654645e-44 or something like that. This
vanished when we declared char s[50]="";
Ups ????????

Further discussion via mail is welcome ...
Thanx, Steffen
 


--
Steffen Neumann                      Computer science is the dangerous 
sneumann@techfak.uni-bielefeld.de    atempt to overcome human intelligence

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

From: finken@conware.de (Michael Finken)
Subject: Adaptec 27xx/28xx SCSI Controllers
Date: 6 Jul 1994 11:25:30 GMT

A friend of mine has a PC with VL-Bus and an Adaptec 2842 (?) controller.
The question is: Does Linux support that controller?

I didn't find special mentioning in the latest Slackware release and the
kernel patches up to 1.1.24.

Thanks,
Michael

===============================================================================
Michael Finken                                Conware Computer Consulting GmbH
E-Mail: finken@conware.de                     Killisfeldstr. 64
                                              76227 Karlsruhe
                                              Tel.: 0721/9495-0
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
You're in a maze of twisty little submenus, all alike.
===============================================================================

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

From: damien@monu1.cc.monash.edu.au (Mr DV Watkins)
Subject: Help needed compiling the kernel with c++ options
Date: 5 Jul 1994 23:34:43 GMT

Can anyone help with compiling the linux kernel?

I wish to compile the kernel after modifying some of the source files 
using c++ extensions. 

I have a version of linux (version 1.0.8) which compiles fine as is.

When I added

CONFIG_CPP = CONFIG_CPP

to the /usr/src/linux/.config file, this causes the Makefile to add 
extra options to the CFLAGS as follows

ifdef CONFIG_CPP
CFLAGS := $(CFLAGS) -x c++
endif

which on my understanding will cause a c++ compile.

All works fine until until the makefile tries to execute the command


make[1]: Leaving directory `/usr/src/linux/lib'
ld  -Ttext 100000 boot/head.o init/main.o tools/version.o \
        kernel/kernel.o mm/mm.o fs/fs.o net/net.o ipc/ipc.o \
        fs/filesystems.a \
        drivers/block/block.a drivers/char/char.a drivers/net/net.a ibcs/ibcs.o drivers/FPU-emu/math.a \
        lib/lib.a \
        -o tools/zSystem

when the following errors occur and the Makefile aborts

kernel/kernel.o: Undefined symbol ___verify_write referenced from data segment
kernel/kernel.o: Undefined symbol _register_blkdev referenced from data segment
kernel/kernel.o: Undefined symbol _register_chrdev referenced from data segment
kernel/kernel.o: Undefined symbol _unregister_blkdev referenced from data 
segment
kernel/kernel.o: Undefined symbol _unregister_chrdev referenced from data 
segment
kernel/kernel.o: Undefined symbol _wake_up_interruptible referenced from data 
segment
drivers/net/net.a(net_init.o): Undefined symbol _memset referenced from text 
segment
make: *** [tools/zSystem] Error 1


Other warnings are issued during the c++ compile but not during the default
c style compile, as shown below, but all files appear to be compiled.

sched.c:106: warning: aggregate has a partly bracketed initializer
sched.c:146: warning: ANSI C++ prohibits conversion from `(const char *, 
int, int)' to `(...)'
sched.c:146: warning: ANSI C++ prohibits conversion from `(unsigned int)' 
to `(...)'

etc...


The only other points I have noted is that the commands shown below do 
not have the CFLAGS included on the compile line in the makefile.


gcc -D__KERNEL__ -E -traditional -DSVGA_MODE=NORMAL_VGA  boot/bootsect.S 
-o boot/bootsect.s

gcc -D__KERNEL__ -E -traditional -DSVGA_MODE=NORMAL_VGA  boot/setup.S 
-o boot/setup.s

gcc -D__KERNEL__ -E -traditional boot/head.S -o boot/head.s


where as other commands use the CFLAGS and expand as shown below

gcc -D__KERNEL__ -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer 
-pipe -x c++ -m386  -c -o init/main.o init/main.c

If anyone can help me with this I would greatly appricate it.

Thnaks
Damien
damien@monu1.cc.monash.edu.au






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

Crossposted-To: comp.os.linux.misc
From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: Linux kernel programming book
Reply-To: pe1chl@rabo.nl
Date: Wed, 6 Jul 1994 07:50:13 GMT

In <2vcosl$29i@orion.cc.andrews.edu> aldy@sauron.cc.andrews.edu (aldy hernandez) writes:

>In article <2vbio1$9h4@hahn.informatik.hu-berlin.de>,
>U.Kunitz <kunitz@informatik.hu-berlin.de> wrote:
>>
>>Language: _german_
>>386 pages
>^^^^^^^^^^
>Hmmm. I got a good laugh out of that one.

The english version will probably be 286 pages :-)

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

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

From: ftlofaro@unlv.edu (Frank Lofaro)
Subject: Re: HD floppy with 1600 kB, why not?
Date: Tue, 5 Jul 94 22:55:18 GMT

In article <2886@nikhefh.nikhef.nl> d70@nikhefh.nikhef.nl (Bram Bouwens) writes:
>
>But now we have a nice OS and nice hardware which can handle disk
>formats up to 1600 kB (within specs), and we only put 1440 kB on
>them. Why is that? Of course, to do so you should use 10 1024 byte
>sectors per track instead of 18 x 512. Indeed, DOS will not be able
>to read these; but who cares?

This would be a _great_ idea?

Would the nonstandard sector size hose the buffer cache, or could it 
be handled in the floppy driver?



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

From: byron@gemini.cc.gatech.edu (Byron A Jeff)
Subject: Re: TCP/IP networking for DOSEMU
Date: 6 Jul 1994 12:08:32 GMT

In article <1994Jul6.004325.9705@titan.westfalen.de>,
Johannes Stille <johannes@titan.westfalen.de> wrote:
-In article <2vbm4g$fml@solaria.cc.gatech.edu> byron@gemini.cc.gatech.edu (Byron A Jeff) writes:
-[...]
->My synopsis: Netware and TCP/IP can share a single NIC because they are 2 
->different protocols. However Linux TCP/IP and DOSEMU TCP/IP on the same NIC
->cannot use the same IP because it's impossible to tell to where packets to
->that IP must go (since they are now both using exactly the same protocol). So 
-
-I completely agree with your analysis.

Thanks

-
->to solve the problem:
->
->- create virtual NICs and a virtual network for the DOSEMU sessions.
->- have the Linux TCP/IP route code route packets from the real
->  net into the virtual net. 
->- The virtual NICs for DOSEMU would consist of a loopback interface for the 
->  lower half and a packet driver interface for the upper half. 
-
-I wouldn't call them "loopback" interfaces, but the code would be about
-as simple as the loopback code. I'd use a character device interface for
-the connection to dosemu: If dosemu writes to the character device, the
-Linux kernel gets the data as a network packet; if the Linux kernel
-sends a packet to the "virtual NIC", dosemu can get the packet with
-read().

OK. That works for me as an implementation.

-
->- So to both the real net and the Linux box, the DOSEMU side would
->  look like a separate network and each DOSEMU session would look like a new
->  machine on the DOSEMU network.
->- The DOSEMU packet driver will have a packet driver interface on the top end
->  for DOS TCP/IP/applications to connect to.
->- The bottom end of the packet driver will connect to the DOSEMU virutal NIC.
-
-One wouldn't use a packet driver accessing virtual hardware, but another
-DOSEMU integrated packet driver, i.e. the driver is running in native
-mode as part of DOSEMU itself, not in virtual 8086 mode under control of
-DOSEMU.

Sorry I didn't clarify that. It wouldn't be a emulated packet driver but
a part of DOSEMU so that one could get better performance.

-
->This way only one packet driver for DOSEMU need be written: the driver for
->the virtual NIC. Linux takes care of the real NIC and routing to the virtual
->NICs.
->
->Question: routing works properly now right? What kernel/net package are
->required for correct routing?
-
-Routing works properly since way before 1.0. You just need the
-appropriate ifconfig and route programs for your kernel.

I've had problems with it in the past when trying to route between multiple
NICs. I had a pl15f kernel running Net2Debugged that I could not get to 
route packets between the main net on one NIC and the subnet on the other.
I haven't tried it since. So I was just asking.

-
->Tell me what you think.
-
-I think that there is hardly any need for a TCP/IP connection to DOSEMU.
-Usually you can get TCP/IP software for Linux that is both cheaper and
-better.
-If I'm wrong, please tell me so. If there is suffcient need, I'd
-probably write the drivers.

Well my take on the subject is that quite a few users are more comfortable
using some DOS software including the networking stuff. I have a department
full of administrative folks that use the U. Minn. Minuet software. They like
it. With this packet driver they could run it.

Just a thought.

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: kruckenb@sal.cs.utah.edu (Pete Kruckenberg)
Subject: Where are kernel versions kept?
Date: 5 Jul 1994 21:54:12 GMT

Quick question: is there anyplace where I can pick up specific
versions of the Linux kernel source without having to apply each patch
level (for example, I could ftp version 1.1.14, rather than getting
1.1.0 and applying patches 1-14)?

Thanks.
Pete.

  ------------------------------------------------------------------------
  Pete Kruckenberg                       School: kruckenb@sal.cs.utah.edu
  University of Utah                       Work: pete@dswi.com
  Computer Engineering    For even more addresses, "finger pete@dswi.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
******************************
