You are not logged in.
matthewbauer wrote:Also is there a way to preserve permissions on files?
I'd like to have a user with predefined settings such as a .xinitrc and .config. Is there a better way to do this.
Doing it at build time is a bit complicated. On larch5 you can use this: http://larch.berlios.de/doc/larch_profiles.html#xpack, but because I can't imagine anyone would really want to do this I dropped it from larch7.
Actually there is someone who would logically like to do this.
Why?
Because in the case of creating an emergency/rescue/backup live-CD for a remote machine, there, you do not need X and a DE, but you need ssh.
There you can have only the root user with an empty password.
But in the case of your own machine if you don't have a second one to ssh into, there you need X and a DE, and it's too risky to login in a DE with root priviledges.
So the correct way would be to create a normal user with its password, and the root user to have a password.
In this case of course, you would not have ssh because you do not need it.
Offline
Yes, of course. I didn't actually mean nobody would want a normal user, I just meant nobody would really want to figure out how to use xpack to include non-root owned files in a larch system. But maybe even that isn't true?
larch: http://larch.berlios.de
Offline
matthewbauer wrote:Also is there a way to preserve permissions on files?
I'd like to have a user with predefined settings such as a .xinitrc and .config. Is there a better way to do this.
Doing it at build time is a bit complicated. On larch5 you can use this: http://larch.berlios.de/doc/larch_profiles.html#xpack
Is it necessary to build an overlay.xpk?
What about simply having an overlay subdirectory.
Isn't it supposed to be the same?
Offline
Yes, you're right wantilles. An overlay.xpk has the advantage, however, that it can be copied easily (without losing file ownership information).
larch: http://larch.berlios.de
Offline
I've a problem with usbboot and usbboot_grub and more particullary with the sfdisk part.
The result of sfdisk is in my native language (dutch) and as a result the size is not fount and also no devices.
I solved this by setting the LANG to en_US and then I was able to run usbboot.
Now my first idea was to update usbboot and usbboot_grub to save the original LANG and put it back after running but maybe there is a better solution.
Any ideas??
Thanks
Offline
Ah, there's one I missed. The easiest way to fix this is probably to put LANG=C in front of the sfdisk calls:
LANG=C sfdisk -d | grep "/dev/sd[a-z][1-4] " | ...
larch: http://larch.berlios.de
Offline
Adding LANG=C fixed it and afterwards my locale is still the original.
Offline
I'll be completely frank. I'm in the process of deciding when/where/how I'll be switching from ubuntu back to arch.
I do not have an arch system installed to test out the live cd scripts so I could not adequately test this but would like to ask a question or two if i could?
1) what is the sizes of the distributions make (mini, max x, mini x)?
2) will adding the packages always resolve dependancies?
I am a bit confused on which command to use. There is a mklarch and mkiso but also a few others. I figured one was for making a live enviroment from current distro and one for a "from scratch" but when I tried to use them it asked for a profile. I tried using -p switch and gave the profile location for minix but it still gave an error (and I think it was looking for a profile folder inside /opt/larch/profiles/minix)
Offline
1) what is the sizes of the distributions make (mini, max x, mini x)?
Mini gets around 150MB.
2) will adding the packages always resolve dependancies?
Yes.
I am a bit confused on which command to use. There is a mklarch and mkiso but also a few others. I figured one was for making a live enviroment from current distro and one for a "from scratch" but when I tried to use them it asked for a profile. I tried using -p switch and gave the profile location for minix but it still gave an error (and I think it was looking for a profile folder inside /opt/larch/profiles/minix)
mklarch makes a live system on optical media from scratch.
mklarch -f -p <profile-directory> -c <pacman-cache-directory> <build-directory>
Offline
Thank you wantilles. I would also like to point out that there is fairly extensive documentation, and that if there are things that are not explained clearly enough therein I would like to hear about it!
larch: http://larch.berlios.de
Offline
Hi
I've this problem with "larchin.py" in my live: the GUI doesn't start, and I get the following message:
...
"global name '_' is not defined"
...
by /modules/gtk/guimain.pyc.
On the netbook I haven't problems, and I've the same file of larchin package, and same packages of Python:
dbus-python 0.83.0-2
gnome-python 2.28.0-1
gnome-python-desktop 2.28.0-2
gnome-python-extras 2.25.3-4
python 2.6.4-1
Any ideas? Suggestions?
Thanks
Sorry for my bad english :-)
Offline
I guess the actual problem must be somewhere else, that problem is with the translation function, which normally would exist. Probably there is a difficulty very early in the run, before this name gets defined. Could you run it in a terminal and send me the full output?
larch: http://larch.berlios.de
Offline
thanks for the support!
[~] sudo /opt/larchin/run/larchin.py
Error in sys.excepthook:
Traceback (most recent call last):
File "/opt/larchin/run/larchin.py", line 38, in errorTrap
popupError(etext, _("This error could not be handled."))
NameError: global name '_' is not defined
Original exception was:
Traceback (most recent call last):
File "/opt/larchin/run/larchin.py", line 86, in <module>
__builtin__.mainWindow = Larchin()
File "/opt/larchin/modules/gtk/guimain.py", line 44, in __init__
% _("Installer for Arch Linux"))
NameError: global name '_' is not defined
[~]
translation.. effectively, it works on my "Italian" arch, but not in the live, where all packages are in English..
Last edited by el_cammello (2009-12-16 20:26:06)
Sorry for my bad english :-)
Offline
I'd guess your 'LANG' environment variable is not set, which larchin won't like. I'm not sure how to manage that with sudo, but maybe if you do
export LANG=C
sudo /opt/larchin/run/larchin.py
it might work (as there is no Italian translation it doesn't need to be an actual language).
This issue should already be fixed in larchin-7, but larchin-7 is not yet usable.
larch: http://larch.berlios.de
Offline
yeah it works !!!!!! :D:D
very very thanks gradgrind
Sorry for my bad english :-)
Offline