On 07/31/15 09:16, jd1008 wrote:
> $ mount /sdc1
> FUSE exfat 1.0.1
> fusermount: option blkdev is privileged
Oh, FWIW, if you want to allow non-root users to mount exfat devices you can do
one potentially dangerous thing and ...
chmod u+s /usr/sbin/mount.exfat-fuse
--
If I wanted a blog or
On Thu, 30 Jul 2015 20:28:03 +0200, Butrus Damaskus wrote:
> > ...
> > it. For a very long time, it considered the main systemd executable as
> > infected, and nobody did anything about that. Everywhere you could
> >
>
> Obviously, given what a mess systemd is. I wouldn't blame chkrootkit for it!
On Fri, 31 Jul 2015 00:03:50 +0200, Patrick Dupre wrote:
> Yes, I run gnome. Do you need additional info?
Where did you try to change it?
"All Settings > Keyboard > Input Sources"
Notice the "Login Screen" button at the top right of that window.
--
users mailing list
users@lists.fedoraprojec
I was luck enough to be bitten by this issue (
https://bugzilla.redhat.com/show_bug.cgi?id=1212907 ) when attempting to do
a clean install of F22. I copied all of my data off and then tried manually
setting things up as separate partitions (instead of in an LVM) but it kept
telling me that /boot co
Linux for many years as supported encrypting most partitions on your system,
with the exception of /boot./boot contains the basic/initial BOOT configuration
of your system... that means, by definition, it must be discernable---and thus
cannot be encrypted. Without an un-encrypted /boot partitio
Linux for many years as supported encrypting most partitions on your system,
with the exception of /boot./boot contains the basic/initial BOOT configuration
of your system... that means, by definition, it must be discernable---and thus
cannot be encrypted. Without an un-encrypted /boot partitio
On 07/30/2015 10:03 PM, Ed Greshko wrote:
On 07/31/15 09:16, jd1008 wrote:
$ grep sdc1 /etc/fstab
UUID=BE5F-383B /sdc1 exfat noauto,rw,user,uid=508,gid=508
1 1
# cat /etc/fuse.conf
# mount_max = 1000
user_allow_other
$ mount /sdc1
FUSE exfat 1.0.1
fusermount: option b
FYI
Forwarded Message
Free Software Foundation
Dear ,
We can't stop all the millions of people who are installing Windows 10
right now, but we can influence our friends and family to skip Windows
and join us in the free world. As you know, Windows 10 puts those that
use i
On 07/31/2015 01:21 AM, Ed Greshko wrote:
On 07/31/15 09:16, jd1008 wrote:
$ mount /sdc1
FUSE exfat 1.0.1
fusermount: option blkdev is privileged
Oh, FWIW, if you want to allow non-root users to mount exfat devices you can do
one potentially dangerous thing and ...
chmod u+s /usr/sbin/mount
2015-07-31 19:10 GMT+03:00 jd1008 :
> FYI
>
>
> Forwarded Message
>
> Free Software Foundation
>
> Dear ,
>
> We can't stop all the millions of people who are installing Windows 10
> right now, but we can influence our friends and family to skip Windows and
> join us in the free
On 07/31/2015 08:28 AM, Dave Johansen wrote:
I was luck enough to be bitten by this issue (
https://bugzilla.redhat.com/show_bug.cgi?id=1212907 ) when attempting
to do a clean install of F22.
That bug looks like it's triggered only when the LVs are encrypted,
which is non-standard and not at
On 07/30/2015 10:03 PM, Ed Greshko wrote:
On 07/31/15 09:16, jd1008 wrote:
$ grep sdc1 /etc/fstab
UUID=BE5F-383B /sdc1 exfat noauto,rw,user,uid=508,gid=508
1 1
# cat /etc/fuse.conf
# mount_max = 1000
user_allow_other
$ mount /sdc1
FUSE exfat 1.0.1
fusermount: option b
On Fri, Jul 31, 2015 at 11:18 AM, Gordon Messmer
wrote:
> On 07/31/2015 08:28 AM, Dave Johansen wrote:
>>
>> I was luck enough to be bitten by this issue (
>> https://bugzilla.redhat.com/show_bug.cgi?id=1212907 ) when attempting to do
>> a clean install of F22.
>
>
> That bug looks like it's trigg
On 08/01/15 00:15, jd1008 wrote:
>
>
> On 07/31/2015 01:21 AM, Ed Greshko wrote:
>> On 07/31/15 09:16, jd1008 wrote:
>>> $ mount /sdc1
>>> FUSE exfat 1.0.1
>>> fusermount: option blkdev is privileged
>> Oh, FWIW, if you want to allow non-root users to mount exfat devices you can
>> do one potentia
On 07/31/2015 12:02 PM, inode0 wrote:
/boot can be on an encrypted partition. I've been looking at this
lately and decided to try to do it after seeing this thread today.
Anaconda won't help you do it though, so you need to install initially
with it unencrypted but you can encrypt it post-install
On Fri, Jul 31, 2015 at 3:37 PM, Gordon Messmer
wrote:
> On 07/31/2015 12:02 PM, inode0 wrote:
>>
>> /boot can be on an encrypted partition. I've been looking at this
>> lately and decided to try to do it after seeing this thread today.
>> Anaconda won't help you do it though, so you need to insta
On 07/31/2015 02:00 PM, inode0 wrote:
grub2 supports LUKS. You'll need to add GRUB_ENABLE_CRYPTODISK=y to
/etc/sysconfig/grub
Interesting. Thanks for the tip! :)
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/m
hmm. I don't know if I'm in the same experience or not. I'm running
fedora 21 and upgraded to kernel 4.0.8 from 4.0.7 on 7/19. I didn't
have any issues until about the 26th. But then my system started to
lock up. It wasn't just GNOME but direct access was locked -- ie no
response via keyboard,
On Fri, Jul 31, 2015 at 4:21 PM, Gordon Messmer
wrote:
> On 07/31/2015 02:00 PM, inode0 wrote:
>>
>> grub2 supports LUKS. You'll need to add GRUB_ENABLE_CRYPTODISK=y to
>> /etc/sysconfig/grub
>
>
> Interesting. Thanks for the tip! :)
For anyone adventurous enough to try I will mention that if so
Am 31.07.2015 um 23:21 schrieb Gordon Messmer:
> On 07/31/2015 02:00 PM, inode0 wrote:
>> grub2 supports LUKS. You'll need to add GRUB_ENABLE_CRYPTODISK=y to
>> /etc/sysconfig/grub
>
> Interesting. Thanks for the tip! :)
The following Link might be of interest for you:
http://dustymabe.com/2015/
Hello,
I had a bad surprise.
After the last update grub2-mkconfig -o /boot/grub2/grub.cfg
the grub.cfg is not correct
I have:
menuentry 'Fedora (4.1.2-200.fc22.i686+PAE) 22 (Twenty Two)' --class fedora
--class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option
'gnulinux-4.1.2-
Hi,
On a new UEFI-boot desktop running Fedora 22, the command (on a terminal
prompt) "reboot" does not actually bring up the system. Actually, it is not
clear that the system even goes down. What happens is that the monitor light
goes off but the desktop light stays on -- and nothing happens. I
Hello,
In fedora 22 (i686) seamonkey web!
core dump.
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale
On Fri, Jul 31, 2015 at 5:09 PM, Ranjan Maitra
wrote:
> Hi,
>
> On a new UEFI-boot desktop running Fedora 22, the command (on a terminal
> prompt) "reboot" does not actually bring up the system. Actually, it is not
> clear that the system even goes down. What happens is that the monitor light
>
Two things to check. Make sure the fstab on both are correct because
grub2-mkconfig depends on both fstabs to build the grub.cfg.
Next would be to add line GRUB_DISABLE_OS_PROBER="true" in the
/etc/default/grub and the it will only make a grub.cfg for Fedora 22
and you can see if that's correct. I
On Fri, Jul 31, 2015 at 9:28 AM, Dave Johansen wrote:
> I was luck enough to be bitten by this issue (
> https://bugzilla.redhat.com/show_bug.cgi?id=1212907 ) when attempting to do
> a clean install of F22. I copied all of my data off and then tried manually
> setting things up as separate partiti
26 matches
Mail list logo
