You are not logged in.
fplolz:
I can't help you with the color mode message, I don't know my way around virtualbox that well, but thanks for the bug report on larchin-install. It's an error in the PKGBUILD, which I'll fix. The new larchin is still very alpha!
Streinleght:
It looks like your build (or burn? are you using CDs?) went wrong somewhere. I would suggest rebuilding, checking the log for errors (you can send it to me) and running the resulting iso directly in virtualbox.
larch: http://larch.berlios.de
Offline
Gradgrind : thank you very much . i appreciate your help
i did get this error after starting it up in the live cd with
sudo larchin-install
#+get-mounts
##/dev/sr0 /.livesys/medium
##/dev/loop0 /tfs/system
##/dev/loop1 /tfs/mods
##/dev/loop0 /.livesys/system
##/dev/loop1 /.livesys/mods
#-get-mounts
!>Bad partition descriptor:
!>No root partition ('/') specified
Last edited by fplolz (2010-02-25 14:42:25)
Offline
You need to tell it where to put the installation! Run 'larchin-install -h' to get a usage message, I hope it's clear enough then.
And I've uploaded a small update.
If anyone is interested there is now also a grub installation script, too, essentially UNTESTED though - please don't use on any important machine: 'larchin-grub -h' for usage info.
Last edited by gradgrind (2010-02-25 15:27:36)
larch: http://larch.berlios.de
Offline
oops ...sorry ! :x my bad..
thank you very much
Offline
I have a small problem. Larch is very nice for testing Arch on a headless machine. So far it seems to work nicely. However, since Larch only asks whether changes should be saved after shutdown has been initialized it is not very ssh-friendly. Also: since an input is required it is quite hard/impossible to shutdown the machine properly.
I can tell from session save page that it should be possible to alter this behavior. I am, however, uncertain on how to do this in practice.
Arch x64 on Thinkpad X200s/W530
Offline
Pank:
Indeed I'm not really surprised you are uncertain, I'm sure that part of the code could be done better. I just haven't touched it because it's been working pretty well. I'm afraid I can't give you any details at the moment (I don't really remember exactly how it works myself), but I can tell you roughly how it's handled in the xmini example profile. The utility larchquit.py writes to /tmp/xlogout, which is then tested by ulogin to see whether to halt or reboot, and then (whilst shutting down) by shutdown2 to see what sort of session saving is to be done. All three scripts are in the larch-live package (usr/sbin or opt/larch/session-save). Maybe you can figure out from there how to use this mechanism.
larch: http://larch.berlios.de
Offline
Shutdown2 is way to complicated for me to understand much less alter. Is it somehow possible to pass the save argument ("1") to shutdown2 by default or to send a signal before hand?
I will probably use the "official" install image once I get the permanent boot disk. I would love to use larch until then though. Also, I understand that one cannot install one's larch system from usb to hdd at the moment (using larch7 at least).
Arch x64 on Thinkpad X200s/W530
Offline
Shutdown2 is way to complicated for me to understand much less alter. Is it somehow possible to pass the save argument ("1") to shutdown2 by default or to send a signal before hand?
I will probably use the "official" install image once I get the permanent boot disk. I would love to use larch until then though. Also, I understand that one cannot install one's larch system from usb to hdd at the moment (using larch7 at least).
I had a quick look, and if I'm not mistaken, it should be enough in your case to do:
For no session saving:
echo "-">/tmp/xlogout
For 'normal' session saving:
echo "S">/tmp/xlogout
For session merging:
echo "M">/tmp/xlogout
before shutting down.
larch: http://larch.berlios.de
Offline
Hi,
It worked
Thanks
Arch x64 on Thinkpad X200s/W530
Offline
Glad to hear it, Pank!
As regards installation. this still has a way to go, but there are basic scripts for installing a live system to a partition (or set of partitions) and setting up grub - in the larchin package (testers welcome). They have usage messages, but no other docs at present.
larch: http://larch.berlios.de
Offline
I will try larchin when I get my DOM and I shall be happy to provide feedback. The installation process of Larch5 worked great as far as I remember.
Arch x64 on Thinkpad X200s/W530
Offline
Trying with all default profiles all with the same errors trying on virtualbox , and vmware player.
Offline
Hello,
I don't know if you remember me, I had the "Unknown widget: :nodevice" error which crashed the "prepare medium" tab.
While I still don't know why it happens, at least now I have a workaround: I was starting larch with "sudo", but if I start larch as root now it's working without error. (I have to use xhost + so I can connect from the root account)
Otherwise everything is working fine with Larch now, I could generate my iso without problem
Offline
Streinleght:
I'm not sure what that could be, the actual error probably occurred earlier in the boot sequence.
farvardin:
I'm glad you got it working, but the current larch version is designed to be run as a normal user - it asks for the root password when it needs it. This allows you to edit your profiles, etc., as the normal user without getting permission problems.
larch: http://larch.berlios.de
Offline
I've made a small change that I've often wanted, which unfortunately means a change to the configuration files in the profiles. 'baseveto' has been replaced by 'vetopacks'. Now packages from any group (not just 'base') can be blocked, so long as they are not required by other packages. Any package group entered in 'addedpacks' will be filtered if it is prefixed by '*'. See the docs for more details.
larch: http://larch.berlios.de
Offline
Hi,
I have another question: I have gotten a larger flash disk. I was lazy so I just copied over the larch folder from my old setup. However, the "space" problem has not gotten better.
Here is a snapshot:
Filesystem Size Used Avail Use% Mounted on
aufs 297M 166M 131M 56% /
tmpfs 297M 166M 131M 56% /.livesys
/dev/sde1 7,6G 570M 7,0G 8% /.livesys/medium
udev 10M 152K 9,9M 2% /dev
none 247M 0 247M 0% /dev/shm
/dev/mapper/array-video
1000G 197G 803G 20% /mnt/data/video
/dev/mapper/array-music
500G 40G 460G 8% /mnt/data/music
/dev/mapper/array-backup
50G 4,6M 50G 1% /mnt/data/backup
/dev/mapper/array-photo
50G 17G 33G 35% /mnt/data/photo
/dev/mapper/array-download
10G 1,1G 9,0G 11% /mnt/data/download
I'd like to resize /. (and /.livesys) if possible to utilize the increased space of /.livesys/medium
Thanks,
Rasmus
Arch x64 on Thinkpad X200s/W530
Offline
Pank:
I'm afraid you didn't read the docs? '/' (and '.livesys') are in memory, they are not on the boot device, so the only way you can make them bigger (safely) is to add more memory to the computer. I think nearly all 'live' systems work like this. If you want to use the space on your boot device for something, first consider exactly what you want to use it for, and then decide how to achieve it, e.g. mounting the partition somewhere. In this respect a 'live' system is quite different from a standard installation.
larch: http://larch.berlios.de
Offline
larch can now add user accounts to the live system it builds. There is some documentation in the 'profiles' doc page, and some editing capabilities in the larchify tab of the GUI.
larch: http://larch.berlios.de
Offline
My connections to ftp.berlios.de are being rejected.
Install or build missing dependencies for larch:
==> Building and installing package
==> larch dependencies:
- pyqt (already installed)
- python (already installed)
- python-pexpect (already installed)
==> Making package: larch 7-1 x86_64 (Mon Mar 15 14:27:13 CST 2010)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Downloading larch-setup...
--2010-03-15 14:27:13-- ftp://ftp.berlios.de/pub/larch/larch7/i686/larch-setup
=> "larch-setup.part"
Resolving ftp.berlios.de... 195.37.77.141
Connecting to ftp.berlios.de|195.37.77.141|:21... failed: Connection refused.
==> ERROR: Failure while downloading larch-setup
Aborting...
Error: Makepkg was unable to build larch package.
Is the site down?
Offline
It's working at the moment, but there have been problems at various times. Why are you trying to build the larch package like that? The ready-built version should be fine if you don't need to make changes, and if you do need to make changes, you should probably be using the git sources.
larch: http://larch.berlios.de
Offline
I am trying to use larchin-install and I keep getting the message that No root partition ('/') specified, I did look at help.
This is what I have tried
larchin-install -p /:/dev/sda1:ext4:,swap:/dev/sda2:: and simular to this, without success.
Googled and found very little on the Internet.
Passing installation partitions:
mount-point:device:format:uuid/label which I understand if left empty is optional.
Can you tell me what I might be doing wrong, Thanks a lot.
Offline
I am trying to use larchin-install and I keep getting the message that No root partition ('/') specified, I did look at help.
This is what I have tried
larchin-install -p /:/dev/sda1:ext4:,swap:/dev/sda2:: and simular to this, without success.
Googled and found very little on the Internet.
Passing installation partitions:
mount-point:device:format:uuid/label which I understand if left empty is optional.Can you tell me what I might be doing wrong, Thanks a lot.
Try something like:
larchin-install -p -l '/:/dev/sda1:ext4:,swap:/dev/sda2::'
Note the -l option for the partition list and the quotes.
larch: http://larch.berlios.de
Offline
Thanks gradgrind
That got me farther, I ran into a problem that I solved with mkswap. Theses are the steps I had to take to make it work.
Booted on my Larch built virtual machine and as the root user did below.
cfdisk /dev/sda (created a / partition and swap partition)
mkswap /dev/sda2 (If you don't do this the larchin-install will complain about the swap partition and being added to fstab, gives grub error 15 on reboot and then boot back on the liveCD and run larchin-grub and then reboot again, the installation seems messed up, booted into a read only file system etc.)
larchin-install -p -l '/:/dev/sda1:ext4:,swap:/dev/sda2::'
larchin-grub -m -l '/:dev/sda1::'
Rebooted and everything seems fine.
Does this seem normal or is the larchin-install suppose to do some of theses steps?
Last edited by drb (2010-04-04 14:31:31)
Offline
That sounds about right - I haven't got round to doing any of the partitioning stuff yet, so you need to do this manually.
larch: http://larch.berlios.de
Offline
Seems aufs2 has a problem:
I used aufs2-2.6.33_20100225-1chakra
http://chakra-project.org/code/index.ph … kra/aufs2/
and aufs2-utils-20100224-1chakra
http://chakra-project.org/code/index.ph … ufs2-util/
Now I'll retry it with aufs2-util 20100116-2 and aufs2-2.6.33_20100225-1
Hmm. Seems something went wrong on my end. With stock-kernel and your mini-profile I get it booten up ... Have to dig a little more ...
Last edited by Amnon82 (2010-04-11 18:52:46)
visit chakra-project.org to get latest Chakra GNU/Linux
Offline