Subject: Linux-Development Digest #779
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:     Tue, 31 May 94 03:13:13 EDT

Linux-Development Digest #779, Volume #1         Tue, 31 May 94 03:13:13 EDT

Contents:
  Linux mailing lists (was Re: New Linux BBS under developement!) (Matthias Urlichs)
  Re: SIGHUP - Where do we go from here? (Matthias Urlichs)
  Re: linux assembler - help please (J. Lawrence Stephan)
  SCSI Problems with 1.1.15 and 1.1.16 (Kang-Jin Lee)
  Re: Which driver for C5610 SCSI-controller ? (Rob Janssen)
  Re: Serial drivers in 1.1.16 (autoconfig for IRQ's) (Rob Janssen)

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

From: urlichs@smurf.noris.de (Matthias Urlichs)
Crossposted-To: comp.os.linux.misc
Subject: Linux mailing lists (was Re: New Linux BBS under developement!)
Date: 31 May 1994 06:52:43 +0200

In comp.os.linux.development, article <CqK56q.2Bz@oea.hacktic.nl>,
  dan@oea.hacktic.nl writes:
> 
> Why not create a mailing list, if one doesn't already exist on, niksula.hut.fi.
> 
Several other mailing lists have dropped off niksula because it's
overloaded. Besides, always having to add the stupid X-Mn-Key: header
seems a royal pain in the *censored* to me, especially when there are
a lot of free mailing list handlers around which don't need stupidities
like that.

NB, whatever happened to their plan to gate the lists to a new linux.* news
hierarchy?

NB2: Followups to comp.os.linux.misc.
-- 
Moral principles can never be compromised; they can only be abandoned.
-- 
Matthias Urlichs        \ XLink-POP N|rnberg  | EMail: urlichs@smurf.noris.de
Schleiermacherstra_e 12  \  Unix+Linux+Mac    | Phone: ...please use email.
90491 N|rnberg (Germany)  \   Consulting+Networking+Programming+etc'ing     42

Click <A HREF="http://smurf.noris.de/~urlichs/finger">here</A>.

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

From: urlichs@smurf.noris.de (Matthias Urlichs)
Subject: Re: SIGHUP - Where do we go from here?
Date: 31 May 1994 06:59:05 +0200

In comp.os.linux.development, article <1994May29.155931.23768@scorch.hna.com.au>,
  lgarde@scorch.hna.com.au (Leon Garde) writes:
> 
> So, all shells will have this largish section added especially for
> linux.
> 
Here's the relevant code from bash-1.13.5:

void hangup_all_jobs ()
{
  register int i;

  for (i = 0; i < job_slots; i++) {
      if (jobs[i]) {
          killpg (jobs[i]->pgrp, SIGHUP);
          if (JOBSTATE (i) == JSTOPPED)
            killpg (jobs[i]->pgrp, SIGCONT);
        }
    }
}

Doesn't seem like any largish section of code to me...

>        i wonder how many POSIX kernel's will handle SIGHUP'ing of
> orphans the same way ...

Since POSIX mandates that behavior, I'd say "all of them", otherwise they
won't be allowed to call themselves POSIX. Assuming, of course, that the
validation suite tests for this...

-- 
If you're already in a hole, there's no use to continue digging.
                                -- Roy W. Walters
-- 
Matthias Urlichs        \ XLink-POP N|rnberg  | EMail: urlichs@smurf.noris.de
Schleiermacherstra_e 12  \  Unix+Linux+Mac    | Phone: ...please use email.
90491 N|rnberg (Germany)  \   Consulting+Networking+Programming+etc'ing     42

Click <A HREF="http://smurf.noris.de/~urlichs/finger">here</A>.

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

From: jlarry@marlin.ssnet.com (J. Lawrence Stephan)
Subject: Re: linux assembler - help please
Date: 31 May 1994 00:58:42 -0400

Onno Hovers (onno@stack.urc.tue.nl) wrote:
: alan@qsss09.eq.gs.com wrote:
: > I am trying to write a program to access my video card that has
: > a direct memory access address which is equivalent to DOS interrupts,
: > without needing BIOS.  I have written the program successfully under
: > DOS (using debug), and tried porting it to Linux.  I am a novice at
: > writing assembler code, but for some reason, when I run the Linux
: > program, I get a "Memory fault" and the program DOESn't work.  The
: > "lcall" appears to be the problem, but I don't know how to determine
: > why.  Can someone offer some advice ?

: AAAAARRRRRGGGGGHHHHHHHH

: Is this a joke of yours? Are you kidding or do you mean this!!!
: Don't you know that you can't just access hardware or the BIOS  under linux.
: Have you ever heard of the infamous protected mode or memory protection?  
: What you are showing here is plain stupid.

Onno, I must apologize for Mr Buckwalter's response - it is totally un-called
for.  However, what he said is right - dos, using real mode, has a totally
different addressing scheme than Linux.  Code, even BIOS code, can't possibly
run under Linux.  The only exception is code that runs on a processor on
the adapter - but that isn't really BIOS code, and you can't call/jump to 
it anyway.

Given that that doesn't work, if you still want assembler info, I have it.
Write if you're interested.

BTW - you may want to investigate the stuff Mr Buckwalter suggested - it's
probably the best way to do anything with video that you'll find.

Larry Stephan
jlarry@ssnet.com


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

From: lee@tengu.in-berlin.de (Kang-Jin Lee)
Subject: SCSI Problems with 1.1.15 and 1.1.16
Date: Mon, 30 May 1994 18:22:52 GMT

I had no problems with 1.1.15 and 1.1.16 but today, after a crash (caused by
me experimenting with suid programms), the kernels boot okay, starts fsck
and checks the filesystems but hangs during fsck with the following message:

scsi0 : reseting for second half of retries
Unable to reset scsi host 0 - Probably a SCSI bus hang

With 1.1.8 I got similar message but 1.1.8 was able to continue and fix
the filesystem inconsistency. Now with the fixed filesystem, 1.1.15 and
1.1.16 runs fsck without any problem.

486/33 ISA, AHA1542B, ext2-fs.

-- 
Kang-Jin Lee
lee@tengu.in-berlin.de

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: Which driver for C5610 SCSI-controller ?
Reply-To: pe1chl@rabo.nl
Date: Mon, 30 May 1994 22:33:15 GMT

In <2scqdfINNbke@kirk.ms.DeTeMobil.de> aj@ms.DeTeMobil.de (Andreas Joppich) writes:


>Hey everybody out there !

>Is there anybody to tell me how to mount a MO-Disc-drive with an
>unknown controller ?  There was a SCSI-Controller named C5610 
>delivered with the drive. But the drivers in the kernel-sources 
>(linux 1.1.15) don't recognize the controller or the MO-drive. 

When your controller isn't supported, by far the easiest way out is
to buy a supported controller :-)

Of course, if you are daring you write your own driver for your card...

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: Serial drivers in 1.1.16 (autoconfig for IRQ's)
Reply-To: pe1chl@rabo.nl
Date: Mon, 30 May 1994 22:38:30 GMT

In <CqMp9p.EzF@scifi.uucp> njs@scifi.uucp (Nick Simicich) writes:


>I have a serial card with four serial ports on it.  These are straight
>16550's, so they each need an interrupt, and are plugged on their own
>interrupt.  

>[...]

Now, you should finally learn about setserial.  It has been around for
a long time, and was there to replace hacking in serial.c
With the new tty drivers, that possibility was removed.

So: get the "setserial" program (current version is 2.10) and use it
instead.

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

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


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