From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LP238-0004lh-6I for garchives@archives.gentoo.org; Mon, 19 Jan 2009 21:52:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0F59DE04C0; Mon, 19 Jan 2009 21:52:49 +0000 (UTC) Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.241]) by pigeon.gentoo.org (Postfix) with ESMTP id BE5A3E04C0 for ; Mon, 19 Jan 2009 21:52:48 +0000 (UTC) Received: by rv-out-0708.google.com with SMTP id b17so3084798rvf.46 for ; Mon, 19 Jan 2009 13:52:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=bY8HTZElf31Z5OeL3pEShhzBmB2XlkTkm0Cqmdb6uNM=; b=Re1mT2ML6Ui/OIDFWR68acNkoiXbNFyooFVe4oj+AcixeASWSym791A8aSVgkM3RtX Zq5HInZaOdFY9gGBcWB2gG7K/UTPKvK7nHhPMLSFP5OuLx/WFymmaJ9RIsZy9s629aud xgGIHzpP4KhFAr2XubmTOv4KD6aGUWtBViNSs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=KR4P4iqnaUJ6L7YR4frryJIkkURXVpkazxihH9Ssmw24gqPOdlYYctu6/PoEQtyoBI VfgwRH7Hp4u0DC2xQC/TUZ+ho7SEMFdyt5b2FzUQH0DBkIbDO8/m7uAyDgs3clBmkvmH 1z+uusvX8N4kJXbLMsTg9b99VemA9mf/VTJjM= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Sender: mryiff@googlemail.com Received: by 10.141.53.4 with SMTP id f4mr3030515rvk.35.1232401968202; Mon, 19 Jan 2009 13:52:48 -0800 (PST) In-Reply-To: <4974F4A4.7010007@badapple.net> References: <4974C635.6090501@badapple.net> <20090119213907.64fe65b2@gentoo.org> <4974F4A4.7010007@badapple.net> Date: Mon, 19 Jan 2009 21:52:48 +0000 X-Google-Sender-Auth: fc5e39fcfd86c644 Message-ID: Subject: Re: [gentoo-user] baselayout and openrc issues from inside a vserver From: Nick Cunningham To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=000e0cd291ba8905860460dcf152 X-Archives-Salt: a4658b0f-8022-4b1b-966a-32d0125e1a4f X-Archives-Hash: 209d25e668e20bae8dcd30296593af8c --000e0cd291ba8905860460dcf152 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 2009/1/19 kashani > Peter Alfredsen wrote: > >> On Mon, 19 Jan 2009 10:28:05 -0800 >> kashani wrote: >> >> I've been putting off the openrc upgrade on my vserver >>> account for some time and think it's finally come around to bite me. >>> >> >> Our vserver team had this to say about it on -dev a few days ago. >> >>> - - baselayout-2/openrc isn't stable yet, in fact it's even masked >>>> in profiles/targets/vserver/package.mask >>>> >>> i don't care. baselayout-vserver is a hack, the vserver profiles are >>> deprecated since ages (although i think the restructuring revived >>> them), and the vserver team (that's only me currently) doesn't >>> support anything else beside openrc. >>> >>> Greets, >>> Bene >>> >> >> So, you should probably migrate to the normal profiles as recommended >> by the vserver howto: >> >> Whoops, missed the link to the vserver howto: >> http://www.gentoo.org/proj/en/vps/vserver-howto.xml >> > > Unfortunately that doc isn't very up to date or very well written. Hell the > mentioned baselayout 1.13 doesn't even exist in portage. > > It appears that I should. > > 1. Change profile from vserver to server so I don't have to go mucking > about in package.mask > 2. emerge -C baselayout-vserver && emerge baselayout-2 openrc > 3. clean up openrc baselayout issues. > 4. Make backups, restart, and hope it doesn't explode. > > That sound about right? > > The other side is that I have no control over the host OS, I just pay for a > hosted vserver. Is any of this goes to have issues if I update the quest > and the host is not aware? > > kashani > > Dont edit anything inside of /usr/portage as it will get wiped out the next time you sync. If you want to unmask openrc and baselayout then use /etc/portage/package.unmask and /etc/portage/package.keywords. Make sure you read the OpenRC migration guide or you risk severely hosing your system! http://www.gentoo.org/doc/en/openrc-migration.xml - Nick --000e0cd291ba8905860460dcf152 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

2009/1/19 kashani <= kashani-list@badapple.net&= gt;
Peter Alfredsen wrote:
<= div class=3D"Wj3C7c"> On Mon, 19 Jan 2009 10:28:05 -0800
kashani <= kashani-list@badapple.net> wrote:

       I've been putting off the openrc upgrade on= my vserver
account for some time and think it's finally come around to bite me.

Our vserver team had this to say about it on -dev a few days ago.
- - baselayout-2/openrc isn't stable yet, in fact it's even masked<= br> in profiles/targets/vserver/package.mask  
i don't care. baselayout-vserver is a hack, the vserver profiles are deprecated since ages (although i think the restructuring revived
them), and the vserver team (that's only me currently) doesn't
support anything else beside openrc.

Greets,
Bene

So, you should probably migrate to the normal profiles as recommended
by the vserver howto:

Whoops, missed the link to the vserver howto:
http://www.gentoo.org/proj/en/vps/vserver-howto.xml

Unfortunately that doc isn't very up to date or very well written. Hell= the mentioned baselayout 1.13 doesn't even exist in portage.

It appears that I should.

1. Change profile from vserver to server so I don't have to go mucking = about in package.mask
2. emerge -C baselayout-vserver && emerge baselayout-2 openrc
3. clean up openrc baselayout issues.
4. Make backups, restart, and hope it doesn't explode.

That sound about right?

The other side is that I have no control over the host OS, I just pay for a= hosted vserver. Is any of this goes to have issues if I update the  q= uest and the host is not aware?

kashani


Dont edit anything inside of /usr/portage as = it will get wiped out the next time you sync.
If you want to unmask open= rc and baselayout then use /etc/portage/package.unmask and /etc/portage/pac= kage.keywords.

Make sure you read the OpenRC migration guide or you risk severely hosi= ng your system!
http://www.gentoo.org/doc/en/openrc-migration.xml

- Nick --000e0cd291ba8905860460dcf152--