HDTenEightyP/NetNews huggingface dataset:
From: newton@iagu.itd.adelaide.edu.au (Mark Newton)
Newsgroups: comp.os.minix
Subject: SIGHUP for Amiga MINIX
Date: 20 Aug 92 15:00:32 GMT
Organization: University of Adelaide, South Australia


I sent a message about this a couple of weeks ago, and haven't received
any response.  I'm asking the question again, in the hope that someone
will at least say "No, sorry, it doesn't exist!" (email, please :-)

Since my Amiga MINIX system is set up for dial-in at various times
throughout the day, I wish to be able to make sure that users who logout
don't leave any forgotten processes behind.  So, what I require is a
SIGHUP patch for the tty driver.

I've already added DTR control to my kernel, so making the system hang up
isn't a problem.  I just wish to have SIGHUP sent to the tty's process
group whenever CD drops.

I am aware of such patches for the PC, and I'm perfectly willing to
port one of them.  However, I feel that I'd be wasting my time if someone
else has already done it.

So, does a SIGHUP patch exist for Amiga MINIX?  For any other m68k MINIX?

Thanks in advance.

  - mark
-- 
------------------------------------------------------------------
         'Do not expose your LaserWriter to naked flame...'
newton@iagu.itd.adelaide.edu.au         - Apple LaserWriter Manual
------------------------------------------------------------------
Newsgroups: comp.os.minix
From: cs902125@ariel.yorku.ca (SHUK C YIP)
Subject: Question?
Organization: York University, Toronto, Canada
Date: Sun, 23 Aug 1992 06:28:34 GMT

Minix supports which terminal emulation? (eg. VT100/200, Tek4010/4014
etc.)
Newsgroups: comp.os.minix
From: hpoe@nyx.cs.du.edu (Howard Poe)
Subject: Re: Help
Keywords: minix 1.5
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Sat, 15 Aug 92 12:00:53 GMT

You'll need to get the 5.25"disks, or a 3.5" disk drive.
The boot disk is designed to only work at the specified size, and so are the
distribution disks.
-Howard J. Poe
falcor@outlaw.uwyo.edu
hpoe@nyx.cs.du.edu
From: sreiz@cs.vu.nl (Reiz Steven)
Newsgroups: comp.os.minix
Subject: Re: AmigaMINIX floppy problems
Date: 22 Aug 92 15:56:14 GMT

dbenn@leven.appcomp.utas.edu.au (David Benn) writes:

>Oh, BTW, can someone give me an answer to the question I posed last time
>about how to get Minix to accept the ROOT and /usr disks in a different
>drive at boot time? The prompt for the ROOT disk says that the bootdev can
>be specified. Does this mean just another disk apart from ROOT in dd0? Or
>can I specify the 2nd or 3rd disk drive...?

You can specify the major and minor device numbers, where major device 2
is the floppy drives, e.g. 2,8 is /dev/dd0, 2,9 is /dev/dd1.

	Steven
From: gibb@cgowgs.enet.dec.com
Newsgroups: comp.os.minix
Subject: Floppy read problems with new 386sx
Date: 14 Aug 92 16:26:06 GMT
Organization: Digital Equipment Corporation, Calgary Canada

Hello,

I been running Minix 1.5 on my XT amiga bridgecard with no problems. I decided
to upgrade my bridgecard to a 386SX.

Minix still boots off my harddive, (lighting fast now) but the problem
I am seeing is that I can't boot off the floppies supplied with the 1.5
distribution. 

It gets a far as printing the welcome banner, then prints read error,
automatic reboot.

I have tried various floppy drives, all with the same results. The strange
thing is that it will boot dos floppies, Linux and SCO Unix floppies with
no problems. I also tried to boot these floppies on another 386, and of 
course they worked. I don't know what is so different between booting a
minix floppy and a dos floppy on this new bridgecard.

Once Minix is booted from the harddrive, I can mount the other
floppies from the 1.5 kit.

I was wondering if anyone else has seen this. When I playing around with the 
demo version on a IBM clone, I saw the same thing but wrote it off as being
a floppy problem.

I am hestitant to do any changes to minix on my hard drive, because I will
not be able to recover from floppies..

Any suggestions or help would be muchly appreciated...

Thanks..

John Gibb
From: dvan@crash.cts.com (David Vandeven)
Subject: MACMINIX remote users
Date: 14 Aug 92 23:36:53 GMT
Summary: Help! The manual blows
Keywords: MACMINIX,remote

Hi there.  I finally got all the patches and stuff installed, and my filesystem
is set up the way I want it, but I can't figure out how to let users log in
remotely.  I know that gettydefs needs to be configured, but the manual fails
to mention the format for gettydefs.  It's also rather sparse on how to set 
up for remote use.
Another problem:  If getty or whatever uses ats0 to answer the phone I need an
alternate method, as my modem's ats0 register doesn't work.

Can someone please email me with instructions on how to set up for remote use?

Thanks, and your patience is appreciated.
David Vandeven-     ********************************************************
Systems Progammer   *   "If you can't say something nice, say something    *
                    *       SURREAL"  Zippy the Pinhead                    *
You down wit OOP?   *               (dvan@crash.cts.com)                   *
 Yeah, you know C!  ********************************************************
From: adamd@rhi.hi.is (Adam David)
Newsgroups: comp.os.minix
Subject: bug in estdio sprintf() ???
Summary: sprintf(foo, "%s", foo) BROKEN
Date: 22 Aug 92 20:38:43 GMT

I just got estdio 2.6 up under minixST (without libfp). It was a little
bit fiddly because the standard minix C preprocessor barfs on the VARARGS
routines. 7 files needed some minor attention.
At last, I have a printf() that returns a value (!!!).

Now I came across this bug in sprintf(). sprintf(foo, "%s", bar) works as it
should if foo and bar are different strings, but sprintf(foo, "%s", foo) adds
a '%' character to the front of the string. Has anyone come across this and
fixed it already?

--
Adam David. (adamd@rhi.hi.is)
From: newton@iagu.itd.adelaide.edu.au (Mark Newton)
Newsgroups: comp.os.minix
Subject: Re: dosread
Date: 22 Aug 92 08:58:41 GMT
Organization: University of Adelaide, South Australia

In article <1992Aug20.083043.5104@email.tuwien.ac.at> hp@vmars.tuwien.ac.at (Peter Holzer) writes:
>newton@iagu.itd.adelaide.edu.au (Mark Newton) writes:
>
>>dosread expects a block special device that it is supposed to read from.
>>So, to read something from drive A:, use a command line like this:
>
>>   dosread -a /dev/fd0 foobar > /tmp/foobar
>
>>/dev/fd0 corresponds to the A: drive.
>
>What version of dosread are you using? All versions I know (1.3 ...
>1.6.16) do not take the pathname of a block device as their first
>arguent, but a single letter from which they build the pathname by

Ah, yes... I was thinking of tosread/toswrite, which does exactly the
same thing (to what is oestensibly exactly the same disk format, too).
tosread and toswrite are supplied with m68k MINIXes.

>(All of this is in the manual, BTW. Is it really that hard to
>understand?)

Agreed :-)

  - mark
-- 
------------------------------------------------------------------
         'Do not expose your LaserWriter to naked flame...'
newton@iagu.itd.adelaide.edu.au         - Apple LaserWriter Manual
------------------------------------------------------------------
From: adamd@rhi.hi.is (Adam David)
Newsgroups: comp.os.minix
Subject: setsid(), setpgid().
Summary: missing functions in minix distribution
Date: 20 Aug 92 13:52:27 GMT

Are these functions already available from somewhere? I'm wanting to do some
process group stuff with minix, but the functions are defined in the headers
and yet are missing from the library routines.

--
Adam David. (adamd@rhi.hi.is)
Newsgroups: comp.os.minix
From: danm@watson.ibm.com (Dan McCabe)
Subject: Re: 32bit clean MacMinix.
Date: Wed, 12 Aug 1992 17:04:17 GMT
Reply-To: danm@grumpy.watson.ibm.com (Dan McCabe)
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: IBM TJ Watson Research


MacMinix is 32bit clean: NOT!

