[CentOS] Update to 3.10.0-693.17.1 breaks ath5k

2018-02-02 Thread Stephen Davies

Where can I find a suitable module or even source code to build here?

(Centos 7)

Cheers and thanks,
Stephen
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Error installing Nvidia driver on a 7.5 beta kernel

2018-02-02 Thread Phil Perry

On 02/02/18 17:32, James Pearson wrote:

Phil Perry wrote:


It looks like a regression. This was originally fixed upstream
(kernel.org) 3 years ago, so if the RHEL7.5 beta kernel has reverted to
'EXPORT_SYMBOL_GPL' then it is a regression that will break building any
out-of-tree non-gpl modules which need to set caching mode in pte's

You should file a bug report with Red Hat.

The correct fix in the kernel is in arch/x86/mm/init.c

-EXPORT_SYMBOL_GPL(__cachemode2pte_tbl);
+EXPORT_SYMBOL(__cachemode2pte_tbl);


Well, that's the rub - RHEL7 have never had that upstream fix - i.e. the
el7.4 kernel (3.10.0-693.el7) has
'EXPORT_SYMBOL_GPL(__cachemode2pte_tbl)' as does the el7.5b kernel
(3.10.0-830.el7) ...

The Nvidia driver builds/installs OK on el7.4 - but not on el7.5b

I'll report this to Red Hat anyway ...

Thanks

James Pearson



Ah, I'd not checked the sources, you are correct. I do not have an 
explanation for the differing behaviour between 7.4 and 7.5beta.


It looks like both __cachemode2pte_tbl and __pte2cachemode_tbl need 
updating in arch/x86/mm/init.c


If you file a bug, please could you mail the link so I can add myself to 
the CC. Thanks.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Anyone using GQRX in Centos-7, for SDR ?

2018-02-02 Thread Fred Smith
On Fri, Feb 02, 2018 at 09:38:17AM +, Nux! wrote:
> Is it a Realtek chipset?

yes it is.

> I've had problems with it on CentOS as the system will load up the DVB 
> drivers (for TV tuner) thus interfering with the SDR.
> What worked for me is blacklisting them & reboot. Give it a try.

Ah, thanks, that's the trick. works now.

> 
> cat /etc/modprobe.d/blacklist_rtl.conf 
> blacklist dvb_usb_rtl28xxu 
> blacklist rtl2832 
> blacklist rtl2830
> 
> BTW there's a new package at http://li.nux.ro/download/nux/tmp/gqrx7/ if you 
> care to test and confirm success so I can move it to the main repo.

I've installed it and it seems to be working fine (based on about 20
minutes of use, and note that I"m not an expert yet).

thanks!

> Nux!
> www.nux.ro
> 
> - Original Message -
> > From: "Fred Smith" 
> > To: "CentOS mailing list" 
> > Sent: Thursday, 1 February, 2018 22:38:09
> > Subject: [CentOS] Anyone using GQRX in Centos-7, for SDR ?
> 
> > I gave myself a toy, one of those cheap USB Software Define Radios, and
> > would like to use it on my C7 box. Having wasted some time on it, I gave
> > up and installed Ubuntu on a USB HD so I can boot that to play with SDR.
> > The Ubuntu GQRX installation is well documented and went off without a 
> > hitch.
> > but I just hate having to boot something else on my main box (partly because
> > it also runs a mailserver for my personal domain, partly because, well,
> > I just want my box running CentOS, not Ubuntu.)
> > 
> > Searching through SDR info on line I see someone has documented installing
> > all the bits for C6, but I suspect the process is different for C7.
> > 
> > BTW, I installed the various bits I could find from, er, I think some
> > came from li.nux.ro, some perhaps from epel, on C7, but couldn't get
> > them to properly function.
> > 
> > Worse, when the USB radio is unplugged from the system, it locks up hard.
> > 
> > then a few days ago, I  had been playing with it using the UBUNTU install,
> > did a reboot and for kicks fired up the GQRX on Centos, and lo and behold
> > it worked! I tried running it on Centos yesterday and it reverted to type,
> > i.e., lock up hard. I suspect that Ubuntu is leaving some hardware in a
> > state that allows it to work on a subsequent Centos boot (without poweroff),
> > but no clue what.
> > 
> > So, if anyone can point me to how  to use it on C7, I'd greatly appreciate 
> > it.
> > 
> > thanks in advance!
> > 
> > Fred
> > --

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
   I can do all things through Christ 
  who strengthens me.
-- Philippians 4:13 ---
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Software does not boot in Secure Boot

2018-02-02 Thread Mikhail Utin
The matter of EUFI’s Secure Boot vs Legacy Boot has been briefly discussed a 
couple of days ago. I would ask the List opinion concerning our case.

