Re: VirtualBox does not work after selinux update

2017-02-26 Thread Ed Greshko
On 02/27/17 04:42, Ed Greshko wrote: > On 02/26/17 23:15, Paul Smith wrote: >> Let me add that I am using Oracle VirtualBox (from >> http://www.virtualbox.org/): >> >> VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 > As am I > > The procedure I gave you will get you going as I did me. > > I'll

Re: VirtualBox does not work after selinux update

2017-02-26 Thread Ed Greshko
On 02/26/17 23:15, Paul Smith wrote: > Let me add that I am using Oracle VirtualBox (from > http://www.virtualbox.org/): > > VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 As am I The procedure I gave you will get you going as I did me. I'll report this against selinux soon. -- Fedora Use

Re: running ssh/remote cmd in the background

2017-02-26 Thread bruce
Hey Jon... You are absolutely correct.. if the parent ssh terminates.. the remote process would "die".. In my use case, the remote process being fired off is actually being run under a remote "Screen" session, so it had better survive the ssh terminating!! (In testing, this has worked, so I have n

Re: running ssh/remote cmd in the background

2017-02-26 Thread Jon LaBadie
On Sun, Feb 26, 2017 at 06:40:50PM +0100, Joachim Backes wrote: > On 02/26/17 18:08, bruce wrote: > > Morn guys... > > > > The following works as a test ssh to fire off a remote cmd. However it > > waits for the cmd to complete befor returning. I'm looking to run th > > cmd as a background on the

Dual booting with external drive

2017-02-26 Thread Patrick O'Callaghan
I have a new USB3 drive and would like to install Windows on one partition of it for occasional dual booting. I already have F25 on my main drives (root on a 128GB SSD and /home on a 1TB internal SATA) so the usual advice of "install Windows first, then Linux" is not really what I want to hear unle

Re: running ssh/remote cmd in the background

2017-02-26 Thread Joachim Backes
On 02/26/17 18:08, bruce wrote: Morn guys... The following works as a test ssh to fire off a remote cmd. However it waits for the cmd to complete befor returning. I'm looking to run th cmd as a background on the local/calling instance. Ultimaely, I'll be testing this from py/php scripts. ssh -t

running ssh/remote cmd in the background

2017-02-26 Thread bruce
Morn guys... The following works as a test ssh to fire off a remote cmd. However it waits for the cmd to complete befor returning. I'm looking to run th cmd as a background on the local/calling instance. Ultimaely, I'll be testing this from py/php scripts. ssh -t user1@67.205.151.05 'cat /cloud/h

Re: Boot F25 live media in text mode

2017-02-26 Thread Ahmad Samir
On 26 February 2017 at 15:44, Ian Pilcher wrote: > On 02/25/2017 08:46 PM, Ed Greshko wrote: >> >> Sorry Forgot to mention, I think this only works with the "netinst" >> image and not the live one. > > > Yeah. I found various links on how to do a text mode install, but > bupkis on booting li

Re: VirtualBox does not work after selinux update

2017-02-26 Thread Paul Smith
On Sun, Feb 26, 2017 at 2:27 PM, Paul Smith wrote: >>> After doing the updates of today (selinux included), virtualbox stopped working: # /usr/lib/virtualbox/vboxdrv.sh setup vboxdrv.sh: Building VirtualBox kernel modules. vboxdrv.sh: Starting VirtualBox services. >>

Re: VirtualBox does not work after selinux update

2017-02-26 Thread Ed Greshko
On 02/26/17 22:27, Paul Smith wrote: > But after doing > > dnf --allowerasing downgrade selinux-policy selinux-policy-targeted > > the reported problem disappears. I just wanted to add to what I just posted. The system I thought was fully updated wasn't. After updating to the latest selinux

Re: VirtualBox does not work after selinux update

2017-02-26 Thread Ed Greshko
On 02/26/17 22:27, Paul Smith wrote: > But after doing > > dnf --allowerasing downgrade selinux-policy selinux-policy-targeted > > the reported problem disappears. OK Then, after upgrading the selinux again and rebooting or rmmod what is already loaded Try ausearch -c 'modprobe' --raw |

Re: VirtualBox does not work after selinux update

2017-02-26 Thread Paul Smith
On Sun, Feb 26, 2017 at 2:18 PM, Paul Smith wrote: >> >>> After doing the updates of today (selinux included), virtualbox stopped >>> working: >>> >>> # /usr/lib/virtualbox/vboxdrv.sh setup >>> vboxdrv.sh: Building VirtualBox kernel modules. >>> vboxdrv.sh: Starting VirtualBox services. >>> vboxd

Re: VirtualBox does not work after selinux update

2017-02-26 Thread Paul Smith
On Sun, Feb 26, 2017 at 12:32 PM, Ed Greshko wrote: > >> After doing the updates of today (selinux included), virtualbox stopped >> working: >> >> # /usr/lib/virtualbox/vboxdrv.sh setup >> vboxdrv.sh: Building VirtualBox kernel modules. >> vboxdrv.sh: Starting VirtualBox services. >> vboxdrv.sh:

Re: Boot F25 live media in text mode

2017-02-26 Thread Ian Pilcher
On 02/25/2017 08:46 PM, Ed Greshko wrote: Sorry Forgot to mention, I think this only works with the "netinst" image and not the live one. Yeah. I found various links on how to do a text mode install, but bupkis on booting live media in text mode. Uugh! Ultimately, I ended up doing a VNC

Re: VirtualBox does not work after selinux update

2017-02-26 Thread Ed Greshko
On 02/26/17 19:37, Paul Smith wrote: > After doing the updates of today (selinux included), virtualbox stopped > working: > > # /usr/lib/virtualbox/vboxdrv.sh setup > vboxdrv.sh: Building VirtualBox kernel modules. > vboxdrv.sh: Starting VirtualBox services. > vboxdrv.sh: Building VirtualBox kerne

VirtualBox does not work after selinux update

2017-02-26 Thread Paul Smith
Dear All, After doing the updates of today (selinux included), virtualbox stopped working: # /usr/lib/virtualbox/vboxdrv.sh setup vboxdrv.sh: Building VirtualBox kernel modules. vboxdrv.sh: Starting VirtualBox services. vboxdrv.sh: Building VirtualBox kernel modules. vboxdrv.sh: failed: modprobe