Re: [gobolinux-devel] Fedora to change the filesystem hierarchy.

Further to Lucas C. Villa Real email: 
http://lists.gobolinux.org//pipermail/gobolinux-devel/2011-November/004318.html 
"[gobolinux-devel] Fedora to change the filesystem hierarchy", I just 
came across a recent interesting discussion: 
http://www.osnews.com/comments/25556 "Understanding the /bin, /sbin, 
/usr/bin, /usr/sbin Split".

A comment by Alfman: http://www.osnews.com/thread?505332 "Re: Filesystem 
Hierarchy Standard" caught my attention. I quote:

""You might think Gobo Linux brings order, but you aren't taking into 
account that it carries the 'legacy' structure too, it just hides it."

Of course you are correct, but solving that is a real conundrum. 
Unfortunately one is required to maintain legacy paths whenever 
compatibility is required since the old paths are hard coded in binaries 
and libraries throughout the linux software codebase. The *inability* to 
change them makes the status quo ideologically imperfect, even those who 
don't mind the legacy paths should recognize this.

In my personal distro, I've given it some thought and came up with two 
possible compatibility solutions. Keep in mind, a motivating goal is to 
keep application specific files together so that, as with GoboLinux, 
applications can be installed by untarring a single directory. A list of 
commands can be built using symlinks pointing to their applicaiton 
directories.

Solution A. Remove the dependency upon legacy paths by modifying the 
kernel and/or libc to treat file requests as "named resources" instead 
of absolute file system paths. This mapping could be stored in either a 

Re: Spam Documents.

GoboLinux Knowledge Base is now extensively infected with span documents.
http://wiki.gobolinux.org/index.php?title=Special:AllPages

With reference to previous emails, none of the suggestions made by James 
Browning were implemented.
http://lists.gobolinux.org//pipermail/gobolinux-users/2011-May/008656.html

Since the Forum has been shut down, perhaps similar action should be 
taken protect the valuable source of GoboLinux Knowledge Base.

Closing the forum

Hi,
The forum is very little used, and mostly just a Q&A with me when it is.
Most of the posts we get through are spam these days, which take a bit
of effort to can each time. The original user demand hasn't really
materialised into a regular community on the forum. The gobolinux-users
list will usually be a better and more responsive venue for people, and
I think the presence of the forum is an attractive nuisance more than
anything.

For those reasons, I'm proposing to close the forum down in a couple of
weeks' time. There are good arguments and reasons for having forums, but
I don't think it's something we can support at this point. If there's
viable demand in the future we could set some up again, but right now
directing people to the mailing lists and IRC seems more appropriate.

If anyone objects strongly to this plan, they should make themselves
known and we'll see what we can do, but otherwise I will shut down the
forums soon.

I've also posted this message on the forum itself, since this may not be
the best place to reach the right audience who might care.
-Michael

_______________________________________________
gobolinux-users mailing list
gobolinux-users <at> lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-users

Oh, I forgot...

Although the recipe contains "unionfs patch" - there doesn't seem to
be any such option available while configuring kernel.
--

-- 
Z.

Kernel 3.3 - Gobohide doesn't work

Using the recipe for 3.2.12 I made a compilation of 3.3 - almost all
went fine, with exception of gobohide: during boot-up there are
several messages "ioctl: Operation not supported". Of course, the
"legacy FHS" has not been hidden.
--

-- 
Z.

New Year Greetings GoboLinux Developers and Users.

This website link might be of interest:
http://sandervanderburg.blogspot.com/2011/12/evaluation-and-comparison-of-gobolinux.html
An evaluation and comparison of GoboLinux

I quote: "The only bad thing I can say about GoboLinux is that the 
latest 014.01 release is outdated (2008) and it looks like 015 is in 
progress for almost three years... I'm not sure if there will be a new 
release soon, which is a pity."

Last Autumn I thought a new updated live CD release was imminent (see 
references) but alas not. Perhaps 2012 will be the Year of GoboLinux 015!

References:
(1) 
http://lists.gobolinux.org//pipermail/gobolinux-devel/2011-September/004302.html
(2) 
http://lists.gobolinux.org//pipermail/gobolinux-devel/2011-September/004307.html
(3) 
http://lists.gobolinux.org//pipermail/gobolinux-devel/2011-September/004309.html
(4) 
http://lists.gobolinux.org//pipermail/gobolinux-devel/2011-September/004313.html
(5) 
http://lists.gobolinux.org//pipermail/gobolinux-devel/2011-September/004314.html

(no subject)

_______________________________________________
gobolinux-users mailing list
gobolinux-users <at> lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-users

Grumpy ContributeRecipe

During recipe contribution it's always complaining:

#v+
Checking Dependencies...
<Timeout>

GetAvailable: Timed out downloading
http://kundor.org/gobo/packages/official/MANIFEST.bz2

GetAvailable: Timed out downloading
http://gobo.calica.com/packages/official/MANIFEST.bz2

GetAvailable: Timed out downloading
http://kundor.org/gobo/packages/contrib/MANIFEST.bz2

GetAvailable: Timed out downloading
http://gobo.calica.com/packages/contrib/MANIFEST.bz2

GetAvailable: Timed out downloading http://gobolinux.org/recipe-store

GetAvailable: Timed out downloading http://gobo.calica.com/recipe-store

GetAvailable: Timed out downloading
http://gobolinux.org/version-tracker/TrackedVersions.bz2
<Timeout>

GetAvailable: Timed out downloading
http://kundor.org/gobo/packages/official/MANIFEST.bz2

GetAvailable: Timed out downloading
http://gobo.calica.com/packages/official/MANIFEST.bz2

GetAvailable: Timed out downloading
http://kundor.org/gobo/packages/contrib/MANIFEST.bz2

GetAvailable: Timed out downloading
http://gobo.calica.com/packages/contrib/MANIFEST.bz2

GetAvailable: Timed out downloading http://gobolinux.org/recipe-store

GetAvailable: Timed out downloading http://gobo.calica.com/recipe-store

GetAvailable: Timed out downloading http://gobolinux.org/version-tracker/Tracked
#v-

What are the proper, working addresses - and where to write them?
--

-- 
Z.

Rootless on OS X Lion

After install Xcode, install Homebrew:
https://github.com/mxcl/homebrew/wiki/installation

brew install wget
brew install coreutils --default-names
brew install gnu-sed --default-names
brew install findutils --default-names
export PATH=/usr/local/bin:$PATH

wget http://svn.gobolinux.org/tools/trunk/Scripts/bin/CreateRootlessEnvironment
bash CreateRootlessEnvironment $HOME/GoboLinux
Say yes for the question: Should a StartRootless line be added to
~/.zshrc? [Y/n]

Then add the follow line in the first line of your .zshrc:
export PATH=/usr/local/bin:$PATH

zsh
InstallPackage Compile # Skip All
Compile Mtail

Is possible that I am forgetting some step!

Fabio Mierlo

Variable pointing for source directory

Does there exist any "Program variable", which points to the
directory, where the program is compiled ($source, or the like)? On
the "Recipe format specification" pages I've found $target - which
points to where program is installed - but not the one I'm looking
for.

--

-- 
Z.

Recipes: 64 vs 32 bit

Sometimes there's a need to change somewhat compilation process,
depending on whether the binaries are compiled for 32-bit, or for
64-bit system.

I think, it should be reflected in recipes somehow (a dedicated section?).
--

-- 
Z.