Subject: Linux-Development Digest #821
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, 12 Jun 94 10:13:07 EDT

Linux-Development Digest #821, Volume #1         Sun, 12 Jun 94 10:13:07 EDT

Contents:
  Re: NTFS filesystem on disk layout (Arnoud Martens)
  Re: in2000-SCSI drivers crashed when using HD intensively (David Willmore)
  Re: My problem? GCC problem? Linux problem? (Brad Pitzel)
  Keyboard: Another query. (Alexander Williams)
  Looking for DPT SCSI driver, Digi driver (Freeman Lowell)
  Re: SLIP panic still with 1.1.19! (was Re: Bugs in 1.18) (Rene COUGNENC)
  Re: wfw/lanman/linux interchange? (R. Stewart Ellis)
  Does a DTC 327 OVL SCSI controller work? (Lyman Chip Copps)
  Re: signal() with BSD semantics (Ken Pizzini)
  Re: My problem? GCC problem? Linux problem? (James Logajan)
  Re: Making a Boot disk for Gateway 2000  (was LI040404) (Gisli Ottarsson)
  Re: Making a Boot disk for Gateway 2000  (was LI040404) (Drew Eckhardt)
  Re: WordPerfect printing (Joel M. Hoffman)
  Re: Looking for DPT SCSI driver, Digi driver (Drew Eckhardt)

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

From: arnoud@ijssel.hacktic.nl (Arnoud Martens)
Subject: Re: NTFS filesystem on disk layout
Date: Fri, 10 Jun 1994 21:16:26 GMT
Reply-To: arnoudm@ijssel.hacktic.nl

Mikael Nykvist writes in newsgroup comp.os.linux.development:
> In <TVO.94Jun5182603@zaphod.swb.de> tvo@zaphod.swb.de (Thomas Vogler) writes:

> >i once posted this some time ago, but received no replies at all.
> >hopefully this one has some more success.

> >i intend to write a filesystem driver for linux supporting NTFS in order
> >to be able to access my NTFS formatted disks under Linux. In a first
> >attempt i plan to support read only access only, write access might follow
> >later.

> >in order to do this, i will need some informations how NTFS files are stored
> >on a disk.

> >does anyone know a source of information where such details can be found ?

> >i checked with all my local computer bookshops and the microsoft developer 
> >network cd's, but could not find anything except a few notes in the 
> >WindowsNT resource guide, which dont help much.

> Because of the B2 (or was it C2 ?...) security, I dont think MS will release
> any 'internal' info about NTFS... If they did, you could make a boot-disk
> that could access the NTFS-partions and the security are lost..

I don't think that is the reason, MS is considering NTFS a major
achievement with advanced thechnology and lots of bright ideas
stuffed into it. Because of that Microsoft is not willing to
share their ideas with others. I tried to get the layout about
one year ago and they wouldn't do it (internal use only). Even a
NDA was not acceptible for them.

Ah well, I gave up, as many others did. So may'be they are a bit
more cooperative now...




-- 
Arnoud Martens                          Delft, the Netherlands
                                        +31-15-563621/572701
                                        arnoudm@ijssel.hacktic.nl


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

From: willmore@iastate.edu (David Willmore)
Subject: Re: in2000-SCSI drivers crashed when using HD intensively
Date: 10 Jun 94 20:22:21 GMT

stefan@pippi.tu-bs.de (Stefan Markgraf) writes:

>Symptoms: The HD-light burns constantly. Switching between virtual consoles
>works, but you cannot halt the system, because the HD do not work anymore.

The light doesn't stay on and the consoles work.  Root is an IDE drive, so
I can run halt, it just can't unmount the scsi drives to finish the halt.

>2) Does anybody have the same problem?

Yes. 

Cheers,
David
-- 
___________________________________________________________________________
willmore@iastate.edu | "Death before dishonor" | "Better dead than greek" | 
David Willmore  | "Ever noticed how much they look like orchids? Lovely!" | 
===========================================================================

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

From: pitzel@cs.sfu.ca (Brad Pitzel)
Subject: Re: My problem? GCC problem? Linux problem?
Date: Sat, 11 Jun 1994 02:55:54 GMT

In article <ablumer.771128485@hubcap> you write:
>Given this code:
>
>> void example(s)
>> char *s;
>> {
>>      *s = 'h';
>>      }
>> void main()
>> {
>>      example("Hello!");
>>      }
>
>Should this code cause a Segmentation fault?
>It does running Linux 1.0 and compiled with GCC 2.5.8!
>It doesn't on my Sun.
>
>
>I'm porting some code that does something similar and
>it always faults.
>
>Thanks for any help,
>Aric.
>ablumer@eng.clemson.edu

