larch-4 testing, can also 'livify' existing Arch installation

gradgrind · 2008-01-13 12:39:15

wantilles wrote:

I see there was an update in i686 larch-4 a few days ago.
Do I need to re-build my x86_64 larch-4, or that was a trivial change?

"It is possible that session saving errors could occur in connection with file names containing spaces. This should be fixed in larch-4.28"

So you can decide for yourself if this is important.

It would also be great if someone could test larch-5 on 64-bit. It is easier to build than larch-4: only one package, and scripts to automate it! See http://forum.faunos.com/viewtopic.php?id=204

But in any case it might be wise to wait a few days - I may need to make a few tweaks to accommodate the new pacman.

wantilles · 2008-01-13 13:58:30

gradgrind wrote:

It would also be great if someone could test larch-5 on 64-bit. It is easier to build than larch-4: only one package, and scripts to automate it! See http://forum.faunos.com/viewtopic.php?id=204
But in any case it might be wise to wait a few days - I may need to make a few tweaks to accommodate the new pacman.

When you include the needed changes for the new pacman, let me know.

Give me the modified PKGBUILD and I will gladly test it on amd64.

gradgrind · 2008-01-14 07:57:01

I hope larch-4.29 and pacin-2.11 should be pacman-3.1 compatible - please give them a spin. The corresponding source package is larch4-20080113.tar.gz (or from svn).

digitalcrypto · 2008-01-14 22:02:21

Will give it a try in a few moments. Couldn't figure out larch5 so I will stick with 4.

digitalcrypto · 2008-01-14 23:39:24

Larch4 seems to be working with pacman 3.1 now. I hard coded the INSTLDIR as it was not picking up as in previous versions.

digitalcrypto · 2008-01-15 00:03:39

larch doesn't finish building as it had done in the past . here is the output from the test

/root/mklarch -d gradplay

=================
//
// *** pacin finished! Archlinux has been installed to /home/larchroot ***
// It is//
// *** pacin finished! Archlinux has been installed to /home/larchroot ***
// It is, however, pretty unconfigured ...
//
/root/larch/bin/mklarch: line 280: /home/larchroot: is a directory, however, pretty unconfigured ...
//
/root/larch/bin/mklarch: line 280: /home/larchroot: is a directory

gradgrind · 2008-01-15 08:33:55

Hi digitalcrypto,

Those are pretty strange problems.

1) Could you please explain what you mean by 'I hard coded the INSTLDIR as it was not picking up as in previous versions.'

2)

digitalcrypto wrote:

larch doesn't finish building as it had done in the past . here is the output from the test
/root/mklarch -d gradplay
=================
//
// *** pacin finished! Archlinux has been installed to /home/larchroot ***
// It is//
// *** pacin finished! Archlinux has been installed to /home/larchroot ***
// It is, however, pretty unconfigured ...
//
/root/larch/bin/mklarch: line 280: /home/larchroot: is a directory, however, pretty unconfigured ...
//
/root/larch/bin/mklarch: line 280: /home/larchroot: is a directory

I don't know what is in your 'gradplay' profile, so I assume it is some modification of my 'gradplay' example, which I have just run to test it. It finished with no problems.

Your output is really very strange - I wonder if something got a bit corrupted. Maybe you could try downloading larch again before another attempt. I would also suggest running larch-setup.sh in another directory, say '/root/larchtest', so as not to pollute /root too much.

digitalcrypto · 2008-01-15 10:31:03

Hey gradgrind,

Yeah I dunno what's happening now. I recently rebuilt my dev machine because of pacman 3.1 weirdness.

I am using the larch-setup.sh from archie.dotsrc.org larch4 stuff.

I don't mind polluting root for now. I usually keep it empty and I toast everything once I've got it working the way I like and move it to /usr/local

I will give it another shot.

digitalcrypto · 2008-01-15 10:59:16

Ok I deleted everything and started again.

Ran larch-setup.sh on archie.dotsrc.org/projects/archie/larch/larch4

I copied over mini to my test profile and touched ./test/baseveto since it complained it coulnd't find it. I didn't modify anything about it.

