public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Multiple Update Issues - what order should things be done?
Date: Sun, 7 Mar 2010 20:17:18 +0200	[thread overview]
Message-ID: <201003072017.18625.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4B92A149.5080306@libertytrek.org>

On Saturday 06 March 2010 20:39:05 Tanstaafl wrote:
> On 2010-03-06 1:53 AM, Alan McKinnon wrote:
> > On Saturday 06 March 2010 01:30:38 Tanstaafl wrote:
> >> So, again, does anyone know if the new version of lvm2 (with
> >> integrated device-mapper) will work ok on the 2.6.23 kernel, or is
> >> there a minimum version required?
> > 
> > Again, this is in the ebuild. You can ignore most of the weird
> > details and look for important stuff. Dependencies are in DEPEND, and
> > in the case of the latest lvm2, the only important limits are:
> > 
> > !!sys-fs/device-mapper
> > 
> >> =sys-apps/util-linux-2.16
> 
> Ok, good, I'm at 2.16.2 - and I guess they're not so scary as I
> remembered. I come from a Windows background, and I'm really enjoying
> learning linux, but still get a little intimidated sometimes. Next time
> I'll look first then ask only if I can't answer it for myself.

Most of the stuff in ebuilds makes sense, it usually means what you think when 
you look at it.

> Thanks for not taking my jab personally...

No problem, no offense taken. If you work in Unix, you get to grow a thick 
skin real quick :-)

[snip]

> > If the box is old, and you have to switch to openrc/baselayout2,
> > that's where your troubles are going to happen.
> 
> Ok, this is an older install, and I've been pretty good (until now)
> about keeping it pretty much up to date. gcc-4.3.4 only went stable on
> amd64 4-5 months ago and I don't usually wait this long to switch to it
> and rebuild world (I usually wait 1-2 months)...
> 
> Baselayout2 is still not stable, so, yes, I'm still on baselayout1, and
> now you've gone and made me nervous again. ;)
> 
> Are you suggesting I should already be using it??

You are going to have to switch sometime, the day will come when baselayout-2 
goes stable. Seeing as you plan a large update anyway, which will have 
downtime, this would be an ideal opportunity.

However, the update is deep and you will be marking a lot of things unstable 
if you do. On a production machine you might not want to do that. Only you can 
say if it's a step you are willing to take. On the plus side, baselayout-1 
will still work for a very long time to come.

When the time to change comes around, set aside an hour or two for the job. 
It's not a complex change, but many files need to be updated, there's all 
sorts of things in /etc/rc.conf and /etc/conf.d that must be re-organized and 
you will want to double check all affected packages.

Like I said, it's not complex, and it won't cause you to meet your maker. 
Everything is well documented, but it is lengthy and tedious and you want to 
finish it all in one sitting - if for no other reason than if you come back to 
it later, you won't remember how far you got :-)

> 
> > This is a deep change that touches many things with lots of configs
> > being updated and things moving around.
> 
> Ok, where is the best place to go to start reading/learning about how to
> prep for it?

http://www.gentoo.org/doc/en/openrc-migration.xml


-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2010-03-07 18:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 19:09 [gentoo-user] Multiple Update Issues - what order should things be done? Tanstaafl
2010-03-05 19:20 ` Alan McKinnon
2010-03-05 20:40   ` Sebastian Beßler
2010-03-05 23:30   ` Tanstaafl
2010-03-06  6:53     ` Alan McKinnon
2010-03-06 18:39       ` Tanstaafl
2010-03-07 18:17         ` Alan McKinnon [this message]
2010-03-07 23:54           ` Dale
2010-03-08  0:55             ` Neil Bothwick
2010-03-08  1:10               ` Dale
2010-03-08 12:44           ` Tanstaafl
2010-03-08 13:05             ` Alan McKinnon
2010-03-08 18:25               ` Tanstaafl
2010-03-08 18:32                 ` Mark Knecht
2010-03-08 19:45                 ` Neil Walker
2010-03-08 20:10                 ` Alan McKinnon
2010-03-08 20:39                   ` Dale
2010-03-08 20:55                     ` Alan McKinnon
2010-03-08 22:39                       ` Dale
2010-03-08 20:53                 ` Neil Bothwick
2010-03-08 21:02                   ` Tanstaafl
2010-03-08 22:41                     ` Dale
2010-03-06 12:17 ` Peter Humphrey
2010-03-06 19:28   ` Tanstaafl
2010-03-07 10:21     ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201003072017.18625.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox