Closed abmusse closed 8 years ago
Original comment by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).
Resolving issue with this commit.
Original comment by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).
I was about to make the change and then I saw line 29 from yum/setup_all.sh. . .
ln -sf /QOpenSys/var /var
The immediate previous mkdir
commands should have resolved my issues. What I realized is the /var
directory already exists and symbolic link creation, even with -f (force), doesn't overwrite the directory and instead silently fails. It was then I realized I was being naughty and not following your directions. I hate the default shell (no tab completion) so I first installed perzl's bash. Well, guess what directory that creates? Yes, /var
. So if I make sure to do nothing else before installing/configuring yum I am fine.
So that begs the question: should we make chroot environments less fickle by adding the following to chroot_minimal.lst
?
:mkdir
/QOpenSys/var
:ln
/QOpenSys/var /var
This takes it further than "minimal" and assumes usage of perzl or yum, which I think is fine.
chroot_minimal.lst
unless I hear otherwise.Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).
YES. Go ahead and add missing directory creates.
Original report by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).
Finally got to test your yum work today. Very exciting.
I am following the yum/README.md and get the following when running
setup_all.sh
(partial paste of larger output)
Some
ls
commands:Doing the following fixed the issues:
I then had this error:
And the following fixed that:
I wasn't sure if a simple
mkdir
in thesetup_xxxxx.sh
scripts should be added or if there is a different issue. If it's justmkdir
then I will fix.