public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 14:53:25 +0100	[thread overview]
Message-ID: <200602281453.25437.ext-dirk.heinrichs@nokia.com> (raw)
In-Reply-To: <200602280329.21135.bss03@volumehost.net>

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

Am Dienstag, 28. Februar 2006 10:29 schrieb ext Boyd Stephen Smith Jr.:
> IMO, finding a binary in /bin or /sbin that links to a library in /usr
> (including /usr/local etc.) is probably grounds for a bug report, even if
> it's not currently causing any problems.

Yep.

> > 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.
>
> This is a good idea, even if none of your particular examples are
> problematic.  The crux of your argument is valid: some very useful
> programs reside in /usr or use libraries in /usr so when trying to umount
> it you must be prepared to do without those programs.

However, the discussion was about unmounting /usr to be able to resize it 
(in case the fs only supports unmounted resize). So these "very useful 
programs" in /usr are not needed during umount -> resize -> mount, anyway.

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 --]

  reply	other threads:[~2006-02-28 14:02 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
2006-02-28  9:23                   ` Zac Slade
2006-02-28  9:29                 ` Boyd Stephen Smith Jr.
2006-02-28 13:53                   ` Dirk Heinrichs [this message]
  -- 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=200602281453.25437.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