larch-7 testing

gradgrind · 2010-02-04 08:14:04

What are you trying to larchify?

Amnon82 · 2010-02-11 01:07:21

Michael can you take on on: http://bbs.archlinux.org/viewtopic.php? … 91#p683191

gradgrind · 2010-02-11 08:14:20

I guess I'll have to update one of my machines ...

I just did a very quick test of larch on a freshly built larch system (Qt 4.6.1) and didn't notice any problems (apart from it not starting when larch-profiles is not installed, which I will fix), could you be a bit more specific about the matter? It looks like you were using sudo to start it? This is probably not a good idea (with the present code), it should be started as a normal user.

Last edited by gradgrind (2010-02-11 13:58:24)

gradgrind · 2010-02-12 08:56:45

I thought I'd mention that I'm having yet another go at the larch installer, and this time trying to do it in 'chunks'. At the moment, there's code to do just the installation bit - that is, format the (existing) partition(s), mount it/them, copy the live system, remove stuff that was only intended or necessary for the live system, generate the new initramfs, and autogenerate an initial /etc/fstab. It gives optional progress feedback, and is designed to be incorporated into an 'installer application' either via an stdio interface, or via a python api.

If anyone is desperate to install a larch system now, you'll have to do the partitioning, and bootloader stuff yourself, but the copying and tidying up might work (it's only been tested a little). Don't use old example profiles with it (anything with a larch/copy/larch0 on the boot medium) because these will probably mess up your live system, this 'installation' script is now called in another way. Actually, now that I am writing this it occurs to me that it would be much less stupid to give the new script a new name ... I'll fix that as soon as possible.

Anyway, you can get what there is from ftp://ftp.berlios.de/pub/larch/larch7/i686 - the latest larchin package.

Amnon82 · 2010-02-14 20:19:53

Me and my boys are busy with a new development rls. We ran into troubles cos of mkinitcpio 0.6. The kernel-image generation seems to be broken. Maybe it is cos of an older kernel I use atm or mkinitcpio itself. I had to use http://arm.konnichi.com/2010/02/14 pkgs to get it work with mkinitcpio 0.5. udev seems not to find the kernel somehow.

/init: line 156: /lib/udev/vol_id: not found
/init: line 156: /lib/udev/vol_id: not found
/init: line 156: /lib/udev/vol_id: not found
/init: line 156: /lib/udev/vol_id: not found
/init: line 156: /lib/udev/vol_id: not found
/init: line 156: /lib/udev/vol_id: not found

... until it goes to bash and stands

I'll test this later when the release spree is getting slower.

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish.  This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
#    FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
#    This setup specifies all modules in the MODULES setting above.
#    No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
#    This setup will autodetect all modules for your system and should
#    work as a sane default
#    HOOKS="base udev autodetect pata scsi sata filesystems"
#
#    This is identical to the above, except the old ide subsystem is
#    used for IDE devices instead of the new pata subsystem.
#    HOOKS="base udev autodetect ide scsi sata filesystems"
#
#    This setup will generate a 'full' image which supports most systems.
#    No autodetection is done.
#    HOOKS="base udev pata scsi sata usb filesystems"
#
#    This setup assembles an pata raid array with an encrypted root FS.
#    Note: See 'mkinitcpio -H raid' for more information on raid devices.
#    HOOKS="base udev pata raid encrypt filesystems"
#
#    This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev usb lvm2 filesystems"

HOOKS="base udev pata scsi sata usb larch1 larch2___aufs___ larch3"

# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"

is the last mkinitcpio.conf.larch0 found in larch-live. I have this actually: mkinitcpio.conf.larch0 (chakra) - firmware don't work anymore. Removing it doesn't help atm. Maybe time will fix that. Do you have any problems with new mkinitcpio so far? I assume larch-hooks need to be edited to fit the new system.

Last edited by Amnon82 (2010-02-16 06:20:30)

gradgrind · 2010-02-15 08:58:40

I haven't tested it yet, but I would expect to need to make some changes to the larch hooks ... when I have time!

fplolz · 2010-02-16 02:32:00

Thank you for the notification of mkinitcpio breaking stuff..

Amnon82 · 2010-02-16 21:08:03

# Replacement for msg which includes leading and trailing spaces
msg_ () { [ "${quiet}" != "y" ] && echo "$@"; }
# Version which requires 'verbose' flag to output
msg_v () { [ "${quiet}" != "y" ] && [ "${verbose}" = "y" ] && echo "$@"; }

testdevice ()
{
    eval $( /sbin/blkid -o udev ${LDEV} )
    #eval $( /lib/udev/vol_id ${LDEV} )
    #eval $( /bin/fstype ${LDEV} )
    # doesn't work for vfat, ntfs:
    #FSTYPE=unknown
    #FSSIZE=0

removes me the first error but I get this:

blkid gives you those outputs:

[phil@philstv-desktop chakra]$ sudo /sbin/blkid -o udev /dev/sdb1
ID_FS_LABEL=sdb1
ID_FS_LABEL_ENC=sdb1
ID_FS_UUID=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_UUID_ENC=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_TYPE=ext3

[phil@philstv-desktop chakra]$ sudo /sbin/blkid -p -o udev /dev/sdb1
ID_FS_LABEL=sdb1
ID_FS_LABEL_ENC=sdb1
ID_FS_UUID=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_UUID_ENC=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_VERSION=1.0
ID_FS_TYPE=ext3
ID_FS_USAGE=filesystem
                                 
[phil@philstv-desktop chakra]$ sudo /sbin/blkid -o udev
ID_FS_UUID=f17d95f2-6e27-4da7-b4d8-6dbfeaf38cbc        
ID_FS_UUID_ENC=f17d95f2-6e27-4da7-b4d8-6dbfeaf38cbc    
ID_FS_TYPE=ext3                                        
ID_FS_LABEL=sda5
ID_FS_LABEL_ENC=sda5
ID_FS_UUID=ebcb4a5f-e2aa-4ce1-a65d-ddb3c4b84597
ID_FS_UUID_ENC=ebcb4a5f-e2aa-4ce1-a65d-ddb3c4b84597
ID_FS_TYPE=ext3
ID_FS_SEC_TYPE=ext2
ID_FS_LABEL=sda6
ID_FS_LABEL_ENC=sda6
ID_FS_UUID=f0807b93-4a68-4a06-a214-1f8105766726
ID_FS_UUID_ENC=f0807b93-4a68-4a06-a214-1f8105766726
ID_FS_TYPE=ext3
ID_FS_LABEL=32bit
ID_FS_LABEL_ENC=32bit
ID_FS_UUID=70296b03-9e81-4548-9c34-83aa5a1fbc38
ID_FS_UUID_ENC=70296b03-9e81-4548-9c34-83aa5a1fbc38
ID_FS_TYPE=ext4
ID_FS_LABEL=64bit
ID_FS_LABEL_ENC=64bit
ID_FS_UUID=5d095102-01ec-402b-93a6-5a576fa8eb04
ID_FS_UUID_ENC=5d095102-01ec-402b-93a6-5a576fa8eb04
ID_FS_TYPE=ext4
ID_FS_LABEL=sdb1
ID_FS_LABEL_ENC=sdb1
ID_FS_UUID=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_UUID_ENC=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_TYPE=ext3
ID_FS_LABEL=sdb2
ID_FS_LABEL_ENC=sdb2
ID_FS_UUID=c7002d34-f4e0-43d8-8ed0-68b361de3302
ID_FS_UUID_ENC=c7002d34-f4e0-43d8-8ed0-68b361de3302
ID_FS_TYPE=ext3
ID_FS_LABEL=sdb3
ID_FS_LABEL_ENC=sdb3
ID_FS_UUID=216a970b-0591-47a7-b82c-e4f888c2404d
ID_FS_UUID_ENC=216a970b-0591-47a7-b82c-e4f888c2404d
ID_FS_TYPE=ext3
ID_FS_UUID=335d97c6-0cc7-42a6-8987-59605760a573
ID_FS_UUID_ENC=335d97c6-0cc7-42a6-8987-59605760a573
ID_FS_TYPE=swap
[phil@philstv-desktop chakra]$

Maybe that helps you. Still searching for the output of eval $( /lib/udev/vol_id ${LDEV} )

We need something like this:

[phil@philstv-desktop chakra]$ sudo /lib/initcpio/udev/vol_id /dev/sdb1
Passwort:
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_UUID_ENC=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_LABEL=sdb1
ID_FS_LABEL_ENC=sdb1

So lets try this:

# Replacement for msg which includes leading and trailing spaces
msg_ () { [ "${quiet}" != "y" ] && echo "$@"; }
# Version which requires 'verbose' flag to output
msg_v () { [ "${quiet}" != "y" ] && [ "${verbose}" = "y" ] && echo "$@"; }

testdevice ()
{
    eval $( /sbin/blkid -p -o udev ${LDEV} )
    #eval $( /lib/udev/vol_id ${LDEV} )
    #eval $( /bin/fstype ${LDEV} )
    # doesn't work for vfat, ntfs:
    #FSTYPE=unknown
    #FSSIZE=0

... no it present me with the same error. Here some more outputs:

[phil@philstv-desktop chakra]$ sudo /sbin/blkid -p -o udev /dev/sdb1
ID_FS_LABEL=sdb1
ID_FS_LABEL_ENC=sdb1
ID_FS_UUID=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_UUID_ENC=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_VERSION=1.0
ID_FS_TYPE=ext3
ID_FS_USAGE=filesystem
[phil@philstv-desktop chakra]$ sudo /sbin/blkid -o udev /dev/sdb1
ID_FS_LABEL=sdb1
ID_FS_LABEL_ENC=sdb1
ID_FS_UUID=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_UUID_ENC=ffbe2f50-18ef-4fc6-86cb-70492491ffc6
ID_FS_TYPE=ext3
[phil@philstv-desktop chakra]$ sudo /sbin/blkid -s LABEL -o udev /dev/sdb1
Passwort:
ID_FS_LABEL=sdb1
ID_FS_LABEL_ENC=sdb1

Last edited by Amnon82 (2010-02-16 22:41:34)

gradgrind · 2010-02-17 08:52:26

Thanks for looking, Amnon. I've made some changes without seeing your comments, so I'll still look over them to see if there's something I need to consider there. I've put up a first attempt at fixing the larch-live package for the new mkinitcpio, so please test it and give me some feedback, positive or negative ...

neofish · 2010-02-17 10:32:50

OMG, thankyou gradgrind. The new larch7 works flawlessly. Even faster boot times than before. Would it be possible to alsa get mkarchiso working to the same standard?

fplolz · 2010-02-17 14:13:49

Thank for you effort Gradgrind .
Larch is once again working

gradgrind · 2010-02-20 12:09:53

I've made a few more tweaks and adjustments in various places to accommodate recent Arch changes. I hope I haven't broken anything ... . The example profiles should now work again on intel chips after the recent kms changes caused problems, I can't test any others.

sHyLoCk · 2010-02-20 12:11:56

Just to confirm, larch7 is working fine here with ArchBang.

wantilles · 2010-02-20 16:46:29

Nothing works in larch7.

A very difficult to use GUI, takes things for granted.

And a very difficult to use command line interface, with extremely poor -> non-existent documentation.

One has to go completely blind just to do what he could do with a simple command in larch5.3, in two minutes.

gradgrind · 2010-02-21 15:40:42

Sorry you don't like the gui. I find it a lot easier to use, it's difficult to please everyone. If you could tell me which things it 'takes for granted' I'll try to improve it. As to the command line, I agree it's not very good, it was not intended as the main user interface, just for use in scripts, etc., but again, I'll try to improve it when I have time.

wantilles · 2010-02-21 16:26:53

All entries of the larch7 repository in pacman.conf & pacman.conf.larch (in /opt/apps/larch/data) must change.

The *platform at the end of the server line has to be deleted, and i686 has to be added.

Why?

Because the larch7 repo is not architecture-specific. All its packages are arch 'any' packages.

Last edited by wantilles (2010-02-21 20:44:31)

gradgrind · 2010-02-21 16:40:43

Ah yes. I haven't thought much about x86_64 because I don't have any computers running it. But I cannot guarantee that there will be no architecture specific packages in this repository, so I don't really want to remove the platform variable. For the moment I have put a symlink on the server so that the platform variable should work on x86_64 too.

fiod · 2010-02-21 20:12:39

When trying to install the system, I keep getting:

:-error: failed retrieving file 'larch-live-7.0.48-1-any.pkg.tar.gz' from ftp.berlios.de : File unavailable (e.g., file not found, no access)

I took a look at the ftp server, and found that there is no larch-live-7.0.48 file there, but only
larch-live-7.0.101-1-any.pkg.tar.gz

The db has to be updated on the server

fiod

gradgrind · 2010-02-22 08:39:39

Oops, must have done something silly while updating. It should be fixed now, thanks for reporting it!

fplolz · 2010-02-22 12:03:00

hm.. after i have created the iso with Larch 7
i tried booting it in virtual box / vmware player..

However , i do not get to the grub screen to choose the kernel to boot into the live system
I just get a blank black screen..
I have tried both isolinux and grub..but i am still not able to get to the default larch boot up screen..

does any 1 have any idea?

Last edited by fplolz (2010-02-25 10:14:00)

wantilles · 2010-02-23 18:46:50

Every time I create a live optical medium, Larch Larchifies the system it is run from (my system).

Thank God I know which 5-6 files to delete, before a reboot, so that damage is avoided.

But this is a very critical bug Gradgrind, and you have to look into it.

Streinleght · 2010-02-24 01:33:17

Im using the same profile without any modifications that was previous working FULL , the only change is the last upgrade on repos of larch7.

When booting now failed giving , failed to load asound.state you cannot access or file doesnt exists. U can wait 3 mins and then... INIT: ID "cX" respawning too fast: disabled for 5 minutes.

Btw is possible using larch with kernel-lts instead of mainstream kernel26?

gradgrind · 2010-02-24 08:19:38

fplolz:

That sounds strange, I've never come across that one before. Have you tested with other isos?

wantilles:

Well, actually, I don't have to do anything. But if you could give me a more detailed bug report - what you did (maybe the contents of ~/.config/larch), and exactly what the result was - I would be happy to investigate.

Streinleght:

The asound.state message is normal - it should not cause any problems. The respawning problem could have various causes. Is anyone else getting this?
And no, it is not possible to use the kernel-lts because, as far as I know, the devs decided not to include aufs support.

fplolz · 2010-02-24 09:06:28

Thanks for the response

I have tried using Isolinux instead of grub yes it did work..but i got this message from virtual box
'The virtual machine window is optimized to work in 32 bit color mode but the virtual display is currently set to 24 bit'
Though...the iso using isolinux did not work on vmware player...
hm.. will be testing on a real com soon
Thanks for the response

p.s .. i do get an error when running larchin 7

sudo larchin-install

#+get-mounts
!+Traceback (most recent call last):
!+ File "/usr/sbin/larchin-install", line 202, in <module>
!+ backend.init(console.Console(options.quiet))
!+ File "/opt/apps/larchin/modules/backend.py", line 94, in init
!+ for d, m in Devices().get_mounts():
!+ File "/opt/apps/larchin/modules/backend.py", line 387, in get_mounts
!+ return [m.split() for m in scripts.script("get-mounts").splitlines()]
!+ File "/opt/apps/larchin/modules/backend.py", line 293, in script
!+ p = self.start_script(*args)
!+ File "/opt/apps/larchin/modules/backend.py", line 276, in start_script
!+ stdout=PIPE, stderr=STDOUT)
!+ File "/usr/lib/python2.6/subprocess.py", line 621, in __init__
!+ errread, errwrite)
!+ File "/usr/lib/python2.6/subprocess.py", line 1126, in _execute_child
!+ raise child_exception
!+OSError: [Errno 2] No such file or directory
!>Something went wrong, quitting (see log)

