RE: 2/bin/ash: bad interpreter: No such file or direct ory

You can use a loop filesystem, really a loop filesystem is easy to put
just about anywhere, for example, if you had a DOS drive mounted on /C,

dd if=/dev/zero bs=10k count=15000 of=/C/loopfile
mke2fs /C/loopfile
mount /C/loopfile /mnt
cd /mnt

-Tom

On Tue, 14 Jan 2003, Ian Stanaway wrote:

> Date: Tue, 14 Jan 2003 09:43:36 -0800
> From: Ian Stanaway <[email protected]>
> To: 'Tom Oehser' <[email protected]>, Ian Stanaway <[email protected]>
> Cc: "'[email protected]'" <[email protected]>
> Subject: RE: [tomsrtbt] 2/bin/ash: bad interpreter: No such file or
>     direct ory
>
> Yes, it does fail w/ rebuild w/ no changes.  Also if I try buildit.s from a
> nfs mounted tomsrtbt slave node the script actually starts but has a file
> writing permisson error when it tries to do something in the nfs directory.
> Permissions shouldn't be a problem because I have the nfs open to anything.
> So as you say in your docs do it under itself as you do.  I have found in
> your docs that if you buildit under itself you need to mount a drive and
> make a filespace.  I'm not sure that I have a partition that I can use for
> that.  Do you have a good howto on using/creating a proper partition for
> such a useage?
> Thanks,
> Ian
>
> -----Original Message-----
> From: Tom Oehser [mailto:[email protected]]
> Sent: Monday, January 13, 2003 7:06 PM
> To: Ian Stanaway
> Cc: '[email protected]'
> Subject: Re: [tomsrtbt] 2/bin/ash: bad interpreter: No such file or
> directory
>
>
>
> Dunno, does it happen when you unpack/rebuild with no changes at all?
>
> -Tom
>
> On Mon, 13 Jan 2003, Ian Stanaway wrote:
>
> > Date: Mon, 13 Jan 2003 14:52:43 -0800
> > From: Ian Stanaway <[email protected]>
> > To: "'[email protected]'" <[email protected]>
> > Subject: [tomsrtbt] 2/bin/ash: bad interpreter: No such file or directory
> >
> > Hi,
> >
> > I'm trying to use 2/bin/buildit.s (and other permutations) and I keep
> > getting this error under RH7.3.  I can see that there is a ash in 2/bin/
> I
> > copied the libc5 from the unpacked directory into my /lib and did the
> proper
> > linking... so it shouldn't be a libc problem with RH.
> >
> > I've read through your mail archives and nothing jumps out that seems to
> > work for my problem.  Any ideas would be great.
> > Thanks
> > Ian
> >
>