From ch at mosaik-software.de Sat Aug 2 05:48:59 2008 From: ch at mosaik-software.de (Christian Holzberger) Date: Fri, 01 Aug 2008 19:48:59 +0200 Subject: [gobolinux-devel] [ANNOUNCE] Scripts 2.9.4, Compile 1.11.2 In-Reply-To: References: Message-ID: <1217612939.12923.1.camel@localhost.localdomain> hi, just a note, news on gobolinux.org aren't updated yet... On Thu, 2008-07-31 at 13:26 +1200, Michael Homer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, > We are pleased to announce new releases of both Scripts and Compile. > These are principally bugfix releases. There are also improvements to > ContributeRecipe and RecipeLint to warn at an earlier stage about non- > standard recipes, and extra validation for packages to avoid a > potential security flaw. > > These new versions are available via `InstallPackage Scripts 2.9.4` and > `InstallPackage Compile 1.11.2`. > > The full changelog follows at the end of this message. > - -Michael > > ChangeLog: > Scripts 2.9.4: > 2008-07-05 23:40 mwh > > * bin/CheckDependencies: Fix dependencyless useflags and > versionless useflags in dependency interpretation. > > 2008-07-05 23:56 mwh > > * bin/CheckDependencies: Fix ConvertRecipeToBinary for new rule > format. Closes #356. > > 2008-07-06 02:14 mwh > > * bin/CheckDependencies: Flags in Dependencies are comma-separated, > not whitespace-separated > > 2008-07-06 13:03 mohjive > > * bin/InstallPackage: Pass on --no-link and --keep to subcalls of > InstallPackage for dependencies. > > 2008-07-10 18:04 lode > > * bin/UnionSandbox: Make sure directory is cleaned up properly when > program dies with a signal trap. > > 2008-07-11 14:37 hisham > > * Functions/File: Add the full path to the FileHash file entries. > If they are tampered with, FileHash.sig will alert. > > 2008-07-12 20:01 mohjive > > * src/FindDependencies.c: If the version outside of the range has > NOT_EQUAL as operator, it's ok, just skip it > > 2008-07-14 10:14 mohjive > > * src/FindDependencies.c: removing stray bracet > > 2008-07-14 10:20 mohjive > > * src/FindDependencies.c: FindDependencies doesn't support use > flags just yet, but we have to take care of it > > 2008-07-25 07:41 mohjive > > * ., Data/CommandNotFound.data: r418 at Hermes: jonas | 2008-07-25 > 09:42:56 +0200 > Adding entries for XDG-Utils > > 2008-07-28 20:30 mohjive > > * bin/InstallPackage, bin/SignProgram, bin/VerifyProgram: Put > package name and version in a meta file and verify it and > revision at install > > 2008-07-29 17:12 mohjive > > * Functions/File: Reverting adding full paths to filehash as we > have other ways of checking correct name and version now > > 2008-07-29 20:01 mohjive > > * Makefile: Clean up the makefile a bit > > 2008-07-29 20:36 mohjive > > * bin/InstallPackage: only warn if we have a revision. > > 2008-07-30 01:14 mwh > > * bin/SignProgram: Wrap Resources/MetaData access in $sudo_exec > > 2008-07-31 00:28 mohjive > > * bin/CreateRootlessEnvironment: Update version. > > Compile 1.11.2: > 2008-07-02 11:46 mohjive > > * bin/Compile: Pass --configure-options to members of meta recipes. > Solving bug #332 > > 2008-07-05 16:27 mohjive > > * ., bin/GetRecipe: r393 at Hermes: jonas | 2008-07-05 18:24:26 +0200 > Catch errors from wget > > 2008-07-06 00:23 mohjive > > * ., bin/RecipeLint: r395 at Hermes: jonas | 2008-07-06 02:20:17 +0200 > Adding cell arch to RecipeLint > > 2008-07-06 20:50 mohjive > > * bin/Compile: Fix spelling error of variable references > > 2008-07-08 13:54 mohjive > > * bin/Compile: Wrap chmod in $sudo_exec if first try fails > > 2008-07-08 15:12 mohjive > > * bin/NewVersion: Add Hg to scm types > > 2008-07-08 15:13 mohjive > > * bin/Compile: Make Compile smarter with versioned scm recipes. > > 2008-07-10 08:50 mohjive > > * bin/Compile: Do not run hooks from recipe when doing safe linking > > 2008-07-12 09:29 mohjive > > * bin/Compile: [U]se the directory if called with "no-web" > > 2008-07-13 08:56 mwh > > * bin/Compile: Move useflag hook execution up above the buildmerged > and installmerged array creation, so that any variable updates > are included in those. > > 2008-07-17 01:06 mwh > > * bin/RecipeLint: RecipeLint should give an error on file_size=0 > (probably indicating a cancelled fetch in MakeRecipe/NewVersion) > > 2008-07-17 01:15 mwh > > * bin/ContributeRecipe: Force contributed recipes to pass > RecipeLint. > > 2008-07-17 01:20 mwh > > * bin/ContributeRecipe: Give list of versions available in > LocalRecipes when ambiguous in the error message. > > 2008-07-17 01:25 mwh > > * bin/ContributeRecipe: Also refuse to submit Description-less > recipes > > 2008-07-17 01:41 mwh > > * bin/RecipeLint: Complain about versionless "GPL" in License > field. > > 2008-07-19 08:02 mwh > > * bin/RecipeLint: Make GPL check case-insensitive > > 2008-07-23 16:58 mohjive > > * bin/PackRecipe: Adding another variant of GNU GPL2 > > 2008-07-26 15:51 mohjive > > * bin/Compile: We need to mark environment=() variables to export > them > > 2008-07-28 00:52 mohjive > > * bin/RecipeLint: We have to unset there variables each loop, so we > start fresh for each arch > > 2008-07-29 20:14 mohjive > > * Makefile: Srtting up the Compile Makefile the same way as Scripts > Makefile > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.3 (GNU/Linux) > > iD8DBQFIkRPytjw6l4s6SlsRAp9aAKCxZkIqHO2Ad0gA6q/K+mRV5RkG6wCfW9BE > mF3bH/pk9JuGRBhNnq4lZ0c= > =BmMx > -----END PGP SIGNATURE----- > _______________________________________________ > gobolinux-devel mailing list > gobolinux-devel at lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel -- MOSAIK Software - Christian Holzberger Web: http://www.mosaik-software.de From michael at gobolinux.org Sat Aug 2 23:24:52 2008 From: michael at gobolinux.org (Michael Homer) Date: Sat, 2 Aug 2008 23:24:52 +1200 Subject: [gobolinux-devel] Generic useflags In-Reply-To: <200807042056.16059.michael@gobolinux.org> References: <200807042056.16059.michael@gobolinux.org> Message-ID: <200808022324.53197.michael@gobolinux.org> On Friday 04 July 2008 20:56:14 you wrote: > Hi all, > There's been some lengthy discussion on #gobolinux about these, and whether > or how they should be implemented. Code checked in to SVN over the last couple of hours contains an initial implementation of these flags. Give them a try, comments and feedback encouraged. They're configured in /System/Settings/GenericFlags.conf; remember to `UpdateSettings Scripts` to install the default file. Also note that specific->generic always works, but generic->specific will only work when passed a recipe directory, as it relies on having the set of potential flags available. For testing that I suggest adding a couple of test generics using some flags that you have around in recipes; they seem to work for me, but I haven't explored all the nuances yet. -Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. Url : http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080802/5cf69399/attachment.pgp From jonka750 at student.liu.se Sat Aug 16 12:00:24 2008 From: jonka750 at student.liu.se (Jonas Karlsson) Date: Fri, 15 Aug 2008 21:00:24 -0300 Subject: [gobolinux-devel] German mirror Message-ID: <76a336670808151700k2f822ab7k8fe20e832bdd41a4@mail.gmail.com> Hello, who's responsible for the german mirror? It seems that the ISO there isn't complete (http://forum.gobolinux.org/discussion/193/german-download-is-only-667m-instead-of-671m/#Item_0) -- /Jonas From lijon at kymatica.com Tue Aug 19 06:15:04 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Mon, 18 Aug 2008 20:15:04 +0200 Subject: [gobolinux-devel] PAM Message-ID: <48A9BC28.4010308@kymatica.com> How is the switch to PAM going? Is there a package or recipe for Shadow with PAM support? -- /Jonatan [ http://kymatica.com ] From jonka750 at student.liu.se Tue Aug 19 08:48:04 2008 From: jonka750 at student.liu.se (Jonas Karlsson) Date: Mon, 18 Aug 2008 17:48:04 -0300 Subject: [gobolinux-devel] PAM In-Reply-To: <48A9BC28.4010308@kymatica.com> References: <48A9BC28.4010308@kymatica.com> Message-ID: <76a336670808181348y7828d030i6e154d28e1d06d73@mail.gmail.com> 2008/8/18 Jonatan Liljedahl : > How is the switch to PAM going? > Is there a package or recipe for Shadow with PAM support? > Just set the +pam use flag and recompile shadow and everything should work (tm) -- /Jonas From lucasvr at gobolinux.org Wed Aug 20 07:13:06 2008 From: lucasvr at gobolinux.org (Lucas C. Villa Real) Date: Tue, 19 Aug 2008 16:13:06 -0300 Subject: [gobolinux-devel] OSnews Message-ID: <2c03f9590808191213v6912029cocfad877a7f464d2a@mail.gmail.com> A GoboLinux discussion is going on here: http://www.osnews.com/comments/20195 Lucas From thomas.heller1 at gmx.de Sat Aug 23 09:16:26 2008 From: thomas.heller1 at gmx.de (Thomas Heller) Date: Fri, 22 Aug 2008 18:16:26 -0300 Subject: [gobolinux-devel] Boot sequence enhancement Message-ID: <200808221816.27288.thomas.heller1@gmx.de> Hi, As I am new to GoboLinux and this list i just want to say hello, and say that i like the way gobo linux is going and the realisation is pretty good, from what i saw. But on the other side, as i did the installation, i noticed some not so good "features" one thing i disliked was, how the boot process gets configured, and the you handle "Tasks", as I am used to handle with /etc/init.d and some simple configuration file here is the proposal to the boot sequence: extending the Config file /System/Settings/BootOptions with a parameter, lets say BootTasks which holds a whitespace sperated list of tasks to start at boot time. This would make the current the current scheme, where you have to edit /System/Settings/BootScripts/* to have the correct behaviour. One benefit would be that you only have one place to configure the boot sequence. Another benefit would be a much cleaner and safer way to control the boot sequence for the user. What do you think about that? I won't be able to to answer you until sunday evening, but if you like that idea i could write a patch for the current bootscripts. Greetings, Thomas Heller From geromao at gmail.com Sat Aug 23 05:03:48 2008 From: geromao at gmail.com (=?ISO-8859-1?Q?F=E1bio_Mierlo?=) Date: Fri, 22 Aug 2008 14:03:48 -0300 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <200808221816.27288.thomas.heller1@gmx.de> References: <200808221816.27288.thomas.heller1@gmx.de> Message-ID: <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> I was think in something like that, but a little different. One file called /S/S/BootScripts/Tasks, where InstallPackage can "grep" for the task name and if isn't in there InstallPackage will "echo #$TaskName >> /S/S/BooScripts". So, the user can "uncomment" the task they want, then BootUp will start the uncommented tasks and Shutdown will "inversely" stop these tasks. On Fri, Aug 22, 2008 at 6:16 PM, Thomas Heller wrote: > Hi, > As I am new to GoboLinux and this list i just want to say hello, and say that > i like the way gobo linux is going and the realisation is pretty good, from > what i saw. > But on the other side, as i did the installation, i noticed some not so > good "features" one thing i disliked was, how the boot process gets > configured, and the you handle "Tasks", as I am used to handle > with /etc/init.d and some simple configuration file here is the proposal to > the boot sequence: > > extending the Config file /System/Settings/BootOptions with a parameter, lets > say BootTasks which holds a whitespace sperated list of tasks to start at > boot time. This would make the current the current scheme, where you have to > edit /System/Settings/BootScripts/* to have the correct behaviour. > One benefit would be that you only have one place to configure the boot > sequence. > Another benefit would be a much cleaner and safer way to control the boot > sequence for the user. > > What do you think about that? > I won't be able to to answer you until sunday evening, but if you like that > idea i could write a patch for the current bootscripts. > > Greetings, > Thomas Heller > _______________________________________________ > gobolinux-devel mailing list > gobolinux-devel at lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel > From thomas.heller1 at gmx.de Sat Aug 23 12:33:09 2008 From: thomas.heller1 at gmx.de (Thomas Heller) Date: Fri, 22 Aug 2008 21:33:09 -0300 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> Message-ID: <200808222133.09230.thomas.heller1@gmx.de> Isn't that a little bit against the idea "the filesystem is the package management"? But in general, you're idea and mine are not disjunct, so they could be easily combined. On Friday 22 August 2008 14:03:48 you wrote: > I was think in something like that, but a little different. > > One file called /S/S/BootScripts/Tasks, where InstallPackage can > "grep" for the task name and if isn't in there InstallPackage will > "echo #$TaskName >> /S/S/BooScripts". > > So, the user can "uncomment" the task they want, then BootUp will > start the uncommented tasks and Shutdown will "inversely" stop > these tasks. > > On Fri, Aug 22, 2008 at 6:16 PM, Thomas Heller wrote: > > Hi, > > As I am new to GoboLinux and this list i just want to say hello, and say > > that i like the way gobo linux is going and the realisation is pretty > > good, from what i saw. > > But on the other side, as i did the installation, i noticed some not so > > good "features" one thing i disliked was, how the boot process gets > > configured, and the you handle "Tasks", as I am used to handle > > with /etc/init.d and some simple configuration file here is the proposal > > to the boot sequence: > > > > extending the Config file /System/Settings/BootOptions with a parameter, > > lets say BootTasks which holds a whitespace sperated list of tasks to > > start at boot time. This would make the current the current scheme, where > > you have to edit /System/Settings/BootScripts/* to have the correct > > behaviour. One benefit would be that you only have one place to configure > > the boot sequence. > > Another benefit would be a much cleaner and safer way to control the boot > > sequence for the user. > > > > What do you think about that? > > I won't be able to to answer you until sunday evening, but if you like > > that idea i could write a patch for the current bootscripts. > > > > Greetings, > > Thomas Heller > > _______________________________________________ > > gobolinux-devel mailing list > > gobolinux-devel at lists.gobolinux.org > > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel From tiagofalcao at gmail.com Sun Aug 24 14:20:33 2008 From: tiagofalcao at gmail.com (Tiago Falcao) Date: Sat, 23 Aug 2008 23:20:33 -0300 Subject: [gobolinux-devel] Recipe Screen 4.0.2 Message-ID: <59c687850808231920q428b0350q7a09a245f9178a3c@mail.gmail.com> Please, change the path for screen-4.0.2.tar.gz to: http://ftp.gnu.org/gnu/screen/screen-4.0.2.tar.gz The other FTP don't connect here. Thanks ========================== Tiago Rezende Campos Falc?o --------------------------------------------------- Laboratory of Information Systems Institute of Computing University of Campinas - UNICAMP 13083-970, Campinas, SP, Brazil -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080823/21e13c82/attachment.htm From lucasvr at gobolinux.org Sun Aug 24 19:07:58 2008 From: lucasvr at gobolinux.org (Lucas C. Villa Real) Date: Sun, 24 Aug 2008 04:07:58 -0300 Subject: [gobolinux-devel] Recipe Screen 4.0.2 In-Reply-To: <59c687850808231920q428b0350q7a09a245f9178a3c@mail.gmail.com> References: <59c687850808231920q428b0350q7a09a245f9178a3c@mail.gmail.com> Message-ID: <2c03f9590808240007u43a6431fq8d61e4e40b81c551@mail.gmail.com> On Sat, Aug 23, 2008 at 11:20 PM, Tiago Falcao wrote: > Please, change the path for screen-4.0.2.tar.gz to: > > http://ftp.gnu.org/gnu/screen/screen-4.0.2.tar.gz > > The other FTP don't connect here. Thanks for the report. The recipe has been updated to reflect the URL change (new revision is r5). Regards, -- Lucas powered by /dev/dsp From martin.p.svensson at gmail.com Sun Aug 24 23:55:02 2008 From: martin.p.svensson at gmail.com (Martin Svensson) Date: Sun, 24 Aug 2008 13:55:02 +0200 Subject: [gobolinux-devel] Problem with FixDirReferences on rootless Message-ID: FixDirReferences may modify files incorrectly on a rootless installation During SymlinkProgram phase the FixDirReferences script may modify paths inside some types of files. Some paths may be modified to /usr (if no better path can be found). This may cause problems on a rootless gobolinux installation. If the problem only occurs in a specific case one might of course "solve" the by editing the offending file. However it would also be nice if a more general solution could be done. My first quick and dirty solution to the problem was to modify FixDirReferences to never use /usr modification on rootless installations (patch as attachment). However I am not certain this is the best solution to the problem. Other solutions might be to make other modifications to FixDirReferences: Perhaps try to use more advanced logic to replace paths using some type of more advanced trickery? (My knowledge about how pkg-config etc is used is close to noneexistant but I surmise it would be possible ) Or perhaps modify FixdirReferences to use some type of goboPrefix/usr instead of /usr ? What do you think would be a good solution to this problem ? I would of course prefer if anyone else could wave a magic wand and solve the problem :) But I would be willing to take a look at this problem assuming an modification would be of interest. /Regards Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: FixDirReferences.patch Type: text/x-diff Size: 1816 bytes Desc: not available Url : http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080824/bfc9ab7f/attachment.patch From tiagofalcao at gmail.com Mon Aug 25 03:26:20 2008 From: tiagofalcao at gmail.com (Tiago Falcao) Date: Sun, 24 Aug 2008 12:26:20 -0300 Subject: [gobolinux-devel] Recipe LibPaper 1.1.23 Message-ID: <59c687850808240826u34c48dc7i4a083bdba5a2e42a@mail.gmail.com> Resolving ftp.debian.org... 128.101.240.212 Connecting to ftp.debian.org|128.101.240.212|:80... connected. HTTP request sent, awaiting response... 404 Not Found The requested URL /debian/pool/main/libp/libpaper/libpaper_1.1.23.tar.g was not found on this server. In Debian FTP the filename has chaged to libpaper_1.1.23+nmu1.tar.gz libpaper (1.1.23+nmu1) unstable; urgency=low * Non-maintainer upload to fix pending l10n issues. * Debconf translations: - Finnish. Closes: #448419 - Basque. Closes: #485430 * [Lintian] No longer ignore errors by "make distclean" * [Lintian] Make the package binNMUable by replacing ${Source-Version} by ${binary:Version} in dependencies * [Lintian] drop (invalid) NEWS.Debian file that documents a very old transition -- Christian Perrier > Wed, 28 May 2008 07:45:35 +0200 Change the recipe's link to: http://ftp.debian.org/debian/pool/main/libp/libpaper/libpaper_1.1.23+nmu1.tar.gz or http://archive.ubuntu.com/ubuntu/pool/main/libp/libpaper/ ========================== Tiago Rezende Campos Falc?o --------------------------------------------------- Laboratory of Information Systems Institute of Computing University of Campinas - UNICAMP 13083-970, Campinas, SP, Brazil -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080824/6d54ef2c/attachment.htm From tiagofalcao at gmail.com Mon Aug 25 04:56:04 2008 From: tiagofalcao at gmail.com (Tiago Falcao) Date: Sun, 24 Aug 2008 13:56:04 -0300 Subject: [gobolinux-devel] Recipe E2FSProgs 1.41.0 Message-ID: <59c687850808240956u1774d11cs394f7ac85cdad5c5@mail.gmail.com> --10:45:20-- http://puzzle.dl.sourceforge.net/sourceforge/e2fsprogs/e2fsprogs-1.41.0.tar.gz (try: 5) => `e2fsprogs-1.41.0.tar.gz' Connecting to puzzle.dl.sourceforge.net|195.141.111.5|:80... failed: Connection timed out. Retrying. --10:48:34-- http://puzzle.dl.sourceforge.net/sourceforge/e2fsprogs/e2fsprogs-1.41.0.tar.gz (try: 6) => `e2fsprogs-1.41.0.tar.gz' Connecting to puzzle.dl.sourceforge.net|195.141.111.5|:80... failed: Connection timed out. Retrying. I found the file in another mirror: http://ufpr.dl.sourceforge.net/sourceforge/e2fsprogs/e2fsprogs-1.41.0.tar.gz We can modify Compile to search in all SourceForge mirrors? ========================== Tiago Rezende Campos Falc?o --------------------------------------------------- Laboratory of Information Systems Institute of Computing University of Campinas - UNICAMP 13083-970, Campinas, SP, Brazil -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080824/9d76ba51/attachment.htm From michael at gobolinux.org Mon Aug 25 10:36:19 2008 From: michael at gobolinux.org (Michael Homer) Date: Mon, 25 Aug 2008 10:36:19 +1200 Subject: [gobolinux-devel] Recipe E2FSProgs 1.41.0 In-Reply-To: <59c687850808240956u1774d11cs394f7ac85cdad5c5@mail.gmail.com> References: <59c687850808240956u1774d11cs394f7ac85cdad5c5@mail.gmail.com> Message-ID: On Mon, Aug 25, 2008 at 4:56 AM, Tiago Falcao wrote: > --10:45:20-- > http://puzzle.dl.sourceforge.net/sourceforge/e2fsprogs/e2fsprogs-1.41.0.tar.gz > (try: 5) => `e2fsprogs-1.41.0.tar.gz' > Connecting to puzzle.dl.sourceforge.net|195.141.111.5|:80... failed: > Connection timed out. > Retrying. > > --10:48:34-- > http://puzzle.dl.sourceforge.net/sourceforge/e2fsprogs/e2fsprogs-1.41.0.tar.gz > (try: 6) => `e2fsprogs-1.41.0.tar.gz' > Connecting to puzzle.dl.sourceforge.net|195.141.111.5|:80... failed: > Connection timed out. > Retrying. > > I found the file in another mirror: > http://ufpr.dl.sourceforge.net/sourceforge/e2fsprogs/e2fsprogs-1.41.0.tar.gz > > > We can modify Compile to search in all SourceForge mirrors? Sourceforge is meant to do that itself. Unfortunately half their mirrors don't actually work and aren't ever removed from the rotation, so downloads.sourceforge.net doesn't always work. Edit Compile.conf and change your $httpSourceforge to point to a local mirror that works for you; everything from Sourceforge will use that mirror from then on. It is possible to specify mirror URLs in recipes, but we usually let existing mirror systems do their work when available. Better and more generalised mirror support would be welcome if somebody wanted to do up a patch. -Michael From lijon at kymatica.com Wed Aug 27 12:02:15 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Wed, 27 Aug 2008 02:02:15 +0200 Subject: [gobolinux-devel] gobo on Eee PC? In-Reply-To: <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> References: <488FAAF3.1000603@kymatica.com> <48907CC7.9080901@kymatica.com> <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> Message-ID: <48B49987.7090703@kymatica.com> > Carlo made an announcement of a LiveFlash edition created especially > for his EEE pc, righ after the release of 014: > > http://lists.gobolinux.org/pipermail/gobolinux-devel/2008-January/003113.html > > He might have improved that edition since then, though. Carlo, do you > have any unpublished changes for LiveFlash since that announcement? When copying contents from ISO to flash, it should be cp -r /Mount/CD-ROM/* instead of /Mount/CD-ROM, right? otherwise the single CD-ROM directory is copied to the root of the flash.. The instructions doesn't mention if the flash partition should be made bootable with fdisk, I guess it should? Anyhow, when I try this my Eee says "invalid or damaged bootable partition". Is it possible that this doesn't work on all usb flashsticks? BTW, Would it be hard to replace the kernel on the livecd/flash with the original asus-xandros-Eee one? There's also this one that might be interesting: http://www.array.org/ubuntu/index.html I'm really interested in creating a GobeeeLinux for the Eee where everything works out of the box. :) I've just set up a lightweight rox-filer + icewm desktop, with super-simple automounting using only udev and some shellscripts, etc.. -- /Jonatan [ http://kymatica.com ] From lijon at kymatica.com Thu Aug 28 02:15:12 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Wed, 27 Aug 2008 16:15:12 +0200 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> Message-ID: <48B56170.4060007@kymatica.com> F?bio Mierlo wrote: > I was think in something like that, but a little different. > > One file called /S/S/BootScripts/Tasks, where InstallPackage can > "grep" for the task name and if isn't in there InstallPackage will > "echo #$TaskName >> /S/S/BooScripts". > > So, the user can "uncomment" the task they want, then BootUp will > start the uncommented tasks and Shutdown will "inversely" stop > these tasks. Or, let it be a directory with symlinks to the actual Tasks. The symlinks could be prefixed with numbers to control the order.. -- /Jonatan [ http://kymatica.com ] From lucasvr at gobolinux.org Thu Aug 28 02:34:21 2008 From: lucasvr at gobolinux.org (Lucas C. Villa Real) Date: Wed, 27 Aug 2008 11:34:21 -0300 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <48B56170.4060007@kymatica.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> Message-ID: <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> On Wed, Aug 27, 2008 at 11:15 AM, Jonatan Liljedahl wrote: > F?bio Mierlo wrote: >> I was think in something like that, but a little different. >> >> One file called /S/S/BootScripts/Tasks, where InstallPackage can >> "grep" for the task name and if isn't in there InstallPackage will >> "echo #$TaskName >> /S/S/BooScripts". >> >> So, the user can "uncomment" the task they want, then BootUp will >> start the uncommented tasks and Shutdown will "inversely" stop >> these tasks. > > Or, let it be a directory with symlinks to the actual Tasks. The > symlinks could be prefixed with numbers to control the order.. This is pretty much how /etc/init.d/rc[n].d works.. -- Lucas powered by /dev/dsp From lijon at kymatica.com Thu Aug 28 02:51:34 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Wed, 27 Aug 2008 16:51:34 +0200 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> Message-ID: <48B569F6.9030102@kymatica.com> Lucas C. Villa Real wrote: > On Wed, Aug 27, 2008 at 11:15 AM, Jonatan Liljedahl wrote: >> F?bio Mierlo wrote: >>> I was think in something like that, but a little different. >>> >>> One file called /S/S/BootScripts/Tasks, where InstallPackage can >>> "grep" for the task name and if isn't in there InstallPackage will >>> "echo #$TaskName >> /S/S/BooScripts". >>> >>> So, the user can "uncomment" the task they want, then BootUp will >>> start the uncommented tasks and Shutdown will "inversely" stop >>> these tasks. >> Or, let it be a directory with symlinks to the actual Tasks. The >> symlinks could be prefixed with numbers to control the order.. > > This is pretty much how /etc/init.d/rc[n].d works.. Yep.. What about using Upstart? It seems interesting. http://upstart.ubuntu.com/index.html -- /Jonatan [ http://kymatica.com ] From pdgiddie at googlemail.com Thu Aug 28 02:57:52 2008 From: pdgiddie at googlemail.com (Paul Gideon Dann) Date: Wed, 27 Aug 2008 15:57:52 +0100 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <48B569F6.9030102@kymatica.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <48B569F6.9030102@kymatica.com> Message-ID: <48B56B70.60804@gmail.com> If I remember correctly, Upstart is a drop-in Sysvinit replacement, with an expanded set of features. I remember reading that it's not at all pretty to work with, because of the backward-compatibility. If GoboLinux's BootScripts is not good enough, it may be worth considering InitNG. I remember being convinced that this was the way to go, but can't remember what I read that made me decide that :) Paul Jonatan Liljedahl wrote: > Lucas C. Villa Real wrote: > >> On Wed, Aug 27, 2008 at 11:15 AM, Jonatan Liljedahl wrote: >> >>> F?bio Mierlo wrote: >>> >>>> I was think in something like that, but a little different. >>>> >>>> One file called /S/S/BootScripts/Tasks, where InstallPackage can >>>> "grep" for the task name and if isn't in there InstallPackage will >>>> "echo #$TaskName >> /S/S/BooScripts". >>>> >>>> So, the user can "uncomment" the task they want, then BootUp will >>>> start the uncommented tasks and Shutdown will "inversely" stop >>>> these tasks. >>>> >>> Or, let it be a directory with symlinks to the actual Tasks. The >>> symlinks could be prefixed with numbers to control the order.. >>> >> This is pretty much how /etc/init.d/rc[n].d works.. >> > > Yep.. > What about using Upstart? It seems interesting. > > http://upstart.ubuntu.com/index.html > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080827/6b7fd8b1/attachment.htm From lijon at kymatica.com Thu Aug 28 04:02:38 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Wed, 27 Aug 2008 18:02:38 +0200 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <48B56B70.60804@gmail.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <48B569F6.9030102@kymatica.com> <48B56B70.60804@gmail.com> Message-ID: <48B57A9E.4080003@kymatica.com> Paul Gideon Dann wrote: > If I remember correctly, Upstart is a drop-in Sysvinit replacement, with > an expanded set of features. I remember reading that it's not at all > pretty to work with, because of the backward-compatibility. > > If GoboLinux's BootScripts is not good enough, it may be worth > considering InitNG. I remember being convinced that this was the way to > go, but can't remember what I read that made me decide that :) BootScripts isn't bad, I was just thinking it might be time to replace that old sysvinit.. :) InitNG seems cool, with the asynchronous starting of processes.. Anyone tried it on Gobo? One could move the Tasks system to initNG ifiles, and while migrating one could use a wrapper, or maybe write a GoboTask plugin for initng? example: service gobotask/HAL { need = system/bootmisc daemon/dbus; script start = StartTask HAL; script stop = StopTask HAL; } One thing I noticed about gobo Tasks is that some takes start/stop arguments and some does not. Doing StopTask Network brings down the interfaces, while StopTask HAL would try to start another copy of hald! -- /Jonatan [ http://kymatica.com ] From geromao at gmail.com Thu Aug 28 04:31:44 2008 From: geromao at gmail.com (=?ISO-8859-1?Q?F=E1bio_Mierlo?=) Date: Wed, 27 Aug 2008 13:31:44 -0300 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> Message-ID: <263e35d10808270931y6bf47495kd9561f63e6d8cfd0@mail.gmail.com> On Wed, Aug 27, 2008 at 11:34 AM, Lucas C. Villa Real wrote: > On Wed, Aug 27, 2008 at 11:15 AM, Jonatan Liljedahl wrote: >> F?bio Mierlo wrote: >>> I was think in something like that, but a little different. >>> >>> One file called /S/S/BootScripts/Tasks, where InstallPackage can >>> "grep" for the task name and if isn't in there InstallPackage will >>> "echo #$TaskName >> /S/S/BooScripts". >>> >>> So, the user can "uncomment" the task they want, then BootUp will >>> start the uncommented tasks and Shutdown will "inversely" stop >>> these tasks. >> >> Or, let it be a directory with symlinks to the actual Tasks. The >> symlinks could be prefixed with numbers to control the order.. > > This is pretty much how /etc/init.d/rc[n].d works.. > Yes, and it is pretty ugly. From geromao at gmail.com Thu Aug 28 04:49:54 2008 From: geromao at gmail.com (=?ISO-8859-1?Q?F=E1bio_Mierlo?=) Date: Wed, 27 Aug 2008 13:49:54 -0300 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <263e35d10808270931y6bf47495kd9561f63e6d8cfd0@mail.gmail.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <263e35d10808270931y6bf47495kd9561f63e6d8cfd0@mail.gmail.com> Message-ID: <263e35d10808270949l635c3abcj497fa7ea1d7b7228@mail.gmail.com> On Wed, Aug 27, 2008 at 1:31 PM, F?bio Mierlo wrote: > On Wed, Aug 27, 2008 at 11:34 AM, Lucas C. Villa Real > wrote: >> On Wed, Aug 27, 2008 at 11:15 AM, Jonatan Liljedahl wrote: >>> Or, let it be a directory with symlinks to the actual Tasks. The >>> symlinks could be prefixed with numbers to control the order.. >> >> This is pretty much how /etc/init.d/rc[n].d works.. >> > > Yes, and it is pretty ugly. > > From the user views, what's more simple than a commented text > file where you can order and choose what task you want to start > at boot time. > > It is just BootUp anda Shutdown made simple. > We can simply support both and others! Those interested only have to send the patches ;-) From andi5.py at gmx.net Thu Aug 28 08:56:04 2008 From: andi5.py at gmx.net (Andreas =?ISO-8859-1?Q?K=F6hler?=) Date: Wed, 27 Aug 2008 22:56:04 +0200 Subject: [gobolinux-devel] Case-insensitive tab completion in bash Message-ID: <1219870564.4206.6.camel@localhost.localdomain> Hi, please consider the attached patch to current Scripts svn which adds a trivial line to Settings/inputrc to enable case-insensitive tab completion in bash. Actually, I wonder why this has not been done yet. Probably I am missing some design decision :-) Ciao, -- andi5 -------------- next part -------------- A non-text attachment was scrubbed... Name: inputrc.patch Type: text/x-patch Size: 300 bytes Desc: not available Url : http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080827/7d7e5749/attachment.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080827/7d7e5749/attachment.pgp From geromao at gmail.com Thu Aug 28 09:49:47 2008 From: geromao at gmail.com (=?ISO-8859-1?Q?F=E1bio_Mierlo?=) Date: Wed, 27 Aug 2008 18:49:47 -0300 Subject: [gobolinux-devel] Case-insensitive tab completion in bash In-Reply-To: <1219870564.4206.6.camel@localhost.localdomain> References: <1219870564.4206.6.camel@localhost.localdomain> Message-ID: <263e35d10808271449l1b06fff0h8943715605e9ac1e@mail.gmail.com> Thanks for the patch, I think the answer is: "Zsh doesn't read /etc/inputrc, which tells the shell what commands sent by the terminal emulator mean." [1] and because the Zsh is the default shell in GoboLinux. 1. wiki.archlinux.org/index.php/Zsh On Wed, Aug 27, 2008 at 5:56 PM, Andreas K?hler wrote: > Hi, > > please consider the attached patch to current Scripts svn which adds a > trivial line to Settings/inputrc to enable case-insensitive tab > completion in bash. > > Actually, I wonder why this has not been done yet. Probably I am > missing some design decision :-) > > Ciao, > -- andi5 > > > _______________________________________________ > gobolinux-devel mailing list > gobolinux-devel at lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel > > From thomas.heller1 at gmx.de Fri Aug 29 03:31:07 2008 From: thomas.heller1 at gmx.de (Thomas Heller) Date: Thu, 28 Aug 2008 17:31:07 +0200 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <263e35d10808270949l635c3abcj497fa7ea1d7b7228@mail.gmail.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <263e35d10808270931y6bf47495kd9561f63e6d8cfd0@mail.gmail.com> <263e35d10808270949l635c3abcj497fa7ea1d7b7228@mail.gmail.com> Message-ID: <978d66bd0808280831n4a8e4fafw6f4217262a0f38cb@mail.gmail.com> On Wed, Aug 27, 2008 at 6:49 PM, F?bio Mierlo wrote: > On Wed, Aug 27, 2008 at 1:31 PM, F?bio Mierlo wrote: > > On Wed, Aug 27, 2008 at 11:34 AM, Lucas C. Villa Real > > wrote: > >> On Wed, Aug 27, 2008 at 11:15 AM, Jonatan Liljedahl > wrote: > >>> Or, let it be a directory with symlinks to the actual Tasks. The > >>> symlinks could be prefixed with numbers to control the order.. > >> > >> This is pretty much how /etc/init.d/rc[n].d works.. > >> > > > > Yes, and it is pretty ugly. > > > > From the user views, what's more simple than a commented text > > file where you can order and choose what task you want to start > > at boot time. > > > > It is just BootUp anda Shutdown made simple. > > > > We can simply support both and others! > > Those interested only have to send the patches ;-) I first was thinking about making BootUp and Shutdown simpler ;) I agree that the old sysv init is pretty ugly and very obscure ... perhaps someone should really look into initNG and/or upstart. Why invent the wheel twice ;) > > _______________________________________________ > gobolinux-devel mailing list > gobolinux-devel at lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080828/2315ee19/attachment.htm From lijon at kymatica.com Fri Aug 29 09:17:54 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Thu, 28 Aug 2008 23:17:54 +0200 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <978d66bd0808280831n4a8e4fafw6f4217262a0f38cb@mail.gmail.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <263e35d10808270931y6bf47495kd9561f63e6d8cfd0@mail.gmail.com> <263e35d10808270949l635c3abcj497fa7ea1d7b7228@mail.gmail.com> <978d66bd0808280831n4a8e4fafw6f4217262a0f38cb@mail.gmail.com> Message-ID: <48B71602.7090104@kymatica.com> Thomas Heller wrote: > On Wed, Aug 27, 2008 at 6:49 PM, F?bio Mierlo wrote: > >> On Wed, Aug 27, 2008 at 1:31 PM, F?bio Mierlo wrote: >>> On Wed, Aug 27, 2008 at 11:34 AM, Lucas C. Villa Real >>> wrote: >>>> On Wed, Aug 27, 2008 at 11:15 AM, Jonatan Liljedahl >> wrote: >>>>> Or, let it be a directory with symlinks to the actual Tasks. The >>>>> symlinks could be prefixed with numbers to control the order.. >>>> This is pretty much how /etc/init.d/rc[n].d works.. >>>> >>> Yes, and it is pretty ugly. >>> >>> From the user views, what's more simple than a commented text >>> file where you can order and choose what task you want to start >>> at boot time. >>> >>> It is just BootUp anda Shutdown made simple. >>> >> We can simply support both and others! >> >> Those interested only have to send the patches ;-) > > > I first was thinking about making BootUp and Shutdown simpler ;) > I agree that the old sysv init is pretty ugly and very obscure ... > > perhaps someone should really look into initNG and/or upstart. > Why invent the wheel twice ;) Here's another one: http://einit.jyujin.de/ -- /Jonatan [ http://kymatica.com ] From carlo at calica.com Fri Aug 29 12:03:38 2008 From: carlo at calica.com (Carlo Calica) Date: Thu, 28 Aug 2008 17:03:38 -0700 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <48B57A9E.4080003@kymatica.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <48B569F6.9030102@kymatica.com> <48B56B70.60804@gmail.com> <48B57A9E.4080003@kymatica.com> Message-ID: On Wed, Aug 27, 2008 at 9:02 AM, Jonatan Liljedahl wrote: > > One thing I noticed about gobo Tasks is that some takes start/stop > arguments and some does not. Doing StopTask Network brings down the > interfaces, while StopTask HAL would try to start another copy of hald! > Yes, our Tasks are a mess. I have a simple #! wrapper that handles the arg processing and calls start()/stop() hooks as required. There are restart() and reload() hooks as well but if they don't exist the wrapper just calls the stop() and start() hooks in order. I haven't had time to benchmark a boot using the wrapper to see if there's a slowdown. The goal is to make Tasks similar to recipes. Metadata could be added as vars and more hooks defined as needed. Some form a dependency handling is worthwhile. See [1] for a "need" based approach. Hopefully, the wrapper could abstract away the differences between basic init, advanced features of Upstart, InitNG. That leaves HOW tasks are selected for boot. I think this should outside the Task files themselves. With dependency handling, this could be an array in BootOptions, but I don't really like that either. [1] http://www.atnf.csiro.au/people/rgooch/linux/boot-scripts/ -- Carlo J. Calica From carlo at calica.com Fri Aug 29 16:41:06 2008 From: carlo at calica.com (Carlo Calica) Date: Thu, 28 Aug 2008 21:41:06 -0700 Subject: [gobolinux-devel] gobo on Eee PC? In-Reply-To: <48B49987.7090703@kymatica.com> References: <488FAAF3.1000603@kymatica.com> <48907CC7.9080901@kymatica.com> <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> <48B49987.7090703@kymatica.com> Message-ID: On Tue, Aug 26, 2008 at 5:02 PM, Jonatan Liljedahl wrote: >> Carlo made an announcement of a LiveFlash edition created especially >> for his EEE pc, righ after the release of 014: >> >> http://lists.gobolinux.org/pipermail/gobolinux-devel/2008-January/003113.html >> >> He might have improved that edition since then, though. Carlo, do you >> have any unpublished changes for LiveFlash since that announcement? > Not really. I was too lazy to but the kernel pieces together. But now there is a Linux-EeePC recipe. > When copying contents from ISO to flash, it should be cp -r > /Mount/CD-ROM/* instead of /Mount/CD-ROM, right? otherwise the single > CD-ROM directory is copied to the root of the flash.. > Yes > The instructions doesn't mention if the flash partition should be made > bootable with fdisk, I guess it should? > > Anyhow, when I try this my Eee says "invalid or damaged bootable partition". > > Is it possible that this doesn't work on all usb flashsticks? > This can be tricky. It depends on how the usb stick is partitioned. The 014.01 was tested on a flash that was partitioned as a normal disk. Early august got a report that it didn't work on a stick partitioned as a superfloppy (no partition table, single block device at sdX). Needed to update initrd, new one can be found at [1]. Now, your error implies it can't find syslinux. Are you sure you ran syslinux on the right block device. could you show the correct line from /proc/mounts when the stick is mounted. Maybe the output from fdisk as well. Also, which model EeePC? > BTW, Would it be hard to replace the kernel on the livecd/flash with the > original asus-xandros-Eee one? There's also this one that might be > interesting: http://www.array.org/ubuntu/index.html > I think most of the needed patches are available somewhere. > I'm really interested in creating a GobeeeLinux for the Eee where > everything works out of the box. :) I've just set up a lightweight > rox-filer + icewm desktop, with super-simple automounting using only > udev and some shellscripts, etc.. > Very interesting. This is motivation I desperately need. [1] http://www.calica.com/gobolinux/iso/initrd -- Carlo J. Calica From lijon at kymatica.com Fri Aug 29 17:37:59 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Fri, 29 Aug 2008 07:37:59 +0200 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <48B569F6.9030102@kymatica.com> <48B56B70.60804@gmail.com> <48B57A9E.4080003@kymatica.com> Message-ID: <48B78B37.1000009@kymatica.com> Carlo Calica wrote: > On Wed, Aug 27, 2008 at 9:02 AM, Jonatan Liljedahl wrote: >> One thing I noticed about gobo Tasks is that some takes start/stop >> arguments and some does not. Doing StopTask Network brings down the >> interfaces, while StopTask HAL would try to start another copy of hald! >> > > Yes, our Tasks are a mess. I have a simple #! wrapper that handles > the arg processing and calls start()/stop() hooks as required. There > are restart() and reload() hooks as well but if they don't exist the > wrapper just calls the stop() and start() hooks in order. I haven't > had time to benchmark a boot using the wrapper to see if there's a > slowdown. > > The goal is to make Tasks similar to recipes. Metadata could be added > as vars and more hooks defined as needed. Some form a dependency > handling is worthwhile. See [1] for a "need" based approach. > Hopefully, the wrapper could abstract away the differences between > basic init, advanced features of Upstart, InitNG. > > That leaves HOW tasks are selected for boot. I think this should > outside the Task files themselves. With dependency handling, this > could be an array in BootOptions, but I don't really like that either. I'd like a /S/S/BootTasks file with one task per line, with # comments.. -- /Jonatan [ http://kymatica.com ] From lijon at kymatica.com Fri Aug 29 17:55:02 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Fri, 29 Aug 2008 07:55:02 +0200 Subject: [gobolinux-devel] gobo on Eee PC? In-Reply-To: References: <488FAAF3.1000603@kymatica.com> <48907CC7.9080901@kymatica.com> <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> <48B49987.7090703@kymatica.com> Message-ID: <48B78F36.9020807@kymatica.com> Carlo Calica wrote: > On Tue, Aug 26, 2008 at 5:02 PM, Jonatan Liljedahl wrote: >>> Carlo made an announcement of a LiveFlash edition created especially >>> for his EEE pc, righ after the release of 014: >>> >>> http://lists.gobolinux.org/pipermail/gobolinux-devel/2008-January/003113.html >>> >>> He might have improved that edition since then, though. Carlo, do you >>> have any unpublished changes for LiveFlash since that announcement? > > Not really. I was too lazy to but the kernel pieces together. But > now there is a Linux-EeePC recipe. Where? >> The instructions doesn't mention if the flash partition should be made >> bootable with fdisk, I guess it should? >> >> Anyhow, when I try this my Eee says "invalid or damaged bootable partition". >> >> Is it possible that this doesn't work on all usb flashsticks? >> > This can be tricky. It depends on how the usb stick is partitioned. > The 014.01 was tested on a flash that was partitioned as a normal > disk. Early august got a report that it didn't work on a stick > partitioned as a superfloppy (no partition table, single block device > at sdX). Needed to update initrd, new one can be found at [1]. I'll try the new initrd. > Now, your error implies it can't find syslinux. Are you sure you ran > syslinux on the right block device. could you show the correct line > from /proc/mounts when the stick is mounted. Maybe the output from > fdisk as well. Also, which model EeePC? Yes, it's the corrent device. fdisk says: Disk /dev/sdb: 1028 MB, 1028653056 bytes 16 heads, 32 sectors/track, 3924 cylinders Units = cylinders of 512 * 512 = 262144 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 3924 1004528 b W95 FAT32 /proc/mounts says: /System/Kernel/Devices/sdb1 /Mount/Media/USB\040DISK vfat rw,nosuid,nodev,uid=1002,gid=100,fmask=0077,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,quiet 0 0 should the device be mounted when running syslinux? It's an EeePC 900. -- /Jonatan [ http://kymatica.com ] From thomas.heller1 at gmx.de Fri Aug 29 21:02:48 2008 From: thomas.heller1 at gmx.de (Thomas Heller) Date: Fri, 29 Aug 2008 11:02:48 +0200 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <48B78B37.1000009@kymatica.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <48B569F6.9030102@kymatica.com> <48B56B70.60804@gmail.com> <48B57A9E.4080003@kymatica.com> <48B78B37.1000009@kymatica.com> Message-ID: <978d66bd0808290202l303da0f7g375f80f6a48749ac@mail.gmail.com> On Fri, Aug 29, 2008 at 7:37 AM, Jonatan Liljedahl wrote: > Carlo Calica wrote: > > On Wed, Aug 27, 2008 at 9:02 AM, Jonatan Liljedahl > wrote: > >> One thing I noticed about gobo Tasks is that some takes start/stop > >> arguments and some does not. Doing StopTask Network brings down the > >> interfaces, while StopTask HAL would try to start another copy of hald! > >> > > > > Yes, our Tasks are a mess. I have a simple #! wrapper that handles > > the arg processing and calls start()/stop() hooks as required. There > > are restart() and reload() hooks as well but if they don't exist the > > wrapper just calls the stop() and start() hooks in order. I haven't > > had time to benchmark a boot using the wrapper to see if there's a > > slowdown. > > > > The goal is to make Tasks similar to recipes. Metadata could be added > > as vars and more hooks defined as needed. Some form a dependency > > handling is worthwhile. See [1] for a "need" based approach. > > Hopefully, the wrapper could abstract away the differences between > > basic init, advanced features of Upstart, InitNG. > > > > That leaves HOW tasks are selected for boot. I think this should > > outside the Task files themselves. With dependency handling, this > > could be an array in BootOptions, but I don't really like that either. > > I'd like a /S/S/BootTasks file with one task per line, with # comments.. > I kind of like the idea with that file too. I will certainly look into the init projects (upstart, initNG, eInit). Lets see if I can provide a patch, or new way of doing stuff, which you all like ;) > > -- > /Jonatan [ http://kymatica.com ] > _______________________________________________ > gobolinux-devel mailing list > gobolinux-devel at lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080829/16a6f367/attachment.htm From lijon at kymatica.com Sat Aug 30 04:03:26 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Fri, 29 Aug 2008 18:03:26 +0200 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <978d66bd0808290202l303da0f7g375f80f6a48749ac@mail.gmail.com> References: <200808221816.27288.thomas.heller1@gmx.de> <263e35d10808221003m46898661o8b578e219edfc33d@mail.gmail.com> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <48B569F6.9030102@kymatica.com> <48B56B70.60804@gmail.com> <48B57A9E.4080003@kymatica.com> <48B78B37.1000009@kymatica.com> <978d66bd0808290202l303da0f7g375f80f6a48749ac@mail.gmail.com> Message-ID: <48B81DCE.60107@kymatica.com> Thomas Heller wrote: > On Fri, Aug 29, 2008 at 7:37 AM, Jonatan Liljedahl wrote: > >> Carlo Calica wrote: >>> On Wed, Aug 27, 2008 at 9:02 AM, Jonatan Liljedahl >> wrote: >>>> One thing I noticed about gobo Tasks is that some takes start/stop >>>> arguments and some does not. Doing StopTask Network brings down the >>>> interfaces, while StopTask HAL would try to start another copy of hald! >>>> >>> Yes, our Tasks are a mess. I have a simple #! wrapper that handles >>> the arg processing and calls start()/stop() hooks as required. There >>> are restart() and reload() hooks as well but if they don't exist the >>> wrapper just calls the stop() and start() hooks in order. I haven't >>> had time to benchmark a boot using the wrapper to see if there's a >>> slowdown. >>> >>> The goal is to make Tasks similar to recipes. Metadata could be added >>> as vars and more hooks defined as needed. Some form a dependency >>> handling is worthwhile. See [1] for a "need" based approach. >>> Hopefully, the wrapper could abstract away the differences between >>> basic init, advanced features of Upstart, InitNG. >>> >>> That leaves HOW tasks are selected for boot. I think this should >>> outside the Task files themselves. With dependency handling, this >>> could be an array in BootOptions, but I don't really like that either. >> I'd like a /S/S/BootTasks file with one task per line, with # comments.. >> > > I kind of like the idea with that file too. > I will certainly look into the init projects (upstart, initNG, eInit). > Lets see if I can provide a patch, or new way of doing stuff, which you all > like ;) If InitNG proves to be the way to go, I'd suggest using initng ifiles instead of gobo Tasks, thus deprecating Tasks. If/when more and more distros move to initng it will make installation of services/daemons more easy (no need to write Task files, if there already is an ifile). -- /Jonatan [ http://kymatica.com ] From carlo at calica.com Sat Aug 30 06:00:31 2008 From: carlo at calica.com (Carlo Calica) Date: Fri, 29 Aug 2008 11:00:31 -0700 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: <48B81DCE.60107@kymatica.com> References: <200808221816.27288.thomas.heller1@gmx.de> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <48B569F6.9030102@kymatica.com> <48B56B70.60804@gmail.com> <48B57A9E.4080003@kymatica.com> <48B78B37.1000009@kymatica.com> <978d66bd0808290202l303da0f7g375f80f6a48749ac@mail.gmail.com> <48B81DCE.60107@kymatica.com> Message-ID: On Fri, Aug 29, 2008 at 9:03 AM, Jonatan Liljedahl wrote: > Thomas Heller wrote: >>> I'd like a /S/S/BootTasks file with one task per line, with # comments.. >>> >> >> I kind of like the idea with that file too. >> I will certainly look into the init projects (upstart, initNG, eInit). >> Lets see if I can provide a patch, or new way of doing stuff, which you all >> like ;) > > If InitNG proves to be the way to go, I'd suggest using initng ifiles > instead of gobo Tasks, thus deprecating Tasks. If/when more and more > distros move to initng it will make installation of services/daemons > more easy (no need to write Task files, if there already is an ifile). > I'm only concerned with a repeat of Runit and Daemon. Even with strong benefits, the added complexity killed them. That said, ifiles are pretty simple. -- Carlo J. Calica From carlo at calica.com Sat Aug 30 06:08:06 2008 From: carlo at calica.com (Carlo Calica) Date: Fri, 29 Aug 2008 11:08:06 -0700 Subject: [gobolinux-devel] gobo on Eee PC? In-Reply-To: <48B78F36.9020807@kymatica.com> References: <488FAAF3.1000603@kymatica.com> <48907CC7.9080901@kymatica.com> <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> <48B49987.7090703@kymatica.com> <48B78F36.9020807@kymatica.com> Message-ID: On Thu, Aug 28, 2008 at 10:55 PM, Jonatan Liljedahl wrote: > Carlo Calica wrote: >> On Tue, Aug 26, 2008 at 5:02 PM, Jonatan Liljedahl wrote: >>>> Carlo made an announcement of a LiveFlash edition created especially >>>> for his EEE pc, righ after the release of 014: >>>> >>>> http://lists.gobolinux.org/pipermail/gobolinux-devel/2008-January/003113.html >>>> >>>> He might have improved that edition since then, though. Carlo, do you >>>> have any unpublished changes for LiveFlash since that announcement? >> >> Not really. I was too lazy to but the kernel pieces together. But >> now there is a Linux-EeePC recipe. > > Where? > Look at: http://recipes.gobolinux.org/review/ >> Now, your error implies it can't find syslinux. Are you sure you ran >> syslinux on the right block device. could you show the correct line >> from /proc/mounts when the stick is mounted. Maybe the output from >> fdisk as well. Also, which model EeePC? > > Yes, it's the corrent device. fdisk says: > > Disk /dev/sdb: 1028 MB, 1028653056 bytes > 16 heads, 32 sectors/track, 3924 cylinders > Units = cylinders of 512 * 512 = 262144 bytes > > Device Boot Start End Blocks Id System > /dev/sdb1 * 1 3924 1004528 b W95 FAT32 > > /proc/mounts says: > /System/Kernel/Devices/sdb1 /Mount/Media/USB\040DISK vfat > rw,nosuid,nodev,uid=1002,gid=100,fmask=0077,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,quiet > 0 0 > > should the device be mounted when running syslinux? > > It's an EeePC 900. > Hmmm. Only guess I have if the partition is setup wierd. Maybe wipe the MBR with dd and /dev/zero and repartition/format. There is also a utility for Windows by HP that can help partition/format the stick for you. Search "usb boot freedos" and you should be able to find it. Will the stick boot on another machine. -- Carlo J. Calica From lijon at kymatica.com Sun Aug 31 02:50:01 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Sat, 30 Aug 2008 16:50:01 +0200 Subject: [gobolinux-devel] Boot sequence enhancement In-Reply-To: References: <200808221816.27288.thomas.heller1@gmx.de> <48B56170.4060007@kymatica.com> <2c03f9590808270734k35552535ne2129c430c910018@mail.gmail.com> <48B569F6.9030102@kymatica.com> <48B56B70.60804@gmail.com> <48B57A9E.4080003@kymatica.com> <48B78B37.1000009@kymatica.com> <978d66bd0808290202l303da0f7g375f80f6a48749ac@mail.gmail.com> <48B81DCE.60107@kymatica.com> Message-ID: <48B95E19.108@kymatica.com> Carlo Calica wrote: > On Fri, Aug 29, 2008 at 9:03 AM, Jonatan Liljedahl wrote: >> Thomas Heller wrote: >>>> I'd like a /S/S/BootTasks file with one task per line, with # comments.. >>>> >>> I kind of like the idea with that file too. >>> I will certainly look into the init projects (upstart, initNG, eInit). >>> Lets see if I can provide a patch, or new way of doing stuff, which you all >>> like ;) >> If InitNG proves to be the way to go, I'd suggest using initng ifiles >> instead of gobo Tasks, thus deprecating Tasks. If/when more and more >> distros move to initng it will make installation of services/daemons >> more easy (no need to write Task files, if there already is an ifile). >> > > I'm only concerned with a repeat of Runit and Daemon. Even with > strong benefits, the added complexity killed them. That said, ifiles > are pretty simple. Yes, they are pretty simple. And there's already iifiles for almost everything you need. Gobo-specific stuff could go in a separate ifile, and there could be a default service running last that just executes a /S/S/LocalBoot or something where users could put stuff if they don't want or know how to create an ifile for it. -- /Jonatan [ http://kymatica.com ] From lijon at kymatica.com Sun Aug 31 03:02:30 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Sat, 30 Aug 2008 17:02:30 +0200 Subject: [gobolinux-devel] gobo on Eee PC? In-Reply-To: References: <488FAAF3.1000603@kymatica.com> <48907CC7.9080901@kymatica.com> <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> <48B49987.7090703@kymatica.com> <48B78F36.9020807@kymatica.com> Message-ID: <48B96106.8050809@kymatica.com> Carlo Calica wrote: > On Thu, Aug 28, 2008 at 10:55 PM, Jonatan Liljedahl wrote: ... >>> Now, your error implies it can't find syslinux. Are you sure you ran >>> syslinux on the right block device. could you show the correct line >>> from /proc/mounts when the stick is mounted. Maybe the output from >>> fdisk as well. Also, which model EeePC? >> Yes, it's the corrent device. fdisk says: >> >> Disk /dev/sdb: 1028 MB, 1028653056 bytes >> 16 heads, 32 sectors/track, 3924 cylinders >> Units = cylinders of 512 * 512 = 262144 bytes >> >> Device Boot Start End Blocks Id System >> /dev/sdb1 * 1 3924 1004528 b W95 FAT32 >> >> /proc/mounts says: >> /System/Kernel/Devices/sdb1 /Mount/Media/USB\040DISK vfat >> rw,nosuid,nodev,uid=1002,gid=100,fmask=0077,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,quiet >> 0 0 >> >> should the device be mounted when running syslinux? >> >> It's an EeePC 900. >> > > Hmmm. Only guess I have if the partition is setup wierd. Maybe wipe > the MBR with dd and /dev/zero and repartition/format. There is also a > utility for Windows by HP that can help partition/format the stick for > you. Search "usb boot freedos" and you should be able to find it. I've now wiped the MBR and repartitioned and formatted the stick. the goboflash.zip contains an isolinux dir with an initrd (which I think you have updated with http://www.calica.com/gobolinux/iso/initrd?), should I replace the initrd from the live CD with this? (the goboflash instructions didn't mention it) > Will the stick boot on another machine. Haven't tried that. -- /Jonatan [ http://kymatica.com ] From andi5.py at gmx.net Sun Aug 31 03:02:02 2008 From: andi5.py at gmx.net (Andreas =?ISO-8859-1?Q?K=F6hler?=) Date: Sat, 30 Aug 2008 17:02:02 +0200 Subject: [gobolinux-devel] Case-insensitive tab completion in bash In-Reply-To: <263e35d10808271449l1b06fff0h8943715605e9ac1e@mail.gmail.com> References: <1219870564.4206.6.camel@localhost.localdomain> <263e35d10808271449l1b06fff0h8943715605e9ac1e@mail.gmail.com> Message-ID: <1220108522.3639.2.camel@localhost.localdomain> Hi F?bio, actually, I think that would be a rather obscure answer, given that if gobolinux only cared about zsh, there would be no reason to include an inputrc file in the Scripts package at all. So, I still ask for the inclusion of my patch :-) Ciao, -- andi5 On Wed, 2008-08-27 at 18:49 -0300, F?bio Mierlo wrote: > Thanks for the patch, I think the answer is: > > "Zsh doesn't read /etc/inputrc, which tells the shell what commands > sent by the terminal emulator mean." [1] > > and because the Zsh is the default shell in GoboLinux. > > 1. wiki.archlinux.org/index.php/Zsh > > On Wed, Aug 27, 2008 at 5:56 PM, Andreas K?hler wrote: > > Hi, > > > > please consider the attached patch to current Scripts svn which adds a > > trivial line to Settings/inputrc to enable case-insensitive tab > > completion in bash. > > > > Actually, I wonder why this has not been done yet. Probably I am > > missing some design decision :-) > > > > Ciao, > > -- andi5 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.gobolinux.org/pipermail/gobolinux-devel/attachments/20080830/cf11caae/attachment.pgp From lijon at kymatica.com Sun Aug 31 03:28:46 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Sat, 30 Aug 2008 17:28:46 +0200 Subject: [gobolinux-devel] gobo on Eee PC? In-Reply-To: References: <488FAAF3.1000603@kymatica.com> <48907CC7.9080901@kymatica.com> <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> <48B49987.7090703@kymatica.com> <48B78F36.9020807@kymatica.com> Message-ID: <48B9672E.1040503@kymatica.com> Carlo Calica wrote: .. >>> Not really. I was too lazy to but the kernel pieces together. But >>> now there is a Linux-EeePC recipe. >> Where? >> > > Look at: http://recipes.gobolinux.org/review/ What's the easiest way to build this kernel on my desktop machine and installing it on my Eee? -- /Jonatan [ http://kymatica.com ] From lijon at kymatica.com Sun Aug 31 03:38:32 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Sat, 30 Aug 2008 17:38:32 +0200 Subject: [gobolinux-devel] gobo on Eee PC? In-Reply-To: References: <488FAAF3.1000603@kymatica.com> <48907CC7.9080901@kymatica.com> <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> <48B49987.7090703@kymatica.com> <48B78F36.9020807@kymatica.com> Message-ID: <48B96978.3070403@kymatica.com> Carlo Calica wrote: ... > Hmmm. Only guess I have if the partition is setup wierd. Maybe wipe > the MBR with dd and /dev/zero and repartition/format. There is also a > utility for Windows by HP that can help partition/format the stick for > you. Search "usb boot freedos" and you should be able to find it. > > Will the stick boot on another machine. No, it did not boot on another machine.. -- /Jonatan [ http://kymatica.com ] From lijon at kymatica.com Sun Aug 31 03:49:02 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Sat, 30 Aug 2008 17:49:02 +0200 Subject: [gobolinux-devel] gobo on Eee PC? In-Reply-To: <48B96978.3070403@kymatica.com> References: <488FAAF3.1000603@kymatica.com> <48907CC7.9080901@kymatica.com> <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> <48B49987.7090703@kymatica.com> <48B78F36.9020807@kymatica.com> <48B96978.3070403@kymatica.com> Message-ID: <48B96BEE.1000009@kymatica.com> Jonatan Liljedahl wrote: > Carlo Calica wrote: > ... >> Hmmm. Only guess I have if the partition is setup wierd. Maybe wipe >> the MBR with dd and /dev/zero and repartition/format. There is also a >> utility for Windows by HP that can help partition/format the stick for >> you. Search "usb boot freedos" and you should be able to find it. >> >> Will the stick boot on another machine. > > No, it did not boot on another machine.. Also tried with another stick of different brand, same thing. It just gives me a black screen, syslinux doesn't load. -- /Jonatan [ http://kymatica.com ] From lucasvr at gobolinux.org Sun Aug 31 04:02:33 2008 From: lucasvr at gobolinux.org (Lucas C. Villa Real) Date: Sat, 30 Aug 2008 13:02:33 -0300 Subject: [gobolinux-devel] Case-insensitive tab completion in bash In-Reply-To: <1220108522.3639.2.camel@localhost.localdomain> References: <1219870564.4206.6.camel@localhost.localdomain> <263e35d10808271449l1b06fff0h8943715605e9ac1e@mail.gmail.com> <1220108522.3639.2.camel@localhost.localdomain> Message-ID: <2c03f9590808300902n51a337edic47bbb31279db39f@mail.gmail.com> On Sat, Aug 30, 2008 at 12:02 PM, Andreas K?hler wrote: > Hi F?bio, > > actually, I think that would be a rather obscure answer, given that if > gobolinux only cared about zsh, there would be no reason to include an > inputrc file in the Scripts package at all. > > So, I still ask for the inclusion of my patch :-) I've just tested in my environment and it worked like a charm. Checked in, thanks! -- Lucas powered by /dev/dsp From lijon at kymatica.com Sun Aug 31 05:24:58 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Sat, 30 Aug 2008 19:24:58 +0200 Subject: [gobolinux-devel] installing to USB stick? Message-ID: <48B9826A.3030500@kymatica.com> I'm trying to install GoboLinux onto a USB stick (not LiveCD on USB, but a real install). The installation goes fine, but the system kernel panics at boot. It complains that it can't mount the root fs. Right after that the console outputs info about found usb device. May it be that usb-storage is a module so that the rootfs on the stick can't be accessed before the module has loaded (which of course is impossible since it's on the rootfs)? (in case I need to replace the kernel) -- /Jonatan [ http://kymatica.com ] From lijon at kymatica.com Sun Aug 31 08:33:39 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Sat, 30 Aug 2008 22:33:39 +0200 Subject: [gobolinux-devel] installing to USB stick? In-Reply-To: <48B9826A.3030500@kymatica.com> References: <48B9826A.3030500@kymatica.com> Message-ID: <48B9AEA3.7050509@kymatica.com> Jonatan Liljedahl wrote: > I'm trying to install GoboLinux onto a USB stick (not LiveCD on USB, but > a real install). The installation goes fine, but the system kernel > panics at boot. > It complains that it can't mount the root fs. Right after that the > console outputs info about found usb device. May it be that usb-storage > is a module so that the rootfs on the stick can't be accessed before the > module has loaded (which of course is impossible since it's on the > rootfs)? (in case I need to replace the kernel) It seems usb-storage and stuff is already compiled in. But google tells me the problem is the delay before detection of usb stick, and that one needs to use an initrd. Just for testing, I created an initramfs with an /init script like this: #!/bin/sh echo "Starting initramfs /init script..." /bin/busybox sh and in GRUB I say: title GoboLinux - Graphic Desktop root (hd0,0) kernel /System/Kernel/Boot/kernel root=/dev/sdb1 vt.default_utf8=0 vga=0 Boot=Graphic initrd /boot/initramfs.img the initramfs is packed with find . | cpio -o -c | gzip -9 > ~/initramfs.img At boot, the initrd is detected and the kernel starts booting, but then it panics at "no file system could mount root". Since the point with initrd is that the kernel should *not* mount the root fs, I guess it's referring to the initramfs image?? Any ideas? -- /Jonatan [ http://kymatica.com ] From lijon at kymatica.com Sun Aug 31 10:06:43 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Sun, 31 Aug 2008 00:06:43 +0200 Subject: [gobolinux-devel] installing to USB stick? [SOLVED] In-Reply-To: <48B9AEA3.7050509@kymatica.com> References: <48B9826A.3030500@kymatica.com> <48B9AEA3.7050509@kymatica.com> Message-ID: <48B9C473.2060509@kymatica.com> Jonatan Liljedahl wrote: > Jonatan Liljedahl wrote: >> I'm trying to install GoboLinux onto a USB stick (not LiveCD on USB, but >> a real install). The installation goes fine, but the system kernel >> panics at boot. >> It complains that it can't mount the root fs. Right after that the >> console outputs info about found usb device. May it be that usb-storage >> is a module so that the rootfs on the stick can't be accessed before the >> module has loaded (which of course is impossible since it's on the >> rootfs)? (in case I need to replace the kernel) > > It seems usb-storage and stuff is already compiled in. But google tells > me the problem is the delay before detection of usb stick, and that one > needs to use an initrd. > > Just for testing, I created an initramfs with an /init script like this: > > #!/bin/sh > echo "Starting initramfs /init script..." > /bin/busybox sh > > and in GRUB I say: > > title GoboLinux - Graphic Desktop > root (hd0,0) > kernel /System/Kernel/Boot/kernel root=/dev/sdb1 vt.default_utf8=0 vga=0 > Boot=Graphic > initrd /boot/initramfs.img > > the initramfs is packed with find . | cpio -o -c | gzip -9 > ~/initramfs.img > > At boot, the initrd is detected and the kernel starts booting, but then > it panics at "no file system could mount root". Since the point with > initrd is that the kernel should *not* mount the root fs, I guess it's > referring to the initramfs image?? Any ideas? I tried using old-style cramfs initrd instead of the new cpio initramfs, and now it works. Seems the kernel isn't configured for initramfs... If anyone is interested in an USB bootable "real" install, here's my initrd: http://www.bitminds.net/kymatica/uploads/Main/gobo-usb-initrd The initrd looks for a real_root kernel cmdline option, example grub entry: title GoboLinux - Graphic Desktop root (hd0,0) kernel /System/Kernel/Boot/kernel init=/init ramdisk_size=4096 root=/dev/ram0 real_root=/dev/sdb1 vt.default_utf8=0 vga=0 Boot=Graphic initrd /boot/initrd and grub/device.map: (hd0) /dev/sdb Now I have a real gobo on USB that I can boot on my EeePC while trying to create a nice GoboEee distro. :) -- /Jonatan [ http://kymatica.com ] From lijon at kymatica.com Sun Aug 31 23:14:10 2008 From: lijon at kymatica.com (Jonatan Liljedahl) Date: Sun, 31 Aug 2008 13:14:10 +0200 Subject: [gobolinux-devel] Fontconfig update Message-ID: <48BA7D02.5030400@kymatica.com> I upgraded my Fontconfig to 2.5.91, but the included default settings seems to be invalid: Fontconfig warning: "/Programs/Fontconfig/Settings/fonts/conf.d/80-delicious.conf", line 16: invalid constant used : heavy Fontconfig warning: "/Programs/Fontconfig/Settings/fonts/conf.d/80-delicious.conf", line 17: invalid match target "scan" Fontconfig warning: line 73: unknown element "cachedir" Fontconfig warning: line 74: unknown element "cachedir" Current/Resources/Defaults/Settings/fonts]grep -n cachedir fonts.conf 73: /System/Variable/cache/fontconfig 74: ~/.fontconfig -- /Jonatan [ http://kymatica.com ] From jeremy at visser.name Sun Aug 31 23:28:58 2008 From: jeremy at visser.name (Jeremy Visser) Date: Sun, 31 Aug 2008 21:28:58 +1000 Subject: [gobolinux-devel] gobo on Eee PC? In-Reply-To: <48B96BEE.1000009@kymatica.com> References: <488FAAF3.1000603@kymatica.com> <48907CC7.9080901@kymatica.com> <2c03f9590807300804g4ab8a0c5rd68b2a5ec7810edf@mail.gmail.com> <48B49987.7090703@kymatica.com> <48B78F36.9020807@kymatica.com> <48B96978.3070403@kymatica.com> <48B96BEE.1000009@kymatica.com> Message-ID: <43253ec50808310428s54815c54m139247cc64f25d3c@mail.gmail.com> On Sun, Aug 31, 2008 at 1:49 AM, Jonatan Liljedahl wrote: > Also tried with another stick of different brand, same thing. It just > gives me a black screen, syslinux doesn't load. Are you sure there's an MBR on the drive? syslinux comes with an MBR you can use. On Ubuntu, it's located in /usr/lib/syslinux/mbr.bin. cat /usr/lib/syslinux/mbr.bin > /dev/sdX (NOT sdx1, just sdx) ...which will install the MBR onto your drive. Also, make sure your partition is flagged with 'boot', but looks like you've already done that. If the MBR is working, you should get the three letters "MBR" printed on your screen briefly when it starts booting off the flash drive.