Text strings in C/C++ such as "Hello!" are regarded as static strings, ie. 
they cannot be changed.  You are getting a seg fault because you are trying
to access memory you are not allowed to write to. The linux kernel and gcc both enfore this.

Many other c compilers and unix variants do not enforce this, but Linux has
for well over a year now.

I think you can force it to work by giving gcc the option -fwriteable-strings
but the best option is to recode using safer methods.

Writing over static text strings has been taken advantage by many hackers to
gain illegal access to unix machines (by using the string as an entry point to
write over the program code in memory).

cheers,
--brad
pitzel@cs.sfu.ca


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

From: thantos@runic.mind.org (Alexander Williams)
Subject: Keyboard: Another query.
Date: Sat, 11 Jun 1994 09:57:00 EST

Much thanks to those that responded to my last question about toggling 
shift keys. The response was swift and sure...

Unfortunately, another rears its ugly head. It seems that termkeys entries
are ignored in X. This, I think, will be a bad thing, since I really want 
to use X to juggle multiple shell windows.

The question becomes: Does -X- have facilities for making shift/ctrl/alt 
toggling response, and if so, how do you invoke it?

Much thanks in advance.
--
thantos@runic.via.mind.org (Alexander Williams) | PGP 2.x keya avail
  Email is the right of the masses. So do it.   | DF 22 16 CE CA 7F
  Do What Thou Wilt Shall Be the Whole of the   | 98 47 13 EE 8E EC
  Law. Love is the Law, Love Under Will. -oOo-  | 9C 2D 9B 9B
===================================================================
"Democracy isn't just the best form of government; its the only one
   even remotely worth a damn. Only democracy guarantees people get
   what they deserve."
    -- Zeno Marley (Early 21st Century Mercenary-Philosopher)
                   [Dark Conspiracy RPG, pg 29]


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

From: p1nadeau@vaxc.stevens-tech.edu (Freeman Lowell)
Subject: Looking for DPT SCSI driver, Digi driver
Date: Sat, 11 Jun 1994 04:25:32 GMT

        I have a 486/50dx EISA machine at work with a rather unusual
SCSI controller in it. It is from a company called DPT (Distributed
Processing Technology) located somewhere in Florida. There is (allegedly)
no nondisclosure agreement or other legal stuff involved in writing a
custom driver for their card, but I don't have the time to write one
myself. Does anybody out there have a driver (even a broken one) for such
a card?

        I also have a Digi PC/8i card that I could use a driver. I don't
know about the legalese for these, however.

        Thanks in advance.
                                                        Phil


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

From: rene@renux.frmug.fr.net (Rene COUGNENC)
Subject: Re: SLIP panic still with 1.1.19! (was Re: Bugs in 1.18)
Date: 10 Jun 1994 15:16:33 GMT
Reply-To: cougnenc@hsc.fr.net (Rene COUGNENC)

Ce brave Frank Lofaro ecrit:

> In article <10251@gos.ukc.ac.uk> sjwk@ukc.ac.uk (S.J.W.Kersley) writes:
> >After fiddling about with 1.1.18. I have noticed the following
> >problems:
> >
> >Performing a flood-ping (ping -f) on a machine connected via
> >a SLIP link caused the linux box to die horribly with 3 or 4
> >'Killing interrupt handler' panics
> >[...]
>
> ping -l 100 slipservername
>
> ALWAYS panics any Linux kernel 1.1.x with x>12. And all the older kernels 
> I tested if the new tty patches are put in (they were mainstreamed in 1.1.13)
> INCLUDING 1.1.19.
> At least for me. I have a 9600bps modem on cua1 with a 16550A.

Yes, I tried ping -f, kernel 1.1.19, v32bis modem:  

        With SLIP, no message, after some packets, the machine rebooted.
        With PPP, kernel panic :-(

Jun 10 16:26:31 renux vmunix: Unable to handle kernel NULL pointer dereference at kernel address 00000128
Jun 10 16:26:51 renux vmunix: current->tss.cr3 = 00073000, %cr3 = 00073000
Jun 10 16:26:52 renux vmunix: *pde = 00102027
Jun 10 16:26:53 renux vmunix: *pte = 00000027
Jun 10 16:26:54 renux vmunix: Oops: 0000
Jun 10 16:26:54 renux vmunix: EIP:    0010:0010d6e8
Jun 10 16:26:54 renux vmunix: EFLAGS: 00010283
Jun 10 16:26:55 renux vmunix: eax: 0010d6d8   ebx: 00000004   ecx: 0000011c   edx: 00000000
Jun 10 16:26:55 renux vmunix: esi: fffffffc   edi: 001ca390   ebp: 00074f98   esp: 00074f94
Jun 10 16:26:55 renux vmunix: ds: 0018   es: 0018   fs: 002b   gs: 002b   ss: 0018
Jun 10 16:26:56 renux vmunix: Process lchatd (pid: 68, process nr: 19, stackpage=00074000)
Jun 10 16:26:56 renux vmunix: Stack: 00000004 00000004 0010f0be 00000000 00075000 
Jun 10 16:26:56 renux vmunix: Code: 8b 41 0c 8b 51 08 8b 19 c7 41 04 00 00 00 00 50 ff d2 89 d9 
Jun 10 16:26:57 renux vmunix: Aiee, killing interrupt handler
Jun 10 16:28:13 renux vmunix: general protection: 0000
Jun 10 16:28:13 renux vmunix: EIP:    0010:00000004
Jun 10 16:28:13 renux vmunix: EFLAGS: 00010202
Jun 10 16:28:14 renux vmunix: eax: 00000000   ebx: 00000000   ecx: 0047ff2e   edx: 00000000
Jun 10 16:28:14 renux vmunix: esi: fffffffc   edi: 001ca390   ebp: 00489f98   esp: 00489f8c
Jun 10 16:28:14 renux vmunix: ds: 0018   es: 0018   fs: 002b   gs: 002b   ss: 0018
Jun 10 16:28:15 renux vmunix: Process ping (pid: 133, process nr: 32, stackpage=00489000)
Jun 10 16:28:15 renux vmunix: Stack: 0010d6fa 00000000 00000004 00000004 0010f0be 
Jun 10 16:28:15 renux vmunix: Code: a6 ea 00 f0 c3 e2 00 f0 a6 ea 00 f0 a6 ea 00 f0 54 ff 00 f0 
Jun 10 16:28:16 renux vmunix: Aiee, killing interrupt handler

0010d6d8 T _tqueue_bh
0010d728 t _do_timer

--
 linux linux linux linux -[ cougnenc@renux.frmug.fr.net ]- linux linux linux 

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

From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: wfw/lanman/linux interchange?
Date: 12 Jun 94 12:09:00 GMT

lars@larski.dseg.ti.com (Lars Anderson) writes:

 >Hello,
 >I am working on a network with many windows for workgroups nodes and lanman nodes.  i would
 >be surprised if there was no way for me with my linux box to access data and devices on the
 >wfw or lanman nodes.  if anyone has any insight or pointers into how this is accomplished,
 >i would be grateful.  my setup is 486/linux1.1.13/3com3c503.
 >thanks in advance,
 >Lars Anderson lars@dseg.ti.com

There is a program named samba that provides a Server Message Block protocol
server on UNIX, as well as a limited client.  Judging from the mailing list,
many people are using it with WFWG.  I am trying to figure out enough about
ODI to get the secretary's computer running Netware over ODI, then LanMan
over NDIS, then MSoft TCP/IP over NDIS.  Once I figure that out I will be
able to try samba.

The FTP site is nimbus.anu.edu.au:/pub/tridge/samba


-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /

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

From: lyman@nntph31.bnr.ca (Lyman Chip Copps)
Subject: Does a DTC 327 OVL SCSI controller work?
Date: Fri, 10 Jun 1994 18:16:41 GMT

Does any one know if the DTC 327 SCSI controller work with LINUX?

Please let me know Chip.

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

From: ken@chinook.halcyon.com (Ken Pizzini)
Subject: Re: signal() with BSD semantics
Date: 11 Jun 1994 03:09:12 GMT

In article <Cr6u6B.1IJ@unifix.de>, Ruediger Helsch <rh@unifix.de> wrote:
>I would like to change the default handling of signal() in my
>system to BSD semantics, but first I want to get some
>opinions.
>
>What is the reason that under Linux signal() uses by default
>the unreliable SYSV mode, and BSD functionality has to be
>expilicitly enabled if desired? Lets look at it from different
>points of view:
[...]
>So what are your opinions? Does anybody know a program
>that would break with BSD signal() semantics?

The C standard, while permitting an unreliable signal() implementation,
does not require it.  I think that it is a great idea to rewrite
signal() in terms of the POSIX sigaction() stuff.

The only objection I can think of is that it may lull Linux-based
C programmers to *expect* signal() to be reliable, and have their
code break when they port to a system with an unreliable implementation
of signal().  ;-)

                --Ken Pizzini

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

