Re: Initial Thoughts, migration from Ubuntu ahead
Michael Homer <[email protected]>
| Newsgroups | gmane.linux.distributions.gobo.general |
|---|---|
| Message-ID | <CAKXQU_GU+G+7M6e+5pj30T9nPks5MLVfzGvZvHOGZzWKARB1DQ@mail.gmail.com> |
On Fri, Jun 7, 2013 at 11:41 AM, Henri Tuhola <[email protected]> wrote: > Are you serious or are you joking? He is serious, but I wouldn't take him too seriously. > I just read the LFS again and realised it can be summarized: > 1. prepare the toolchain and a target file system > 2. compile everything and install into the file system > 3. install boot scripts you need to start it up. > > Therefore I were wrong with the proposal that I'd learn something new > from actually doing the things in LFS. > > It seems to be essentially same for GoboLinux. Just instead of > installing programs into specific places, you install them into the > hierarchy provided by GoboLinux and provide symbolic links into the > /System directory. The /boot seems to sit in /System/Kernel/Boot . > > Also, you already have automatic installer, that I used to install it > into virtualbox at the first time. It is located in > /Programs/Installer. It's even written in my favorite language, which > means I can easily read there how GoboLinux goes to my hard drive. > Apparently no "Gobo From Scratch" is needed here. It's possible that doing it from LFS will help just because everything on the CD is so old - it's a real pain to get an up-to-date system from an 014.01 installation. There are some (probably slightly dated themselves) instructions around for updating things here: <https://gist.github.com/hishamhm/1360997>. The separate repositories are no longer required, but the rest is probably pretty close. I wouldn't be surprised if LFS-with-obvious-changes were easier to manage, but that's really up to you. It is possible to do either way, and you will need to do a lot of exploring on your own however you do it. The Udev issue is real and will be something you have to deal with - in essence, udev has been merged into systemd and is no longer independently maintained, which means either switching to systemd or using one of the forks. > > The current kernel in my virtualbox installation seems to be of > version 2.6.24. On the new versions of gcc etc.. Doesn't GoboLinux > allow multiple installations of gcc, that I can swap? The software > that goes behind.. Couldn't I just tell them to use older versions of > gcc and ld at compiling? You can switch between them at will, but consistently using the newest one will give you the best result. > You were correct with your first post.. Maybe I should just hop into > this new system and really take it my own! If something is missing, > I'd be able of *creating* it anyway. You're also right about the > documentation though. I should document what I am going to do, and > what I've already done. This is good. -Michael