I ran /root/mklarch -d test/ from /root/larch/share/larch/profiles directory

And this is what it spat back on generating ISO.

(This is the way I was building them before pacman updated)

==============================

// I really mean it ... Are you sure you want to do this?
// **********************************************************
[y/N]: y

// Kernel version: 2.6.23-ARCH
// -> regenerating kernel dependencies

Using aufs
ls: cannot access /home/larchroot/var/lib/pacman/local: No such file or directory
ERROR: Package cdrkit is not installed on target
ls: cannot access /home/larchroot/var/lib/pacman/local: No such file or directory
ERROR: Package dvd\+rw-tools is not installed on target
ls: cannot access /home/larchroot/var/lib/pacman/local: No such file or directory
ERROR: Package squashfs-tools is not installed on target
ls: cannot access /home/larchroot/var/lib/pacman/local: No such file or directory
ERROR: Package initcpio_larch is not installed on target
ls: cannot access /home/larchroot/var/lib/pacman/local: No such file or directory
WARNING: Package python is recommended
ls: cannot access /home/larchroot/var/lib/pacman/local: No such file or directory
WARNING: Package archin is recommended
ls: cannot access /home/larchroot/var/lib/pacman/local: No such file or directory
WARNING: Package larchin is recommended
[root@FuzionX profiles]#

All these packages are installed on the local machine and the [larch] repo is in my /etc/pacman.conf

Last edited by digitalcrypto (2008-01-15 11:08:05)

digitalcrypto · 2008-01-15 11:35:42

I tried installing larch4 using pacman but the package seems broken. it's looking for files in /opt/larch which don't exist as they are all installed in /usr/share/larch

gradgrind · 2008-01-15 13:46:29

I'm afraid I can't reproduce any of this, it all works fine here.

ls: cannot access /home/larchroot/var/lib/pacman/local: No such file or directory
ERROR: Package cdrkit is not installed on target
ls: cannot access /home/larchroot/var/lib/pacman/local: No such file or directory
ERROR: Package dvd\+rw-tools is not installed on target
...

This stuff suggests that the first stage, the installation, didn't work properly, but you haven't posted the output of that.
Perhaps you could send me all the output from such a run?

digitalcrypto wrote:

I tried installing larch4 using pacman but the package seems broken. it's looking for files in /opt/larch which don't exist as they are all installed in /usr/share/larch

Hmmm. Are you sure you have removed all the stuff from your experiments with installing larch packages? Have you got an /etc/profile.d/larch.sh file? larch is only installed in /opt/larch in version 5! Try 'which mklarch' - there should be none.

digitalcrypto · 2008-01-15 22:46:37

I will run up in a moment here to show you what I am talking about and pastebin the results.

digitalcrypto · 2008-01-15 23:03:45

I doubled checked to make sure there were no existing files on the system. I cleaned root completely out and scripted the output file so you could follow steps.

http://pastebin.archlinux.org/24019

Also just noting that nothing is showing up in /home/larchroot/var/cache/pacman/pkg

Everything there is empty. Perhaps a missing symlink?

Last edited by digitalcrypto (2008-01-15 23:09:51)

digitalcrypto · 2008-01-16 05:17:32

Line 97 buildlive

Changed fail=1 to fail=0 to bypass checks for non-existent files.

Builds ok now.

gradgrind · 2008-01-16 06:21:34

digitalcrypto wrote:

http://pastebin.archlinux.org/24019

There's something very wrong here! Could you post your /etc/pacman.conf, please?

digitalcrypto · 2008-01-16 08:08:21

Yep here it is

#
# /etc/pacman.conf
#
# See the pacman manpage for option directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
RootDir = /
DBPath = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
LogFile = /var/log/pacman.log
HoldPkg = pacman glibc
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u

#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
#
#[testing]
#Include = /etc/pacman.d/mirrorlist
[larch]

Server = ftp://archie.dotsrc.org/projects/archie/larch/larch4

[core]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist

[extra]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist

[community]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist

#[unstable]
# Add your preferred servers here, they will be used first
#Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs

gradgrind · 2008-01-16 10:44:09

Ahhhh. As I suspected, here's the problem:

digitalcrypto wrote:

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
RootDir = /
DBPath = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
LogFile = /var/log/pacman.log
HoldPkg = pacman glibc
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u

Please comment these out (or delete them completely!) ->

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u

The meaning of these options changed in pacman-3.1 and now if you use them it will cause mklarch to malfunction. (There is no need to have them uncommented anyway, because these values are the defaults.)

You also don't need the [larch] entry as it will be added automatically by mklarch, but it should do no harm.

digitalcrypto · 2008-01-16 23:03:09

Ahh yep that works perfectly! Thank you!

I have machines that can't boot from USB but save sessions well enough on CD/DVD. Are you going to leave Larch4 as it is even though you are moving onto 5?

gradgrind · 2008-01-17 06:15:19

digitalcrypto wrote:

Ahh yep that works perfectly! Thank you!

Glad to hear it.

digitalcrypto wrote:

I have machines that can't boot from USB but save sessions well enough on CD/DVD. Are you going to leave Larch4 as it is even though you are moving onto 5?

I think that depends on how difficult it is to maintain with changes in Arch, etc. Of course, it's easy enough to make a boot CD which will handle the actual booting but use the system on USB stick. That's what I'm using on my computers that can't boot from USB.

lilsirecho · 2008-01-17 06:53:27

Gradgrind:

Perhaps you would like to try a compact flash/IDE boot. I boot Faunos in 33 secs with mine. My system doesn't boot from USB either so this makes it boot faster anyhow

I haven't tried a really fast compact flash device yet, 100x is my best.

Am able to boot into ram and remove the flash, too.

With a second flash/IDE unit, I have a local repo for packages I don't use much so I can delete them from the boot device and install when needed.

Waiting for the release of a beta for Faun soon.

Nice and warm in California!!!!!!

gradgrind · 2008-01-18 08:55:13

lilsirecho wrote:

Gradgrind:
Perhaps you would like to try a compact flash/IDE boot. I boot Faunos in 33 secs with mine. My system doesn't boot from USB either so this makes it boot faster anyhow

My video/music player has been running Arch (larch) from compact flash/IDE for over a year now - a great solution.

lilsirecho wrote:

I haven't tried a really fast compact flash device yet, 100x is my best.

$$$$

lilsirecho wrote:

Nice and warm in California!!!!!!

That was uncalled for - consider forum etiquette!

Cold and grey here.

foxbunny · 2008-01-27 15:09:22

I didn't want to start a new topic for this, since larch-4 thread already here, and all...

Anyway, I've successfully compiled my first Live DVD today, and I have a few questions. I've installed KDEmod on it rather than stock KDE. However, the /usr/bin/startkde seems to be missing (which I suspect is KDEmod package not creating it post-install). Anyway, what would be the best way to deal with this?

Also, someone mentioned a way to make the save session feature save to USB rather than DVD which is not writable. How do I do this?

Apart from these questions, great THANKS to gradgrind! You are GOD!

gradgrind · 2008-01-27 21:01:07

foxbunny wrote:

I didn't want to start a new topic for this, since larch-4 thread already here, and all...
Anyway, I've successfully compiled my first Live DVD today, and I have a few questions. I've installed KDEmod on it rather than stock KDE. However, the /usr/bin/startkde seems to be missing (which I suspect is KDEmod package not creating it post-install). Anyway, what would be the best way to deal with this?

Isn't the standard location /opt/kde/bin/startkde? Anyway, if it's missing, you'll probably want to add it ... session save? ...

foxbunny wrote:

Also, someone mentioned a way to make the save session feature save to USB rather than DVD which is not writable. How do I do this?

Is the DVD really not writable? I think DVD's are normally written in a way that allows extension. The easiest way by far though is to use USB from the beginning - put the larch system on a USB stick and boot from that. Indeed, in larch-5 I have dropped session saving to CD/DVD. If your system won't boot from USB you can make a boot CD which will boot and then load the larch system from USB.