A bit of the history. We’ve been in the research of malicious hypervisor threat 
since 2013. We finally developed publicly available HyperCatcher freeware. It 
runs on specially built Ubuntu 14.4. We tried CentOS 6/7 as well.  The OS was 
compiled to minimize the number of services and OS features to only essential 
to the application. The software is ISO bootable image.

The problem.  As of today, we recommend to switch to Legacy option before 
booting. Our attempts to find out how to boot in Secure were unsuccessful. I 
believe that it is not possible if Secure Boot functions correctly. Does 
anybody know (excepting hacking the UEFI firmware and utilizing nice 0-day) if 
boot-up is still possible in Secure Boot? We tried so far a few Dell models. 
What could we add in bootable image so Secure Boot considered it as OK?

There is yet another small issue of Ubuntu output messages while booting, which 
you could see is you try to use and boot our software. Such “leftovers” are not 
really important but a bit disturbing people who use our software. Is there 
anything like compilation option etc. we can use to block Ubuntu boot-up screen 
output?

One technical note on our research. We experimented with VMware hypervisor 
(CentOS 6/7 and Ubuntu 14 OS as operating environment as well). The conclusion 
is that well-designed hypervisor adds less than one percent (0.7% in most 
cases) of current CPU utilization. For instance, 100% utilization means 99.3% 
user software and 0.7% the hypervisor. You can use your system for years but 
will never notice that a hypervisor runs below your OS. It can come from 
anywhere and even from your motherboard firmware.



Mikhail Utin, CISSP

Rubos, Inc.

mu...@rubos.com

mikhailutin@!hotmail.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS-es] Iptables + hashlimit OT

2018-02-02 Thread César Martinez M .

Saludos amigos listeros, espero todos se encuentren bien

Tengo un requerimiento de ver si se puede segmentar el consumo de 
internet, para ello me puse a investigar un poco en la red y encontré 
que se puede usar iptables + hashlimit para ello, no he encontrado mayor 
información de pronto alguien ha tenido experiencia con esto o me pueden 
sugerir con que herramienta se podría realizar esto de una forma fácil 
para que un usuario de pronto pueda administrarlo vis gráfica o a través 
de webmin. La idea seria por ejemplo no restringir el uso del youtube 
pero que no se consuma todo el ancho de banda.


Gracias a todos


--
|Saludos Cordiales
|César Martínez M. | Ingeniero de Sistemas
|Consultor & Proyectos Software Libre| SERVICOM
|Teléfono: (593-2)554-271 2221-386 | Ext 4501
|Celular:593 999374317 |Skype servicomecuador
|Web www.servicomecuador.com Síguenos en:
|Twitter: @servicomecuador |Facebook: servicomec
|Zona Clientes: www.servicomecuador.com/billing
|Blog: http://servicomecuador.com/blog
|Dir. Av. 10 de Agosto N29-140 Entre
|Acuña y  Cuero y Caicedo
|Quito - Ecuador - Sudamérica

___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es


Re: [CentOS] Slightly OT : newsletters, mail formatting and netiquette

2018-02-02 Thread Nicolas Kovacs
Le 02/02/2018 à 16:03, Mikhail Utin a écrit :
> The same story is in OS desktop GUI including Linux. I use CentOS 6
> and 7 and still do not like 7. Not to mention in the morning Win 10
> with all its crap included.

On a side note, I've written a complete post-install script for CentOS 7
and an Xfce-based bells-and-whistles desktop that starts from a minimal
installation.

https://blog.microlinux.fr/poste-de-travail-xfce-centos-7/

And here's the script:

https://github.com/kikinovak/centos-7-desktop-xfce

Cheers,

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site : https://www.microlinux.fr
Blog : https://blog.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Allowing non-root users to reboot a workstation

2018-02-02 Thread m . roth
Felipe Westfields wrote:
> I would like to be able to allow regular users that don't have admin
> privileges to be able to reboot their workstation. (they're software
> developers so rebooting their workstation doesn't affect anybody else)
>
> I tried changing the ownership of /sbin/reboot and /sbin/shutdown to
> root:users and permissions to 550, but that didn't work - it's still
> asking
> for root privileges.
>
> Possibly the problem might be that there's centralized LDAP
> authentication, not local, so the changes I made only apply to
> local accounts?
>
> Any suggestions?

Um, I take it that a three-finger kill doesn't work?

   mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Allowing non-root users to reboot a workstation

2018-02-02 Thread Marcin Trendota
W dniu 02.02.2018 o 18:27, Felipe Westfields pisze:
> That seems to have worked on my own test account - I applied it to the user
> having the issue and asked for his feedback when he gets a chance.
> Thanks!
> On Fri, Feb 2, 2018 at 11:40 AM, Darr247  wrote:
>> Did you try adding
>> UserName ALL= NOPASSWD: /sbin/reboot
>> As the last line of their /etc/sudoers files?
>> (replacing UserName with their actual user name, of course.)
>> That should grant them root access to only the /sbin/reboot command (add
>> more commands using comma delimiting).


It may be more appropriate to place this line in separate file under
/etc/sudoers.d/

-- 
MoonWolf

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS-virt] kernel-ml-4.15.0-1.el7.elrepo.x86_64 doesn't boot as Xen PV domU

2018-02-02 Thread Karl Johnson
Hello,

I can also reproduce with Xen 4.8.2-10.el6:

(XEN) d6v0: unhandled page fault (ec=)
(XEN) Pagetable walk from 0028:
(XEN)  L4[0x000] =  
(XEN) domain_crash_sync called from entry.S: fault at 82d08023d440
cpufreq.c#create_bounce_frame+0x137/0x146
(XEN) Domain 6 (vcpu#0) crashed on cpu#8:
(XEN) [ Xen-4.8.2-10.el6  x86_64  debug=n   Not tainted ]
(XEN) CPU:8
(XEN) RIP:e033:[]
(XEN) RFLAGS: 0292   EM: 1   CONTEXT: pv guest (d6v0)
(XEN) rax:    rbx: 81e05720   rcx: 
(XEN) rdx: 0030   rsi: 82203efc   rdi: 8241d460
(XEN) rbp: 82203ec8   rsp: 82203e10   r8:  
(XEN) r9:  82203f00   r10:    r11: 82203f04
(XEN) r12: 82203e78   r13: 82203e7c   r14: 82203e80
(XEN) r15: 82203e84   cr0: 8005003b   cr4: 26e0
(XEN) cr3: 000c15f0d000   cr2: 0028
(XEN) ds:    es:    fs:    gs:    ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=82203e10:
(XEN) 82203f04  8103f261
(XEN)0001e030 00010092 82203e58 e02b
(XEN) 8241d460  
(XEN)   
(XEN)  8241d460 82203f04
(XEN)82203f00 82203efc 82203ef8 82203f40
(XEN)8103fce6 82203f14 82203f10 82203f0c
(XEN)82203f08 3028  8008
(XEN)   
(XEN)  82203ff8 8246c490
(XEN)   
(XEN)   
(XEN)   
(XEN)   
(XEN)   
(XEN)  0f0060c0c748 c305
(XEN)   
(XEN)   
(XEN)   
(XEN)   

Karl

On Tue, Jan 30, 2018 at 7:01 PM, Adi Pircalabu  wrote:

> Replicated on another Xen node, CentOS 6.9 running Xen-4.6.6-8.el6. xl
> dmesg:
> (XEN) d38v0: unhandled page fault (ec=)
> (XEN) Pagetable walk from 0028:
> (XEN) L4[0x000] =  
> (XEN) domain_crash_sync called from entry.S: fault at 82d080230983
> create_bounce_frame+0x12b/0x13a
> (XEN) Domain 38 (vcpu#0) crashed on cpu#2:
> (XEN) [ Xen-4.6.6-8.el6 x86_64 debug=n Not tainted ]
> (XEN) CPU: 2
> (XEN) RIP: e033:[]
> (XEN) RFLAGS: 0292 EM: 1 CONTEXT: pv guest (d38v0)
> (XEN) rax:  rbx: 81e05720 rcx: 
> (XEN) rdx: 0030 rsi: 82203efc rdi: 8241d460
> (XEN) rbp: 82203ec8 rsp: 82203e10 r8: 
> (XEN) r9: 82203f00 r10:  r11: 82203f04
> (XEN) r12: 82203e78 r13: 82203e7c r14: 82203e80
> (XEN) r15: 82203e84 cr0: 8005003b cr4: 000426e4
> (XEN) cr3: 00049c571000 cr2: 0028
> (XEN) ds:  es:  fs:  gs:  ss: e02b cs: e033
> (XEN) Guest stack trace from rsp=82203e10:
> (XEN)  82203f04  8103f261
> (XEN) 0001e030 00010092 82203e58 e02b
> (XEN)  8241d460  
> (XEN)    
> (XEN)   8241d460 82203f04
> (XEN) 82203f00 82203efc 82203ef8 82203f40
> (XEN) 8103fce6 82203f14 82203f10 82203f0c
> (XEN) 82203f08 3026  8008
> (XEN)    
> (XEN)   82203ff8 8246c490
> (XEN)    
> (XEN)    
> (XEN)    
> (XEN)    
> (XEN) 

Re: [CentOS] Error installing Nvidia driver on a 7.5 beta kernel

2018-02-02 Thread James Pearson
Phil Perry wrote:
> 
> It looks like a regression. This was originally fixed upstream
> (kernel.org) 3 years ago, so if the RHEL7.5 beta kernel has reverted to
> 'EXPORT_SYMBOL_GPL' then it is a regression that will break building any
> out-of-tree non-gpl modules which need to set caching mode in pte's
> 
> You should file a bug report with Red Hat.
> 
> The correct fix in the kernel is in arch/x86/mm/init.c
> 
> -EXPORT_SYMBOL_GPL(__cachemode2pte_tbl);
> +EXPORT_SYMBOL(__cachemode2pte_tbl);

Well, that's the rub - RHEL7 have never had that upstream fix - i.e. the 
el7.4 kernel (3.10.0-693.el7) has 
'EXPORT_SYMBOL_GPL(__cachemode2pte_tbl)' as does the el7.5b kernel 
(3.10.0-830.el7) ...

The Nvidia driver builds/installs OK on el7.4 - but not on el7.5b

I'll report this to Red Hat anyway ...

Thanks

James Pearson
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Allowing non-root users to reboot a workstation

2018-02-02 Thread Felipe Westfields
That seems to have worked on my own test account - I applied it to the user
having the issue and asked for his feedback when he gets a chance.

Thanks!

On Fri, Feb 2, 2018 at 11:40 AM, Darr247  wrote:

> Did you try adding
>
> UserName ALL= NOPASSWD: /sbin/reboot
>
> As the last line of their /etc/sudoers files?
> (replacing UserName with their actual user name, of course.)
>
> That should grant them root access to only the /sbin/reboot command (add
> more commands using comma delimiting).
>
> Then they just run
> $ sudo reboot
>
>
> If you want to require they enter their own password before rebooting, use
> the line
>
> UserName ALL=/sbin/reboot
>
> Instead.
>
> Use of sudo is recorded in /var/log/secure, if I recall correctly.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Allowing non-root users to reboot a workstation

2018-02-02 Thread Valeri Galtsev



On 02/02/18 10:09, Felipe Westfields wrote:

I would like to be able to allow regular users that don't have admin
privileges to be able to reboot their workstation. (they're software
developers so rebooting their workstation doesn't affect anybody else)

I tried changing the ownership of /sbin/reboot and /sbin/shutdown to
root:users and permissions to 550, but that didn't work - it's still asking
for root privileges.

Possibly the problem might be that there's centralized LDAP authentication,
not local, so the changes I made only apply to local accounts?

Any suggestions?


If they are local users (sitting in front of that computer), they will 
be able to use the commands


shutdown
reboot
poweroff

without any need of special privileges, which tells RedHat and CentOS 
apart from majority of Linuxes. This is incredibly logical (Thanks, 
RedHat!), as local user can just press power button, or yank AC cord.


To allow remote users reboot machine you can allow them execute some 
commands via sudo , like:


sudo reboot

Command sudo means Substitute User DO; when username of substitute user 
is not mentioned in command user "root: is used as substitute user, this 
is where misinterpreting the command as "super user do" originates, and 
the last is wrong. Do "man visudo", "man sudo", to learn details.


Incidentally, rebooting machine is rather big deal, if that is used to 
resolve some trouble happening every so often, I would rather look into 
fixing the cause of that trouble.


Valeri



FW
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



--

Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Allowing non-root users to reboot a workstation

2018-02-02 Thread Tate Belden
Personally, this is what I'd use sudo for.

You can configure sudo to allow only certain commands with or without a
password. Not a lot of detail, but you can either require or skip the
password. And, instead of individuals - you can use groups. If you look
through the soders file, you'll see how it's doen.

This very brief article goes into a limited how-to:

http://www.atrixnet.com/allow-an-unprivileged-user-to-run-a-certain-command-with-sudo/

On Fri, Feb 2, 2018 at 9:09 AM, Felipe Westfields <
felipe.westfie...@gmail.com> wrote:

> I would like to be able to allow regular users that don't have admin
> privileges to be able to reboot their workstation. (they're software
> developers so rebooting their workstation doesn't affect anybody else)
>
> I tried changing the ownership of /sbin/reboot and /sbin/shutdown to
> root:users and permissions to 550, but that didn't work - it's still asking
> for root privileges.
>
> Possibly the problem might be that there's centralized LDAP authentication,
> not local, so the changes I made only apply to local accounts?
>
> Any suggestions?
>
> FW
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



-- 
Natrona County Beekeepers 
Casper Amateur Radio Club 

By sending an email to or replying in any way to ANY of my addresses,
numbers, comments or messages, you are agreeing that:
1. I am, by definition, "the intended recipient" - in spite of and
regardless of your intent, real or imaginary.
2. If you need to know that you know who is receiving your communications
and must also be able to verify they were not tampered with in any way,
while en route as well as verify receipt (but not comprehension), you must
use PKI and have a verified Public Key published in an accessible location.
NOTE: if your PKI Public Key is not signed by anyone I recognize, it will
not be trusted. Unless I choose otherwise.
2. All information in any received communication is mine to do with as I
see fit. I will make such financial gain, profit, political mileage, social
satire, public value or jokes - as it lends itself and as I choose. In
particular, I may quote it on usenet, IRC, SMS and/or future SMTP
communications, regardless of SSL or TLS implementation, not inclusive.
3. I may take the contents of your messages as representing the views of
your company, country or agency. Particularly if you've used a TLD owned by
or under control of said entity.
4. This agreement - now that you've read this far - is now a contract and
absolutely overrides any disclaimer or statement of confidentiality that
may or may not be included, implied or missing in any of your messages.
Especially as such things are meaningless, pointless and carry no weight,
authority or validity, be they mass, legal or emotional, in spite of what
your cousin said.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Allowing non-root users to reboot a workstation

2018-02-02 Thread Darr247
Did you try adding

UserName ALL= NOPASSWD: /sbin/reboot

As the last line of their /etc/sudoers files?
(replacing UserName with their actual user name, of course.)

That should grant them root access to only the /sbin/reboot command (add
more commands using comma delimiting).

Then they just run
$ sudo reboot


If you want to require they enter their own password before rebooting, use
the line

UserName ALL=/sbin/reboot

Instead.

Use of sudo is recorded in /var/log/secure, if I recall correctly.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Error installing Nvidia driver on a 7.5 beta kernel

2018-02-02 Thread Phil Perry

On 02/02/18 15:30, James Pearson wrote:

OK, I know CentOS has nothing to do with RHEL beta releases, but I
wanted to test if el7.5 has added support for a particular peripheral
(Wacom Pro 2 tablet) ... but was unable to install the propriety Nvidia
display driver (v390.25) on a test workstation - and was wondering if
anyone could explain on what is going on.

All I've done is upgrade an existing CentOS 7.4 install with the RHEL
7.5 beta kernel RPMS

However, when installing the Nvidia driver, it fails with:

   FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__cachemode2pte_tbl'

A bit of Googling seems to suggest that this issue has been 'fixed' in
later upstream kernels by changing the export of this symbol from
'EXPORT_SYMBOL_GPL' to 'EXPORT_SYMBOL'

However, 7.4 and earlier el7 kernels also export this symbol as
EXPORT_SYMBOL_GPL - but the Nvidia driver builds/installs fine on 7.4
kernels ...

So, I'm not really sure what the issue is - i.e. is it an Nvidia or
Redhat issue ?



It looks like a regression. This was originally fixed upstream 
(kernel.org) 3 years ago, so if the RHEL7.5 beta kernel has reverted to 
'EXPORT_SYMBOL_GPL' then it is a regression that will break building any 
out-of-tree non-gpl modules which need to set caching mode in pte's


You should file a bug report with Red Hat.


For now, I've managed to hack around this by patching the stub Nvidia
driver src to change MODULE_LICENSE from "NVIDIA" to "GPL" - and the
Nvidia driver now installs and loads OK



The correct fix in the kernel is in arch/x86/mm/init.c

-EXPORT_SYMBOL_GPL(__cachemode2pte_tbl);
+EXPORT_SYMBOL(__cachemode2pte_tbl);


If anyone knows any more about this, then please let me know

Thanks

James Pearson


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Allowing non-root users to reboot a workstation

2018-02-02 Thread Felipe Westfields
I would like to be able to allow regular users that don't have admin
privileges to be able to reboot their workstation. (they're software
developers so rebooting their workstation doesn't affect anybody else)

I tried changing the ownership of /sbin/reboot and /sbin/shutdown to
root:users and permissions to 550, but that didn't work - it's still asking
for root privileges.

Possibly the problem might be that there's centralized LDAP authentication,
not local, so the changes I made only apply to local accounts?

Any suggestions?

FW
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Error installing Nvidia driver on a 7.5 beta kernel

2018-02-02 Thread James Pearson
OK, I know CentOS has nothing to do with RHEL beta releases, but I 
wanted to test if el7.5 has added support for a particular peripheral 
(Wacom Pro 2 tablet) ... but was unable to install the propriety Nvidia 
display driver (v390.25) on a test workstation - and was wondering if 
anyone could explain on what is going on.

All I've done is upgrade an existing CentOS 7.4 install with the RHEL 
7.5 beta kernel RPMS

However, when installing the Nvidia driver, it fails with:

  FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'__cachemode2pte_tbl'

A bit of Googling seems to suggest that this issue has been 'fixed' in 
later upstream kernels by changing the export of this symbol from 
'EXPORT_SYMBOL_GPL' to 'EXPORT_SYMBOL'

However, 7.4 and earlier el7 kernels also export this symbol as 
EXPORT_SYMBOL_GPL - but the Nvidia driver builds/installs fine on 7.4 
kernels ...

So, I'm not really sure what the issue is - i.e. is it an Nvidia or 
Redhat issue ?

For now, I've managed to hack around this by patching the stub Nvidia 
driver src to change MODULE_LICENSE from "NVIDIA" to "GPL" - and the 
Nvidia driver now installs and loads OK

If anyone knows any more about this, then please let me know

Thanks

James Pearson
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Slightly OT : newsletters, mail formatting and netiquette

2018-02-02 Thread Mikhail Utin
I would prefer simple text in tech and security related news but you are right 
- they are HTML formatted. I think it is pure marketing thing. people dump 
other stuff to remind you who they are and for a sort of entertaining us.

The same story is in OS desktop GUI including Linux. I use CentOS 6 and 7 and 
still do not like 7. Not to mention in the morning Win 10 with all its crap 
included.


Mikhail Utin



From: CentOS  on behalf of Nicolas Kovacs 

Sent: Friday, February 2, 2018 04:36
To: centos@centos.org
Subject: [CentOS] Slightly OT : newsletters, mail formatting and netiquette

Hi,

This question is not exactly CentOS-related strictly speaking, but here
goes. I'm running a few newsletter servers for myself and a handful of
clients on public CentOS servers with PHPList.

For the last twenty years or so I've followed the basic rule that mails
should have no formatting whatsoever, only simple text. And now I wonder
if that basic rule of netiquette also applies to newsletters.

I'm a subscriber to a series of tech-related newsletters, and I couldn't
help but notice that they all seem to be HTML-formatted, even those from
respectable hardcore geek groups.

So my somewhat naive question: is HTML formatting acceptable in
newsletters?

Cheers,

Niki
--
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site : https://www.microlinux.fr
[https://s0.wp.com/i/blank.jpg]

Microlinux – Solutions informatiques durables – Linux et 
...
www.microlinux.fr
Microlinux a apporté la solution idéale pour ma société : une station de 
travail ultra-stable, avec une utilisation d’emploi très simple.



Blog : https://blog.microlinux.fr
[https://s0.wp.com/i/blank.jpg]

Le blog technique de Microlinux | Linux est long et la vie 
...
blog.microlinux.fr
Linux est long et la vie est brève



Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
CentOS Info Page
lists.centos.org
This is a General discussion list for all issues CentOS. Security updates are 
currently announced on this list once daily. This list is read and reply for 
anyone that ...



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Slightly OT : newsletters, mail formatting and netiquette

2018-02-02 Thread m . roth
Cameron Smith wrote:
> Look into mutipart and offer both html and plain text in the same email.
> This allows the client to view it as they see fit.
>
> If you do send html it has a much more restrictive implementation than
> html
> and css for a webpage so study up on what you can and can't do.
> Mailchimp has some great info about this.
>
Personally, I'd suggest giving the subscribers the *option* of either. I
really dislike HTML email, and even when I can read it, it's *really*
ugly.

But then, I also consider HTML email a *great* way to spread malware.

mark
> Cameron
>
> On Fri, Feb 2, 2018 at 1:36 AM, Nicolas Kovacs  wrote:
>
>> Hi,
>>
>> This question is not exactly CentOS-related strictly speaking, but here
>> goes. I'm running a few newsletter servers for myself and a handful of
>> clients on public CentOS servers with PHPList.
>>
>> For the last twenty years or so I've followed the basic rule that mails
>> should have no formatting whatsoever, only simple text. And now I wonder
>> if that basic rule of netiquette also applies to newsletters.
>>
>> I'm a subscriber to a series of tech-related newsletters, and I couldn't
>> help but notice that they all seem to be HTML-formatted, even those from
>> respectable hardcore geek groups.
>>
>> So my somewhat naive question: is HTML formatting acceptable in
>> newsletters?
>>
>> Cheers,
>>
>> Niki
>> --
>> Microlinux - Solutions informatiques durables
>> 7, place de l'église - 30730 Montpezat
>> Site : https://www.microlinux.fr
>> Blog : https://blog.microlinux.fr
>> Mail : i...@microlinux.fr
>> Tél. : 04 66 63 10 32
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Slightly OT : newsletters, mail formatting and netiquette

2018-02-02 Thread Cameron Smith
Look into mutipart and offer both html and plain text in the same email.
This allows the client to view it as they see fit.

If you do send html it has a much more restrictive implementation than html
and css for a webpage so study up on what you can and can't do.
Mailchimp has some great info about this.

Cameron

On Fri, Feb 2, 2018 at 1:36 AM, Nicolas Kovacs  wrote:

> Hi,
>
> This question is not exactly CentOS-related strictly speaking, but here
> goes. I'm running a few newsletter servers for myself and a handful of
> clients on public CentOS servers with PHPList.
>
> For the last twenty years or so I've followed the basic rule that mails
> should have no formatting whatsoever, only simple text. And now I wonder
> if that basic rule of netiquette also applies to newsletters.
>
> I'm a subscriber to a series of tech-related newsletters, and I couldn't
> help but notice that they all seem to be HTML-formatted, even those from
> respectable hardcore geek groups.
>
> So my somewhat naive question: is HTML formatting acceptable in
> newsletters?
>
> Cheers,
>
> Niki
> --
> Microlinux - Solutions informatiques durables
> 7, place de l'église - 30730 Montpezat
> Site : https://www.microlinux.fr
> Blog : https://blog.microlinux.fr
> Mail : i...@microlinux.fr
> Tél. : 04 66 63 10 32
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] CentOS-announce Digest, Vol 156, Issue 1

2018-02-02 Thread centos-announce-request
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2018:0260 Moderate CentOS 7 systemd Security Update
  (Johnny Hughes)
   2. CESA-2018:0262 Important CentOS 7 thunderbird Security Update
  (Johnny Hughes)
   3. CESA-2018:0262 Important CentOS 6 thunderbird Security Update
  (Johnny Hughes)


--

Message: 1
Date: Thu, 1 Feb 2018 23:43:31 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2018:0260 Moderate CentOS 7 systemd
SecurityUpdate
Message-ID: <20180201234331.ga46...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2018:0260 Moderate

Upstream details at : https://access.redhat.com/errata/RHSA-2018:0260

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
a7ff6697cba768a37cfbf5b08cd4fea42887544e64fa81d652726fac42328c22  
libgudev1-219-42.el7_4.7.i686.rpm
ae8a35516e4db15022c7bdf3dc7fb17d565c3566bfe0598e9e83fd79f7bcb78e  
libgudev1-219-42.el7_4.7.x86_64.rpm
387700a80d251f5fd2c4ed4f4d6be0c0dd31cd13218034b7bee995602965c794  
libgudev1-devel-219-42.el7_4.7.i686.rpm
b1e7c83f256176b876f5f9df330e2c97011efd1e301c8e2b8bd6951479f9fced  
libgudev1-devel-219-42.el7_4.7.x86_64.rpm
b048c461c24df985cf5d3daa80c79fddfd435b01c81ece0543b8f6e44902b3c2  
systemd-219-42.el7_4.7.x86_64.rpm
5b8a7713fe41db817ca9e7d734f9fc7e3e9bb2c751317adec9129529b1a3a711  
systemd-devel-219-42.el7_4.7.i686.rpm
df475636c40dff17bb76c95952b1a84df70234ce6164ec5d8d6e0622c18a26de  
systemd-devel-219-42.el7_4.7.x86_64.rpm
8b0f6580d8ac768bb2bdd2d3fea37471c12f69622070c028c6654a67d9ed62ba  
systemd-journal-gateway-219-42.el7_4.7.x86_64.rpm
39996be3a24fea93dd74b3858e849bd13d42b3618933646c014999301f74c989  
systemd-libs-219-42.el7_4.7.i686.rpm
d7ba060ecee893b2e60d18394899768fe93a9199a3eba7eb0e2b2942a4d5b03f  
systemd-libs-219-42.el7_4.7.x86_64.rpm
efe57fcbf99513a07140cb9ab10780cc416bbc0a3fa51775fb628331ee99910a  
systemd-networkd-219-42.el7_4.7.x86_64.rpm
ccff4b016165af8c211c4ff5c0dd2668498487130c7a18da188281f0b8c2fcac  
systemd-python-219-42.el7_4.7.x86_64.rpm
6179b555b0aea983902a99e83a2e2687ef6cdba897e8fe804c9c860f36fa1642  
systemd-resolved-219-42.el7_4.7.i686.rpm
73889e7ca81e3d4f6c918e5c7928ab47927f227a833a20821a2f9f994e393d80  
systemd-resolved-219-42.el7_4.7.x86_64.rpm
4669da503e9376fc14044bd230db80452c595c09c439dc769d92b6844b4a5488  
systemd-sysv-219-42.el7_4.7.x86_64.rpm

Source:
6857f944bb775fce5c2ec5942d5b9bbff74b3ac0d7466b4b0d2c10ed5c6e898a  
systemd-219-42.el7_4.7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS



--

Message: 2
Date: Thu, 1 Feb 2018 23:44:38 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2018:0262 Important CentOS 7
thunderbird Security Update
Message-ID: <20180201234438.ga46...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2018:0262 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2018:0262

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
c5a42870fd0dbb44e82f8030a889a0bdf8cb2f8b1becb9d49763070d47820ff0  
thunderbird-52.6.0-1.el7.centos.x86_64.rpm

Source:
92c034d0d0f6895453c4e371841d78a5bfdedb11df63cf21a1d1c341c5216f35  
thunderbird-52.6.0-1.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS



--

Message: 3
Date: Thu, 1 Feb 2018 23:45:44 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2018:0262 Important CentOS 6
thunderbird Security Update
Message-ID: <20180201234544.ga46...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2018:0262 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2018:0262

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
4c5faa32a2ce2a7945e7e58a31c90a29f5c8bbc1522299ca8074ff0b179fe244  
thunderbird-52.6.0-1.el6.centos.i686.rpm

x86_64:

Re: [CentOS] Slightly OT : newsletters, mail formatting and netiquette

2018-02-02 Thread Nux!
Not only is it acceptable, but it has become the norm unfortunately.

If you do switch to HTML format, bare in mind it may have consequences on how 
other servers label you (or not) as SPAM, so do a few thorough test rounds.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nicolas Kovacs" 
> To: "CentOS mailing list" 
> Sent: Friday, 2 February, 2018 09:36:14
> Subject: [CentOS] Slightly OT : newsletters, mail formatting and netiquette

> Hi,
> 
> This question is not exactly CentOS-related strictly speaking, but here
> goes. I'm running a few newsletter servers for myself and a handful of
> clients on public CentOS servers with PHPList.
> 
> For the last twenty years or so I've followed the basic rule that mails
> should have no formatting whatsoever, only simple text. And now I wonder
> if that basic rule of netiquette also applies to newsletters.
> 
> I'm a subscriber to a series of tech-related newsletters, and I couldn't
> help but notice that they all seem to be HTML-formatted, even those from
> respectable hardcore geek groups.
> 
> So my somewhat naive question: is HTML formatting acceptable in
> newsletters?
> 
> Cheers,
> 
> Niki
> --
> Microlinux - Solutions informatiques durables
> 7, place de l'église - 30730 Montpezat
> Site : https://www.microlinux.fr
> Blog : https://blog.microlinux.fr
> Mail : i...@microlinux.fr
> Tél. : 04 66 63 10 32
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Anyone using GQRX in Centos-7, for SDR ?

2018-02-02 Thread Nux!
Is it a Realtek chipset?
I've had problems with it on CentOS as the system will load up the DVB drivers 
(for TV tuner) thus interfering with the SDR.
What worked for me is blacklisting them & reboot. Give it a try.

cat /etc/modprobe.d/blacklist_rtl.conf 
blacklist dvb_usb_rtl28xxu 
blacklist rtl2832 
blacklist rtl2830

BTW there's a new package at http://li.nux.ro/download/nux/tmp/gqrx7/ if you 
care to test and confirm success so I can move it to the main repo.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Fred Smith" 
> To: "CentOS mailing list" 
> Sent: Thursday, 1 February, 2018 22:38:09
> Subject: [CentOS] Anyone using GQRX in Centos-7, for SDR ?

> I gave myself a toy, one of those cheap USB Software Define Radios, and
> would like to use it on my C7 box. Having wasted some time on it, I gave
> up and installed Ubuntu on a USB HD so I can boot that to play with SDR.
> The Ubuntu GQRX installation is well documented and went off without a hitch.
> but I just hate having to boot something else on my main box (partly because
> it also runs a mailserver for my personal domain, partly because, well,
> I just want my box running CentOS, not Ubuntu.)
> 
> Searching through SDR info on line I see someone has documented installing
> all the bits for C6, but I suspect the process is different for C7.
> 
> BTW, I installed the various bits I could find from, er, I think some
> came from li.nux.ro, some perhaps from epel, on C7, but couldn't get
> them to properly function.
> 
> Worse, when the USB radio is unplugged from the system, it locks up hard.
> 
> then a few days ago, I  had been playing with it using the UBUNTU install,
> did a reboot and for kicks fired up the GQRX on Centos, and lo and behold
> it worked! I tried running it on Centos yesterday and it reverted to type,
> i.e., lock up hard. I suspect that Ubuntu is leaving some hardware in a
> state that allows it to work on a subsequent Centos boot (without poweroff),
> but no clue what.
> 
> So, if anyone can point me to how  to use it on C7, I'd greatly appreciate it.
> 
> thanks in advance!
> 
> Fred
> --
>  Fred Smith -- fre...@fcshome.stoneham.ma.us -
>   Show me your ways, O LORD, teach me your paths;
> Guide me in your truth and teach me,
> for you are God my Savior,
>And my hope is in you all day long.
> -- Psalm 25:4-5 (NIV) 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Slightly OT : newsletters, mail formatting and netiquette

2018-02-02 Thread Nicolas Kovacs
Hi,

This question is not exactly CentOS-related strictly speaking, but here
goes. I'm running a few newsletter servers for myself and a handful of
clients on public CentOS servers with PHPList.

For the last twenty years or so I've followed the basic rule that mails
should have no formatting whatsoever, only simple text. And now I wonder
if that basic rule of netiquette also applies to newsletters.

I'm a subscriber to a series of tech-related newsletters, and I couldn't
help but notice that they all seem to be HTML-formatted, even those from
respectable hardcore geek groups.

So my somewhat naive question: is HTML formatting acceptable in
newsletters?

Cheers,

Niki
-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site : https://www.microlinux.fr
Blog : https://blog.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos