Why Upgrade? Getting tired...

[ronw]

SteveRiley's post #54 got me curious, so I cloned an existing Saucy VM, and changed /etc/apt/sources.list to all the devel stuff:

deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel main restricted multiverse universe
deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel restricted main multiverse universe 

deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-updates main restricted multiverse universe
deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-updates restricted main multiverse universe 

deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-backports main restricted universe multiverse 
deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-backports main restricted universe multiverse 

deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-security main restricted multiverse universe
deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-security restricted main multiverse universe 

# deb http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-proposed restricted main universe multiverse 
# deb-src http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ devel-proposed restricted main universe multiverse

As you can see, I haven't pulled the trigger on 'proposed' yet.

After an aptitude update I got these warnings:

W: Conflicting distribution: http://mirror.cc.columbia.edu devel Release (expected devel but got saucy)
W: Conflicting distribution: http://mirror.cc.columbia.edu devel-updates Release (expected devel-updates but got saucy)
W: Conflicting distribution: http://mirror.cc.columbia.edu devel-backports Release (expected devel-backports but got saucy)
W: Conflicting distribution: http://mirror.cc.columbia.edu devel-security Release (expected devel-security but got saucy)

But everything seems to be updating fine.

[Snowhog]

They are probably using VirtualBox to run a virtual instances of their system as a guest inside their host system. You could potentially run multiple OS's at the same time depending on your resources. The nice thing is you can do anything to the guest without changing anything on the host.

Here is a fresh install of a raring guest inside my precise host.

Where did you get the wallpaper? I'd like to get it myself.

[life0riley]

Where did you get the wallpaper? I'd like to get it myself.

http://www.crestock.com/uploads/blog...-1920x1200.jpg

[Buddlespit]

Where did you get the wallpaper? I'd like to get it myself.

google nasa earth, then select Images

edit: Or, just use the link provided

[tek_heretik]

They are probably using VirtualBox to run a virtual instances of their system as a guest inside their host system. You could potentially run multiple OS's at the same time depending on your resources. The nice thing is you can do anything to the guest without changing anything on the host.

Yep, got all that, was just wondering if it was possible to 'reboot' a 'virtual OS', that's all, it's all good bro, love that wallpaper too, got me a copy.

Don't know if you can read this light grey whispering, lol, but I play dumb because I'm getting lazy in my old age, shhhhh.

[SteveRiley]

Don't know if you can read this light grey whispering, lol, but I play dumb because I'm getting lazy in my old age, shhhhh.

Sometimes it's difficult for us tell if you're really just playing.

[tek_heretik]

Sometimes it's difficult for us tell if you're really just playing.

Oh, yer baaaaaaaaaad Steve, real bad, lol.

Edit: I think I do alright for somebody with no formal computer related education, you know 'that guy' that can fix anything and answer tech questions in your 'hood, well that's me, and most likely a lot of you, you just get paid money for it, and probably lots of it, so excuse me if I don't remember every single command that passes under my nose.

See that green bar to the left? I pay YOU guys because I'm lazy.

[NickStone]

Nice idea to add the development database to your repository in the hope that you can have a "rolling release" of Kubuntu, but by doing this all you will be doing is rolling on to the next development of Kubuntu. A rolling release distro is one thatt pushes the latest stable version of packages to the end user which is what Arch does. If by adding the development branch all your doing is keeping Kubuntu at the Alpha/Beta stage. It will never be a stable system. Plus you will have issues of breakages and may need to download nightly builds all the time.

It would be a lot of hard work just to have a "rolling release"

[Snowhog]

Well, yesterday, I messed up with my experiment on my Toshiba to get 13.10 as a 'rolling release'. Long story short, I managed to remove most of the system. Didn't intend to, but....

Even us 'veterans' can and do, on occasion, make mistakes just like a newbie!

So, I downloaded the latest 32-bit daily build of 13.10 for i386 and formatted the partitions on the Toshiba and did a fresh install. I finished with my customizing this morning. It's very stable. I'm using these repositories:

deb http://us.archive.ubuntu.com/ubuntu/ saucy main restricted
deb http://us.archive.ubuntu.com/ubuntu/ saucy-updates main restricted
deb http://us.archive.ubuntu.com/ubuntu/ saucy universe
deb http://us.archive.ubuntu.com/ubuntu/ saucy-updates universe
deb http://us.archive.ubuntu.com/ubuntu/ saucy multiverse
deb http://us.archive.ubuntu.com/ubuntu/ saucy-updates multiverse
deb http://us.archive.ubuntu.com/ubuntu/ saucy-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu saucy-security main restricted
deb http://security.ubuntu.com/ubuntu saucy-security universe
deb http://security.ubuntu.com/ubuntu saucy-security multiverse
deb http://archive.canonical.com/ubuntu saucy partner
deb http://extras.ubuntu.com/ubuntu saucy main
deb http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu saucy main
deb http://ppa.launchpad.net/kubuntu-ppa/beta/ubuntu saucy main
deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu saucy main
deb http://ppa.launchpad.net/samrog131/ppa/ubuntu saucy main

[Frank616]

Snowhog:

Even us 'veterans' can and do, on occasion, make mistakes just like a newbie!

Yeah. I dd'd the blank drive onto the one I wanted to save once. Trashed the data good and proper..... Fortunately, I had an earlier backup, so only lost some of the more recent data.

Frank.

[SteveRiley]

Nice idea to add the development database to your repository in the hope that you can have a "rolling release" of Kubuntu, but by doing this all you will be doing is rolling on to the next development of Kubuntu. A rolling release distro is one thatt pushes the latest stable version of packages to the end user which is what Arch does. If by adding the development branch all your doing is keeping Kubuntu at the Alpha/Beta stage. It will never be a stable system. Plus you will have issues of breakages and may need to download nightly builds all the time.

The way it works now is that all development and testing occurs in the -proposed pocket. Once certain tests have passed, the packages are pushed to the release pocket. I would imagine that running a system as we're describing here wouldn't be maintenance-free, of course, but it probably is sufficiently usable to approximate a "rolling" style by skilled users.

[SteveRiley]

I dd'd the blank drive onto the one I wanted to save once. Trashed the data good and proper.....

dd : Data Destroyer

[kubicle]

Sorry for the late responses, been off the grid for a week or so

So you're simply changing to the next release the moment the archives open.

Yes. When the archives open the upgrades start to push in at a moderate rate...so there is no huge one-time upgrade if you hop in from the get-go.

How many cycles have elapsed since you last built from the ground up?

Can't remember, but it's been at least 3 years (or six cycles)

Hey, Kubicle, looks like someone was reading your mind!
http://archive.ubuntu.com/ubuntu/dists/devel/
http://archive.ubuntu.com/ubuntu/dists/devel-proposed/

Ooh, that's nice

[oshunluvr]

OK, since 13.10 is officially "out" time to get this thread back to it's roots (oshun roles eyes at thread-jackers )...

Is there any obvious reason to upgrade at this point? I've been ignoring the widget-panel-NAG-button to upgrade but haven't removed it completely yet.

I realize this is often a personal choice - to upgrade or not. Currently, I'm busy with other projects (like setting up a home built dvr/media server and client) so the desire to upgrade is at an all-time low. I've skipped an upgrade in the past and survived so I may just leave well-enough alone. On another personal note, as we'll be moving to North Carolina next summer, I doubt I'll be embracing 14.04 either. Seems I might end up waiting for the mir-vs.-wayland dust to settle or just move to Sid and forget this roller-coaster.

Comments?

[kubicle]

Is there any obvious reason to upgrade at this point?

Featurewise...I guess no, if you're "happy" with 13.04.

The most obvious reason to upgrade non-LTS releases is the shortened support cycle (9 months), which means 13.04 will reach EOL on January, 2014.

If you're pondering Sid, you might as well go to ubuntu devel (of course there is nothing wrong in switching to Sid, either).