Last edited by fplolz (2010-02-25 10:14:11)

Streinleght · 2010-02-24 18:24:05

Trying with default profiles to see if is broken tooon all profiles i get:

INIT: version 2.86 booting
SQUASHFS error: zlib_inflate error , data probably corrupt.
SQUASHFS error: squashfs_read_data failed to read block 0xb1af3
.
.
.
.

Enter runlevel:

Arch Linux

#101 2010-02-04 08:14:04

Re: larch-7 testing

#102 2010-02-11 01:07:21

Re: larch-7 testing

#103 2010-02-11 08:14:20

Re: larch-7 testing

#104 2010-02-12 08:56:45

Re: larch-7 testing

#105 2010-02-14 20:19:53

Re: larch-7 testing

#106 2010-02-15 08:58:40

Re: larch-7 testing

#107 2010-02-16 02:32:00

Re: larch-7 testing

#108 2010-02-16 21:08:03

Re: larch-7 testing

#109 2010-02-17 08:52:26

Re: larch-7 testing

#110 2010-02-17 10:32:50

Re: larch-7 testing

#111 2010-02-17 14:13:49

Re: larch-7 testing

#112 2010-02-20 12:09:53

Re: larch-7 testing

#113 2010-02-20 12:11:56

Re: larch-7 testing

#114 2010-02-20 16:46:29

Re: larch-7 testing

#115 2010-02-21 15:40:42

Re: larch-7 testing

#116 2010-02-21 16:26:53

Re: larch-7 testing

#117 2010-02-21 16:40:43

Re: larch-7 testing

#118 2010-02-21 20:12:39

Re: larch-7 testing

#119 2010-02-22 08:39:39

Re: larch-7 testing

#120 2010-02-22 12:03:00

Re: larch-7 testing

#121 2010-02-23 18:46:50

Re: larch-7 testing

#122 2010-02-24 01:33:17

Re: larch-7 testing

#123 2010-02-24 08:19:38

Re: larch-7 testing

#124 2010-02-24 09:06:28

Re: larch-7 testing

#125 2010-02-24 18:24:05

Re: larch-7 testing

Board footer