[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

4992.0. "Minix probs - what else!!" by GIDDAY::MORAN () Sat Aug 24 1991 06:41

    All right all you minix guru's time to show off and tell me what stupid
    things I have done wrong :-)
    
    
    After hearing all the rave review's and with Field service work
    requiring more and more ULTRIX experience I decided to buy MINIX.
    
    After paying out $250 Australian!! I took it home and followed the
    instructions to the letter. But no luck - I have the same problems
    Bob Dupre had. I'll list out exactly what happened.
    
    Running under 1.3 I executed the minstall1.3 script. After that
    sucessfully ran I reset the machine and rebooted with the minix boot
    disk. It loads the .img file and then prints up Amiga MINIX blah blah
    blah and then it hangs.
    
    Machine type : A3000 10Megs memory with 50Meg SCSI.
    
    After reading John's notes about bad bugs with earlier version of Minix
    I copied down the amiga_1_5_10_boot.lzh file off DFS. I then compared
    the copyright notice on both the minix boot loader files. I was'nt
    suprised when I saw the the program I had bought was copyright 1989 and
    john's copy was copyright 1990,1991!!!
    
    So  I then rebooted minix with the new files off DFS and it asked for the
    root disk. Gave it that and then I gave it the /usr1 disk. I then
    succesfully logged in as the root user but now I have the problem Bob
    had were I try to do an LS and it says NOT ENOUGH CORE.
    
    Is this a problem because I using the latest loader and .IMG file and
    an old version of the Root disk ?????
    
    The only way I can get MINIX close to working is to use the loader and .IMG
    file that comes with Fish disk 530? which has the DEMO version of MINIX
    on it.
    
    Is there something stupid I have left out or do I have to sent my MINIX
    disks to prentice-hall for 3 months to get my upgrade??
    
    
    Thanks in advance --
    
    Shaun (who really would like to run UNIX on his AMY one day)
    
                                                     
T.RTitleUserPersonal
Name
DateLines
4992.1chmem ?STAR::GUINEAUbut what was the question?Sat Aug 24 1991 09:3911
Try using the chmem command. It set's the memory usage limits for
other commands.

# chmem  /bin/ls  (I think this will work to show what it's at now)
# chmem +5000 /bin/ls


I'm not sure of the path to ls (/bin or /usr/bin). The idea is to
add x number of bytes to the ls command's memory usage limits

john
4992.2Some quick questionsGIDDAY::MORANSat Aug 24 1991 10:2825
    Ok I'm impressed John - that was a QUICK reply!!
    
    I tried what you said and it worked fine. What is the policy of
    Prentice-Hall regarding upgrade's since I've been given and older
    version of MINIX.
    
    Just a couple of wuick questions if you don't mind ..
    
    
    - Is there and FTP file area where MINIX patches/manual's are kept.
    
    - With the DEMO version of minix there is a device already created
    in /dev called s0l0. This is for the first SCSI drive. There was no
    such device in the Root disk that I been given. I take that I create
    this special 'file' using the MKNOD command ?
    
    - How does one go about making it possible so a terminal connected to
    the terminal line will work.
    
    Thanks again for the quick response. It just proves once again tht this
    notes conference is one of the best reason's to work for DEC!
    
    Shaun.
    
    
4992.3STAR::GUINEAUbut what was the question?Sat Aug 24 1991 13:0958
>                       <<< Note 4992.2 by GIDDAY::MORAN >>>
>                            -< Some quick questions >-
> 
>     Ok I'm impressed John - that was a QUICK reply!!
>     

I just happened to be working on these NASA images today and need to 
grab various PD things now and then...


>     I tried what you said and it worked fine. What is the policy of
>     Prentice-Hall regarding upgrade's since I've been given and older
>     version of MINIX.
>     

I'm not sure, although I don't think the patches we have are at PH yet.
Besides, you can get the latest patches off the net much faster and sooner
than dealing with PH (YARTWFD - Yet another reason to work for DEC :-)


>     Just a couple of wuick questions if you don't mind ..
>     
>     
>     - Is there and FTP file area where MINIX patches/manual's are kept.

Yes, there's a bunch. They are listed in the Minix FAQ (Frequently Asked
Questions) which is posted to comp.os.minix periodically. Do you read
Usenet? 

>     
>     - With the DEMO version of minix there is a device already created
>     in /dev called s0l0. This is for the first SCSI drive. There was no
>     such device in the Root disk that I been given. I take that I create
>     this special 'file' using the MKNOD command ?

Yup. And then I think you do a mkfs. The docs with the update describe how
to make more partitions come alive.

>     
>     - How does one go about making it possible so a terminal connected to
>     the terminal line will work.
>     

People have used various methods. I've used kermit to dial into work 
(didn't try file transfers). Again, Usenet is a good source for experiences
with this stuff...


>     Thanks again for the quick response. It just proves once again tht this
>     notes conference is one of the best reason's to work for DEC!
>     
>     Shaun.
>     
>     
> 


john
4992.4comp.os.minix?GIDDAY::MORANSun Aug 25 1991 08:5813
    The only acces to USENET I have is through using VNEWS which
    unfortunately with my location in the scale of easynet makes things a
    big slow at times.
    
    When you said the docs with the update metion how to make new device
    files I take it that these docs are on comp.os.minix??
    
    Thanks again for the help - I extracted and printed the minix notes
    conference but unfortunately there was'nt much amiga specific
    information in there.
    
    Shaun.
    
4992.5STAR::GUINEAUbut what was the question?Sun Aug 25 1991 22:41115
>     
>     When you said the docs with the update metion how to make new device
>     files I take it that these docs are on comp.os.minix??

There should be a text file with the update kit which describes how to set
up hard disk partitions.


Here is the README-FIRST file from an update I received from the Minix
developers. It's older than the current stuff, but the information should
still be valid.



Some info about this version of amiga minix.

New features:

	The harddisk driver should work with the A590, A2091 and A3000.
	Minix runs on 68000, 68010, 68020 and 68030 processors.
	The serial task works properly with zmodem up to 9600 baud.
	Disk fonts can be used as the minix font, by using the -fn
		option of the loader.
	The minix readclock binary is no longer needed, the AmigaDOS
		time is now used for minix.

Please put diskfont.library in boot:libs!
Please add 'setclock opt load' to the boot:s/startup-sequence,
and put setclock in boot:c.

Minor device numbers:

	We have devised a new mapping between disks and minor device numbers.
	All hard disks still have major device number 3. The minor device 
	numbers are allocated as follows:

        minor   physical disk                   suggested name

        0       SCSI addr 0, whole disk         /dev/s00
        1..7    SCSI addr 0, partition 1..7     /dev/s00p1 .. /dev/s00p7
        32      SCSI addr 1, whole disk         /dev/s10
        33..39  SCSI addr 1, partition 1..7     /dev/s10p1 .. /dev/s10p7
          :           :          :                   :

        224     'XT' drive 0, whole disk        /dev/xt0
        225..231        partitions 1..7         /dev/xt0p1 .. /dev/xt0p7


Partition table:

When MINIX boots, a partition table is printed (for debugging purposes).
The format is: minor device number, 1st cylinder, size, (name).
Example:

   1     2      0 M (MDH0)      # a SCSI hard disk with 3 partitions
   2     6     33 M (MDH2)
   3   513     33 M (MDH1)

XTinfo: 782, 27, 2, 54          # 'XT' drive found. 782 cyls, 27 sec/tk,
 225     2     10 M (DH0)       #  2 heads, so 54 sec/cyl.
 226   401      7 M (MINIX)
 227   692      1 M (DH1)
 228   760      0 M (MBOOT)

If the information does not (roughly) correspond with the information given
by HDToolBox DO NOT MAKE an AmigaMINIX partition, since that may overwrite
your AmigaDOS partitions.

For now, SCSI LUNs (logical unit numbers) other than 0 are not supported.

Once in a while an "a590: ISTR = ..." line is printed for debugging
purposes. If the hard disk driver seems to hang please wait until the
next "a590: ISTR..." line shows up. It may contain valuable information.

To be able to access your hard disk under AmigaMINIX you have to make
nodes in /dev; for example
mknod /dev/s00p1 b 3 1 0
mknod /dev/xt0 b 3 224 0
mknod /dev/xt0p2 b 3 226 0

The /dev/*hd* nodes are not used, so you might as well remove them.



How to set up your harddisk for AmigaMINIX.

1)	Create a partition on your harddisk called "MINIX" of at least
	1 MB. (The name is not very important).

2)	Make a copy of your (original) BOOT: floppy and copy the loader
	(called 'minix') and the new minix.img file onto that copy.

3)	Modify the S:startup-sequence of that floppy so that the loader
	is called without any options. You don't need the "-s" and "-e"
	options any more. The only option that you might want to try
	is -d 1, which will cause the loader to print some debugging output.

4)	Now you can boot AmigaMINIX and use the normal ROOT and USR floppies.

	If Minix has been able to work with your harddisk a partition table
	will be printed. The first number of each line is the minor device
	number, the string between parens in the partition name.

	You can mount the MINIX partition as follows:
	- Look up the minor device number of your minix partition in the
	  partition table, let's say 129.
	- Decide on which size the partition should be, at most the actual 
	  size of the partition, of course. Let's say 2048 (kilobytes).
	- mknod /dev/hdmx b 3 129 2048
	- mkfs /dev/hdmx 2048
	- /etc/mount /dev/hdmx /user

	You can access other partitions by making devices for the other
	minor device numbers shown in the partition table.