If you need help with any details, please post again.

foxbunny · 2008-01-27 21:16:03

So, how do I make a CD that boots from USB?

Aw, I feel so stupid.... If I burn a multisession DVD, it will be able to save sessions, right?

EDIT: but I can't burn multisession DVD in K3B when burning a iso...

Last edited by foxbunny (2008-01-28 00:08:29)

gradgrind · 2008-01-28 06:43:40

foxbunny wrote:

So, how do I make a CD that boots from USB?

I'll assume you are using larch-4.

There are various ways of achieving this, but in principle: you just need a boot CD (not a straight burn of the files!) containing the kernel and the initramfs file (larch.img) and the boot stuff (isolinux or grub). It doesn't matter what else is on there, so long as there is no 'larchboot' file. If you use mklarch to put your larch system on USB stick (using the -u option to mklarch), you can then use the usb2bootiso script to make the iso.

foxbunny wrote:

... If I burn a multisession DVD, it will be able to save sessions, right?
EDIT: but I can't burn multisession DVD in K3B when burning a iso...

I think what you get from k3b (in the case of DVDs) is automatically 'multisession', it was the last time I tried it. To be sure you can always use growisofs directly. Try session save on the DVD you've already got. It might not work anyway, though. The last time I tried it there was some problem with duplicate Rock Ridge names in mkisofs, which I guess is a bug in that program.

Arch Linux

#51 2008-01-13 12:39:15

Re: larch-4 testing, can also 'livify' existing Arch installation

#52 2008-01-13 13:58:30

Re: larch-4 testing, can also 'livify' existing Arch installation

#53 2008-01-14 07:57:01

Re: larch-4 testing, can also 'livify' existing Arch installation

#54 2008-01-14 22:02:21

Re: larch-4 testing, can also 'livify' existing Arch installation

#55 2008-01-14 23:39:24

Re: larch-4 testing, can also 'livify' existing Arch installation

#56 2008-01-15 00:03:39

Re: larch-4 testing, can also 'livify' existing Arch installation

#57 2008-01-15 08:33:55

Re: larch-4 testing, can also 'livify' existing Arch installation

#58 2008-01-15 10:31:03

Re: larch-4 testing, can also 'livify' existing Arch installation

#59 2008-01-15 10:59:16

Re: larch-4 testing, can also 'livify' existing Arch installation

#60 2008-01-15 11:35:42

Re: larch-4 testing, can also 'livify' existing Arch installation

#61 2008-01-15 13:46:29

Re: larch-4 testing, can also 'livify' existing Arch installation

#62 2008-01-15 22:46:37

Re: larch-4 testing, can also 'livify' existing Arch installation

#63 2008-01-15 23:03:45

Re: larch-4 testing, can also 'livify' existing Arch installation

#64 2008-01-16 05:17:32

Re: larch-4 testing, can also 'livify' existing Arch installation

#65 2008-01-16 06:21:34

Re: larch-4 testing, can also 'livify' existing Arch installation

#66 2008-01-16 08:08:21

Re: larch-4 testing, can also 'livify' existing Arch installation

#67 2008-01-16 10:44:09

Re: larch-4 testing, can also 'livify' existing Arch installation

#68 2008-01-16 23:03:09

Re: larch-4 testing, can also 'livify' existing Arch installation

#69 2008-01-17 06:15:19

Re: larch-4 testing, can also 'livify' existing Arch installation

#70 2008-01-17 06:53:27

Re: larch-4 testing, can also 'livify' existing Arch installation

#71 2008-01-18 08:55:13

Re: larch-4 testing, can also 'livify' existing Arch installation

#72 2008-01-27 15:09:22

Re: larch-4 testing, can also 'livify' existing Arch installation

#73 2008-01-27 21:01:07

Re: larch-4 testing, can also 'livify' existing Arch installation

#74 2008-01-27 21:16:03

Re: larch-4 testing, can also 'livify' existing Arch installation

#75 2008-01-28 06:43:40

Re: larch-4 testing, can also 'livify' existing Arch installation

Board footer