(And why are all these IBMers posting about MacMinix? ;-) ;-) ;-)

I have attempted to make MacMinix 32bit clean. The problem is that the
kernel and all sorts of other code assumes that a click fits into 16 bits.
You can increase click_shift to 16 (or 14 or whatever the max that Sys 7
allows), but then you make allocation granularity excessively coarse.
Alternately, you can make a click ptr fit into 32 bits (as should have been
the case in the first place), but retrofitting that change has its fingers
everywhere. I and Joe Pickert had chosen the latter route. What follows is a 
(partial?) list of files that change:
	/usr/include/minix/type.h
	/usr/src/kernel/cstart.c
	/usr/src/kernel/system.c
	/usr/src/kernel/copy68k.s
	/usr/src/kernel/mpx.s
	/usr/src/mm/main.c
	/usr/src/mm/exec.c
	/usr/src/fs/main.c
	/usr/src/fs/glo.h
	/usr/src/lib/mac/crt/head.s
	/usr/src/lib/other/syslib.c
I don't have all of the details of the changes readily available, since the
disk with my minix system is packed away. However, Joe Pickert confirms
that at least these files change when you go to a 32bit clean MacMinix.
I was finally able to boot MacMinix and ran it for all of 30 seconds
without crashing. I then shut it down and haven't worked on it since,
with school and work beckoning me onto more serious pursuits.

When my disk gets unpacked, I will consider distributing my mods to those
interested parties (actually, I beleive that I made this offer previously
and got no takers).

In the 1.5 years following my changes, I have heard no response from
Joe Pickert. Will he ever make MacMinix 32bit clean, or must we do it
ourselves? I guess that is one of the beauties of getting source code.
But when you pay $175 for a product, ... (yeah, I know, you pay a lot
more for a real *nix, but you also get a lot more support).

MacMinix is dead. Long live MacMinix.

Cheers,
danm
Newsgroups: comp.os.minix
From: ice@eskimo.celestial.com (Greg Toth)
Subject: Help
Keywords: minix 1.5
Organization: -> ESKIMO NORTH (206) For-Ever <-
Date: Fri, 14 Aug 1992 21:15:52 GMT


I am attempting to run minix 1.5 on my pc clone.  I ordered the software
on 3.5" idsks but my drive a is 5.25. I used "diskcopy" command of dos
to get the software from the 3.5 to the 5.25 but when I try to boot
i get a message saying "Non system disk in drive A". This is with
both hard and soft reboots (warm and cold). What am I doing wrong?
.
From: DMEGGINS@acadvm1.uottawa.ca (David Megginson)
Newsgroups: comp.os.minix
Subject: Re: minix on Apple's Powerbooks
Date: 22 Aug 92 00:11:02 GMT
Organization: University of Delaware
Originator: mmdf@louie.udel.edu

On Fri, 21 Aug 1992 18:59:48 GMT Lars Andreas Stole said:
>I apologize if this is a FAQ, but I seem to remember that mninix will not
>run on a powerbook, even though it is part of the macintosh family.  Is
>this true?  I just bought a powerbook and would love to run Minix if
>possible. Thanks in advance.

Out of the box, MacMinix does not run under System 7, from what I have
read here.  Every time someone posts a question about MacMinix, s/he
is told that there are patches available to make it boot under System
7.  I would like to know how you can apply patches and recompile the
kernel if you cannot boot Minix in the first place?

In any case, System 6.0.8 will also run on the Powerbooks (the Powerbook
100, anyway).  Perhaps MacMinix will boot out of the box then?


David


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
David Megginson                        Department of English,
dmeggins@acadvm1.uottawa.ca            University of Ottawa
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-- 
Mail System (MMDF)
From: smackinla@cc.curtin.edu.au
Subject: XT MFM HD Driver help
Organization: Curtin University of Technology
Date: Wed, 12 Aug 1992 14:20:02 GMT


Hi all. I posted a message previously asking for help with an XT MFM hard
disk controller. Just to repeat, what I'm after is help with writing a driver
for Linux. I know that there is such a driver in Minix and I have the source
to it. Unfortunately, the source is not as clear as it could be in some parts.
At the beginning of the code are the names of four people who have worked on
the driver, and I am posting here in the hope of being able to contact them.

