Archiso-Testing 20090620 Release

Changes since last release:

* This iso uses the testing repo and the lastest packages in testing.

* Kernel is its own module now.

* Added packages.list to the iso. This is so the iso can be mirror without the package list and still have it in the iso.

* Added rpcbind to replace portmap.

* Updated my build scripts so there can update older .working folders without rebuilding all of the squashfs modules. This is good cause it means that your only rebuild squashfs modules that are needed and that will save a lot of time when using less powerful computers.

Everything is up2date as of 5:00 PM EST on 20090620. ( The iso doesnt have the new xfce4 plugins and new tzdata in testing that came out today.)

Here is the iso, md5, and packages list.

Packages changes are here.

Advertisements

~ by godane on June 20, 2009.

14 Responses to “Archiso-Testing 20090620 Release”

  1. hi,
    check out Icadyptes – it is another Arch based flavor. The most interesting stuff is that they do some innovation on packages. For example, they use eglibc and OSS4(http://mailman.opensound.com/pipermail/oss-devel/2008-September/000740.html)
    They have created appropriate PKGBUILD scripts for packages that have shitty build systems of their own – like OSS4 (ftp://icadyptes.org/icadyptes/abs/extra/multimedia/oss/PKGBUILD). Development on this has slowed down because of personal reasons, however Im sure you could collaborate.

    I would love to see OSSv4 and eglibc on small and lightweight archiso!

  2. Does the installer work from Xfce now?

  3. Hi Godane, do you have any detailed step-by-step procedures for using your archlive scripts? Thanks.

  4. Again : thank you for providing this nice piece of work!
    Have intalled Archiso-Testing 20090620 on hard disk with larchin. Nice!!
    Some programs need old libraries. Simplest way to solve this problem?

  5. Thanks, Godane. I did those steps exactly as listed and at the line of the script:

    cp: cannot stat ‘modules/*; no such file or directory

    and–

    syslinux not found on host system cannot install

    This was after a very long process (it took two hours). Was this my error? Should the script check for all necessary directories before it begins?

    Also: would it be possible to simply use an existing install, instead of downloading all of the packages on a package list and installing to a isolated directory? That way I can make sure that I’m getting all of my custom changes to the desktop, programs, etc. and so that locales, docs and help files are deleted. Thanks.

  6. I did those steps exactly as listed and at the line of the script:

    cp: cannot stat ‘modules/*; no such file or directory

    and–

    syslinux not found on host system cannot install

    This was after a very long process (it took two hours). Was this my error? Should the script check for all necessary directories before it begins?

    Also: would it be possible to simply use an existing install, instead of downloading all of the packages on a package list and installing to a isolated directory? That way I can make sure that I’m getting all of my custom changes to the desktop, programs, etc. and so that locales, docs and help files are deleted. Thanks.

    • @LinuxHead
      You need syslinux installed. I forgot to added that into the wiki. Also i have updated the scripts so that i only updated modules now that have newer packages. This way it only builds new modules have updated packages. As long as the .working folder stay where it is it will only update modules needing updating.
      You can also do a ./build makeimg after you install syslinux. This will just make the iso with install or updating anything.

      @joji
      I been using testing repo for the last 2 week so people can try out testing with doing anything to there system. This is mostly cause of the big rebuilds that are going on in testing repo.

  7. have been too fast! have seen that may programs have been updated to ue the new libraries from ‘test’

  8. Thanks Godane. That did work. But what I end up with is the same ISO you’ve made available for download. So I’m still interested in how, exactly, your scripts are used (or if they can be used) to make a live CD out of my existing, installed Arch system. I’m using GNOME (instead of xfce), NetworkManager (instead of Wicd) and Splashy, among other things. Is it possible? Am I on my own to modify your scripts? Thanks for making your scripts available.

    • @LinuxHead
      This is mostly cause you have to added .list in the list folder of archiso-live. These .list files have the name of packages and group packages that are installed. The modules name and order in union is in the config file. I will try to see about document this more in the next week. Sorry about this.

  9. I’ll look forward to reading your new documentation, thanks very much. But I do know about the list folder and config file. What I’m asking is whether you’ve considered building the modules out of a running, installed Arch system. You’ve combined Archiso with Linux Live Scripts, but the final product has more in common with Archiso than LLS. I’m just wondering if you’ve considered making it more like LLS, that is, build the modules (and the live CD) out of a running, installed system, rather than downloading and installing Arch packages to a discrete folder and running LLS against that.

    I think you’ve got a really good thing going here, and I’m sure I could (over time) figure it out myself, but you know this stuff so well it seems like it would faster for you. If you build the ISO out of a running system there wouldn’t be a need for lists of packages.

    Anyway, I’ll drop the issue after this post. Thanks for your responses so far,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: