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.
Hi,
After installing CentOS 7 in a server with 2 NICs, system detects eth0
and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as
eth1. I have forced HWADDR attribute in
/etc/sysconfig/network-scripts/ifcfg-etc{0,1}, but after rebooting,
order is the same...
How can I solv
El Lunes 01/02/2016, Daniel Ruiz Molina escribió:
> Hi,
>
> After installing CentOS 7 in a server with 2 NICs, system detects eth0
> and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as
> eth1. I have forced HWADDR attribute in
> /etc/sysconfig/network-scripts/ifcfg-etc{0,1}, bu
On Mon, Feb 1, 2016 at 9:31 AM, Ricardo J. Barberis
wrote:
> El Lunes 01/02/2016, Daniel Ruiz Molina escribió:
>> Hi,
>>
>> After installing CentOS 7 in a server with 2 NICs, system detects eth0
>> and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as
>> eth1. I have forced HWAD
The issue here may be systemd (I've seen/agree with the venting, this is
another example). If you're getting non-eth names there's a program called
biosdevname which may be deciding how to name NICs for you. If that's the case
then then the -net.rules may be ineffective unless the following is
I got an email from a user that I'd just handed a new CentOS 7 workstation
to, wondering where all the printers were.
It took some investigation to find /etc/cups/cups-browsed.conf, and see,
in it, at the very bottom of the file:
# NOTE: This file is not part of CUPS. You need to start & enable
c
On Mon, February 1, 2016 9:17 am, m.r...@5-cent.us wrote:
> I got an email from a user that I'd just handed a new CentOS 7 workstation
> to, wondering where all the printers were.
>
> It took some investigation to find /etc/cups/cups-browsed.conf, and see,
> in it, at the very bottom of the file:
El Lunes 01/02/2016, Leroy Tennison escribió:
> The issue here may be systemd (I've seen/agree with the venting, this is
> another example).
So far, this is my only big grip with systemd: It apparently never worked,
though IME it only stopped working with recent versions of udev.
> If you're get
Hi All,
I am in the process of trying to install Lustre on CentOS 7 and I was wondering
if anyone could point me to any good documentation. I found
https://wiki.hpdd.intel.com/pages/viewpage.action?pageId=8126821 but this
really doesn’t help. I am trying to install version 2.7.1.
Regards,
Ben
On 02/01/2016 07:00 AM, Leroy Tennison wrote:
The issue here may be systemd
...
Web documentation at freedesktop.org says net.ifnames needs to be set to zero,
I found just the opposite but if it doesn't work for you try both before giving
up.
Just to clarify: net.ifnames=0 disables the syst
> Just to clarify: net.ifnames=0 disables the systemd/udev interface renaming
> feature.
Well, I tried that and it didn't change the behavior, using 1 as a value did.
Don't know if there's been tampering between freedesktop and Ubuntu 14.04LTS
but that was my experience.
> Also, if you add r
I have installed the kate editor on Centos 6.7 but it seems to be a very old
version, 3.3.4, installed as part of kdesdk. On Centos 7 I can simply run 'yum
install kate' but, alas, not on Centos 6.
What is the recommended way of updating kate on Centos 6?
Thank you.
___
Valeri Galtsev wrote:
>
> On Mon, February 1, 2016 9:17 am, m.r...@5-cent.us wrote:
>> I got an email from a user that I'd just handed a new CentOS 7
>> workstation to, wondering where all the printers were.
>>
>> It took some investigation to find /etc/cups/cups-browsed.conf, and see,
>> in it, at
On Mon, February 1, 2016 1:00 pm, m.r...@5-cent.us wrote:
> Valeri Galtsev wrote:
>>
>> On Mon, February 1, 2016 9:17 am, m.r...@5-cent.us wrote:
>>> I got an email from a user that I'd just handed a new CentOS 7
>>> workstation to, wondering where all the printers were.
>>>
>>> It took some inves
On Mon, 1 Feb 2016 19:22, H wrote:
I have installed the kate editor on Centos 6.7 but it seems to be a very old
version, 3.3.4, installed as part of kdesdk. On Centos 7 I can simply run 'yum
install kate' but, alas, not on Centos 6.
What is the recommended way of updating kate on Centos 6?
Gordon Messmer wrote:
> On 02/01/2016 07:00 AM, Leroy Tennison wrote:
>> The issue here may be systemd
> ...
>> Web documentation at freedesktop.org says net.ifnames needs to be set
to zero, I found just the opposite but if it doesn't work for you try
both before giving up.
>
> Just to clarify: net
Excerpt:
Running rm -rf / on any UEFI Linux distribution can potentially
perma-brick your system.
As a public service announcement, recursively removing all of your files
from / is no longer recommended. On UEFI distributions by default where
EFI variables are accessible via /sys, this can now mea
Once upon a time, m.r...@5-cent.us said:
> Gordon Messmer wrote:
> > Also, if you add rules to /etc/udev/rules.d, you should rebuild your
> initrd.
>
> ?!?!?!?! THAT I had never considered, nor done, and I'm sure that in
> CentOS 6, I've changed things there, and just rebooted.
That's only neces
Once upon a time, m.r...@5-cent.us said:
> Excerpt:
> Running rm -rf / on any UEFI Linux distribution can potentially
> perma-brick your system.
Did someone think running "rm -rf /" is a good idea?
> Ok, *now* tell me why we shouldn't hate systemd?
This has zero to do with systemd. This is a b
On 01/02/16 09:16 AM, Daniel Ruiz Molina wrote:
> Hi,
>
> After installing CentOS 7 in a server with 2 NICs, system detects eth0
> and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as
> eth1. I have forced HWADDR attribute in
> /etc/sysconfig/network-scripts/ifcfg-etc{0,1}, but
On Mon, February 1, 2016 1:33 pm, m.r...@5-cent.us wrote:
> Excerpt:
> Running rm -rf / on any UEFI Linux distribution can potentially
> perma-brick your system.
Yes, I kind of like "rm -rf /". If my memory doesn't fail me, long ago it
was one of the tricky questions in sysadmin exam (not that an
On Mon, 1 Feb 2016 13:44:48 -0600
Chris Adams wrote:
> Did someone think running "rm -rf /" is a good idea?
Quote from one of the people who commented on that article:
QUOTE:
You have this in a script: rm -rf "${DIRECTORY}"/
Now, you have a bug in the script and ${DIRECTORY} is not initialized
On 02/01/2016 11:54 AM, Frank Cox wrote:
You have this in a script: rm -rf "${DIRECTORY}"/
Now, you have a bug in the script and ${DIRECTORY} is not initialized.
On GNU systems, rm should not remove '/' recursively unless
--no-preserve-root is specified.
__
>> Excerpt:
>> Running rm -rf / on any UEFI Linux distribution can potentially perma-brick
>> your system.
>
> "And they closed the ticket"? That tuxedo on the cockroach is so elegent!
> Ok, *now* tell me why we shouldn't hate systemd?
> mark
As much as I don't like systemd, it has NOTHING
On Mon, February 1, 2016 1:56 pm, Valeri Galtsev wrote:
>
> On Mon, February 1, 2016 1:33 pm, m.r...@5-cent.us wrote:
>> Excerpt:
>> Running rm -rf / on any UEFI Linux distribution can potentially
>> perma-brick your system.
>
> Yes, I kind of like "rm -rf /". If my memory doesn't fail me, long ag
wait. would deleting the inode /sys/(whatever) actually modify UEFI
memory?sure, writing to those inodes could do all sorts of harm, but
deleting the inodes in the /sys filesystem, I'm not so sure this isn't a
tempest in a teapot so to speak.
--
john r pierce, recycling bits in sant
John R Pierce wrote:
> wait. would deleting the inode /sys/(whatever) actually modify UEFI
> memory?sure, writing to those inodes could do all sorts of harm, but
> deleting the inodes in the /sys filesystem, I'm not so sure this isn't a
> tempest in a teapot so to speak.
It's going to get /
On 2/1/2016 2:07 PM, m.r...@5-cent.us wrote:
John R Pierce wrote:
>wait. would deleting the inode/sys/(whatever) actually modify UEFI
>memory?sure, writing to those inodes could do all sorts of harm, but
>deleting the inodes in the /sys filesystem, I'm not so sure this isn't a
>tempest in
John R Pierce wrote:
> On 2/1/2016 2:07 PM, m.r...@5-cent.us wrote:
>> John R Pierce wrote:
>>> >wait. would deleting the inode/sys/(whatever) actually modify UEFI
>>> >memory?sure, writing to those inodes could do all sorts of harm,
>>> but deleting the inodes in the /sys filesystem, I'm no
On 02/01/2016 02:07 PM, m.r...@5-cent.us wrote:
It's going to get /boot. And under there, it'll get /boot/EFI.
Yes, but that's not the problem. /sys/firmware/efi/efivars is.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/l
On 02/01/2016 01:48 PM, Valeri Galtsev wrote:
I just discovered that I couldn't even re-cite alphabet correctly today:
it is /bin that you loose, but /etc alphabetically goes after /dev, so
will not even loose your /etc,
I'm pretty sure none of that is correct. Once "rm" launches, all of the
On 02/01/2016 01:59 PM, John R Pierce wrote:
would deleting the inode /sys/(whatever) actually modify UEFI memory?
Yes. That is how the UEFI management interface works.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listin
On Mon, February 1, 2016 4:24 pm, Gordon Messmer wrote:
> On 02/01/2016 01:59 PM, John R Pierce wrote:
>> would deleting the inode /sys/(whatever) actually modify UEFI memory?
>
> Yes. That is how the UEFI management interface works.
Will doing
rm -rf /
actually delete anything in /sys? IMHO,
On 02/01/2016 02:46 PM, Valeri Galtsev wrote:
Will doing
rm -rf /
actually delete anything in /sys? IMHO, not.
Yes, it will. Probably. It's possible that it'll hang on some of the
files in /proc if it gets to that directory before /sys, but that's
largely a matter of chance.
The abov
On Mon, February 1, 2016 4:23 pm, Gordon Messmer wrote:
> On 02/01/2016 01:48 PM, Valeri Galtsev wrote:
>> I just discovered that I couldn't even re-cite alphabet correctly today:
>> it is /bin that you loose, but /etc alphabetically goes after /dev, so
>> will not even loose your /etc,
>
> I'm pr
On 02/01/2016 11:54 AM, Frank Cox wrote:
On Mon, 1 Feb 2016 13:44:48 -0600
Chris Adams wrote:
Did someone think running "rm -rf /" is a good idea?
Quote from one of the people who commented on that article:
QUOTE:
You have this in a script: rm -rf "${DIRECTORY}"/
Now, you have a bug in the
On 01/31/16 22:10, Fred Smith wrote:
> On Sun, Jan 31, 2016 at 09:42:43PM -0500, Mark LaPierre wrote:
>> On 12/30/15 23:03, Mark LaPierre wrote:
>>> Hey Y'all,
>>>
>>> I have the Stanford University Folding At Home project running on three
>>> of my machines. I had them all set up so that I could
Once upon a time, Valeri Galtsev said:
> All true, except for: to actually write stuff permanently to hard drive
> (that is modify whatever the content of hard drive is) the system needs to
> access /dev/sda1 (I call from now /dev/sda1 device which "/" filesystem
> lives on), and once /dev/sda1 is
On 02/01/16 14:20, Yamaban wrote:
> On Mon, 1 Feb 2016 19:22, H wrote:
>
>> I have installed the kate editor on Centos 6.7 but it seems to be a
>> very old version, 3.3.4, installed as part of kdesdk. On Centos 7 I
>> can simply run 'yum install kate' but, alas, not on Centos 6.
>>
>> What is the
On Mon, Feb 01, 2016 at 06:23:26PM -0500, Mark LaPierre wrote:
> On 01/31/16 22:10, Fred Smith wrote:
> > On Sun, Jan 31, 2016 at 09:42:43PM -0500, Mark LaPierre wrote:
> >> On 12/30/15 23:03, Mark LaPierre wrote:
> >>> Hey Y'all,
> >>>
> >>> I have the Stanford University Folding At Home project r
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of m.r...@5-cent.us
> Sent: den 1 februari 2016 20:34
> To: CentOS
> Subject: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System
>
> As a public service announcement, recursively r
41 matches
Mail list logo