So, if: Adri Koppes, Gary Oliver, Harry McGauran or Mike Mitchell are
somewhere out there, or anyone knows where they are, could they get in touch
with me?

Perhaps even Andy could help? Do you still read this group?

Pat -- Have a day!
From: glalonde@VNET.IBM.COM ("Glen Lalonde")
Newsgroups: comp.os.minix
Subject: MacMinix on an SE with an ...
Date: 19 Aug 92 13:22:51 GMT

I guess it is time to state this again, to run MacMinix under system
7 you need to use version 1.5.10.7, the upgrade patch from version
1.5.10 and 1.5.10.1 is on plains(see faq sheet for address)

I also have a patch to enable protected memory on 68030 accelerators for
use with MacMinix, but you will need to free up the MMU for me first ie
turn off compact virtual.

I am using a SE with a Magic Railgun(a.k.a. Novy quick30) 16Mhz board with
4MB 32-bit ram.
From: amercer@desire.wright.edu (Art Mercer)
Newsgroups: comp.os.minix
Subject: Re: Amiga MINIX floppy problems
Date: 21 Aug 92 18:08:31 GMT
Reply-To: amercer@desire.wright.edu

From article <1992Aug21.034442.17351@nap.amoco.com>, by stmckenna@nap.amoco.com (Stephen T. McKenna):
> 
> Just to let you know your problems aren't unique:

I'll agree to that, in my case it was the Amiga boot disk.  Thankfully, I had
down-loaded the 1.5.10.1 & 1.5.10.2 patches and got a good .img file...

[omitted...]

> Although Minix is running now, it goes through disks at a furious rate.  The
> typical situation is sudden unrecoverable read or write errors, frequently in
> groups of 5 consecutive blocks.  The transfer command is particularly prone
> to corrupting disks this way; when transferring from the Amiga to the Minix
> side I usually write a half dozen disks in hope that one will read.
> 

I have yet to get transfer to work.  But CrossDos has solved most of my
problems.

> I don't think patches are the answer; I've patched up to 1.5.10.2 and not
> seen any improvement, although the patches are worthwhile anyway.  My advice
> on muddling by is to keep everything write-protected whenever possible; this
> includes /usr at boot and login time (Minix will gripe about the write-protect
> when it tries to write /usr/adm/wtmp, but that's harmless).

On the subject of 1.5.10.2, I cannot get it working with the supplied "ttys"
file and haven't had time to write Michael.  Any suggestions???
> 
> I have admittedly old hardware (6 year old A1000 with a 68020 add-on) but it
> has never had disk drive problems.
> 
> Can anyone out there offer explanations or (hopefully) suggestions?
> 
> Steve McKenna
> stmckenna@nap.amoco.com
> Amoco Research Center
> Naperville, IL, USA
> 


Art Mercer
Sr. Consultant, Academic Computing Resources
040H Library Annex
Wright State University
Col. Glenn HWY
Dayton, OH 45435

EMail:
	amercer@eve.wright.edu
 <or>
	amercer@wright.bitnet
PHONE:	(513)873-4038

---
From: 87p0786@csdvax.csd.unsw.edu.au
Newsgroups: comp.os.minix
Subject: Help? Need Minix v1.5 IBM disk 6
Date: 17 Aug 92 17:09:13 +1000
Organization: University of New South Wales

Dear Minix users,

My friend bought his Minix v1.5 (IBM) package one year ago, and he did
not install it until now (he just got a 486 last week). When he install
it, he found disk 6 (user binaries) is un-readable by installation 
program.


Is there any one (especially in Australia) kindly send him a copy of the
disk 6 (720K 3.5"), he is willing to pay for the cost, since without 
this disk, the whole package is no use. 

Please send your replay to:

87p0786@csdvax.csd.unsw.oz.au

Thanks in advance.

Hongbo Ni.
Newsgroups: comp.os.minix
From: dbenn@leven.appcomp.utas.edu.au (David Benn)
Subject: Amiga MINIX floppy problems
Originator: dbenn@leven
Organization: University of Tasmania at Launceston
Date: Thu, 20 Aug 92 02:46:22 GMT

I just received another copy of the Amiga MINIX disks from Prentice-Hall,
since my first disks had a large number of bad sectors.

All the latest disks but one copied okay, with a PC (the manual recommends
you use an Amiga utility which can copy PC disks). When booting the system,
the boot and root phases go smoothly. However, when inserting the /usr
disk, I get a heap of sector unreadable (or such like) errors and some disk
not writable errors after the /dev/dd0 mounted message. Sometimes the login
prompt comes up and other times not.

My df0: has always been a little flakey, so there could be something wrong
there (with the write protect problem). On booting MINIX, how does one
specify the boot drive (ie: before inserting root), eg: dd1? dd2? (rather
than dd0). I should add that by "flakey" I don't mean severely. df0: just
sometimes says that a disk is write-protected when it's not.

Also, I've heard that a lot of people have had similar problems with the
Amiga MINIX disks. Now I'm well aware that there are patches for Minix 1.5.
But SURELY (!!!!) I don't need the patches JUST to get the darn thing to
start doing SOMETHING past the /usr mounted stage??? If so, then the $250
is a total rip-off.

I'd appreciate some responses on this, because I'm getting a little fed up
with trying to get Minix going on my Amiga.

in earnest...

 

-- 
dbenn@leven.appcomp.utas.edu.au
David Benn - Applied Computing, University of Tasmania at Launceston.
---------------------------------------------------------------------
Everything should be as simple as possible, but not simpler. 
Newsgroups: comp.os.minix
From: dbenn@leven.appcomp.utas.edu.au (David Benn)
Subject: Re: AmigaMINIX floppy problems
Originator: dbenn@leven
Organization: University of Tasmania at Launceston
Date: Sat, 22 Aug 92 01:40:26 GMT

 
Thanks for that. At least I know it wasn't just me.
I'll keep your tips in mind.
 
Now for the good news! Although I consistently got errors by using a PC
diskcopy program (on a PC in fact), when using transfer -f in AmigaDOS
mode, followed by diskcopy in Minix, things worked just dandy. I noticed a
couple of weird things however:
 
	1. If I tried to write protect my originals when diskcopying
	   Minix seemed to assume that the target disk was
	   write-protected too. Does Minix only check for the write
	   protected status of the source disk?
 
	2. If I used a disk that I had previously used to copy one
 	   of the Minix originals onto (via PC diskcopy), it would
	   come through the transfer -f okay, but a Minix diskcopy
	   would fail to work correctly, instead giving a heap of
	   bad sector errors.
 
Along with the PC diskcopy failures, 2 leads me to conclude that the floppy
drivers must be very sensitive in Minix...
 
Now that I have Minix up and running, I intend to install the patches, and
customise things a little.
 
I apologise for the severe tone of "voice" I used in my last posting. I
guess I was just getting a tad frustrated.
 
Oh, BTW, can someone give me an answer to the question I posed last time
about how to get Minix to accept the ROOT and /usr disks in a different
drive at boot time? The prompt for the ROOT disk says that the bootdev can
be specified. Does this mean just another disk apart from ROOT in dd0? Or
can I specify the 2nd or 3rd disk drive...?
 
Regards...
 
--
dbenn@leven.appcomp.utas.edu.au
David Benn - Applied Computing, University of Tasmania at Launceston.
---------------------------------------------------------------------
Joyous distrust is a sign of health;

-- 
dbenn@leven.appcomp.utas.edu.au
David Benn - Applied Computing, University of Tasmania at Launceston.
---------------------------------------------------------------------
One Age cannot be completely understood if all the others are not
From: newton@iagu.itd.adelaide.edu.au (Mark Newton)
Newsgroups: comp.os.minix
Subject: Re: dosread
Date: 19 Aug 92 23:23:22 GMT
Organization: University of Adelaide, South Australia

In article <1992Aug18.183026.8428@udel.edu> hilander@silver.lcs.mit.edu (Most things are better eaten than forgotten) writes:
>i do a dosread -a foobar > /tmp/foobar
>with no luck
>i have tried to get a file off of the a drive.. no luck

dosread expects a block special device that it is supposed to read from.

So, to read something from drive A:, use a command line like this:

   dosread -a /dev/fd0 foobar > /tmp/foobar

/dev/fd0 corresponds to the A: drive.

If you want to use dosread with a hard disk partition, then you'll have to
make sure that a block special device exists which has major and minor
device numbers corresponding to your DOS partition.

   - mark


-- 
------------------------------------------------------------------
         'Do not expose your LaserWriter to naked flame...'
newton@iagu.itd.adelaide.edu.au         - Apple LaserWriter Manual
------------------------------------------------------------------
From: hilander@silver.lcs.mit.edu (Kewpie Stabs)
Newsgroups: comp.os.minix
Subject: man page sources
Date: 18 Aug 92 04:40:17 GMT
Organization: University of Delaware
Originator: mmdf@louie.udel.edu

where can i find man pages sources...
the FAQ i looked at had a site that discontinues carrying it?

thanx
hilander@silver.lcs.mit.edu
-- 
Mail System (MMDF)
From: awoodhull@hamp.hampshire.edu
Subject: Re: Does the Shoe Fit?
Organization: Hampshire College
Date: Sat, 15 Aug 1992 12:40:17 GMT

In article <281@darth.pgh.pa.us>, jones@darth.pgh.pa.us (Davey Jones) writes:
> 
> ... I bought OS/2 while it was still $49.
> Now my problem is how to run the multiple operating systems!  IBM supplies
> a so called Boot Manager but before I get into that I wonder if Shoelace,
> which I am presently using to switch between DOS and Minix, can handle
> the booting of OS/2?
> 
The advantage of the OS/2 Boot Manager is that it allows you to use the OS/2
high performance file system. For me this was very much outweighed by
the fact that the Boot Manager itself would require one partition on the 
hard disk and the OS/2 HPFS file system would use another partition which
would be unreadable by DOS, which I still expect to be my major operating
environment. I don't think I will consider using the Boot Manager until 
a real use for OS/2 comes along or until I get multiple hard drives and
have more than four partitions available.

(...at last getting around to the original question) I found the OS/2
Dual Boot system entirely consistent with MXBoot, which I use to boot Minix. 
The Dual Boot uses the FAT file system, and actually boots MS-DOS, then 
either continues to install MS-DOS or boots OS/2 depending upon which version
of config.sys is currently on the boot partition. This allows both
MS-DOS and OS/2 to share partitions and read each other's files and leaves
the other three partitions available for up to three other bootable
operating systems if something like MXBoot is available. I would think
Shoelace would work equally well. 

Albert S. Woodhull  
School of Natural Science, Hampshire College, Amherst, MA 01002
413-549-4600 ext 581 (office), 413-549-4740 (home)
awoodhull@hamp.hampshire.edu, woodhull@dawn.hampshire.edu
From: wkt@rodos1.adfa.oz.au (Warren Toomey)
Newsgroups: comp.os.minix
Subject: Re: man page sources
Date: 19 Aug 92 02:04:28 GMT
Organization: Australian Defence Force Academy, Canberra, Australia

From article <1992Aug18.044036.13529@udel.edu>, by Kewpie Stabs <hilander@silver.lcs.mit.edu>:
> where can i find man pages sources...
> the FAQ i looked at had a site that discontinues carrying it?

minnie.cs.adfa.oz.au, anonymous ftp, cd minix/manuals, mget *.*

:-)

	Warren


  Warren Toomey VK1XWT, on the path to insanity
  No longer in the bowels of ADFA Comp Science.
   `Version 7 Job Control: just use ptrace(2).'
From: iiitac@PYR.SWAN.AC.UK (Alan Cox)
Newsgroups: comp.os.minix
Subject: TAS instructions
Date: 19 Aug 92 09:42:34 GMT


I can't speak for the mac but any code relying on the TAS instruction
ois very very likely not to work if ported across to the Amiga. The 
amiga expansion bus cards often dont support the special read-modify-
write cycle used by the 68k to do the instruction.

Alan