I aleady checked everything in a previous thread.
(Google in this newsgroup for "NFS install is giving",
and a thread with 20 articles comes up). The sort-of-conclusion
here was that this is a bug.

So also the proposed workaround - install from premounted dir -
doesn't work.

The symptons are that all package directories (a, ap, etc)
are flashed by,l but nothing get's installed.

And yes: the directory given is ok

Has anyone submitted this bug or found the solution?

aku

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On 10 Nov 2003 14:55:16 GMT, aku <aku@europe.com> wrote:
> Has anyone submitted this bug or found the solution?

I emailed Pat V originally when I was unable to install from an ISO-9660
loopback-mounted image on the destination drive, using it as a directory
pre-mounted. He responded, essentially stating it should have worked. I
wasn't completely sure what I was trying to do *should* have worked, nor
was I sure I actually did everything properly, so I just let it drop for
the time being. I didn't think much of it.

Then I came here and saw other folks with nearly identical problems and
decided to email Pat again. After I emailed him, I extracted the setup
scripts used for installing Slackware and went diving in, looking for a
possible answer to the problems folks seem to be seeing...

I did see a few places where the problem could be coming up... it almost
seemed to me like the switch media function was getting called before we
actually got installing, for some reason, but that doesn't totally align
with the way things work fine if you install from CD-ROM. I emailed Pat
regarding those spots that looked questionable, suggesting how to insert
a little bit of error-checking in there to be sure certain functions are
supposed to be called within the functions themselves, but never totally
got around to actually *testing* these myself. Pat never replied to the
email, so I just dropped it. I'm not exactly a bash scripping wizard, I
don't ever do things as complicated as install an OS from it... so I let
him do his thing without any more interference from me.

--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/r9n3hm6KEoOOAe0RAn7pAJ9gGWCO/BLemol+0t2Y5gioR4W5CwCgnFgl
ANP829muu+dXCFC7XJMws5Y=
=K8j/
-----END PGP SIGNATURE-----

Had a similar problem some time back and found that it was a problem
with NFS permissions. The NFS mount to the distribution libraries
appeared to work just fine but in fact I did not even have read
permission onto the directories, which needed to be addressed on the NFS
server side. I was able to isolate the problem however. During the
install, after the NFS mount has been done, switch to a different
console and try and access the mounted drive using something like "cat"
to list a file and prove that there is at least read access onto the
drive.

aku wrote:

> I aleady checked everything in a previous thread.
> (Google in this newsgroup for "NFS install is giving",
> and a thread with 20 articles comes up). The sort-of-conclusion
> here was that this is a bug.
>
> So also the proposed workaround - install from premounted dir -
> doesn't work.
>
> The symptons are that all package directories (a, ap, etc)
> are flashed by,l but nothing get's installed.
>
> And yes: the directory given is ok
>
> Has anyone submitted this bug or found the solution?
>
> aku

On 2003-11-16, cjb10 <cjb10@rogers.com> wrote:
> Had a similar problem some time back and found that it was a problem
> with NFS permissions. The NFS mount to the distribution libraries
> appeared to work just fine but in fact I did not even have read
> permission onto the directories, which needed to be addressed on the NFS
> server side. I was able to isolate the problem however. During the
> install, after the NFS mount has been done, switch to a different
> console and try and access the mounted drive using something like "cat"
> to list a file and prove that there is at least read access onto the
> drive.

problem is solved now...see slack changelog...it turned out to be
a problem with custom tagfiles not NFS.

>
> aku wrote:
>
> > I aleady checked everything in a previous thread.
> > (Google in this newsgroup for "NFS install is giving",
> > and a thread with 20 articles comes up). The sort-of-conclusion
> > here was that this is a bug.
> >
> > So also the proposed workaround - install from premounted dir -
> > doesn't work.
> >
> > The symptons are that all package directories (a, ap, etc)
> > are flashed by,l but nothing get's installed.
> >
> > And yes: the directory given is ok
> >
> > Has anyone submitted this bug or found the solution?
> >
> > aku
>