Very Computer

My problem is that when I boot the Linux system, it reports (correctly)
that it cannot find /etc/rc.d/rc.D, and other rc.* files therein.  The
files are there, but don't seem to be found at boot time for some
reason.  Any help would be greatly appreciated.  I'd love to execute
those scripts when I startup. <grin>

Can I execute them manually somehow?  I tried changing to the directory
they are in, and typing the exact file names (ie "> rc.D") but nothing
happened.  

Many thanks,
Scott Davis.

:    My problem is that when I boot the Linux system, it reports (correctly)
:    that it cannot find /etc/rc.d/rc.D, and other rc.* files therein.  The
:    files are there, but don't seem to be found at boot time for some
:    reason.  Any help would be greatly appreciated.  I'd love to execute
:    those scripts when I startup. <grin>

: I tried installing a UMSDS version over the weekend, and it failed
: too. I think it is due to the fact that the installation process
: (i.e. the root or boot disk) didn't ask me for a swap file
: (I seem to remember it used to do). Hence I had to make one (setup really
: doesn't work on 4Mb physical memory , believe me, you get
: really bizarre errors), which I did by mounting /dev/hda1, (-t msdos)
: and creating a swap with dd, then mkswap and swapon.

Nice to hear that somebody else has the same problem, at least. (??!!)  
<grin>  I'll re-install and manually setup a partition.  Thanks for the tip!

Best wishes,
Scott.

   I just installed the latest slackware UMSDOS version from sunsite.  My
   machine is a 486SX/25, 4 Megs Ram, IDE 200 Meg hard drive.  

   My problem is that when I boot the Linux system, it reports (correctly)
   that it cannot find /etc/rc.d/rc.D, and other rc.* files therein.  The
   files are there, but don't seem to be found at boot time for some
   reason.  Any help would be greatly appreciated.  I'd love to execute
   those scripts when I startup. <grin>

   Can I execute them manually somehow?  I tried changing to the directory
   they are in, and typing the exact file names (ie "> rc.D") but nothing
   happened.  

I tried installing a UMSDS version over the weekend, and it failed
too. I think it is due to the fact that the installation process
(i.e. the root or boot disk) didn't ask me for a swap file
(I seem to remember it used to do). Hence I had to make one (setup really
doesn't work on 4Mb physical memory , believe me, you get
really bizarre errors), which I did by mounting /dev/hda1, (-t msdos)
and creating a swap with dd, then mkswap and swapon.
However, in the process your disk is mounted with the msdos file
system, and I noted all kinds of error messages whenever files
were copied by setup that didn't fit in the 8+3 dos naming
convention. Seems to fit your description of errors too.

Anyways, this was the  conclusion I reached. Basically, the installation
procedure has changed since 2.0 (or 2.1) when it *did* ask me from
within the boot/root to create a swap. Now I had to do it manually,
and thus the rest failed. Perhaps I've overlooked something,
in which case no doubt somebody will give us the right answer.

perhaps UMSDS is broken, or this part of slakware installation.
The manuals have never been very clear about this bootstrapping,
it's worth a mini FAQ.

peter
       _/_/_/  _/_/_/  _/_/_/  _/_/_/  _/_/_/
      _/  _/  _/        _/    _/      _/  _/
     _/_/_/  _/_/_/    _/    _/_/_/  _/_/_/
    _/      _/        _/    _/      _/    _/
   _/      _/_/_/    _/    _/_/_/  _/     _/   _/

                        |  URL       : http://www.astro.umd.edu/~teuben

Astronomy Department    |  FTP:      : ftp.astro.umd.edu          _-\_<,    /
University of Maryland  |  MA-BELL   : (301) 405-1540 (office)   (*)/'(*)  /
College Park, MD 20742  |              (301) 405-1502 (secr.)   __________/
L 38 58 50 N  76 56 14 W|  FAX:        (301) 314-9067
---------------------------------------------------------------
--
       _/_/_/  _/_/_/  _/_/_/  _/_/_/  _/_/_/
      _/  _/  _/        _/    _/      _/  _/
     _/_/_/  _/_/_/    _/    _/_/_/  _/_/_/
    _/      _/        _/    _/      _/    _/
   _/      _/_/_/    _/    _/_/_/  _/     _/   _/

                        |  URL       : http://www.astro.umd.edu/~teuben

Astronomy Department    |  FTP:      : ftp.astro.umd.edu          _-\_<,    /
University of Maryland  |  MA-BELL   : (301) 405-1540 (office)   (*)/'(*)  /
College Park, MD 20742  |              (301) 405-1502 (secr.)   __________/
L 38 58 50 N  76 56 14 W|  FAX:        (301) 314-9067
---------------------------------------------------------------

  When I was helping a friend install Linux on his MSDOS partition,
we were installing on a 24 MB Pentium 90MHz machine so we skipped
over the making of a swap file.  When we did this and started installing,
we started getting a lot of invalid file names.  When we went back and just
looked at things under the boot/root mount it had the hard disk mounted
under /mnt, but the /mnt/linux directory was a standard DOS file system.
When we created the --linux-.--- file there (touch /mnt/linux/--linux-.---)
we were then able to create long file names and proceed with the install.
  I did not have the time to try and diagnose further, but is it possible
that the install script was not making the UNIX-to-DOS mapping file?

  Dan

OBLinux-FS-on-DOS-hack: If you run out of space on your linux partition,
but don't feel like reinstalling to make the partition bigger (or can't)
just do this.  Instead of mounting your DOS file systems as "MSDOS",
mount them as a UMSDOS filesystem.  Regular DOS files will still show up
and be accessable, but if you create a directory and put the "magic"
--linux-.--- file in it, Linux can use that directory with long file names!

  When I was helping a friend install Linux on his MSDOS partition,
we were installing on a 24 MB Pentium 90MHz machine so we skipped
over the making of a swap file.  When we did this and started installing,
we started getting a lot of invalid file names.  When we went back and just
looked at things under the boot/root mount it had the hard disk mounted
under /mnt, but the /mnt/linux directory was a standard DOS file system.
When we created the --linux-.--- file there (touch /mnt/linux/--linux-.---)
we were then able to create long file names and proceed with the install.
  I did not have the time to try and diagnose further, but is it possible
that the install script was not making the UNIX-to-DOS mapping file?

  Dan

OBLinux-FS-on-DOS-hack: If you run out of space on your linux partition,
but don't feel like reinstalling to make the partition bigger (or can't)
just do this.  Instead of mounting your DOS file systems as "MSDOS",
mount them as a UMSDOS filesystem.  Regular DOS files will still show up
and be accessable, but if you create a directory and put the "magic"
--linux-.--- file in it, Linux can use that directory with long file names!