Re: DKMS not Issuing Modprobe After Driver Compile at Boot Time

2017-02-12 Thread Ed Greshko
On 02/13/17 11:43, Ed Greshko wrote: > I have done some checking and have yet to determine why dkms feels the > need to rebuild the modules. > > Does the module loading succeed on subsequent boots? Well, my knowledge seems "Out of Date". Even though the additions install process mentions "dkms"

Re: sed question!

2017-02-12 Thread Jon LaBadie
On Sun, Feb 12, 2017 at 08:06:28PM -0500, bruce wrote: > Hey guys. > > Thanks for the delete replies.. > > Got a quick sed question now.. > > test file:: > head -2 sed.dat > 228d98f0_f16a_11e6_9544_1ad613f05f7b,1486934882 > 22b93712_f16a_11e6_a6ad_1ad613f05f7b,1486934883 > > want to simply tru

Re: DKMS not Issuing Modprobe After Driver Compile at Boot Time

2017-02-12 Thread Ed Greshko
On 02/13/17 05:14, Stephen Morris wrote: > To test out dkms compiling and installing my wifi driver I have > uninstalled the driver from the kernel with dkms, removed the driver > from dkms and re-added the driver to dkms. > > When I boot Fedora dkms compiles and installs the driver into t

Re: sed question!

2017-02-12 Thread Steve Forsythe
On 02/12/2017 08:06 PM, bruce wrote: > Hey guys. > > Thanks for the delete replies.. > > Got a quick sed question now.. > > test file:: > head -2 sed.dat > 228d98f0_f16a_11e6_9544_1ad613f05f7b,1486934882 > 22b93712_f16a_11e6_a6ad_1ad613f05f7b,1486934883 > > want to simply truncate/search/repla

Re: sed question!

2017-02-12 Thread Clifford Snow
I'm a awk user. cat sed.dat | awk -F"," '{print $1}' or awk -F"," '{print $1}' sed.dat On Sun, Feb 12, 2017 at 5:06 PM, bruce wrote: > Hey guys. > > Thanks for the delete replies.. > > Got a quick sed question now.. > > test file:: > head -2 sed.dat > 228d98f0_f16a_11e6_9544_1ad613f05f7b,1486

Re: sed question!

2017-02-12 Thread Fred Smith
On Sun, Feb 12, 2017 at 08:06:28PM -0500, bruce wrote: > Hey guys. > > Thanks for the delete replies.. > > Got a quick sed question now.. > > test file:: > head -2 sed.dat > 228d98f0_f16a_11e6_9544_1ad613f05f7b,1486934882 > 22b93712_f16a_11e6_a6ad_1ad613f05f7b,1486934883 > > want to simply tru

Re: sed question!

2017-02-12 Thread Gordon Messmer
On 02/12/2017 05:06 PM, bruce wrote: the following isn't working sed -i 's/\,+$//' sed.da That would remove one or more commas, if they immediately precede the end of the line. You mean: sed 's/,.*$//' or: cut -f1 -d, ___ users mailing list

sed question!

2017-02-12 Thread bruce
Hey guys. Thanks for the delete replies.. Got a quick sed question now.. test file:: head -2 sed.dat 228d98f0_f16a_11e6_9544_1ad613f05f7b,1486934882 22b93712_f16a_11e6_a6ad_1ad613f05f7b,1486934883 want to simply truncate/search/replace the end of each line starting with the "," to get 228d98f

DKMS not Issuing Modprobe After Driver Compile at Boot Time

2017-02-12 Thread Stephen Morris
Hi, To test out dkms compiling and installing my wifi driver I have uninstalled the driver from the kernel with dkms, removed the driver from dkms and re-added the driver to dkms. When I boot Fedora dkms compiles and installs the driver into the kernel but it does not issue a modprob

Re: remove/delete files with dots "." in the name..

2017-02-12 Thread Stephen Morris
On 11/02/2017 22:24, bruce wrote: Hi. Test file with a name of: 67.205.168.80_PID.dat find . -name '*.dat' -exec ls {} \; displays the file but find . -name '*.dat' -exec rm -f {} \; doesn't delete it. thoughts? Just a thought, does the delete fail because your userid doesn't have enough ac

Re: Fedora 24 Update: nitrokey-app-0.6.3-1.fc24

2017-02-12 Thread Kevin Fenzi
On Sat, 11 Feb 2017 16:03:37 +1030 Tim wrote: > Allegedly, on or about 09 February 2017, Kevin Fenzi sent: > > Unfortunately, it's kind of subjective what a good summary / > > description would be. Perhaps the guideline could say "Describe what > > the package is as if to someone who had no idea

Re: remove/delete files with dots "." in the name..

2017-02-12 Thread Ahmad Samir
On 11 February 2017 at 14:24, bruce wrote: > Hi. > > Test file with a name of: > > 67.205.168.80_PID.dat > > find . -name '*.dat' -exec ls {} \; > displays the file > > but > find . -name '*.dat' -exec rm -f {} \; > doesn't delete it. > > thoughts? > I am not sure this is the problem, but I alway