[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: m68k boot-floppies ready



Hi Nick,
  Here are my comments on the debian-vme.txt you sent.  I've sent them
to the lists also, as some comments may be relevant to other sub-archs.

Cheers,
  Richard



Section 4:

    At the 'LILO Boot:' prompt enter one of the following to boot Linux and
    begin installation proper:

       install <Return>

Reads badly, as there is only one choice now.



In section 10:

    Press Return to accept the selected partition When asked whether you want
    to do a bad-block scan, you can safely skip this step, so select "No" here
    using Tab and then Return. When asked whether you really want to

I wasn't asked if I want a bad-block scan at any time in the install; has
that question been removed?



Section 11:

    Once the network is configure instead of selecting 'Initialize a Linux

Should be "configured,".



Section 13:

    If you are installing from an NFS mounted file system enter the NFS server
    address and mount path. Then enter the directory where the appropriate
    images-1.44/rescue.bin and drivers.tgz disk images are stored.
    Note: the rescue.bin file must exists in a subdirectory named images-1.44.

Could be replaced with:

    If you are installing from an NFS mounted file system you will be
    prompted to configure your network, if you have not already done so.
    Next enter the NFS server address and mount path.  You will then be
    prompted to enter the path inside the mounted NFS filsystem where
    the Debian Archive resides.  You should enter a path prefixed with
    /instmnt, which is the NFS mount point within the local filesystem.
    You are then prompted to select from a list or manually enter a further
    path within the archive to the directory holding <subarch>.  You can
    generally just hit <return> twice at this point.

Too many paths involved there.  Don't think the Note above is really
needed, if people have followed the layout in section 2.  In any case,
you really need to enter directory holding <subarch> and base2_2.tgz,
not the directory holding images-1.44.


Section 14:

Could add that for VME the ethernet driver, scsi, adn serial drivers are
compiled in, so that people dont go searching for modules.



Section 16:

Seems to tail off half way through a sentence.



--end--


Reply to: