Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Rob Lembree <lembree@sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Success at last...
Date: Wed, 9 Sep 1998 16:03:00 +0200	[thread overview]
Message-ID: <19980909160300.C423@uni-koblenz.de> (raw)
In-Reply-To: <35F59FCD.F7A6E459@sgi.com>; from Rob Lembree on Tue, Sep 08, 1998 at 05:21:17PM -0400

On Tue, Sep 08, 1998 at 05:21:17PM -0400, Rob Lembree wrote:

> > This is really weird.  Can you explain in greater detail what you changed
> > to make sure that it worked?
> 
> I found that IRIX's tar wasn't very careful with modification dates,
> which I don't think is a problem, but the major and minor IDs of the
> dev files were all zero -- clearly broken.  I haven't experimented,
> but I believe this to be the failure.

This seems to indicate to me that we should replace the dev directory
with a script that creates the inodes.  Luckily we already have one which
is called ``MAKEDEV''.  As we already know the representation of the
minor / major device number isn't transparent through NFS, so the MAKEDEV
will have to detect the NFS server's OS and to corrospondingly munge the
device number used as argument for mkdev in a way that after exporting
from the NFS server the client sees what he expects to see.  If that is
at all possible in all cases.  Yuck.  But it's a longstanding problem
which before has already been reported by people using other operating
systems like HP/UX.

  Ralf

  reply	other threads:[~1998-09-09 23:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-04 16:03 Success at last Leon Verrall
1998-09-04 17:09 ` Alex deVries
1998-09-08 15:52   ` Leon Verrall
1998-09-08 21:21   ` Rob Lembree
1998-09-09 14:03     ` ralf [this message]
1998-09-10 14:56       ` Alex deVries

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=19980909160300.C423@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=lembree@sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox