From: German <gentgerman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
Date: Thu, 5 Mar 2015 16:28:54 -0500 [thread overview]
Message-ID: <20150305162854.058617b783a1d0f9e7b039bc@gmail.com> (raw)
In-Reply-To: <CAJ0EP40M+Mn+f5uvarxkqW_ELSujygym+tYNX42eaFPTua67ig@mail.gmail.com>
On Thu, 5 Mar 2015 16:13:59 -0500
Mike Gilbert <floppym@gentoo.org> wrote:
> On Thu, Mar 5, 2015 at 2:08 PM, German <gentgerman@gmail.com> wrote:
> > On Thu, 5 Mar 2015 13:45:51 -0500
> > Mike Gilbert <floppym@gentoo.org> wrote:
> >
> >> On Thu, Mar 5, 2015 at 12:28 PM, German <gentgerman@gmail.com> wrote:
> >> > On Thu, 5 Mar 2015 12:47:36 +0000
> >> > Neil Bothwick <neil@digimed.co.uk> wrote:
> >> >
> >> >> On Thu, 5 Mar 2015 07:37:39 -0500, German wrote:
> >> >>
> >> >> > > > > Is /var on your root filesystem? If so, it sounds like something
> >> >> > > > > is trying to write to it before it has been remounted rw. Try
> >> >> > > > > adding rw (and removing ro if present) to your kernel options.
> >> >> > > > >
> >> >> > > >
> >> >> > > > Ok, thanks. What file should I write these options to?
> >> >> > >
> >> >> > > Your bootloader config, that's where you specify the kernel boot
> >> >> > > options.
> >> >> >
> >> >> > That's what I thought, however I use gummiboot. Can you give an
> >> >> > example, to show your gummiboot config once again?
> >> >>
> >> >> Add it to the options line in the relavent file in /boot/loader/entries.
> >> >>
> >> >> Or test it first by pressing e at the menu and adding it there
> >> >
> >> >
> >> > So any other idea on hhow to fix it? Anyone?
> >>
> >> Can you please post the output of the following commands?
> >>
> >> stat /lib64/rc
> >>
> >> stat /lib64/rc/cache
> >
> > stat /lib64/rc/cache
> >
> > stat: cannot stat /lib64/rc/cache: No such file or directory
> >
> > I'll also put stat /lib64/rc later. I am thinking if there is no "cache" file, probably this will give you some clue. I am retyping this from my laptop screen and /lib64/rc is quite lengthy. Thank you. Please tell me if you really need it ( and me) and I'll take my time and retype it.
>
> It's supposed to be a directory. Try running mkdir -p /lib64/rc/cache.
It seems the error is gone. But I wonder why I didn't have /lib64/rc/cache directory. This was a fresh install.
>
--
German <gentgerman@gmail.com>
next prev parent reply other threads:[~2015-03-05 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 8:09 [gentoo-user] Warning: /lib64/rc/cache is not writable German
2015-03-05 8:24 ` Neil Bothwick
2015-03-05 10:10 ` German
2015-03-05 12:34 ` Neil Bothwick
2015-03-05 12:37 ` German
2015-03-05 12:47 ` Neil Bothwick
2015-03-05 13:33 ` German
2015-03-05 17:28 ` German
2015-03-05 18:45 ` Mike Gilbert
2015-03-05 19:08 ` German
2015-03-05 21:13 ` Mike Gilbert
2015-03-05 21:28 ` German [this message]
2015-03-05 10:22 ` Alan McKinnon
2015-03-05 10:22 ` German
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=20150305162854.058617b783a1d0f9e7b039bc@gmail.com \
--to=gentgerman@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