You are not logged in.
I am making this new thread here, so we can discuss specifically about larch-5 SVN.
Gradgrind, is larch-5 pacman 3.1 compliant?
Last edited by wantilles (2008-01-20 08:23:33)
Offline
I am making this new thread here, so we can discuss specifically about larch-5 SVN.
Gradgrind, is larch-5 pacman 3.1 compliant?
Yes, it should be - please report any problems.
larch: http://larch.berlios.de
Offline
A PKGBUILD would also be nice.
Offline
A PKGBUILD would also be nice.
It's all in there - do
svn export svn://svn.berlios.de/larch/trunk
and follow the instructions in the README file(s).
larch: http://larch.berlios.de
Offline
wantilles wrote:A PKGBUILD would also be nice.
It's all in there - do
svn export svn://svn.berlios.de/larch/trunk
and follow the instructions in the README file(s).
OK, thank you.
Offline
There are so many bugs in larch-5, that indicate you may have done no initial testing yourself at all.
Offline
There are so many bugs in larch-5, that indicate you may have done no initial testing yourself at all.
I have indeed only run minimal tests - it is still under development, that is why there are no release packages yet. But I don't remember receiving any bug reports ...
larch: http://larch.berlios.de
Offline
Well, now there is a release, to make it easier for people to test, so that I perhaps get some bug reports, or other feedback. See http://forum.faunos.com/viewtopic.php?id=273
larch: http://larch.berlios.de
Offline
when running mklarch i get this error:
./mklarch: line 202: inpacs: command not found
:-\
We can't stop here! This is bat country!!
Offline
when running mklarch i get this error:
./mklarch: line 202: inpacs: command not found
:-\
Strange! It looks like a problem with PATH, which should get the larch script directory added at the beginning of mklarch.
How did you use mklarch? (Did you follow the steps in the announcement, or did you do something else?)
Maybe you could add these lines to larch/run/mklarch after line 47 and tell me what output you get when you run it again:
echo "PATH = ${PATH}"
echo "apppath = ${apppath}"
echo "FULLPATH = ${FULLPATH}"
OR:
Did you maybe install the larch package? Then you might find the problem goes away if you log out and then back in.
Last edited by gradgrind (2008-02-18 12:58:32)
larch: http://larch.berlios.de
Offline
i followed the steps in the announcement.
i got this error and thought maybe the inpacs command is in the larch package so i installed it, but nothing changed.
i logged out and back in and tried your echo commands, but it still doesn't work
We can't stop here! This is bat country!!
Offline
OK.
I got the i686 release.
I also made an x86_64 release as mentioned in the README.
And made two output ISOs (one i686 and one x86_64) from the same profile.
Both outputs when tested at boot, produce a kernel panic at some point.
Does the larch-5-SVN need any package from testing (for example aufs)?
Offline
i followed the steps in the announcement.
i got this error and thought maybe the inpacs command is in the larch package so i installed it, but nothing changed.
i logged out and back in and tried your echo commands, but it still doesn't work
Hmmm, could you try the following?:
1) Make sure you have absolutely no packages starting with 'larch' installed on your machine.
2) Then try the test I suggested above (putting the extra lines in mklarch and letting me know what gets output).
Thank you.
larch: http://larch.berlios.de
Offline
OK.
I got the i686 release.
I also made an x86_64 release as mentioned in the README.
And made two output ISOs (one i686 and one x86_64) from the same profile.
Both outputs when tested at boot, produce a kernel panic at some point.
Does the larch-5-SVN need any package from testing (for example aufs)?
If you made the i686 version from the instructions in the announcement, it should have picked up aufs from the larch repository (aufs-20080210, you can check in /home/larchroot/var/lib/pacman/local), which should be fine - it works here, anyway.
But even the old aufs never caused a kernel panic during boot here - it was only a problem with 'pacman -Sy'.
On x86_64 it might be worth using the latest aufs from testing - you can put it in your larch5 repository (and then run repo-add on it - see 'repo-add -h' for instructions).
Could you post the output of the kernel panic? Where exactly does it happen?
larch: http://larch.berlios.de
Offline
ok still the same error. here is the output:
PATH = /home/larchroot/larch/run:/opt/java/jre/bin:/opt/texlive/bin/:/opt/mozilla/bin/:/opt/java/jre/bin:/opt/texlive/bin/:/opt/mozilla/bin/:/bin:/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/games:/usr/NX/bin
apppath =
FULLPATH = /home/larchroot/larch/run/mklarch
Last edited by xsdnyd (2008-02-18 18:15:04)
We can't stop here! This is bat country!!
Offline
ok still the same error. here is the output:
PATH = /home/larchroot/larch/run:/opt/java/jre/bin:/opt/texlive/bin/:/opt/mozilla/bin/:/opt/java/jre/bin:/opt/texlive/bin/:/opt/mozilla/bin/:/bin:/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/games:/usr/NX/bin apppath = FULLPATH = /home/larchroot/larch/run/mklarch
Aha! Please try again from the beginning but don't put your working directory (where you put and run larch-setup) in /home/larchroot, please don't, maybe use /home/xsdnyd/larch, for example. /home/larchroot is where the live installation will get built, so of course anything you put in there will get stomped on.
larch: http://larch.berlios.de
Offline
ah ok, now it works!
since mklarch deletes the larchroot folder contents, the scripts are gone too...
now i see...
sorry for the wasted time
Last edited by xsdnyd (2008-02-18 19:13:12)
We can't stop here! This is bat country!!
Offline
Could you post the output of the kernel panic? Where exactly does it happen?
How do I do that?
Any other way than using a digital camera?
Offline
OK.
Here is a shot of the kernel panic.
http://www.imageshack.gr/view.php?file= … basrsw.png
Last edited by wantilles (2008-02-19 08:51:57)
Offline
Thanks wantilles!
Have you also tried without c2r (copy-to-ram)?
If it's not a problem with the c2r, it looks like something went wrong building the overlay.ovl file. Could you run larchify to rebuild the live medium and send me the output (assuming you haven't wiped /home/larchroot yet)? (something like: ./larchify -p yourprofile)
larch: http://larch.berlios.de
Offline
Have you also tried without c2r (copy-to-ram)?
Same behavior.
If it's not a problem with the c2r, it looks like something went wrong building the overlay.ovl file. Could you run larchify to rebuild the live medium and send me the output (assuming you haven't wiped /home/larchroot yet)? (something like: ./larchify -p yourprofile)
I do not want to build an existing installation.
Just a profie.
Offline
gradgrind wrote:Have you also tried without c2r (copy-to-ram)?
Same behavior.
gradgrind wrote:If it's not a problem with the c2r, it looks like something went wrong building the overlay.ovl file. Could you run larchify to rebuild the live medium and send me the output (assuming you haven't wiped /home/larchroot yet)? (something like: ./larchify -p yourprofile)
I do not want to build an existing installation.
Just a profie.
I'll try to explain a bit more clearly what I meant.
When you produced your live medium you ran, say, './mklarch -p larch/profiles/xmini'. If you didn't do another build after that, you should still have the system that mklarch installed at /home/larchroot. There should also be a symlink (larchroot) to that in the working directory. If you now go to the working directory and run './larchify -p larch/profiles/xmini', it will rebuild the live medium without doing the installation all over again. I would be grateful if you could do that and tell me what you get as output, because I guess there could be something going wrong.
Another thing you can do:
Test /home/larchroot/.larch/cd/overlay.ovl to see if it is ok. You can unpack it like this:
cd /home/larchroot/.larch/cd
lzop -d < overlay.ovl | tar -xf -
If that works, then the problem is probably not with the live medium building, so we will have to look somewhere else.
larch: http://larch.berlios.de
Offline
The same behavior occurs with your own "xmini" profile.
Offline
The same behavior occurs with your own "xmini" profile.
I'm sorry to hear that, but it would be great if you could apply the tests I suggested. I can't do it here because it doesn't fail here.
larch: http://larch.berlios.de
Offline
wantilles, something just struck me. Do you actually have 'lzop' installed? larch needs that to build the lzo overlay, but I haven't made that clear anywhere. Sorry about that! I'll try to get this done chrooted into the larch system so that the build system doesn't need it, but for now you do need it.
larch: http://larch.berlios.de
Offline