qemu + plan9(virtfs) and access(still) denied

[peljasz]

hi everybody

I wonder if you had a chance to use virtfs with passthrough in qemu?
I have a host that passes through a directory to a guest, in the guest I can 
mount the tag successfully and list the content of the mountpoint, but when I 
try to create a file or make a dir I get "permission denied", but... I can 
remove files/dirs - is this not weird?
I believe I've fished out all denials and also with disabled silent denials I 
do not see anything.
I wonder if somebody can comment whether it is selinux problem? I'm on Centos 
7.2 with elrepo's kernel 4.7.
many thanks.
L
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor not detected correctly

[Paul Smith]

On Wed, Aug 31, 2016 at 10:08 PM, Tom Horsley  wrote:
>
>> Yes, it probably is correct.  The same driver could be used for both 22" and 
>> 27".
>>
>> Are you having any specific problems with your display?
>
> A lot of monitor firmwares always report the same size even when
> there are many different models of the monitors with different sizes.
> This can screw up gnome DPI computations and give you
> funny sized fonts.
>
> I bodged the EDID info for my samsung 46 inch TV
> that reported its size as 9 inches and used the kernel
> parameter to point to my new EDID:
>
> drm_kms_helper.edid_firmware=edid/zootyrgb.bin
>
> Now all modesetting video drivers always get the dadgum
> DPI correct (of course the binary nvidia driver
> doesn't do modesetting, but you can create an
> xorg.conf.d file for it to explicitly set the DPI).

Thanks, Ed, Rick and Tom. Notwithstanding the reported problem,
everything seems to working fine.

EDID reports the following in my case:


Extracted contents:
header:  00 ff ff ff ff ff ff 00
serial number:   1e 6d b6 5a c5 cb 00 00 07 1a
version: 01 03
basic params:6c 30 1b 78 ea
chroma info: 31 35 a5 55 4e a1 26 0c 50 54
established: a5 4b 00
standard:71 4f 81 80 95 00 b3 00 a9 c0 81 00 81 c0 90 40
descriptor 1:02 3a 80 18 71 38 2d 40 58 2c 45 00 e0 0e 11 00 00 1e
descriptor 2:00 00 00 fd 00 38 4b 1e 53 0f 00 0a 20 20 20 20 20 20
descriptor 3:00 00 00 fc 00 4c 47 20 49 50 53 20 46 55 4c 4c 48 44
descriptor 4:00 00 00 ff 00 36 30 37 4e 54 4b 46 31 4a 31 36 35 0a
extensions:  00
checksum:80

Manufacturer: GSM Model 5ab6 Serial Number 52165
Made week 7 of 2016
EDID version: 1.3
Analog display, Input voltage level: 0.7/0.7 V
Sync: Separate Composite
Maximum image size: 48 cm x 27 cm
Gamma: 2.20
DPMS levels: Standby Suspend Off
RGB color display
First detailed timing is preferred timing
Established timings supported:
  720x400@70Hz
  640x480@60Hz
  640x480@75Hz
  800x600@60Hz
  800x600@75Hz
  1024x768@60Hz
  1024x768@75Hz
  1280x1024@75Hz
Standard timings supported:
  1152x864@75Hz
  1280x1024@60Hz
  1440x900@60Hz
  1680x1050@60Hz
  1600x900@60Hz
  1280x800@60Hz
  1280x720@60Hz
  1400x1050@60Hz
Detailed mode: Clock 148.500 MHz, 480 mm x 270 mm
   1920 2008 2052 2200 hborder 0
   1080 1084 1089 1125 vborder 0
   +hsync +vsync
Monitor ranges (GTF): 56-75Hz V, 30-83kHz H, max dotclock 150MHz
Serial number: 607NTKF1J165
Checksum: 0x80 (valid)
EDID block does NOT conform to EDID 1.3!
Name descriptor not terminated with a newline


Paul
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor not detected correctly

[Tom Horsley]

On Thu, 1 Sep 2016 04:56:30 +0800
Ed Greshko wrote:

> Yes, it probably is correct.  The same driver could be used for both 22" and 
> 27". 
> 
> Are you having any specific problems with your display?

A lot of monitor firmwares always report the same size even when
there are many different models of the monitors with different sizes.
This can screw up gnome DPI computations and give you
funny sized fonts.

I bodged the EDID info for my samsung 46 inch TV
that reported its size as 9 inches and used the kernel
parameter to point to my new EDID:

drm_kms_helper.edid_firmware=edid/zootyrgb.bin

Now all modesetting video drivers always get the dadgum
DPI correct (of course the binary nvidia driver
doesn't do modesetting, but you can create an
xorg.conf.d file for it to explicitly set the DPI).
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor not detected correctly

[Ed Greshko]

On 09/01/16 04:40, Paul Smith wrote:
> On Wed, Aug 31, 2016 at 9:34 PM, Ed Greshko  wrote:
>>> I have just bought a monitor, which is detected by Fedora 24 as a
>>>
>>> Goldstar company Lda 22",
>>>
>>> but the monitor is a LG of 27".
>>>
>>> How can this be fixed?
>> FYI, LG = Lucky Goldstar, the official name of the South Korean electronics 
>> company.
> Thanks, Ed and Stan. So, since the brand LG corresponds to Goldstar
> Company, the driver Fedora uses (Goldstar Company Lda 22") may be the
> correct one, that is, the driver maybe the same for both the LG 22"
> monitors and the LG 27" ones.
>
>

Yes, it probably is correct.  The same driver could be used for both 22" and 
27". 

Are you having any specific problems with your display?


-- 
You're Welcome Zachary Quinto
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor not detected correctly

[Paul Smith]

On Wed, Aug 31, 2016 at 9:34 PM, Ed Greshko  wrote:
>
>> I have just bought a monitor, which is detected by Fedora 24 as a
>>
>> Goldstar company Lda 22",
>>
>> but the monitor is a LG of 27".
>>
>> How can this be fixed?
>
> FYI, LG = Lucky Goldstar, the official name of the South Korean electronics 
> company.

Thanks, Ed and Stan. So, since the brand LG corresponds to Goldstar
Company, the driver Fedora uses (Goldstar Company Lda 22") may be the
correct one, that is, the driver maybe the same for both the LG 22"
monitors and the LG 27" ones.

Paul
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor not detected correctly

[Rick Stevens]

On 08/31/2016 01:18 PM, stan wrote:
> On Wed, 31 Aug 2016 19:25:21 +0100
> Paul Smith  wrote:
> 
>> Dear All,
>>
>> I have just bought a monitor, which is detected by Fedora 24 as a
>>
>> Goldstar company Lda 22",
>>
>> but the monitor is a LG of 27".
>>
>> How can this be fixed?
> 
> I am not an expert.  But this sounds like a faulty EDID, or path to
> read the EDID. Fedora / linux reads the information about the monitor
> directly from the monitor itself. I think this can be overridden by
> putting a configuration file in /etc/X11/xorg.conf.d/ with the
> information needed.  A search should turn up samples.  Is it possible
> that you already have an override file there, for a 22" Goldstar
> monitor?  Or that the connection to the LG is flaky, so the EDID can't
> be read properly?
> 
> I vaguely recall that it is possible to dump the EDID into a file, and
> point to it in the kernel start line somehow.  Could be a faulty
> memory, though.

Make sure you have the xorg-x11-utils RPM installed, then do

xrandr --prop

In the output, look for something like:

EDID:
00000469f6270bec0100
1e150103803c22782aeed5a555489b26
125054b7ef00714f81c0814081809500
b300d1c00101023a801871382d40582c
45005650211e00ff0042374c
4d54463132353936330a00fd0032
55185c11000a20202020202000fc
00415355532056453237380a202001d4
020322714f0102031112130414050e0f
1d1e1f1023090701830165030c00
10008c0ad08a20e02d10103e96000925
2118011d007251d01e206e285500
0925211e011d00bc52d01e20b828
55400925211e8c0ad09020403120
0c40550009252118
0073

relating to the output of your active screen. Copy JUST the hex data to
a temporary file and convert it all to one line. Once you've done that,
then do

edid-decode /path/to/temp/file

and you'll see what the monitor reports itself as. Using the above data,
edid-decode says this about my monitor:

--- CUT HERE -
[root@prophead ~]# edid-decode /tmp/edid
Extracted contents:
header:  00 ff ff ff ff ff ff 00
serial number:   04 69 f6 27 0b ec 01 00 1e 15
version: 01 03
basic params:80 3c 22 78 2a
chroma info: ee d5 a5 55 48 9b 26 12 50 54
established: b7 ef 00
standard:71 4f 81 c0 81 40 81 80 95 00 b3 00 d1 c0 01 01
descriptor 1:02 3a 80 18 71 38 2d 40 58 2c 45 00 56 50 21 00 00 1e
descriptor 2:00 00 00 ff 00 42 37 4c 4d 54 46 31 32 35 39 36 33 0a
descriptor 3:00 00 00 fd 00 32 55 18 5c 11 00 0a 20 20 20 20 20 20
descriptor 4:00 00 00 fc 00 41 53 55 53 20 56 45 32 37 38 0a 20 20
extensions:  01
checksum:d4

Manufacturer: ACI Model 27f6 Serial Number 125963
Made week 30 of 2011
EDID version: 1.3
Digital display
Maximum image size: 60 cm x 34 cm
Gamma: 2.20
DPMS levels: Off
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
  720x400@70Hz
  640x480@60Hz
  640x480@67Hz
  640x480@75Hz
  800x600@56Hz
  800x600@60Hz
  800x600@72Hz
  800x600@75Hz
  832x624@75Hz
  1024x768@60Hz
  1024x768@70Hz
  1024x768@75Hz
  1280x1024@75Hz
Standard timings supported:
  1152x864@75Hz
  1280x720@60Hz
  1280x960@60Hz
  1280x1024@60Hz
  1440x900@60Hz
  1680x1050@60Hz
  1920x1080@60Hz
Detailed mode: Clock 148.500 MHz, 598 mm x 336 mm
   1920 2008 2052 2200 hborder 0
   1080 1084 1089 1125 vborder 0
   +hsync +vsync
Serial number: B7LMTF125963
Monitor ranges (GTF): 50-85Hz V, 24-92kHz H, max dotclock 170MHz
Monitor name: ASUS
Has 1 extension blocks
Checksum: 0xd4 (valid)

CEA extension block
Extension version: 3
30 bytes of CEA data
  Video data block
VIC 01 640x480@60Hz
VIC 02 720x480@60Hz
VIC 03 720x480@60Hz
VIC 17 720x576@50Hz
VIC 18 720x576@50Hz
VIC 19 1280x720@50Hz
VIC 04 1280x720@60Hz
VIC 20 1920x1080i@50Hz
VIC 05 1920x1080i@60Hz
VIC 14 1440x480@60Hz
VIC 15 1440x480@60Hz
VIC 29 1440x576@50Hz
VIC 30 1440x576@50Hz
VIC 31 1920x1080@50Hz
VIC 16 1920x1080@60Hz
  Audio data block
Linear PCM, max channels 1
Supported sample rates (kHz): 48 44.1 32
Supported sample sizes (bits): 24 20 16
  Speaker allocation data block
  Vendor-specific data block, OUI 000c03 (HDMI)
Source physical address 1.0.0.0
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 27.000 MHz, 521 mm x 293 mm
720  736  798  858 hborder 0
480  489  495  525 vborder 0
   -hsync -vsync
Detailed mode: Clock 74.250 MHz, 521 mm x 293 mm
   1280 1390 1430 1650 hborder 0
720  725  

Re: Monitor not detected correctly

[Ed Greshko]

On 09/01/16 02:25, Paul Smith wrote:
> Dear All,
>
> I have just bought a monitor, which is detected by Fedora 24 as a
>
> Goldstar company Lda 22",
>
> but the monitor is a LG of 27".
>
> How can this be fixed?

FYI, LG = Lucky Goldstar, the official name of the South Korean electronics 
company.



-- 
You're Welcome Zachary Quinto
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor not detected correctly

[stan]

On Wed, 31 Aug 2016 19:25:21 +0100
Paul Smith  wrote:

> Dear All,
> 
> I have just bought a monitor, which is detected by Fedora 24 as a
> 
> Goldstar company Lda 22",
> 
> but the monitor is a LG of 27".
> 
> How can this be fixed?

I am not an expert.  But this sounds like a faulty EDID, or path to
read the EDID. Fedora / linux reads the information about the monitor
directly from the monitor itself. I think this can be overridden by
putting a configuration file in /etc/X11/xorg.conf.d/ with the
information needed.  A search should turn up samples.  Is it possible
that you already have an override file there, for a 22" Goldstar
monitor?  Or that the connection to the LG is flaky, so the EDID can't
be read properly?

I vaguely recall that it is possible to dump the EDID into a file, and
point to it in the kernel start line somehow.  Could be a faulty
memory, though.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Monitor not detected correctly

[Paul Smith]

Dear All,

I have just bought a monitor, which is detected by Fedora 24 as a

Goldstar company Lda 22",

but the monitor is a LG of 27".

How can this be fixed?

Thanks in advance,

Paul
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Rick Stevens]

On 08/30/2016 03:44 PM, Ranjan Maitra wrote:
> Rick,
> 
> Thanks! 
> 
> On Tue, 30 Aug 2016 13:54:38 -0700 Rick Stevens  wrote:
> 
>>
>> I believe this is caused by the startup sequence and a "bug" in
>> nm-applet. On boot, NetworkManager (NM) is started by systemd. When you
>> log in, your desktop session starts nm-applet (it is optional after
>> all). nm-applet queries NM when nm-applet starts, gets the status and
>> tracks it as long as your session is running.
>>
>> On wake up from hibernate, nm-applet picks up where it left off, but it
>> doesn't "check in" with NM so it doesn't know what the status is. I'm
>> not sure how they coordinate (dbus, etc.), but that seems to be the
>> issue. Perhaps NM gets a different dbus identity on wakeup and
>> nm-applet doesn't find out about it. I simply don't know. I do recall
>> that on a previous version I saw errors in the system log that
>> nm-applet couldn't "find" NM for some odd reason. I don't have the
>> records any longer so I can't tell you exactly what it said, but that
>> was the gist of it.
>>
>> IMHO, nm-applet should periodically query NM and, if it doesn't get a
>> response, restart itself. If it still doesn't get a response, then it
>> should pop up an error message about it (e.g. that NM isn't running or
>> some such thing).
> 
> Your explanation may be right, but I wonder why this problem has only 
> happened to me with F24 systems. This problem did not happen with F23 
> installations. So, unless this bug recently came in, then I don't know why it 
> worked just fine with the old setup.

I had issues with F23 doing this on occasion. I believe it was a point
where NM had been updated but nm-applet hadn't caught up yet. I don't
recall exactly. Had similar issues with bluetooth (those were definitely
dbus-related).

> Btw, assuming that this is a bug, where should I file it? Before that, I 
> should perhaps make sure and look at the logs that you talked about here? 
> Which logs should I check?

I'd assume the bug should be filed against both NM and nm-applet since
it's some sort of mis-interaction between them and it's not clear whose
mechanism should be followed. As far as logs, I'd check both dmesg and
the system log for things containing "network".
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- IGNORE that man behind the keyboard!   -
-- The Wizard of OS  -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Browser Privacy

[Christian Stadelmann]

Thanks for sharing this!

Some more addons I use:
1. HTTPS Everywhere – force-redirects to HTTPS on a list (whitelist) of known 
sites. Doesn't break much stuff. I think this is a must-have.
2. RequestPolicyContinued – can be configured to disable _all_ requests from 
any server but the page source host. This preference is pretty safe but breaks 
_lots_ and *lots* of pages. In contrast to uBlock Origin (which does 
blacklisting, same as AdBlock and other ad blockers) this addon can do 
whitelisting. Better protection, more sites break.
3. CanvasBlocker – blocks canvas elements used to track you.

More addons, not security-related:
* Config Descriptions – for heavy users of about:config

Video without flash:
I highly recommend you don't use any plugins in firefox, not only for security 
reasons but also for safety (crashers!) reasons. You won't need flash on many 
sites anyway.

You probably should disable search suggestions too, because due to correlations 
on your typing frequency you could be tracked even through "anonymizing" search 
engines like DuckDuckGo.

The Firefox-inside-VM sounds like [Qubes 
OS](https://en.wikipedia.org/wiki/Qubes_OS) to me, maybe that's of interest for 
you. Since you're not saving any history at all, why don't you use the tor 
browser? It has some more very nice anti-tracking features btw.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Greg Woods]

On Tue, Aug 30, 2016 at 6:05 PM, Doug H. 
wrote:

> While waiting for a bug fix, you might try setting up a post hybernate
> action.
>

I have done something similar myself. I use ipsec-tools based VPN, and this
has never properly recovered from a hibernate without a restart. I also
have one to kill all my ssh sessions; I am a server administrator by trade,
so I usually have several ssh sessions to different hosts open, and if I
don't kill the ssh before hibernate, I wind up with a bunch of hung windows
on resume that I then have to close manually.

--Greg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Copr builds for Fedora 25?

[Patrick O'Callaghan]

On Wed, 2016-08-31 at 17:28 +0100, Richard W.M. Jones wrote:
> I see in the settings of my Copr repository that Fedora 25 isn't
> available.  Of course F25 is only in Alpha at the moment, but there is
> a Fedora Rawhide option, which is even more "alpha" than F25.
> 
> Importantly this means I cannot build nor install the packages on the
> Fedora 25 Alpha server that I just set up.
> 
> Could F25 be added earlier?  Perhaps when it branches?

Wrong list. Please take F25 questions to the Test list.

poc
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora in the Middle Kingdom

[Patrick O'Callaghan]

On Wed, 2016-08-31 at 08:48 -0700, Sherman Grunewagen wrote:
> I may soon be living in China, and wanted to ask those
> with experience what VPN they've found that
> works best to get through the GFC.  I've done some research
> on my own, and one name keeps coming up---ExpressVPN.  But
> I would like your opinions, esp. as it relates to Fedora.
> (I'm running 21.)

F21 is over a year out of date and lacks recent security patches, so
better start with a supported version before doing anything else.

poc
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Copr builds for Fedora 25?

[Richard W.M. Jones]

I see in the settings of my Copr repository that Fedora 25 isn't
available.  Of course F25 is only in Alpha at the moment, but there is
a Fedora Rawhide option, which is even more "alpha" than F25.

Importantly this means I cannot build nor install the packages on the
Fedora 25 Alpha server that I just set up.

Could F25 be added earlier?  Perhaps when it branches?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Fedora in the Middle Kingdom

[Sherman Grunewagen]

I may soon be living in China, and wanted to ask those
with experience what VPN they've found that
works best to get through the GFC.  I've done some research
on my own, and one name keeps coming up---ExpressVPN.  But
I would like your opinions, esp. as it relates to Fedora.
(I'm running 21.)

Thanks!
Sherman
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

F24: wakeup multiple screen config random

[Neal Becker]

Congratulations are in order!  It has long been believed that truly random 
sequences can't be produced by deterministic machines, but this has now been 
demonstrated.  Every time my laptop wakes up, it's screen config is 
different (multiple screens).  Including the presence and locations of any 
panels. I set it for external monitor right-of laptop, but when it wakes it
could be any of:
monitor off
any random geometric arrangement
and this morning: clone 
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org