Unslung 6.8 large file problem

[randy_holcomb]

Got an issue with Unslung with files over 1 GB:

They don't show up when you do an ls,
You can't do a chmod against them.

What's interesting is that when the files get created, the
permissions get set to 750, but I'd like to get them set to 755.

Ideas?

Randy

[randy_holcomb]

--- In nslu2-linux@..., "randy_holcomb" <raholco@...>
wrote:

>
> Got an issue with Unslung with files over 1 GB:
>
> They don't show up when you do an ls,
> You can't do a chmod against them.
>
> What's interesting is that when the files get created, the
> permissions get set to 750, but I'd like to get them set to 755.
>
> Ideas?
>
> Randy
>

I looked around and found coreutils, so I did an ipkg install
coreutils and rebooted the Slug, but I still have the same problem.

[rolandkbs-2]

The coreutils are installed inot /opt/bin. Either adapt your path
environment variable or use the path in front of the command, e.g.
/opt/bin/ls.

Roland

--- In nslu2-linux@..., "randy_holcomb" <raholco@...> wrote:

>
> --- In nslu2-linux@..., "randy_holcomb" <raholco@>
> wrote:
> >
> > Got an issue with Unslung with files over 1 GB:
> >
> > They don't show up when you do an ls,
> > You can't do a chmod against them.
> >
> > What's interesting is that when the files get created, the
> > permissions get set to 750, but I'd like to get them set to 755.
> >
> > Ideas?
> >
> > Randy
> >
>
> I looked around and found coreutils, so I did an ipkg install
> coreutils and rebooted the Slug, but I still have the same problem.
>

[randy_holcomb]

--- In nslu2-linux@..., "rolandkbs" <roland.krebs@...>
wrote:
>
> The coreutils are installed inot /opt/bin. Either adapt your path
> environment variable or use the path in front of the command, e.g.
> /opt/bin/ls.
>
> Roland
>
> --- In nslu2-linux@..., "randy_holcomb" <raholco@>
wrote:

> >
> > --- In nslu2-linux@..., "randy_holcomb" <raholco@>
> > wrote:
> > >
> > > Got an issue with Unslung with files over 1 GB:
> > >
> > > They don't show up when you do an ls,
> > > You can't do a chmod against them.
> > >
> > > What's interesting is that when the files get created, the
> > > permissions get set to 750, but I'd like to get them set to 755.
> > >
> > > Ideas?
> > >
> > > Randy
> > >
> >
> > I looked around and found coreutils, so I did an ipkg install
> > coreutils and rebooted the Slug, but I still have the same

problem.
> >
>

Where is the file that contains the PATH that needs to be modified?

[Dan Grunberg]

I downloaded SlugOs-4.8-beta and compiled it on a Debian (Etch ) system in
Slugos/BE mode.

There were 4 errors that had to be fixed to get it to work, detailed below:

(Below, let slugos be the path to the top of the source tree)

 

In slugos: 'make image'

 

1. The build failed at the libltdl library.  After tracking down the
problem, It appears that the cd command echoing the

directory after a successful change caused the problem (and will cause
problems later in the build if not fixed).

 

  I changed slugos/openembedded/classes/base.bbsclass

 

   added "> /dev/null" after the cd in base.bbsclass at line "dir=$dir`(cd
$dir; find .) | sed ."

 

2. fakeroot-1.8.3 does not exist anymore.  I renamed 4 dirs/files:

   At slugos/openembedded/packages/fakeroot:

   mv fakeroot-1.8.3 fakeroot-1.9.5

   mv fakeroot-native-1.8.3 fakeroot-native-1.9.5

   mv fakeroot_1.8.3.bb fakeroot_1.9.5.bb

   mv fakeroot-native_1.8.3.bb  fakeroot-native_1.9.5.bb

 

3. Had to put in the 2 microcode files .zip along with .zip.md5sum files
as described in the MasterMakefile HowTo - used version 2.4.

 

4. in
slugos/nslu2be.tmp/work/i686-linux/git-native-1.5.3-r2/git-1.5.3/templates/M
akefile

    (cd blt && $(TAR).  has same problem as #1 - changed to

    (cd blt >/dev/null && $(TAR).

 

The changes above are in files that do not exist in the archive, as they are
created on the fly, so I am not sure the proper way to patch this,

Other than wait until the build fails and make the changes described above.

 

After this, I was able to update the flash in the NSLU2 as described in the
Wiki and everything worked fine.

 

Is there some variant of cd that does not echo its path, which would allow
these files to work previously but not on Debian?

 

-Dan

Immedia Semiconductor

 

[rolandkbs-2]

If you login as root then create in /root a file named .profile.
Here's mine:
# cat .profile
export PATH="/opt/bin:$PATH"
#

Roland

--- In nslu2-linux@..., "randy_holcomb" <raholco@...> wrote:

>
> --- In nslu2-linux@..., "rolandkbs" <roland.krebs@>
> wrote:
> >
> > The coreutils are installed inot /opt/bin. Either adapt your path
> > environment variable or use the path in front of the command, e.g.
> > /opt/bin/ls.
> >
> > Roland
> >
> > --- In nslu2-linux@..., "randy_holcomb" <raholco@>
> wrote:
> > >
> > > --- In nslu2-linux@..., "randy_holcomb" <raholco@>
> > > wrote:
> > > >
> > > > Got an issue with Unslung with files over 1 GB:
> > > >
> > > > They don't show up when you do an ls,
> > > > You can't do a chmod against them.
> > > >
> > > > What's interesting is that when the files get created, the
> > > > permissions get set to 750, but I'd like to get them set to 755.
> > > >
> > > > Ideas?
> > > >
> > > > Randy
> > > >
> > >
> > > I looked around and found coreutils, so I did an ipkg install
> > > coreutils and rebooted the Slug, but I still have the same
> problem.
> > >
> >
>
> Where is the file that contains the PATH that needs to be modified?
>

[Mike (mwester)]

randy_holcomb wrote:

> Where is the file that contains the PATH that needs to be modified?

Install openssh, and use an ssh client; openssh will correctly set your
PATH variable.

In addition, it will be more secure, more stable, and protect you from
accidentally losing access to your NSLU2 due to software config or
installation errors.

Mike (mwester)

[Rod Whitby-2]

Daniel Grunberg wrote:
> I downloaded SlugOs-4.8-beta and compiled it on a Debian (Etch ) system
> in Slugos/BE mode.
>
> There were 4 errors that had to be fixed to get it to work, detailed below:
(I skipped 2 and 3, as they are real problems or known steps that need
to be done)

> 1. The build failed at the libltdl library.  After tracking down the
> problem, It appears that the cd command echoing the
> directory after a successful change caused the problem (and will cause
> problems later in the build if not fixed).
>   I changed slugos/openembedded/classes/base.bbsclass
>    added “> /dev/null” after the cd in base.bbsclass at line
> “dir=$dir`(cd $dir; find …) | sed …”
> 4. in
> slugos/nslu2be.tmp/work/i686-linux/git-native-1.5.3-r2/git-1.5.3/templates/Makefile
>     (cd blt && $(TAR)…  has same problem as #1 – changed to
>     (cd blt >/dev/null && $(TAR)…
> Is there some variant of cd that does not echo its path, which would
> allow these files to work previously but not on Debian?

Normally, cd does not echo the directory it is entering.  You must have
something special in your /etc/profile or .bashrc - once you remove that
special shell setup, everything will work as expected.

-- Rod

[Thomas Reitmayr]

Hi,
this looks like the environment variable CDPATH being set.
-Thomas



----- Ursprüngliche Mail ----
Von: Rod Whitby <rod@...>
An: nslu2-linux@...
Gesendet: Samstag, den 19. Juli 2008, 14:06:43 Uhr
Betreff: Re: [nslu2-linux] slugosBE-4.8-beta compiling problems and solutions


Daniel Grunberg wrote:
> I downloaded SlugOs-4.8-beta and compiled it on a Debian (Etch ) system
> in Slugos/BE mode.
>
> There were 4 errors that had to be fixed to get it to work, detailed below:
(I skipped 2 and 3, as they are real problems or known steps that need
to be done)

> 1. The build failed at the libltdl library.  After tracking down the
> problem, It appears that the cd command echoing the
> directory after a successful change caused the problem (and will cause
> problems later in the build if not fixed).
>   I changed slugos/openembedded /classes/ base.bbsclass
>    added “> /dev/null” after the cd in base.bbsclass at line
> “dir=$dir`(cd $dir; find …) | sed …”
> 4. in
> slugos/nslu2be. tmp/work/ i686-linux/ git-native- 1.5.3-r2/ git-1.5.3/ templates/ Makefile
>     (cd blt && $(TAR)…  has same problem as #1 – changed to
>     (cd blt >/dev/null && $(TAR)…
> Is there some variant of cd that does not echo its path, which would
> allow these files to work previously but not on Debian?

Normally, cd does not echo the directory it is entering.  You must have
something special in your /etc/profile or .bashrc - once you remove that
special shell setup, everything will work as expected.

-- Rod
   


      __________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com

[Dan Grunberg]

Yes, I checked it.  If you unset CDPATH, then cd commands are not echoed.  However, if it is set, then it does.  It does not
echo cd's to full paths, only relative paths where the CDPATH search is required.
Doesn't everyone use CDPATH?


-Dan
  ----- Original Message -----
  From: Thomas Reitmayr
  To: nslu2-linux@...
  Sent: Saturday, July 19, 2008 10:12 AM
  Subject: Re: [nslu2-linux] slugosBE-4.8-beta compiling problems and solutions



  Hi,
  this looks like the environment variable CDPATH being set.
  -Thomas



  ----- Ursprüngliche Mail ----
  Von: Rod Whitby <rod@...>
  An: nslu2-linux@...
  Gesendet: Samstag, den 19. Juli 2008, 14:06:43 Uhr
  Betreff: Re: [nslu2-linux] slugosBE-4.8-beta compiling problems and solutions


  Daniel Grunberg wrote:
  > I downloaded SlugOs-4.8-beta and compiled it on a Debian (Etch ) system
  > in Slugos/BE mode.
  >
  > There were 4 errors that had to be fixed to get it to work, detailed below:
  (I skipped 2 and 3, as they are real problems or known steps that need
  to be done)
  > 1. The build failed at the libltdl library. After tracking down the
  > problem, It appears that the cd command echoing the
  > directory after a successful change caused the problem (and will cause
  > problems later in the build if not fixed).
  > I changed slugos/openembedded /classes/ base.bbsclass
  > added “> /dev/null” after the cd in base.bbsclass at line
  > “dir=$dir`(cd $dir; find …) | sed …”
  > 4. in
  > slugos/nslu2be. tmp/work/ i686-linux/ git-native- 1.5.3-r2/ git-1.5.3/ templates/ Makefile
  > (cd blt && $(TAR)… has same problem as #1 – changed to
  > (cd blt >/dev/null && $(TAR)…
  > Is there some variant of cd that does not echo its path, which would
  > allow these files to work previously but not on Debian?

  Normally, cd does not echo the directory it is entering. You must have
  something special in your /etc/profile or .bashrc - once you remove that
  special shell setup, everything will work as expected.

  -- Rod




------------------------------------------------------------------------------
  Gesendet von Yahoo! Mail.
  Dem pfiffigeren Posteingang.

   

[Mike (mwester)]

dan grunberg wrote:
> 
> Yes, I checked it.  If you unset CDPATH, then cd commands are not
> echoed.  However, if it is set, then it does.  It does not
> echo cd's to full paths, only relative paths where the CDPATH search is
> required.
> Doesn't everyone use CDPATH?

:-)  Apparently not; this is the first time anyone has reported breakage
with the SlugOS build related to this!  (Of course, it could also mean
that others have run into this, resolved their own problem, and never
told anyone or updated the wiki -- shame on them!)

The most recent bitbake version will "unset" all but a select few
environment variables, so it should resolve this problem for us in the
future.  Until then, I guess somebody should update the wiki so that
nobody else spends time sorting this out in the future.

Thanks for finding that!

Mike (mwester)

>  
> -Dan
>
>     ----- Original Message -----
>     *From:* Thomas Reitmayr <mailto:treitmayr@...>
>     *To:* nslu2-linux@... <mailto:nslu2-linux@...>
>     *Sent:* Saturday, July 19, 2008 10:12 AM
>     *Subject:* Re: [nslu2-linux] slugosBE-4.8-beta compiling problems
>     and solutions
>
>     Hi,
>     this looks like the environment variable CDPATH being set.
>     -Thomas
>
>     ----- Ursprüngliche Mail ----
>     Von: Rod Whitby <rod@... <mailto:rod@...>>
>     An: nslu2-linux@... <mailto:nslu2-linux@...>
>     Gesendet: Samstag, den 19. Juli 2008, 14:06:43 Uhr
>     Betreff: Re: [nslu2-linux] slugosBE-4.8-beta compiling problems and
>     solutions
>
>     Daniel Grunberg wrote:
>     > I downloaded SlugOs-4.8-beta and compiled it on a Debian (Etch )
>     system
>     > in Slugos/BE mode.
>     >
>     > There were 4 errors that had to be fixed to get it to work,
>     detailed below:
>     (I skipped 2 and 3, as they are real problems or known steps that need
>     to be done)
>     > 1. The build failed at the libltdl library. After tracking down the
>     > problem, It appears that the cd command echoing the
>     > directory after a successful change caused the problem (and will
>     cause
>     > problems later in the build if not fixed).
>     > I changed slugos/openembedded /classes/ base.bbsclass
>     > added “> /dev/null” after the cd in base.bbsclass at line
>     > “dir=$dir`(cd $dir; find …) | sed …”
>     > 4. in
>     > slugos/nslu2be. tmp/work/ i686-linux/ git-native- 1.5.3-r2/
>     git-1.5.3/ templates/ Makefile
>     > (cd blt && $(TAR)… has same problem as #1 – changed to
>     > (cd blt >/dev/null && $(TAR)…
>     > Is there some variant of cd that does not echo its path, which would
>     > allow these files to work previously but not on Debian?
>
>     Normally, cd does not echo the directory it is entering. You must have
>     something special in your /etc/profile or .bashrc - once you remove
>     that
>     special shell setup, everything will work as expected.
>
>     -- Rod