From: maillists <lists@gmnet.net>
To: gentoo-laptop@lists.gentoo.org
Subject: Re: [gentoo-laptop] problem with glibc update
Date: Wed, 03 Jan 2007 19:57:02 -0500 [thread overview]
Message-ID: <1167872223.16744.89.camel@localhost> (raw)
In-Reply-To: <1167869840.5054.11.camel@localhost>
On Wed, 2007-01-03 at 19:17 -0500, Randy Barlow wrote:
> On Wed, 2007-01-03 at 16:47 -0500, maillists wrote:
> > I tried this:
> > thor rbragg # chown root.portage /var/lib/portage/world
> > chown: changing ownership of `/var/lib/portage/world': Read-only file
> > system
>
> It seems like your file system is mounted read only. What is the output
> of mount for the file system that the file is on? Is the mount option
> ro, or rw?
>
> Randy Barlow
> http://www.electronsweatshop.com
> NAPOLEON: What shall we do with this soldier, Giuseppe? Everything he
> says is wrong. GIUSEPPE: Make him a general, Excellency, and then
> everything he says will be right. -- G. B. Shaw, "The Man of Destiny"
>
wow your right, I can't even do a "touch"!
That seems drastic, how might that have happened? when I started, I did
an emerge -auvDN system, and had to unmerge pam-login because it was
blocking many things. now I don't want to log out or reboot because I
will not be able to get back in!
Is there a way I can remount or fix this without logging out or
re-booting?
I started a new thread called "emerge broken after update gcc"
Thanks
rick
--
gentoo-laptop@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-04 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 0:55 [gentoo-laptop] problem with glibc update maillists
2007-01-03 7:28 ` Praveen C
2007-01-03 13:18 ` maillists
2007-01-03 19:08 ` Devon Miller
2007-01-03 21:47 ` maillists
2007-01-04 0:17 ` Randy Barlow
2007-01-04 0:57 ` maillists [this message]
2007-01-04 16:26 ` Devon Miller
-- strict thread matches above, loose matches on Subject: below --
2007-01-03 16:42 Longman, Bill
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=1167872223.16744.89.camel@localhost \
--to=lists@gmnet.net \
--cc=gentoo-laptop@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