Not signed in (Sign In)

Choose a language

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

Support and General Discussion: Upgrading Gobolinux

Bottom of Page

1 to 13 of 13

  1.  
    • CommentAuthoranyedge
    • CommentTimeDec 3rd 2007
     # 1
    When 014 comes out, will there be a way to upgrade your system from 013--or will you have to do a complete reinstall? Thanks in advance.
    • CommentAuthorMichael
    • CommentTimeDec 3rd 2007 edited
     # 2
    Nothing stops you from just upgrading the packages, there's nothing else special about them.

    [edited: yeah, that was a little terse and unclear]
    • CommentAuthorMohjive
    • CommentTimeDec 3rd 2007
     # 3
    To clarify: the difference between 013 and 014 is packages only. There are no changes beyond that, so upgrading packages is the way.
    • CommentAuthorm@cCo
    • CommentTimeDec 4th 2007
     # 4
    But we won't get the "Welcome to Gobolinux 015" message! :D
    • CommentAuthorMichael
    • CommentTimeDec 4th 2007
     # 5
    It's true, it won't be exactly the same as a fresh install, but the effect on a working system is pretty much the same. You can edit /S/S/GoboLinuxVersion to say whatever you want, too.
  6.  # 6
    Hi everybody,

    attracted by the obviously only Linux (or UNIX?) distro with a usable file system hierarchy I've installed 014 today: All on 1 partition except swap (not off-topic, bear with me). On other Linuxes I use a separate partition for /home. As with most distros an upgrade every second time failes, every second time a fresh install has to be done. A seperate home partition makes this an easy job: Just install the binaries and the config data are still/already there.

    How is this done with GoboLinux? The 2nd partition has been mounted under /Mount/...

    Which directory tree am I supposed to move to that partition? Is it /Users ? Is there any script guiding me in this? Is there any installer option letting me choose that at the very beginning of the install process?

    This way even a fresh GoboLinux install would almost look like a simple upgrade.

    Kind regards
    Thin Myrna
    • CommentAuthorm@cCo
    • CommentTimeJan 3rd 2008 edited
     # 7
    I really don't know how to manage separated partitions' directories in the installer, but yes, the /home folder becomes /Users in gobo, so you can mount your partition by adding a line similar to this in /System/Settings/fstab:

    /System/Kernel/Devices/<your_home_partition> /Users defaults 0 0
    I must admit I don't know what the "0 0" at the and means, but the root partition uses it, so it shouldn't do much harm :P
    • CommentAuthorMohjive
    • CommentTimeJan 3rd 2008 edited
     # 8
    Yes, that's what I use as well. If you had a partition when you installed GoboLinux you have an entry like
    /System/Kernel/Devices/hda2 /Mount/HDA2 defaults 0 0
    where 'hda2' would be you partition. Just change /Mount/HDA2 to /Users. Don't forget to copy the contents over from /Users to /System/Kernel/Devices/hda2 before mounting the partition.
    • CommentAuthorMichael
    • CommentTimeJan 3rd 2008
     # 9
    Posted By: m@cCoI must admit I don't know what the "0 0" at the and means, but the root partition uses it, so it shouldn't do much harm :P
    Since you've already answered the actual question, I'll field this one. The first 0 is a boolean flag for dump/don't dump, which is not so relevant now (I don't even have dump(8) here). The last is a non-negative integer that determines the order fsck looks at the partitions at boot time, so I wouldn't suggest using 0 0 for any filesystem you cared about (unless you're arranging fsck runs some other way). Checks are parallelised over entries with the same value, so 1 for the root and 2 for everything else works for most cases.
    • CommentAuthorm@cCo
    • CommentTimeJan 3rd 2008
     # 10
    Posted By: Michael
    Posted By: m@cCoI must admit I don't know what the "0 0" at the and means, but the root partition uses it, so it shouldn't do much harm :P
    Since you've already answered the actual question, I'll field this one. The first 0 is a boolean flag for dump/don't dump, which is not so relevant now (I don't even have dump(8) here). The last is a non-negative integer that determines the order fsck looks at the partitions at boot time, so I wouldn't suggest using 0 0 for any filesystem you cared about (unless you're arranging fsck runs some other way). Checks are parallelised over entries with the same value, so 1 for the root and 2 for everything else works for most cases.
    Thanks for the reply. But I can't undestand yet, why shouldn't 0 be used? It should indicate that the partition in question is to be checked first, or not? Then the ones with 1, 2, and so on. Or am I wrong?
    • CommentAuthorploxiln
    • CommentTimeJan 4th 2008
     # 11
    The last two columns are used, I think, during the first bootup after a system crash. Thus it would make sense that if you had a small partition with important data, you might want it to be "dumped" somewhere so you could try different methods to recover it after a potentially data-corrupting crash (I think).

    A 0 in the second column means don't fsck (filesystem check) the partition after a crash.

    On another note, you'll notice that ext2/3 will still fsck every 30 reboots or so by default just as a standard feature of that filesystem.
    • CommentAuthorMichael
    • CommentTimeJan 4th 2008
     # 12
    0 in the fsck column (fs_passno, really) means disable, so the ordering starts from one.

    The dump column is for use with dump(8), a backup tool. See man 8 dump for possible details, although I have neither the executable nor the man page installed and you probably don't either. It isn't an ideal way of backing up data in any case, so I wouldn't worry about it.
    • CommentAuthorm@cCo
    • CommentTimeJan 5th 2008
     # 13
    Thanks both for answering :D

1 to 13 of 13

  1.