From: jamesl@netcom.com (James Logajan)
Subject: Re: My problem? GCC problem? Linux problem?
Date: Fri, 10 Jun 1994 22:01:08 GMT

Wayne Throop (throopw%sheol@concert.net) wrote:
: ::     void main() { example("Hello!"); }

: It probably doesn't cause your sigsegv on linux,
: but it may be worth noting that defining main to return void
: is illegal in C, and always has been.  Borrowing from the
: comp.lang.c FAQ:

: 5.12: Can I declare main as void, to shut off these annoying "main
:       returns no value" messages?  (I'm calling exit(), so main
:       doesn't return.)

: A:    No.  main must be declared as returning an int, and as taking
:       either zero or two arguments (of the appropriate type).  If
:       you're calling exit() but still getting warnings, you'll have to
:       insert a redundant return statement (or use some kind of
:       "notreached" directive, if available).

The void main() issue is irrelevant to the original discussion, but since
it has been brought up, a couple of points:

Old K&R 'C' defined 'void' the same as 'int'. Lots of old code placed
voids in front of a lot of things that properly returned 'int', like
printf. This was done, obviously in bad form, to shut up lint.

I'll have to take serious issue with the so-called "comp.lang.c FAQ"
on what main takes as arguments: it can take 0, 1, 2, or 3 arguments. The
common names and types of these arguments is left as an exercise for
the reader. I've never read it, and after getting something as basic
and simple as main() arguments wrong, I can't suggest it to anyone.
(I have no quarrel with its statements regarding the return type of
main. But it should be noted that virtually all standard 'C' compilers
are not as strident as the authors of this FAQ.)

Just out of curiousity, anybody know of any systems where void main() {}
causes problems?

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

From: gisli@timoshenko.eecs.umich.edu (Gisli Ottarsson)
Crossposted-To: comp.os.linux.admin
Subject: Re: Making a Boot disk for Gateway 2000  (was LI040404)
Date: 12 Jun 1994 13:02:07 GMT


 In article <LJS.94Jun9164435@gano.cs.brown.edu>,
 Lee J. Silverman <ljs@cs.brown.edu> wrote:

  >> Well, I solved my problem with creating a boot floppy to get my
  >> Gateway 2000 going.  I thought it would be appropriate for me to
  >> share the recipe with everyone.  If anyone else is dealing with
  >> this, I hope this helps!

  >> The original problem is that Gateway's large IDE drives have more
  >> than 1048 cylinders, which means you can't install LILO on them
  >> easily.

>>>>> "DE" == Drew Eckhardt <drew@kinglear.cs.colorado.edu> replies:

  DE> There's no problem - you just have to use the BIOS mapping 
  DE> returned by the drive when partitioning it and you need 
  DE> a disktab entry reflecting the BIOS mapping.  

Easier still: In DOS fire up the CMOS setup utility (ctrl+alt+S on my
system), find the disk parameters and copy them to a user defined mode
(USER1).  Linux doesn't seem to like the "Auto" feature.  On my
Gateway 4DX2-66P with 1048 cyl, this works famously.

                                        Gisli
--

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gisli Ottarsson                                    
Grad Student and a Gentleman                      
                                                   Delenda est Carthago.      
University of Michigan                                   
gisli@umich.edu

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Crossposted-To: comp.os.linux.admin
Subject: Re: Making a Boot disk for Gateway 2000  (was LI040404)
Date: 11 Jun 1994 04:18:50 GMT

In article <LJS.94Jun9164435@gano.cs.brown.edu>,
Lee J. Silverman <ljs@cs.brown.edu> wrote:
>
>       Well, I solved my problem with creating a boot floppy to get
>my Gateway 2000 going.  I thought it would be appropriate for me to
>share the recipe with everyone.  If anyone else is dealing with this,
>I hope this helps!
>
>       The original problem is that Gateway's large IDE drives have
>more than 1048 cylinders, which means you can't install LILO on them
>easily.  

There's no problem - you just have to use the BIOS mapping 
returned by the drive when partitioning it and you need 
a disktab entry reflecting the BIOS mapping.  

While I haven't used this on one of the Gateway PCs, I have
used it with an Allways IN-2000 SCSI system with a 1.3G SCSI
drive where under DOS, the drive geometry reflected something 
< 1024 cylinders and the Linux HDIO_GETGEO ioctl() was returning
something with over 1300 cylinders, and I had the Linux partitions 
past the 1024 cylinder mark according to the bogus geometry.

>The easiest solution is to boot from a floppy disk.  

IMHO, vi /etc/lilo/disktab or vi /etc/disktab depending on your 
configuration is a lot simpler.  Unless, of course, you are an 
EMACS user and prefer to use emacs instead :-)

Booting from hard disk is also significantly faster, and means 
you don't have to feel arround for a floppy disk for those 
infrequent changes from Linux back to DOS.

>3)Repartition it with fdisk.  type:

Why?  Linux won't do anything with a partition table on a floppy 
disk, and when you run LILO with bootdevice set to the floppy
drive, you overwrite it anyways.

-- 
Drew Eckhardt drew@Colorado.EDU
1970 Landcruiser FJ40 w/350 Chevy power
1982 Yamaha XV920J Virago

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

From: joel@wam.umd.edu (Joel M. Hoffman)
Subject: Re: WordPerfect printing
Date: Sun, 12 Jun 1994 13:10:58 GMT

In article <2tcp64$o8c@bones.et.byu.edu> haymoree@newt.ee.byu.edu (Ed Haymore) writes:
>Hui-Hui Hu (hdesiato@cs.umd.edu) wrote:
>| As I'm anxiously waiting for a release of dosemu that works with
>| new kernels, and being bothered by a stream of in-house DOS weenies :)
>| I think that something I would *truly* be grateful for is
>| something like 'wp2ps': convert WordPerfect files to PostScript,
>| or actually anything, as long as I can print it.
>
>What about using WP's built-in postscript capability?  I installed a

I think the original idea was to avoid having to fire up dosemu just
to print a WP file.  (BTW, there is a wp2latex program, which works
fairly well.)

Can dosemu read from stdin? If so, that would also provide a way of
doing what the poster wants.  E.g., something like:

        #!/bin/sh
        #
        # hypothetical script to print a wp file.
        dosemu <<EOF
        wp
        ^[[21~ $1       # ^[[21~ is F10, the code to load a file in WP (?)
        ...
        EOF

Of course, there are problems.  How to we encode SHIFT-F5 via stdin.
This must be defined in a termcap entry.  

Anyway, that's the idea.  It would also provide a way of compiling DOS
binaries from within Unix.

-Joel
(joel@wam.umd.edu)

        
-- 
=============================================================================
|_|~~ Germany, Europe. 1943.    "The diameter of the bomb was 30 centimeters,
__|~| 16 Million DEAD.           and the diameter of its destruction, about 7
                                meters, and in it four killed and 11 wounded. 
 cnc  Bosnia, Europe. 1993.     And around these, in a larger circle of  pain
 cnc  HOW MANY MORE?          and time,  are scattered two  hospitals and one
                          cemetery.   But the young woman who was  buried  in
                    the place from where she came, at a distance of more than
             than 100 kilometers, enlarges the circle considerably.   And the 
      lonely man who is mourning her death in a distant  country incorporates
into the circle the whole world.  And I won't speak of the cry of the orphans
that reaches God's chair and from there makes the circle endless and godless."
=============================================================================
     Tell Clinton to stop the genocide:  president@whitehouse.gov

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

From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Looking for DPT SCSI driver, Digi driver
Date: 11 Jun 1994 04:21:52 GMT

In article <1994Jun10.232532.1@vaxc.stevens-tech.edu>,
Freeman Lowell <p1nadeau@vaxc.stevens-tech.edu> wrote:
>       I have a 486/50dx EISA machine at work with a rather unusual
>SCSI controller in it. It is from a company called DPT (Distributed
>Processing Technology) located somewhere in Florida. There is (allegedly)
>no nondisclosure agreement or other legal stuff involved in writing a
>custom driver for their card, but I don't have the time to write one
>myself. Does anybody out there have a driver (even a broken one) for such
>a card?



        A SCSI DPT driver is available on ftp.ibp.fr in the directory
/pub/linux/ALPHA/scsi.  It was uploaded to tsx-11 and it should be
in the same directory.

        
Contact cyrilsz@renux.frmug.fr.net if you need to get in touch with the 
author.

-- 
Drew Eckhardt drew@Colorado.EDU
1970 Landcruiser FJ40 w/350 Chevy power
1982 Yamaha XV920J Virago

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


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