From: Dirk Heinrichs <ext-dirk.heinrichs@nokia.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo LVM Newbie Question
Date: Tue, 28 Feb 2006 10:03:12 +0100 [thread overview]
Message-ID: <200602281003.16895.ext-dirk.heinrichs@nokia.com> (raw)
In-Reply-To: <200602272301.09811.krakrjak@volumehost.net>
[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]
Am Dienstag, 28. Februar 2006 06:01 schrieb ext Zac Slade:
> On Monday 27 February 2006 00:48, Dirk Heinrichs wrote:
> > Wrong. Switch to runlevel 1 (using "telinit 1"), which is for
> > maintenance. In RL 1, no user processes are running and you can umount
> > everything except /.
>
> Partially right. Gentoo has several gotchas in runlevel 1. If /usr is a
> seperate filesystem you have to be careful. Bash by default is not
> statically linked and requires readline (which is installed in /usr/lib).
> ls will require libgpm which is also in /usr/lib. So you have to be
> careful. One of the best things you can do for yourself is install an all
> in one shell for maintenece like busybox or nash. Also lvm is not
> statically linked and can require libraries out of /usr/lib also. So be
> careful and understand what you are doing. You just might need a livecd
> in some cases for shrinking.
Oops, you're right, telinit 1 doesn't work as expected in Gentoo (are there
any bugreports about it?). However, I can reboot into RL 1 just fine and
umount /usr w/o problems. I can also use ls just fine with /usr unmounted,
all fs maintenance tools should also work.
However, after trying it out, it seems that even telinit 3 (when booted into
RL 1) doesn't work properly, so using a LiveCD indeed looks to be the
better option for the moment.
Bye...
Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211 47068 111
Capgemini Deutschland | Mail: dirk.heinrichs@capgemini.com
Hambornerstraße 55 | Web: http://www.capgemini.com
D-40472 Düsseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2006-02-28 9:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 20:22 [gentoo-user] Gentoo LVM Newbie Question CR Little
2006-02-23 20:41 ` Boyd Stephen Smith Jr.
2006-02-23 20:59 ` Alexander Skwar
2006-02-23 21:15 ` Qv6
2006-02-23 21:59 ` John Jolet
2006-02-23 22:35 ` Boyd Stephen Smith Jr.
2006-02-24 6:03 ` Alexander Skwar
2006-02-25 3:35 ` Zac Slade
2006-02-25 4:13 ` John Jolet
2006-02-25 4:32 ` Zac Slade
2006-02-25 5:14 ` John Jolet
2006-02-25 6:52 ` Alexander Skwar
2006-02-25 6:44 ` Alexander Skwar
2006-02-25 6:43 ` Alexander Skwar
2006-02-25 11:24 ` Holly Bostick
2006-02-25 12:21 ` Alexander Skwar
2006-02-25 7:55 ` Jarry
2006-02-25 10:26 ` Alexander Skwar
2006-02-25 10:44 ` Jarry
2006-02-25 11:11 ` Alexander Skwar
2006-02-25 15:01 ` [gentoo-user] [OT] " Boyd Stephen Smith Jr.
2006-02-27 6:48 ` [gentoo-user] " Dirk Heinrichs
2006-02-28 5:01 ` Zac Slade
2006-02-28 9:03 ` Dirk Heinrichs [this message]
2006-02-28 9:23 ` Zac Slade
2006-02-28 9:29 ` Boyd Stephen Smith Jr.
2006-02-28 13:53 ` Dirk Heinrichs
-- strict thread matches above, loose matches on Subject: below --
2006-02-23 20:58 CR Little
2006-02-23 21:36 ` Boyd Stephen Smith Jr.
2006-02-23 21:41 CR Little
2006-02-23 23:29 CR Little
2006-02-23 23:57 ` Boyd Stephen Smith Jr.
2006-02-24 14:40 CR Little
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=200602281003.16895.ext-dirk.heinrichs@nokia.com \
--to=ext-dirk.heinrichs@nokia.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