On Mar 12, 2014, at 1:11 PM, Chris Murphy wrote:
> Anyway I always do a 1/2 dozen reboots with it enabled, checking
> systemd-analyze each time; and then disable it and reboot and check
> systemd-analyze again.
That is, I do this with each new major version of systemd. Because this
readahea
For posterity:
https://bugzilla.redhat.com/show_bug.cgi?id=696821
It's not exactly the OP's problem, but there appears to be a kernel bug that
can cause systemd readahead problems. Anyway I always do a 1/2 dozen reboots
with it enabled, checking systemd-analyze each time; and then disable it an
On Mar 12, 2014, at 4:36 AM, takCoder wrote:
> systemd-readahead[416]: Failed to open pack file: Read-only system
I'm not sure the problem is Bluetooth at all. Systemd has a way to optimize
boot times with its own read ahead mechanism, and puts the hint for what to
read ahead in (I'm guessin
On Wed, 2014-03-12 at 17:57 +0330, takCoder wrote:
> would anyone please give me any hints?
> can I disable bluetooth servive from repair mode?
[Please don't top-post on the Fedora lists. See the Guidelines document
referenced at the end of every post.]
F18 is EOL, i.e. no longer supported, howev
would anyone please give me any hints?
can I disable bluetooth servive from repair mode?
Best Regards,
t.a.k
On Wed, Mar 12, 2014 at 2:06 PM, takCoder wrote:
> Hi All,
>
> I'm new in fedora world and here's my first unsolved problem there.. It's
> an un-reasoned hang during boot up of a health
Hi All,
I'm new in fedora world and here's my first unsolved problem there.. It's
an un-reasoned hang during boot up of a healthy system..
I have installed fedora 18 on a ssd, followed a given process to install
required packages of my goal system, and it was working fine before..
Today I power
