> Are you aware of the existence of /etc/debian_chroot?  This is
shame on me -- I couldn't recall the name of that file at the moment of
filing... and I guess I managed to screw up my 'grep' command since I
did grep for the name in etc but haven't found it... sorry

> $ schroot -c unstable
> I: [sid-amd64-sbuild-c8773e4d-a52b-4378-9975-baaeb3c2bd48 chroot] Running 
> login shell: ‘/bin/sh’
> (sid-amd64-sbuild)rle...@ravenclaw:/tmp$ cat /etc/debian_chroot
> sid-amd64-sbuild

sorry again -- my PS* are customized heavily, hence I managed to don't
account for it... now modified bash configs to work with it properly


> I can add a SCHROOT_SESSION_ID environment variable very easily.
cool! thanks in advance

> Adding the original chroot name is somewhat harder (it's replaced
> by the session ID, and so is not longer known at the time we set
> up the environment).  I would need to store the original chroot
> name somewhere for that.
I think I meant just the content of /etc/debian_chroot, so it is already
there and just needs to be exported in a variable

-- 
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student  Ph.D. @ CS Dept. NJIT
Office: (973) 353-1412 | FWD: 82823 | Fax: (973) 353-1171
        101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW:     http://www.linkedin.com/in/yarik        



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to