On 06/05/14 09:37, Luke Nath wrote:
Hi All,
Will FC20 have a hibernate option for shutdown?
Thanx.
Dell Inspiron 15R running F20 Mate distro. The hibernate function
appears in shutdown and is working
~~R
--
"When you're a nail, every problem looks like a hammer."
-- Anon.
--
users mailing
On 15/06/14 03:29, Joe Zeff wrote:
On 06/14/2014 05:19 PM, Jackson Byers wrote:
yum update && grub2-mkconfig -o /boot/grub2/grub.cfg
Unless there's something very, very strange going on with your machine,
the second half of that command is redundant, because AFAIK, part of
installing a new ke
On 06/14/2014 07:39 PM, Jackson Byers wrote:
what still puzzles me :
sometimes I don't need the
"grub2-install /dev/sda"
when doing yum update...
What puzzles me is why you ever need it.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
h
On Sun, Jun 15, 2014 at 8:09 AM, Jackson Byers wrote:
> Solved:aa
> after
> "grub2-install /dev/sda"
> and rebooting, I now get 3.14.7:
> $ uname -rsvp
> Linux 3.14.7-200.fc20.x86_64 #1 SMP Wed Jun 11 22:38:05 UTC 2014 x86_64
>
>
> what still puzzles me :
> sometimes I don't need the
> "gr
Solved:aa
after
"grub2-install /dev/sda"
and rebooting, I now get 3.14.7:
$ uname -rsvp
Linux 3.14.7-200.fc20.x86_64 #1 SMP Wed Jun 11 22:38:05 UTC 2014 x86_64
what still puzzles me :
sometimes I don't need the
"grub2-install /dev/sda"
when doing yum update...
Jack
On 06/14/2014 05:19 PM, Jackson Byers wrote:
yum update && grub2-mkconfig -o /boot/grub2/grub.cfg
Unless there's something very, very strange going on with your machine,
the second half of that command is redundant, because AFAIK, part of
installing a new kernel is rebuilding grub2. I do kn
yum update from 3.14.4 looks ok
in /boot
vmlinuz-3.14.3-200.fc20.x86_64
vmlinuz-3.14.4-200.fc20.x86_64
vmlinuz-3.14.7-200.fc20.x86_64
I can't seem to get 3.14.7 to 'take'
after reboot still in 3.14.4
exact command used for update:
yum update && grub2-mkconfig -o /boot/grub2/grub.cfg
followed by
On 14.06.2014 20:31, poma wrote:
On 14.06.2014 19:19, Bob Goodwin - Zuni, Virginia, USA wrote:
On 06/14/14 13:02, poma wrote:
Nope for this particular model, it's just one example for comparison.
BTW dd-wrt is versatile and covers a lot more devices, besides the
excellent documentation.
Your
On 14.06.2014 19:19, Bob Goodwin - Zuni, Virginia, USA wrote:
On 06/14/14 13:02, poma wrote:
Nope for this particular model, it's just one example for comparison.
BTW dd-wrt is versatile and covers a lot more devices, besides the
excellent documentation.
Your Linksys E3000 is literally twice
On 06/14/14 13:02, poma wrote:
Nope for this particular model, it's just one example for comparison.
BTW dd-wrt is versatile and covers a lot more devices, besides the
excellent documentation.
Your Linksys E3000 is literally twice as expensive, if a new one can
be purchased, at all.
It's no
On 14.06.2014 18:21, Bob Goodwin - Zuni, Virginia, USA wrote:
On 06/14/14 12:04, poma wrote:
For the same price category you can get e.g. TL-WDR4310[2] which is
BTW covered[4] for free by the dd-wrt(v1.x) and OpenWRT(v1.0), has
newer Atheros SoC with additional USB functionality, etc.
poma
On 06/14/14 12:04, poma wrote:
For the same price category you can get e.g. TL-WDR4310[2] which is
BTW covered[4] for free by the dd-wrt(v1.x) and OpenWRT(v1.0), has
newer Atheros SoC with additional USB functionality, etc.
poma
[1] http://mcsindex.com/
[2] http://wiki.openwrt.org/toh/tp
On 14.06.2014 15:52, Richard Shaw wrote:
On Sat, Jun 14, 2014 at 7:17 AM, poma wrote:
On 14.06.2014 05:21, Richard Shaw wrote:
Well thanks for all the pointers and ideas but I think I've got it "fixed"
now... I'm still not sure what caused the breakage though...
I noticed there was a new re
On Sat, Jun 14, 2014 at 7:17 AM, poma wrote:
> On 14.06.2014 05:21, Richard Shaw wrote:
>
>> Well thanks for all the pointers and ideas but I think I've got it "fixed"
>> now... I'm still not sure what caused the breakage though...
>>
>> I noticed there was a new release of the UniFi software (3.
On 14.06.2014 05:21, Richard Shaw wrote:
Well thanks for all the pointers and ideas but I think I've got it "fixed"
now... I'm still not sure what caused the breakage though...
I noticed there was a new release of the UniFi software (3.2.1) and managed
to upgrade it and then updated the firmware
After checking some of the documentation the solution as the follows:
setsebool -P use_ecryptfs_home_dirs 1
Thanks for the inspiration :)
L:
On 13 June 2014 06:38, Daniel J Walsh wrote:
> How is ecryptfs supposed to work?
>
>
> On 06/12/2014 03:13 PM, Pal, Laszlo wrote:
>
> node= type=SYSCALL
16 matches
Mail list logo
