All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Kalogirou <harkal@gmx.net>
To: jb1@btstream.com
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: "mount" bug
Date: 25 Oct 2002 16:30:06 +0300	[thread overview]
Message-ID: <1035545532.5491.4.camel@cool> (raw)
In-Reply-To: <Pine.LNX.4.33.0210250226530.26009-100000@olympus.btstream.com>

> /dev/fd1 seems to mount, but be inaccessible.
> 
> After booting ELKS 0.1.1 from a 3-1/2" diskette in /dev/fd0, "mkdir /mnt",
> "ls -l /" shows 2 hard links and a 32-byte size for mnt.
> 
> "mount /dev/fd1 /mnt", when /dev/fd1 contains a 5-1/4" ELKS diskette,
> shows:
> fd: probing disc in /dev/fd1
> fd: /dev/fd1 probably has 15 sectors and 80 cylinders
> MINIX-fs: mounting unchecked file system, running fsck is recommended.
> 
> "ls -l /" now shows 10 hard links and a 160-byte size for mnt.
> 
> "ls /mnt" now shows:
> /mnt:
> /mnt/in/sh
> : No such file or directory
> 
> After this point, "meminfo" shows *more* free and the system rapidly
> deteriorates ("Cannot fork", a blank commandline prompt, a garbage 
> commandline prompt, etc.)
> 
> Changing /mnt's permissions, owner and group don't help. Interchanging the 
> 3-1/2" and 5-1/4" drives didn't help, although there were more error 
> messages from mount. Using 5-1/4" drives for both /dev/fd0 and /dev/fd1 
> (with an ELKS 0.1.0 diskette in /dev/fd1) didn't help.
> 

I tried it on my machine, but with 2 3-1/2 drives and it works fine.

Harry





  reply	other threads:[~2002-10-25 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25  9:28 "mount" bug jb1
2002-10-25 13:30 ` Harry Kalogirou [this message]
2002-10-26  8:55   ` jb1
2002-10-26 14:49     ` Harry Kalogirou
2002-10-27 12:57       ` fork bug [WAS: Re: "mount" bug] jb1
2002-10-27 19:49         ` Harry Kalogirou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1035545532.5491.4.camel@cool \
    --to=harkal@gmx.net \
    --cc=jb1@btstream.com \
    --cc=linux-8086@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.