HDTenEightyP/NetNews huggingface dataset:
From: Glen Cornell <gcornell%core1@kssib.ksc.nasa.gov>
Subject: WANTED: AMIGA MINIX
Originator: mmdf@louie.udel.edu
Organization: University of Delaware
Date: Tue, 1 Sep 1992 11:53:23 GMT



If anyone has a copy of MINIX for the Amiga that they aren't using,
I'd like to buy it.  Send responces directly to me, please.

Glen

-----------------------------------------------------------
          Glen Cornell
          Office:   MZ-608
          Phone:    (407) 633-3917
          e-mail:   gcornell@core1.hssc.ksc.nasa.gov
-----------------------------------------------------------
-- 
Mail System (MMDF)
From: system@kryton.UUCP (Scott Beckstead)
Newsgroups: comp.os.minix
Subject: Minix on amiga
Date: 29 Aug 92 18:59:50 GMT
Organization: Paradox Alley F&SF BBS 805-492-8789

Hi all,
   I want to try out amiga minix, I have the demo disk and the book. 
I have had some success with the PC version.  Are the file systems 
compatable ( some one mentioned crossdos) Also my hard disk is made 
by C-ltd (out of business) Has anyone got either a driver for it or 
hardware specs so I can write the driver??  Alternately a driver
that will let me use a large file as a filesystem (hmmm I have 
code for that under dos perhaps it's adaptable).  
Thanks for the airtime
Scott



SYSOP: Paradox Alley  F&SF BBS and Usenet News/Mail 
805-492-8789  The Place For Science Fiction and Fantasy
"Spin My Nipple Nuts and Send Me to Alaska!"
Newsgroups: comp.os.minix
From: dbenn@leven.appcomp.utas.edu.au (David Benn)
Subject: Misc. AmigaMINIX questions
Originator: dbenn@leven
Organization: University of Tasmania at Launceston
Date: Tue, 1 Sep 92 06:22:41 GMT

From: dbenn@leven.appcomp.utas.edu.au (David Benn)
Newsgroups: comp.os.minix
Subject: Misc. AmigaMINIX quns
Distribution: world
Organization: University of Tasmania at Launceston

Well, I've managed to get a basic Amiga Minix environment set up but have
run into a few problems.

Firstly, is there anything special required to get elvis working? I've
tried giving elvis more memory with chmem (quite a lot) and as I have 3
Meg, there's plenty to give away. elvis just keeps crashing with a type 4
exception (illegal instruction I presume).

Also, stterm starts the writer but not the reader, then just hangs. Is
there anything special required to get stterm going? (ie: does another
program(s) have to be run first, or files changed?)

su has given me problems. Ideally I want to be able to su to root from my
user account. However, su never seems to give me root privileges. Any
suggestions?

Lastly, when moving from 1.5.10 to 1.5.10.1 and 1.5.10.2, is it NECESSARY
to apply all the patches? In other words can JUST the boot disks be used
without applying any patches? I extracted Makedev and format from the
1.5.10.1 src.tar.Z file, but are the other patches only source file patches
in which case does the whole system have to be recompiled? Is this the same
for the 1.5.10.2 src.tar.Z patch archive? 

I'm just a little confused about the extent to which these patches must be
applied. Any and all help appreciated...



-- 
dbenn@leven.appcomp.utas.edu.au
David Benn - Applied Computing, University of Tasmania at Launceston.
---------------------------------------------------------------------
Once you are open to questioning rituals and time-honoured practices,
From: newton@iagu.itd.adelaide.edu.au (Mark Newton)
Newsgroups: comp.os.minix
Subject: Re: Everything you wanted to ask (but waited for me to)
Date: 26 Aug 92 23:54:38 GMT
Organization: University of Adelaide, South Australia

In article <1992Aug25.224119.10931@news.Hawaii.Edu> newsham@wiliki.eng.hawaii.edu (Timothy Newsham) writes:
>(1) why is the disk so flakey?  my drive 2 which is internal (df1:)
>on my A2000 refuses to accept minix disks (or rather minix refuses
>to play along with it)

The floppy disk device driver as distributed by Prentice Hall is
_very_ buggy.  If you install the v1.5.10.1 patches (and, for that
matter, v1.5.10.2) then those problems are alleviated.  You can ftp
the patches from ftp.cs.vu.nl.

>(2) has there been any device driver written for amiga disks that
>uses amiga standard tracks rather than the ibm mfm format? (I would
>imagine such devices would be faster and more reliable on amiga
>drives,  and have slightly better capacity.  But disk compatibility
>would be lost)

I thought about doing something like that myself... then I bought
a hard disk :-)  It certainly has its merits, though.

>(3) Which hard drives are currently supported, including any
>available via ftp on internet.  

The v1.5.10.1 patches include a device driver for Commodore hard disks
(the A590, A2090, A2091 and A3000).  You'll have to ask around for any
others.

>(4) has there been any work done on MMU support or other (better than
>'000 can support) features?

Don't think so.

>(5) Where are all the diff's at, where are minix binaries at?  where
>is the manual page set at?  Is there a nice organized ftp list
>concerning minix that details what programs and which type of programs
>are available?

See the FAQ for some details;  The MINIX Software List (available
by ftp from minnie.cs.adfa.oz.au) also tells you where to get some
major-ish packages.

    - mark
-- 
------------------------------------------------------------------
         'Do not expose your LaserWriter to naked flame...'
newton@iagu.itd.adelaide.edu.au         - Apple LaserWriter Manual
------------------------------------------------------------------
From: newton@iagu.itd.adelaide.edu.au (Mark Newton)
Newsgroups: comp.os.minix
Subject: Re: Misc. AmigaMINIX questions
Date: 2 Sep 92 23:59:02 GMT
Organization: University of Adelaide, South Australia

In article <1992Sep1.062241.5410@cam.compserv.utas.edu.au> dbenn@leven.appcomp.utas.edu.au (David Benn) writes:
>Also, stterm starts the writer but not the reader, then just hangs. Is
>there anything special required to get stterm going? (ie: does another
>program(s) have to be run first, or files changed?)

Nope.  Try recompiling it (and, perhaps, elvis, since you seem to be having
inexplicable problems with that too).  Some of the programs in the P-H
distribution do have bugs, but they're fixable by recompiling (ghod knows
why;  Perhaps they were originally compiled for a Mac/Atari with slightly
different libraries).

>su has given me problems. Ideally I want to be able to su to root from my
>user account. However, su never seems to give me root privileges. Any
>suggestions?

Yes:  chmod 4755 /usr/bin/su

su needs to be setuid root, otherwise it can't start a root shell.

>Lastly, when moving from 1.5.10 to 1.5.10.1 and 1.5.10.2, is it NECESSARY
>to apply all the patches? In other words can JUST the boot disks be used

The 1.5.10.2 patches include some fixes to the C library which eliminate
countless bugs.  It is in your own best interests to apply the patches
and recompile the kernel/library.

>without applying any patches? I extracted Makedev and format from the
>1.5.10.1 src.tar.Z file, but are the other patches only source file patches
>in which case does the whole system have to be recompiled? Is this the same
>for the 1.5.10.2 src.tar.Z patch archive? 

Whole system?  If you mean the kernel/mm/fs, then yes.  You don't have
to recompile all the commands, though.

   - mark


-- 
------------------------------------------------------------------
         'Do not expose your LaserWriter to naked flame...'
newton@iagu.itd.adelaide.edu.au         - Apple LaserWriter Manual
------------------------------------------------------------------
From: waltje@cs.vu.nl (Kempen van Fred)
Newsgroups: comp.os.minix
Subject: Re: Looking for Peter Housel
Keywords: Peter Housel
Date: 30 Aug 92 22:14:04 GMT

tim@maths.tcd.ie (Timothy Murphy) writes:

>Apologies for wasting the bandwidth,
>but I wonder if anyone would have Peter Housel's e-mail address?

Peter Housel is currently living in Korea, where he is
teaching English classes.  I have his home (US..) address
here, but I promised not to e-mail that out on the net,
because that is his parental address.

Please send e-mail to me for an arrangement...

Fred.
-- 
--
Fred N. van Kempen                           | Home: waltje@uwalt.nl.mugnet.org
VU Amsterdam, Fac. Math && Computer Science  | Work: waltje@cs.vu.nl
Newsgroups: comp.os.minix
From: newsham@wiliki.eng.hawaii.edu (Timothy Newsham)
Subject: 68k gcc.. yet another faq
Organization: University of Engineering, College of Engineering
Date: Sat, 29 Aug 1992 06:41:03 GMT

I cant seem to be able to locate gcc binaries for minix 68k
(in particular I am on an amiga)
Seems that the sites that are supposed to have it either
dont or are unreachable by me at the current time ...
Anyway,  if you know of ftp sites with gcc for minix 68k please
drop me a line, or better if you have it online, mail it to
me or drop me a line or something...  thank you very much
                                 ...
From: osymh@giac1.oscs.montana.edu (Michael L. Hitch)
Newsgroups: comp.os.minix
Subject: Re: Everything you wanted to ask (but waited for me to)
Keywords: n
Date: 28 Aug 92 17:20:19 GMT
Organization: Montana State University, Bozeman  MT

In article <15918@star.cs.vu.nl> sreiz@cs.vu.nl (Reiz Steven) writes:
>newsham@wiliki.eng.hawaii.edu (Timothy Newsham) writes:
>>on my A2000 refuses to accept minix disks (or rather minix refuses
>>to play along with it)
>
>The Prentice Hall distribution of amiga minix has some bugs in, a.o.,
>the floppy driver. Please try 1.5.10.1 or 1.5.10.2.

  I had problems with the floppy drive on my Amiga 1000, even with the
1.5.10.1/1.5.10.2 versions.  I have been working on an AmigaDOS program
to read/write a Minix filesystem and by using the messydisk.device from
MSH (MessyDOS FileSystem Handler), and it seemed to work much better.

>>(3) Which hard drives are currently supported, including any
>>available via ftp on internet.  
>
>The PH distribution supports neither harddisks, nor 68010 and higher
>processors.
>The 1.5.10.1 (and higher) support processors up to the 68030 (68040 untested)
>and Commodore harddisk controllers (A590, A2091, A3091 (builtin-A3000)).
>

  1.5.10.2 won't run on the 68040 if you are using AmigaDOS 2.04.  The loader
attempts to turn off the MMU translation, and the 68030 instruction for that
is invalid on the 68040.  Also the cache control instructions are different,
so the cache invalidate routines have to be modified.

  Also, even though amwini.c says it supports the A2090, it doesn't.  I was
able to borrow a friend's A2090 card and try it out.  I disassembled the
AmigaDOS driver enough to determine that the A2090 interface is quite 
different from the way amwini.c tries to use it.

	Michael L. Hitch

-- 
Michael L. Hitch			BITNET:    OSYMH@MTSUNIX1.BITNET
Computer Services Consultant		INTERNET:  osymh@msu.oscs.montana.edu
Office of Systems and Computing Services
Montana State University	Bozeman, MT	USA
From: tvf@cci632.cci.com (Tom Frauenhofer)
Newsgroups: comp.os.minix
Subject: Seagate ST02 SCSI Driver for MINIX?
Date: 27 Aug 92 15:43:00 GMT
Organization: Northern Telecom, Network Applications Systems, Rochester, NY

Does anyone have a SCSI driver for Minix that is compatible with the
Seagate ST02 controller?  I just installed one of these puppies on my
system and would like to do more than just DOS around.

Thanks in advance!
--
Thomas V. Frauenhofer, WA2YYW, tvf@cci.com, ...!uunet!uupsi!cci632!tvf
Mandlebratwurst: The Meal that Eats Itself!
From: glalonde@vnet.ibm.com ("Glen Lalonde")
Newsgroups: comp.os.minix
Subject: error when compiling c68 v4 source code for c68.
Date: 29 Aug 92 03:41:57 GMT

The file msgout.c had an include of varagrs.h, this file is not on
my system(MacMinix 1.5.10) anyone else have trouble compiling it?
Can I just use stdargs.h?????
From: jaapv@accucx.cc.ruu.nl (Jaap Verhage)
Newsgroups: comp.os.minix
Subject: Re: More help
Keywords: minix help
Date: 2 Sep 92 16:40:19 GMT
Reply-To: jaapv@accucx.cc.ruu.nl
Organization: Academic Computer Centre Utrecht

ice@eskimo.celestial.com (Greg Toth) writes:


>Ok, I have Minix on 3.5" disks. tThe boot drive of my IBM is a 5.25.
>I can borrow a IBM with a 3.5" boot drive and 5.25 second drive and
>run but how can I back up my 3.5" boot disk to the 5.25?
>Just by readn the manual it is not even clear which command , if any,
>is used to perform backups. I probably sound a little stupid but
>the manual is not clear and I do not have a lot of time to experiment.
>Thanks in advance.
I'd say:
`dd' the 3.5" to your 5.25" drive , assuming you have a HD-5.25"
drive and a program capable of formatting the disk to the capacity
of your 3.5" disk. FDFORMAT comes to mind (for DOS). Or just try
`dd' without worrying; I guess the boot images on 3.5" and 5.25"
are the same. Good luck.
-- 
Regards, Jaap.

Jaap Verhage, Academic Computer Centre, Utrecht University, Holland.
jaapv@accucx.cc.ruu.nl   +<-*|*->+  I claim *every*thing and speak for myself
From: okir@monad.swb.de (Olaf Kirch)
Newsgroups: comp.os.minix
Distribution: world
Subject: uucico (probably outdated)
Date: Sun, 30 Aug 92 18:36:32 MESZ

Hi, everybody,

I want to report a bug on a certain uucico implementation, of which I
neither know its official name, nor if it's still used by anyone but me.
The source files say it was written by Lamb, Lynne, Housel, van Kempen,
and some 'cwr', and version is 3.9. as of May 30, 1991. I'm posting this
bug report to te net, since I don't know if there's still anybody
maintaining this  version. (and I don't have his/her address :-)

When I tried to change packet and window size to 128/7, I ran aground
some problems. Some of them were speed-related, since I'm still running
MINIX on an ST. Two others were not.

1. When debugging with level 12, uucico bombed out with a core dump. This
   is because the debugging function (yes:-)) visib(), which translates
   unprintable characters to \xxx octals has a buffer of only 256 bytes.
   You have to change that to at least 4*desired packet size.
 
2. After having transmitted a file, or having received one, uucico regularly
   hung. This was becasue of an error in the way it handles short data
   packets where the difference is more than 127 bytes.
   When a file transfer is complete, an empty short data packet is
   sent to signal EOF. Now, the correct thing to do would be to store
   the difference in length in the first two bytes of the packet data,
   low seven bits first with high bit set to one, then the upper bits.
   This implementation does it the other way round.

   	+---------------+---------------+
   	| byte 0	| byte 1	|
   	|7 6 5 4 3 2 1 0|7 6 5 4 3 2 1 0|
   	+---------------+---------------+
   	|1| bits 6-0	| bits 14-7	|	<-- correct
   	|1| bits 14-8	| bits 7-0	|	<-- wrong
   	+---------------+---------------+

   You have to go to gspack() and grpack() in the g protocol driver
   source, and change it.

3. In the 'g' init sequence, uucico takes over the values for packet and window
   size given to it by the other host. The correct way would be to compare
   them to the predefined values, and use them only if they're
   smaller. At least that's what I think, but I may be wrong here.

4. Oh, and yes! I forgot to mention! If you're compiling this with a
   compiler which has 16 bit integers on a machine which has 32bit pointers,
   make sure to include stdlib.h and time.h (ctime() and malloc()
   will appreciate this :-)

 Hope I've not been saying something that's already an old hat :-)
 
 	Olaf

-- 
---------------------------------------------------------------------------
| Olaf Kirch          Darmstadt          | okir@monad.swb.de              |
---------------------------------------------------------------------------
From: newton@iagu.itd.adelaide.edu.au (Mark Newton)
Newsgroups: comp.os.minix
Subject: Re: Question init.c <--> /etc/utmp
Keywords: init login utmp wtmp
Date: 27 Aug 92 05:49:42 GMT
Organization: University of Adelaide, South Australia

In article <meulenbr.714819852@cstw168> meulenbr@prl.philips.nl (Frans Meulenbroeks) writes:
>leno@grumpy.cray.com (Scott J. Leno) writes:
>
>>  I have been looking into why I seem to be logged in several times when I
>> run the who command. It stems from init not zeroing the /etc/utmp entry
>
>In /etc/rc add the line:
>>/etc/utmp
>which will clear the file whenever the system is booted.
>No need to change init.

Actually, there is a need to change init to handle wtmp properly in the
Amiga MINIX Prentice-Hall distribution (and probably the other m68k
MINIXes as well).

There's a call to time() that looks something like "ut.ut_time = time()"
which doesn't work due to the fact that init.c doesn't #include <time.h>.
The compiler thinks, "Duh!  time() hasn't been prototyped, so I'll
assume that it returns an int!" when it should be returning a long.
m68k byte ordering no doubt makes it work properly under PC MINIX,
but the 68000 version of the ACK compiler makes time() (and most other
functions, for that matter) return incorrect values if they're not
prototyped.

So, if any m68k MINIX users have been puzzled about all the question
marks in the output from the "last" command, you can fix it by putting
#include <time.h> at the top of init.c and rebuilding.

   - mark
-- 
------------------------------------------------------------------
         'Do not expose your LaserWriter to naked flame...'
newton@iagu.itd.adelaide.edu.au         - Apple LaserWriter Manual
------------------------------------------------------------------
From: root@frmxqnx.hanse.de (Frank Rabe)
Newsgroups: comp.os.minix
Distribution: world
Subject: C386 v4 tested
Organization: frmxqnx running Minix-386
Date: Thu,  3 Sep 92 23:56:35 +0100

Hi Minixer's

I have compiled c386 with code generated for (bruce evans) bas and bld.
I used bcc. - No problems
Then I compiled c386 with itself (will work only if you use com I+D for c386).
Other then com I+D no problems.

I run Minix386 with a lot of extensions (mini-X, vc, sym-links, scheduler, 
shared text,...) and have tried the following:
  I compiled fs and mm. - No problems, minix behave like normal.
  I compiled kernel too. - Real problems, minix prints "Starting Minix" and
    reboots. I used bcc -0 for the real mode parts of minix. Any ideas ?


Looks like a nice compiler. Not much slower than bcc. 
I think it could be a usefull ANSI compiler for minix386 and as I red also for
the 68xxx. The only thing which is needed is a assembler which is able to use
the generated floating code, bas doesn't do it. No, No, not gas (gnu assembler) 
much to big for minix. Has somebody done something on that field? Is it possible
to modify bas and bld? - 
	Hi Bruce (Evans), (hope you are listening) is it 
	possible to get the source for bcc, as and ld, or 
	at least for as and ld?

The assembler and the linker are the last things I need to have EVERYTHING in 
source. 
I believe the gnu tools like gcc, gas and gld are not of the appropriate size
for a small and smart system like minix.

Is someone (except me) still playing with mini-X sometime?
A small window manager and a mini-X-terminal based on mini-X would be nice. 
Wouldn' t it?


Enjoy minix.

Frank
From: newton@iagu.itd.adelaide.edu.au (Mark Newton)
Newsgroups: comp.os.minix
Subject: Re: Anyone ported shh or tcsh to MacMinix?
Date: 26 Aug 92 23:56:38 GMT
Organization: University of Adelaide, South Australia

In article <drew.714790351@cs.anu.edu.au> drew@cs.anu.edu.au (Drew Corrigan) writes:
>I am trying to port either of shh or tcsh to MacMinix and have experienced
>difficulties with both.
>Has anyone else done this successfully?

Yes.  You can ftp the tcsh binary from ftp.uni-koeln.de, found
in /thp/minix/commands/shells/tcsh6_01m68k.tar.Z

   - mark


-- 
------------------------------------------------------------------
         'Do not expose your LaserWriter to naked flame...'
newton@iagu.itd.adelaide.edu.au         - Apple LaserWriter Manual
------------------------------------------------------------------
Newsgroups: comp.os.minix
From: hp@vmars.tuwien.ac.at (Peter Holzer)
Subject: Re: Minix/386: why are 16-bit binaries not allowed?
Keywords: Minix 386
Organization: Technical University Vienna, Dept. for Realtime Systems, AUSTRIA
Date: Thu, 3 Sep 1992 16:16:53 GMT

rwmj@st-andrews.ac.uk (Richard William Martin Jones) writes:

>Hi.

>As it stands, you don't appear to be able to run 16-bit binaries under
>Bruce's 32-bit kernel. Why is this? 

I think the main reason is that the data sizes are different. The
kernel and the servers would have to use different message formats
depending on wether they communicate with a 16-bit or a 32-bit program.
This probably means a lot of little changes everywhere.

	Peter
-- 
|    _  | Peter J. Holzer                       | Think of it   |
| |_|_) | Technical University Vienna           | as evolution  |
| | |   | Dept. for Real-Time Systems           | in action!    |
| __/   | hp@vmars.tuwien.ac.at                 |     Tony Rand |
From: grundy@rtf.bt.co.uk (Martin Grundy)
Newsgroups: comp.os.minix
Subject: Re: SIGHUP with a MUGNET kernel
Date: 26 Aug 92 08:37:21 GMT
Organization: BT Customer Systems, Brighton, UK

In article <920825109@comsat.hacktic.nl> marcel@comsat.hacktic.nl (Marcel Kat) writes:
>I have a problem with the SIGHUP package as posted in Februari this year.
>
>As soon as an interference occurs on the 'mains', like when i put
>a light on, Minix or more likely INIT goes in a SUSPEND state.
>As a result a reboot is the only way out. It happens about 3 times a day.

I installed the SIGHUP package (from James de Silve) on my Minix386 and
have noticed a similar thing, although not so serious.  If I apply power
to a modem when it is already connected to the com port, it *sometimes*
crashes the system.  It has never trashed the filesystem though (yet:-) -
it probably does a sync().

I haven't looked into the problem; I always make sure to disconnect the
v24 cable if I need to connect/disconnect the power to the modem.
-- 
--
Martin Grundy                     |  email: grundy@rtf.bt.co.uk
British Telecom Customer Systems  |
Hyperion House                    |  phone: +44 273 762105
96-99 Queens Road                 |  fax:   +44 273 722038
Brighton BN1 3XF.                 |
Newsgroups: comp.os.minix