[CentOS] Re: Latest version of kate editor

[Yamaban]

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?

Thank you.


First you find out from wich package (rpm) your kate is.

either you try to as yum: "yum search kate",

or you do the full monty:
locate the binary "type kate", usually /usr/bin/kate,
then you ask rpm from which package this file comes:
"rpm -qf /usr/bin/kate"
take the main package name (the part before the version numbers)
and feed it to yum:

yum update [kate-package-name]

YMMV, depening on what repos you have enabled or not.

You can search most of what is available via pkgs.org,
for kate, for example

http://pkgs.org/search/kate

then select "Centos 6" (maybe you have to scroll down for that)

The EPEL repo seems to have version 0.3.8 of libkate at least.

Have a nice week.
 - Yamaban
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Valeri Galtsev]

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 anymore if I
read what you, Michael, write further correctly...). Anyway, let's imagine
we are back then, then what

rm -rf /

will do you your system? How dramatic this command is?

Well, it definitely will obliterate your /etc with all your settings. Then
it will start deleting /dev, and once it deletes the block device your
root filesystem "/" lives on, all trouble ends there. So, you just take
your drive, and you will be able to mount on different machine /home,
/usr, /var and what's left of your / partition. /etc is gone, bit this
only as dramatic as it gets (thanks for alphabetical order the command
follows).

Sorry about long spam message, everybody. I just so liked that tricky
question from my past, I couldn't hold myself.

Valeri

>
> 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 mean trashing your
> UEFI implementation.
>
> There is this systemd bug report requesting that UEFI variables be mounted
> as read-only by default. Lennart Poettering had initially responded and
> simply said, "Well, there are tools that actually want to write it. We
> also expose /dev/sda accessible for root, even though it can be used to
> hose your system. The ability to hose a system is certainly reason enought
> to make sure it's well protected and only writable to root. But beyond
> that: root can do anything really." He then closed the ticket.
> --- end excerpt ---
>
> 
>
> "And they closed the ticket"? That tuxedo on the cockroach is so elegent!
>
> Ok, *now* tell me why we shouldn't hate systemd?
>
>mark
>
> ___
> 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] NICs order

[Chris Adams]

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 necessary for things that are initialized in the initrd.
Unless you are using network boot, the initrd won't have any of the
network initialization, so rebuilding it is not necessary for changing
network-related config (including udev rules).
-- 
Chris Adams 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Frank Cox]

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. You then 
get rm -rf / executed. One should always ensure that DIRECTORY is not empty 
before running this. Or better, never end with /. If you have rm -rf 
"${DIRECTORY}", then only rm -rf gets executed, causing rm to fail since no 
file/directory is provided.
END OF QUOTE

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Richard Zimmerman]

>> 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 to do with system and 
everything to a poor admin or newbie blindly following others advice. 

My suggestion is to ALWAYS fully qualify *ANY* directory you want to rm -rf, 
period. 

I speak from experience. Years ago had a script that would cd into a directory 
and then rm - rf * it. Problem started when I accidently deleted said dir and 
the PREVIOUS dir was /. Needless to say, the server was happily committing 
suicide before I figured out the problem.

Lessons learned:
1. Fully qualify ANY rm -rf command
2. Make sure you always have good backups, I did!
3. I became really, really good at disaster recovery :)
4. Upper Management WILL get cranky over an event like this!

Just my 2 cents worth...

Richard


---
Richard Zimmerman
Systems / Network Administrator
River Bend Hose Specialty, Inc.
 S Main Street
South Bend, IN   46601-3337
(574) 233-1133
(574) 280-7284 Fax

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

Re: [CentOS] CentOS 7 and network printers: FYI

[Valeri Galtsev]

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 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
>>> cups-browsed service.
>>>
>>> Which appears to be brand new with 7, and I have not seen any mention
>>> of
>>> it.
>>>
>>> Enabled and started, and the network printers are visible on the cups
>>> localhost web page->printers.
>>
>> Unrelated to the topic, but may be helpful for somebody who uses cups
>> browsing option. I usually turn off cups browsing. Here is why: someone
>> brings laptop to our network, and may have one of his/her printers
>> "shared". Somebody else finds, sets it up, and happily uses it. Till the
>> first person goes away. Then second person comes to me telling my
>> printer
>> doesn't work. Which is not my printer, in a sense I can do nothing about
>> what the second person had done about that printer...
>>
> You're in a different environment. I guarantee no one's wandering in with
> a printer here. Plus, on our VLAN, we are the ones giving out IP
> addresses, and *only* to MAC addresses we know. We don't know 'em, they
> don't get on the network.

As I said, my comment was _unrelated_ to the topic. As, as you said,
environments are different, and as ours is different from yours,
somebody's may be similar to ours as well...

Thanks for your original post though: everyone of us may hit the snag you
described some day!

Valeri


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] NICs order

[m . roth]

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.ifnames=0 disables the systemd/udev interface
renaming feature.  biosdevname=0 disables the biosdevname interface
renaming feature, which is completely separate.  If you want the
traditional, non-deterministic Linux interface naming, you must specify
both.

You call it "deterministic". I will note that it is, in fact, straight
from Sun - 20 years ago, that was the naming on the Sparc Server that I
first picked up sysadmin work. Which was fine... FOR SUN HARDWARE. For
admins and users, it's *really* NOT a great idea, given that the system
could have a m/b from any OEM, and even trying to set up a std. kickstart
is a pain with that, much less anything more arcane. Why ethx, with the
option of adding the firmware MAC address, is such a bad idea, I have no
clue.
>
> 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. Oh, great, I'm
getting flashes of WinDoze.

Thanks for that info, though. I need to remember that.

  mark



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

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Gordon Messmer]

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.

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

Re: [CentOS] CentOS 7 and network printers: FYI

[m . roth]

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 the very bottom of the file:
>>
>> # NOTE: This file is not part of CUPS. You need to start & enable
>> cups-browsed service.
>>
>> Which appears to be brand new with 7, and I have not seen any mention of
>> it.
>>
>> Enabled and started, and the network printers are visible on the cups
>> localhost web page->printers.
>
> Unrelated to the topic, but may be helpful for somebody who uses cups
> browsing option. I usually turn off cups browsing. Here is why: someone
> brings laptop to our network, and may have one of his/her printers
> "shared". Somebody else finds, sets it up, and happily uses it. Till the
> first person goes away. Then second person comes to me telling my printer
> doesn't work. Which is not my printer, in a sense I can do nothing about
> what the second person had done about that printer...
>
You're in a different environment. I guarantee no one's wandering in with
a printer here. Plus, on our VLAN, we are the ones giving out IP
addresses, and *only* to MAC addresses we know. We don't know 'em, they
don't get on the network.

  mark

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

[CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[m . roth]

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 mean trashing your
UEFI implementation.

There is this systemd bug report requesting that UEFI variables be mounted
as read-only by default. Lennart Poettering had initially responded and
simply said, "Well, there are tools that actually want to write it. We
also expose /dev/sda accessible for root, even though it can be used to
hose your system. The ability to hose a system is certainly reason enought
to make sure it's well protected and only writable to root. But beyond
that: root can do anything really." He then closed the ticket.
--- end excerpt ---



"And they closed the ticket"? That tuxedo on the cockroach is so elegent!

Ok, *now* tell me why we shouldn't hate systemd?

   mark

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

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Chris Adams]

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 by-product of how the
kernel driver and user-space tools for EFI are implemented.  The kernel
driver exposes EFI variables in a writable sysfs filesystem, and so
that's how the user-space tools set/update/delete the variables.  Trying
to force a change on that interaction from an intermediary is just
wrong.  If the maintainers for the EFI-related code think it should
change, they'll need to coordinate that change between the kernel and
user-space.

The bigger issue is that there is apparently some UEFI implementations
that can't handle certain variables being deleted or overwritten.  Yes,
that could happen from an errant rm, but there are other ways that could
happen.  Vendors that can't recover in some way (like BIOS CMOS
corruption can be recovered with a jumper) should be named-and-shamed as
well as potentially blacklisted in some way in the EFI driver.

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

Re: [CentOS] NICs order

[Digimer]

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 after rebooting,
> order is the same...
> 
> How can I solve it?
> 
> Thanks.

https://alteeve.ca/w/Changing_Ethernet_Device_Names_in_EL7_and_Fedora_15%2B

That covers renaming NICs on EL7.

-- 
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-virt] How to build CentOS 7 AMI

[Alan Ivey]

I'd like to revisit the thread about how the CentOS 7 AMIs are created (
https://lists.centos.org/pipermail/centos-devel/2015-July/013652.html) and
see if the process can be published in the
https://github.com/CentOS/sig-cloud-instance-build repository or another
relevant location.

With CentOS 7 AMIs only being available in the Marketplace, all resulting
EC2 instances have the Marketplace codes attached to the EBS volumes. A
significant restriction of this is that a resulting image cannot be the
non-primary volume of an instance unless it is powered down. This presents
itself to be a problem in at least the following scenarios:

   - Unable to attach a CentOS 7 boot volume to another instance for repair
   without either creating a temporary instance or shutting down an existing
   one. For example, if you messed up the /etc/sudoers file and logged out,
   and wanted to repair, you would not be able to repair by mounting to
   another instance and editing the file without incurring additional (albeit
   small) cost, or having an existing instance be temporarily unavailable.
   - The "amazon-chroot" Packer Builder (
   https://www.packer.io/docs/builders/amazon-chroot.html) does not work
   because it starts by mounting a copy of the snapshot tied to the AMI as
   part of a scripted operation and therefore cannot power off to do so


Custom AMIs, snapshots, copied EBS volumes, etc, all have the marketplace
codes copied to them and inherit the restrictions. If an org was to use
these features for automating environments and was disconnected from the
original Marketplace agreement, they may be unaware of this limitation.

I would also appreciate being able to have the additional transparency of
seeing how an AWS AMI is created as the docker/openstack/etc images from
the repository referenced above. This would be useful in environments with
regulatory compliance concerns, such as AWS GovCloud, HIPAA, FedRAMP, etc.

I understand the benefit that Marketplace registrations allow for the
ability to notify users of any changes, and I am not necessarily advocating
for switching away from the Marketplace as the primary AMI location. I
would like to be provided the opportunity to build a private AMI in the
exact same procedure as the official image so as to avert the restrictions
provided by the Marketplace.

Thank you,
Alan
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Valeri Galtsev]

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 pretty sure none of that is correct.  Once "rm" launches, all of the
> libraries and files that it needs are memory mapped and reference
> counted, so they're going to remain available while it removes the
> entire filesystem structure.

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 deleted there will be no further hard
drive write operations. There will be no way for system to access anything
under /, which will cause "rm" command to fail fataly. I will kickstart
install centos 7 in a moment and will do exactly this:

cd /

rm -rf /

(the first command is to avoid even "can not get CWD", which shouldn't
matter ;-)

So, I'll see in a moment how much I'll loose on the drive, and will it or
will it not be sufficient to rsync /boot from "twin" box, and restore /bin
symlink. Will get back with either "crap, indeed I was wrong", or "yes,
even on latest CentOS 7 system it is still so". Whatever the result is,
I'll enjoy this experiment. Thanks for giving me incentive to do it!

Incidentally, let me know if there is anything I should change in my
experiment for that to give us more definite answers that just "oh, look,
I still have /etc, /home, /usr... intact on hard drive". What specifically
should I do to learn that in a course of this command /sys was never
touched? Any ideas?

Valeri



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] Latest version of kate editor

[Mark LaPierre]

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 recommended way of updating kate on Centos 6?
>>
>> Thank you.
> 
> First you find out from wich package (rpm) your kate is.
> 
> either you try to as yum: "yum search kate",
> 
> or you do the full monty:
> locate the binary "type kate", usually /usr/bin/kate,
> then you ask rpm from which package this file comes:
> "rpm -qf /usr/bin/kate"
> take the main package name (the part before the version numbers)
> and feed it to yum:
> 
> yum update [kate-package-name]
> 
> YMMV, depening on what repos you have enabled or not.
> 
> You can search most of what is available via pkgs.org,
> for kate, for example
> 
> http://pkgs.org/search/kate
> 
> then select "Centos 6" (maybe you have to scroll down for that)
> 
> The EPEL repo seems to have version 0.3.8 of libkate at least.
> 
> Have a nice week.
>  - Yamaban
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> 

yum install kdesdk-4.3.4-9.el6.x86_64

-- 
_
   °v°
  /(_)\
   ^ ^  Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/

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

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[John R Pierce]

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 santa cruz

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

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Gordon Messmer]

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 
libraries and files that it needs are memory mapped and reference 
counted, so they're going to remain available while it removes the 
entire filesystem structure.


Spin up a VM and try it out.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Gordon Messmer]

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/listinfo/centos

Re: [CentOS-es] VM dentro de VM con KVM

[Ing . Ernesto Pérez Estévez , Mg .]

On 01/02/16 16:39, daniel wrote:
> Gracias Ernesto,
> 
> Solucionado, siguiendo estos pasos =>
> https://fedoraproject.org/wiki/How_to_enable_nested_virtualization_in_KVM
exacto!! gracias por buscarle por mi.. la verdad hoy he tenido un día
tenso.. efectivamente ese es el howto. Como ves la verdad no es difícil.

saludos
epe

-- 
CEDIA
La principal herramienta de Investigación en el Ecuador.

Calle La Condamine 12-109 "Casa Rivera".
Cuenca -  Ecuador
Telf: (593) 7405 1000 Ext. 4220/4223
i...@cedia.org.ec
www.cedia.org.ec

Email secured by Check Point
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Chris Adams]

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 deleted there will be no further hard
> drive write operations.

Incorrect.  Once the filesystem is mounted, the kernel access doesn't go
through the filesystem /dev node, similar to how once rm is running, it
doesn't need the /lib64/libc.so.6 node.

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

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Valeri Galtsev]

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, not. The above command first will
get to removing /dev, and it will delete /dev/sda1 or whichever device /
filesystem lives on. And after that the command will fail, as there will
be nothing accessible under / on that system after device root filesystem
"/" lives on will be deleted. So, IMHO, that nasty command will never get
to /sys, so all related to UEFI vars controlled through /sys filesystem
will stay as they are. You will brick the box, but only in a sense you
will have to restore /boot on your hard drive and /bin which these days is
symlink (on CentOS 7), so actual content of /usr/bin where symlink points
will stay intact. And portion of /dev - whatever alphabetically is before
root filesystem device.

Valeri


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] In A UEFI World, "rm -rf /" Can Brick Your System

[John R Pierce]

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 a teapot so to speak.

It's going to get /boot. And under there, it'll get /boot/EFI.


so it will delete inodes there...does that damage the EFI 
hardware?I would think you'd have to open files and write data to 
actually modify the EFI stuff.


my only C7 systems right now are VMs which don't have uefi, so I can't 
look and see what all this stuff actually is.



--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[m . roth]

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 not so sure this
>>> isn't a >tempest in a teapot so to speak.

>> It's going to get /boot. And under there, it'll get /boot/EFI.
>
> so it will delete inodes there...does that damage the EFI
> hardware?I would think you'd have to open files and write data to
> actually modify the EFI stuff.
>
> my only C7 systems right now are VMs which don't have uefi, so I can't
> look and see what all this stuff actually is.

Yeah, I don't think we really know, until someone's willing to brick a
many-thousand-dollar server

 mark

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

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Gordon Messmer]

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 above command first will
get to removing /dev, and it will delete /dev/sda1 or whichever device /
filesystem lives on. And after that the command will fail, as there will
be nothing accessible under / on that system after device root filesystem
"/" lives on will be deleted.


Access to your filesystems doesn't depend on the device nodes after 
they're mounted.  You can remove all of the nodes in /dev, and your 
filesystems remain available.  Spin up a VM and test it.  I promise, it 
works.



And portion of /dev - whatever alphabetically is before
root filesystem device.


rm doesn't process files in alphabetical order.  It processes them in 
directory order, which is unpredictable.

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

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[m . roth]

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 /boot. And under there, it'll get /boot/EFI.

  mark

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

Re: [CentOS] More Folding At Home

[Mark LaPierre]

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 control them all
>>> from my main machine, 192.168.15.101, but some time ago something
>>> changed so that I can no longer connect to the FAH clients on the other
>>> two machines.  I figured it wasn't really important so I would look into
>>> it later.  Well time has passed and my Christmas break is almost passed
>>> too to I guess this is the time to figure it out.
>>>
>>> I can still SSH onto both machines.  I can ping both machines.
>>>
>>> When I open the FAH Control on my machine connection to clients running
>>> on 192.168.15.105 and 192.168.15.107 fails.
>>>
>>> I'm assuming that there would be an entry in a log on those two machines
>>> detailing the failed connection attempt.
>>>
>>> What log file should I be looking at?
>>>
>>
>> Hey CentOS FAH team members.  Do any of you have a GPU that is actually
>> folding in CentOS 6?
> 
> I tried GPU folding in Centos-6, but the FAH log file showed continuous
> errors for the GPU (which was, at the time a Nvidia n460GTX). Inquiries
> on the FAH forums indicated that there are library incompatibilities 
> on Centos-6 and that it would be difficult or impossible to make it
> work.
> 
> I eventually upgraded to Centos-7 and then easily got GPU folding to
> work on the same video card without difficulty.
> 
> FYI, I had previously (couple of years ago) attempted GPU folding on 
> C6 using a 9800GT, and was told (again, on the FAH forums) that that
> GPU was no longer supported. I'd guess that your 9600GT is also too
> old.
> 
> Here's the FAH forum thread on that GPU compatibility issue:
> https://foldingforum.org/viewtopic.php?f=80=25284=252427=9800GT#p252427
> 
> I've recently replaced the 460GTX with a new 750ti card, and found
> two amazing benefits:
> 1. according to my KillaWatt meter, the computer's power draw dropped from
> 275-295 watts to 190-195 watts,
> 2. my PPD total per week has gone from around 200K to more like 400K.
>In fact, the last 3 weeks have all been around 440K, some slightly
>lower, some a little higher.
> 
> The 750ti was a fairly cheap card, at $129.
> 
>> If you do please tell me exactly what video card and what driver you are
>> using?
> 
> I'm using the Nvidia 340 driver from the elrepo repository. Be sure to
> install the dkms package from epel before installing these nvidia drivers.
> 
>>
>> I have a GeForce 9600 GT card that will not fold.  FAH finds the GPU and
>> sets up a slot for it but it always says "Update Core" in the slot
>> status field with zero progress.  I'm not happy with that.
> 
> See above for compatibility comments on this card.
> 

Thanks for the input Fred.

The GeForce 9600 GT is listed in the GPUs.txt file as of Jan 20.  It
should be compatible but I guess it won't work on C6 though.  I'm not in
any hurry to move to C7.

-- 
_
   °v°
  /(_)\
   ^ ^  Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/

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

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Alice Wonder]

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 script and ${DIRECTORY} is not initialized. You then get rm 
-rf / executed. One should always ensure that DIRECTORY is not empty before running this. 
Or better, never end with /. If you have rm -rf "${DIRECTORY}", then only rm 
-rf gets executed, causing rm to fail since no file/directory is provided.
END OF QUOTE



Yeah, that can happen, but I remember being taught that was an extremely 
bad scripting practice back in 1998 when I took my first Linux class.

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

Re: [CentOS-es] VM dentro de VM con KVM

[daniel]

Gracias Ernesto,

Solucionado, siguiendo estos pasos =>
https://fedoraproject.org/wiki/How_to_enable_nested_virtualization_in_KVM

Saludos

Daniel Ortiz Gutiérrez


El lun., 1 de feb. de 2016 a la(s) 10:56, Ernesto Pérez Estévez <
ernesto.pe...@cedia.org.ec> escribió:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
>
> On 02/01/2016 11:44 AM, daniel wrote:
> > Buenos Dias Lista,
> >
> > Con la novedad de que necesito virtualizar un hipervisor que
> > contiene una maquina virtual, alguien me puede decir si esto es
> > posible? Estoy utlizando KVM y al crear la máquina virtual en la
> > opción del procesador selecciono "Copy host CPU configuration".
> > Pero parece no tomar los cambios, ya que el
>
> eso se llama nested virtualization, efectivamente le he usado... funcion
> a.
>
> saludos
> epe
>
> > tipo de procesador me aparece como un Broadwell pero yo tengo un
> > Haswell, si selecciono la opción de Haswell el hypervisor si ve un
> > procesador Haswell pero no ve la bandera VMX por lo que cuando
> > trato de encender una VM me dice que la virtualizacion no esta
> > activada en la configuración del CPU.
> >
> > Saludos
> >
> > Daniel Ortiz Gutiérrez
> > ___ CentOS-es mailing
> > list CentOS-es@centos.org
> > https://lists.centos.org/mailman/listinfo/centos-es
> >
>
>
> - --
> CEDIA
> La principal herramienta de Investigación en el Ecuador.
>
> Calle La Condamine 12-109 "Casa Rivera".
> Cuenca -  Ecuador
> Telf: (593) 7405 1000 Ext. 4220/4223
> i...@cedia.org.ec
> www.cedia.org.ec
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJWr44eAAoJEI8SQ0eoZD/X8NAQAI2xevJynqkzhFG4skvbP2ln
> BXjf7knB9zjlm6nUSp+l8UzLjH5QVYpfuD1NeHTLDnNYc7l8/+RaMcYbVr/idovo
> LcEAN9Pcp0k0ZJndIPPiBeLCopK0CHjLr2Na4V6xLlXKwguRfs1yWSODFi/Hepq+
> kUgmG7c6EA6oM+1CrO/gMyMK69Fk3s/7pKGk2Cgs4JyxvHkgknTYfITBiwbdAoDR
> zhta+fz+C65hP0kxdtpD+kLe/ROtfHyJREBFWyOpq2o62dqZAmZ7z1TJKezriZ8B
> F2sBafAsWKwL+L/VzxCC8PXGfhTbOfUBu8O2CzTJ83unpkrsjkshZQlEji9XxcIR
> DyNN+GYRh8ItP3p2jiv7NRWOfXACb1tfjixjBanrOsdnB1mlXlA2pK220OXbufb+
> uM1Kk5PqfIpfmIzqnJY6wCNGMdwQLoubrYBLLfcSt0B4TdrvB9fJ/1j1njfq6kwA
> az+SW7TpAtvfMHB8icznCw3Vmta2ndLg9zWmlTrnAzPaBBfpNakJuhWfUq8S5P9a
> 0m2uiPyf2Ecbp0cObUMtQKIXe2BJZjwOUy0txR8KOUitRlsq34b9XH/k7vQCRrL+
> OS67xYuVIWzHdaWlOwP50dROyGBy6R4URmAtbVV1Iun/L39bqz5UyXdh9MRHiYDj
> dp0bXix37Sge2mJk2ulK
> =+ra6
> -END PGP SIGNATURE-
>
> Email secured by Check Point
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Valeri Galtsev]

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 ago it
> was one of the tricky questions in sysadmin exam (not that anymore if I
> read what you, Michael, write further correctly...). Anyway, let's imagine
> we are back then, then what
>
> rm -rf /
>
> will do you your system? How dramatic this command is?
>
> Well, it definitely will obliterate your /etc with all your settings. Then
> it will start deleting /dev, and once it deletes the block device your
> root filesystem "/" lives on, all trouble ends there. So, you just take
> your drive, and you will be able to mount on different machine /home,
> /usr, /var and what's left of your / partition. /etc is gone, bit this
> only as dramatic as it gets (thanks for alphabetical order the command
> follows).

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, all you will need it to restore portion of
your /dev and the whole /bib (which you can do easily if you have "twin"
system around...)

>
> Sorry about long spam message, everybody. I just so liked that tricky
> question from my past, I couldn't hold myself.
>
> Valeri
>
>>
>> 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 mean trashing your
>> UEFI implementation.
>>
>> There is this systemd bug report requesting that UEFI variables be
>> mounted
>> as read-only by default. Lennart Poettering had initially responded and
>> simply said, "Well, there are tools that actually want to write it. We
>> also expose /dev/sda accessible for root, even though it can be used to
>> hose your system. The ability to hose a system is certainly reason
>> enought
>> to make sure it's well protected and only writable to root. But beyond
>> that: root can do anything really." He then closed the ticket.
>> --- end excerpt ---
>>
>> 
>>
>> "And they closed the ticket"? That tuxedo on the cockroach is so
>> elegent!
>>
>> Ok, *now* tell me why we shouldn't hate systemd?
>>
>>mark
>>
>> ___
>> 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
>



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] In A UEFI World, "rm -rf /" Can Brick Your System

[Gordon Messmer]

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/listinfo/centos

Re: [CentOS] More Folding At Home

[Fred Smith]

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 running on three
> >>> of my machines.  I had them all set up so that I could control them all
> >>> from my main machine, 192.168.15.101, but some time ago something
> >>> changed so that I can no longer connect to the FAH clients on the other
> >>> two machines.  I figured it wasn't really important so I would look into
> >>> it later.  Well time has passed and my Christmas break is almost passed
> >>> too to I guess this is the time to figure it out.
> >>>
> >>> I can still SSH onto both machines.  I can ping both machines.
> >>>
> >>> When I open the FAH Control on my machine connection to clients running
> >>> on 192.168.15.105 and 192.168.15.107 fails.
> >>>
> >>> I'm assuming that there would be an entry in a log on those two machines
> >>> detailing the failed connection attempt.
> >>>
> >>> What log file should I be looking at?
> >>>
> >>
> >> Hey CentOS FAH team members.  Do any of you have a GPU that is actually
> >> folding in CentOS 6?
> > 
> > I tried GPU folding in Centos-6, but the FAH log file showed continuous
> > errors for the GPU (which was, at the time a Nvidia n460GTX). Inquiries
> > on the FAH forums indicated that there are library incompatibilities 
> > on Centos-6 and that it would be difficult or impossible to make it
> > work.
> > 
> > I eventually upgraded to Centos-7 and then easily got GPU folding to
> > work on the same video card without difficulty.
> > 
> > FYI, I had previously (couple of years ago) attempted GPU folding on 
> > C6 using a 9800GT, and was told (again, on the FAH forums) that that
> > GPU was no longer supported. I'd guess that your 9600GT is also too
> > old.
> > 
> > Here's the FAH forum thread on that GPU compatibility issue:
> > https://foldingforum.org/viewtopic.php?f=80=25284=252427=9800GT#p252427
> > 
> > I've recently replaced the 460GTX with a new 750ti card, and found
> > two amazing benefits:
> > 1. according to my KillaWatt meter, the computer's power draw dropped from
> > 275-295 watts to 190-195 watts,
> > 2. my PPD total per week has gone from around 200K to more like 400K.
> >In fact, the last 3 weeks have all been around 440K, some slightly
> >lower, some a little higher.
> > 
> > The 750ti was a fairly cheap card, at $129.
> > 
> >> If you do please tell me exactly what video card and what driver you are
> >> using?
> > 
> > I'm using the Nvidia 340 driver from the elrepo repository. Be sure to
> > install the dkms package from epel before installing these nvidia drivers.
> > 
> >>
> >> I have a GeForce 9600 GT card that will not fold.  FAH finds the GPU and
> >> sets up a slot for it but it always says "Update Core" in the slot
> >> status field with zero progress.  I'm not happy with that.
> > 
> > See above for compatibility comments on this card.
> > 
> 
> Thanks for the input Fred.
> 
> The GeForce 9600 GT is listed in the GPUs.txt file as of Jan 20.  It
> should be compatible but I guess it won't work on C6 though.  I'm not in
> any hurry to move to C7.
> 

Mark:

You'll note that the 9800GT is listed there, too. nevertheless it isn't
supported.  I was told that current GPU software required a Nividia 
Fermi or later GPU, which leaves out the entire 9xxx series. See

http://nouveau.freedesktop.org/wiki/CodeNames/

Re upgrading to C7, I can see how you may be nervous about that, given
the number of things changed. I just upgraded my personal desktop during
Christmas week, seeing as how I never rush into upgrading to a new version
until it has had time to "settle". There are  a lot of differences, but
i'm learning to deal with them. When my old system gets old enough that
a lot of newer stuff will no longer build, then it's time for me to do
the deed. then all I have to do is steel myself up for a week of putting
it all back together. :)

good luck, Mark!

Fred

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
   "For the word of God is living and active. Sharper than any double-edged 
   sword, it penetrates even to dividing soul and spirit, joints and marrow; 
  it judges the thoughts and attitudes of the heart."  
 Hebrews 4:12 (niv) --
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-announce] CESA-2016:0082 Important CentOS 6 qemu-kvm Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2016:0082 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0082.html

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

i386:
a1f7d969256f40bceda80f8b528483daa4c46ffd1aa161d688b5213e82534728  
qemu-guest-agent-0.12.1.2-2.479.el6_7.4.i686.rpm

x86_64:
1e0bbdb48082401bf939242e8365ed87d978d810461fd5f5f8a07fb27cc68908  
qemu-guest-agent-0.12.1.2-2.479.el6_7.4.x86_64.rpm
5659db7806844d947e48a239a10e171bfe614f6ec55e41dc4456bbf681ed93a3  
qemu-img-0.12.1.2-2.479.el6_7.4.x86_64.rpm
02c1fb0cf175af0ef966c9bdba504598dcc296acd84943e84c6950b660119858  
qemu-kvm-0.12.1.2-2.479.el6_7.4.x86_64.rpm
3a706f6a6c9dd68d53403d9bf28e0460d166ccb14b5e236cb3a570fed8981945  
qemu-kvm-tools-0.12.1.2-2.479.el6_7.4.x86_64.rpm

Source:
15dd53d31a04e2fbff8ed17825a00a8db774e4b765d21cb8e425dfa7f420e1ed  
qemu-kvm-0.12.1.2-2.479.el6_7.4.src.rpm



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

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

[CentOS-announce] CESA-2016:0083 Important CentOS 7 qemu-kvm Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2016:0083 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0083.html

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

x86_64:
4b32c17ff1beedcb1f6061718d320fabefdfbc097c158d4b1dae708fd42fdcea  
libcacard-1.5.3-105.el7_2.3.i686.rpm
e67108224ae1a48a7e3fe50c844eb72cbb1f2577e14a8b4125223a7733fae0d1  
libcacard-1.5.3-105.el7_2.3.x86_64.rpm
d87a6e35540834492782b7b8912a4585aa1aed9bc8e8be2411869ac629992b2e  
libcacard-devel-1.5.3-105.el7_2.3.i686.rpm
de52616bc23aa304b8e5754dbd01ea01885be400a7c1971f175a71a4c319c8e2  
libcacard-devel-1.5.3-105.el7_2.3.x86_64.rpm
9d5121b15522703d568ef24aa6445d70aa25cce27bff49c94ebebe0d484b461e  
libcacard-tools-1.5.3-105.el7_2.3.x86_64.rpm
f6b81452aa1929447d9bc9b1801276e11c20f356a5f4817994da23073ce6  
qemu-img-1.5.3-105.el7_2.3.x86_64.rpm
21eaddeefef89775defa32724cb48d501184212b8d05d128a3c83911c1fc2099  
qemu-kvm-1.5.3-105.el7_2.3.x86_64.rpm
89bb7aa5f7b8d0ed361b7b9090f7a3a508213829237da9e39b3a1d7a674b4fcc  
qemu-kvm-common-1.5.3-105.el7_2.3.x86_64.rpm
eb6f93064a64451b608d32f292e94fad18c53a16790507fe2d97bf1d0b78e006  
qemu-kvm-tools-1.5.3-105.el7_2.3.x86_64.rpm

Source:
f963af3a6d471d8b82c5afef2fc76ef4f1dd3985e10ceafe2b04e04ef1571bf4  
qemu-kvm-1.5.3-105.el7_2.3.src.rpm



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

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

[CentOS] NICs order

[Daniel Ruiz Molina]

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 solve it?

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

Re: [CentOS-es] VM dentro de VM con KVM

[Ernesto Pérez Estévez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 02/01/2016 11:44 AM, daniel wrote:
> Buenos Dias Lista,
> 
> Con la novedad de que necesito virtualizar un hipervisor que
> contiene una maquina virtual, alguien me puede decir si esto es
> posible? Estoy utlizando KVM y al crear la máquina virtual en la
> opción del procesador selecciono "Copy host CPU configuration".
> Pero parece no tomar los cambios, ya que el

eso se llama nested virtualization, efectivamente le he usado... funcion
a.

saludos
epe

> tipo de procesador me aparece como un Broadwell pero yo tengo un
> Haswell, si selecciono la opción de Haswell el hypervisor si ve un
> procesador Haswell pero no ve la bandera VMX por lo que cuando
> trato de encender una VM me dice que la virtualizacion no esta
> activada en la configuración del CPU.
> 
> Saludos
> 
> Daniel Ortiz Gutiérrez 
> ___ CentOS-es mailing
> list CentOS-es@centos.org 
> https://lists.centos.org/mailman/listinfo/centos-es
> 


- -- 
CEDIA
La principal herramienta de Investigación en el Ecuador.

Calle La Condamine 12-109 "Casa Rivera".
Cuenca -  Ecuador
Telf: (593) 7405 1000 Ext. 4220/4223
i...@cedia.org.ec
www.cedia.org.ec
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWr44eAAoJEI8SQ0eoZD/X8NAQAI2xevJynqkzhFG4skvbP2ln
BXjf7knB9zjlm6nUSp+l8UzLjH5QVYpfuD1NeHTLDnNYc7l8/+RaMcYbVr/idovo
LcEAN9Pcp0k0ZJndIPPiBeLCopK0CHjLr2Na4V6xLlXKwguRfs1yWSODFi/Hepq+
kUgmG7c6EA6oM+1CrO/gMyMK69Fk3s/7pKGk2Cgs4JyxvHkgknTYfITBiwbdAoDR
zhta+fz+C65hP0kxdtpD+kLe/ROtfHyJREBFWyOpq2o62dqZAmZ7z1TJKezriZ8B
F2sBafAsWKwL+L/VzxCC8PXGfhTbOfUBu8O2CzTJ83unpkrsjkshZQlEji9XxcIR
DyNN+GYRh8ItP3p2jiv7NRWOfXACb1tfjixjBanrOsdnB1mlXlA2pK220OXbufb+
uM1Kk5PqfIpfmIzqnJY6wCNGMdwQLoubrYBLLfcSt0B4TdrvB9fJ/1j1njfq6kwA
az+SW7TpAtvfMHB8icznCw3Vmta2ndLg9zWmlTrnAzPaBBfpNakJuhWfUq8S5P9a
0m2uiPyf2Ecbp0cObUMtQKIXe2BJZjwOUy0txR8KOUitRlsq34b9XH/k7vQCRrL+
OS67xYuVIWzHdaWlOwP50dROyGBy6R4URmAtbVV1Iun/L39bqz5UyXdh9MRHiYDj
dp0bXix37Sge2mJk2ulK
=+ra6
-END PGP SIGNATURE-

Email secured by Check Point
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] NICs order

[Ricardo J. Barberis]

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 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 added as kernel
> command line parameters: 
>
> net.ifnames=1 and biosdevname=0

I tried that (and several other combinations), but with net.ifnames=0 which is 
what the docs say:
https://wiki.freedesktop.org/www/Software/systemd/PredictableNetworkInterfaceNames/

Nevertheless, I was never able to reliably use eth0 and eth1, I even got to 
the point of adding 'modprobe -r nic_module ; modprobe nic_module' 
to /etc/rc.d/rc.local to make it work, but it seemed a really ugly hack.

> I need to add big cautions here, my experience with this is on Ubuntu
> (where it's 70-net.rules)

Yeah, on CentOS 6 it aldo is that, on CentOS 7 it still works but I read 
somewhere that 60-net.rules was the new preferred name (and now it seems to 
be 80-net-setup-link.rules?)

> and a hardware platform which has 10 NICs. systemd/biosdevname... named the
> first six NICs 'ens...' and the last four 'eth...'.  ( I really do
> wish the developers would stop trying to decide what's best for us and leave
> control in our hands or at least provide documentation which is easily
> findable that allows us to take control back. ).

Amen :)

> 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.  I know where to set these parameters on Ubuntu but you'll
> have to find where on CentOS.  Hope this helps.

Ah, should have tried this. I'm probably not going to try it though (I'm 
already accustomed to my new naming scheme) but it can be useful to the OP, 
thanks.

> - Original Message -
> From: "Ricardo J. Barberis" 
> To: "CentOS mailing list" 
> Sent: Monday, February 1, 2016 8:31:42 AM
> Subject: Re: [CentOS] NICs order
>
> 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}, but after rebooting,
> > order is the same...
> >
> > How can I solve it?
> >
> > Thanks.
>
> You could put the MAC addresses in /etc/udev/rules.d/60-net.rules, e.g.:
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*",
> NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*",
> NAME="eth1"
>
>
> But that never worked reliably for me, no matter what I tried.
>
> In the end I had to use different names instead of eth0 and eth1, like:
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*",
> NAME="nic0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*",
> NAME="nic1"
>
>
> And also rename /etc/sysconfig/network-scripts/ifcfg-ethX to ifcfg-nicX and
> modify them accordingly.
>
> HTH,



-- 
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] NICs order

[Leroy Tennison]

> 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 rules to /etc/udev/rules.d, you should rebuild your initrd.

Thanks for the information.  I didn't and it has been working for a while 
(through reboots), what bad thing(s) may happen if I don't?

- Original Message -
From: "Gordon Messmer" 
To: "CentOS mailing list" 
Sent: Monday, February 1, 2016 11:26:38 AM
Subject: Re: [CentOS] NICs order

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 systemd/udev interface 
renaming feature.  biosdevname=0 disables the biosdevname interface 
renaming feature, which is completely separate.  If you want the 
traditional, non-deterministic Linux interface naming, you must specify 
both.

Also, if you add rules to /etc/udev/rules.d, you should rebuild your initrd.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Confidentiality Notice | This email and any included attachments may be 
privileged, confidential and/or otherwise protected from disclosure.  Access to 
this email by anyone other than the intended recipient is unauthorized.  If you 
believe you have received this email in error, please contact the sender 
immediately and delete all copies.  If you are not the intended recipient, you 
are notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

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

[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-2016:0082 Important CentOS 6 qemu-kvmSecurity Update
  (Johnny Hughes)
   2. CESA-2016:0083 Important CentOS 7 qemu-kvmSecurity Update
  (Johnny Hughes)


--

Message: 1
Date: Mon, 1 Feb 2016 10:06:38 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2016:0082 Important CentOS 6 qemu-kvm
Security Update
Message-ID: <20160201100638.ga48...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2016:0082 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0082.html

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

i386:
a1f7d969256f40bceda80f8b528483daa4c46ffd1aa161d688b5213e82534728  
qemu-guest-agent-0.12.1.2-2.479.el6_7.4.i686.rpm

x86_64:
1e0bbdb48082401bf939242e8365ed87d978d810461fd5f5f8a07fb27cc68908  
qemu-guest-agent-0.12.1.2-2.479.el6_7.4.x86_64.rpm
5659db7806844d947e48a239a10e171bfe614f6ec55e41dc4456bbf681ed93a3  
qemu-img-0.12.1.2-2.479.el6_7.4.x86_64.rpm
02c1fb0cf175af0ef966c9bdba504598dcc296acd84943e84c6950b660119858  
qemu-kvm-0.12.1.2-2.479.el6_7.4.x86_64.rpm
3a706f6a6c9dd68d53403d9bf28e0460d166ccb14b5e236cb3a570fed8981945  
qemu-kvm-tools-0.12.1.2-2.479.el6_7.4.x86_64.rpm

Source:
15dd53d31a04e2fbff8ed17825a00a8db774e4b765d21cb8e425dfa7f420e1ed  
qemu-kvm-0.12.1.2-2.479.el6_7.4.src.rpm



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



--

Message: 2
Date: Mon, 1 Feb 2016 10:07:16 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2016:0083 Important CentOS 7 qemu-kvm
Security Update
Message-ID: <20160201100716.ga48...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2016:0083 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0083.html

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

x86_64:
4b32c17ff1beedcb1f6061718d320fabefdfbc097c158d4b1dae708fd42fdcea  
libcacard-1.5.3-105.el7_2.3.i686.rpm
e67108224ae1a48a7e3fe50c844eb72cbb1f2577e14a8b4125223a7733fae0d1  
libcacard-1.5.3-105.el7_2.3.x86_64.rpm
d87a6e35540834492782b7b8912a4585aa1aed9bc8e8be2411869ac629992b2e  
libcacard-devel-1.5.3-105.el7_2.3.i686.rpm
de52616bc23aa304b8e5754dbd01ea01885be400a7c1971f175a71a4c319c8e2  
libcacard-devel-1.5.3-105.el7_2.3.x86_64.rpm
9d5121b15522703d568ef24aa6445d70aa25cce27bff49c94ebebe0d484b461e  
libcacard-tools-1.5.3-105.el7_2.3.x86_64.rpm
f6b81452aa1929447d9bc9b1801276e11c20f356a5f4817994da23073ce6  
qemu-img-1.5.3-105.el7_2.3.x86_64.rpm
21eaddeefef89775defa32724cb48d501184212b8d05d128a3c83911c1fc2099  
qemu-kvm-1.5.3-105.el7_2.3.x86_64.rpm
89bb7aa5f7b8d0ed361b7b9090f7a3a508213829237da9e39b3a1d7a674b4fcc  
qemu-kvm-common-1.5.3-105.el7_2.3.x86_64.rpm
eb6f93064a64451b608d32f292e94fad18c53a16790507fe2d97bf1d0b78e006  
qemu-kvm-tools-1.5.3-105.el7_2.3.x86_64.rpm

Source:
f963af3a6d471d8b82c5afef2fc76ef4f1dd3985e10ceafe2b04e04ef1571bf4  
qemu-kvm-1.5.3-105.el7_2.3.src.rpm



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



--

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


End of CentOS-announce Digest, Vol 132, Issue 1
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] LUSTRE Install Guide

[Ben Archuleta]

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
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System

[Sorin Srbu]

> -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 removing all of your files
> from / is no longer recommended. 

I'm not following, has it ever been recommended (on a working system)??

Or is this one of those ironic posts? 8-)

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

[CentOS-es] VM dentro de VM con KVM

[daniel]

Buenos Dias Lista,

Con la novedad de que necesito virtualizar un hipervisor que contiene una
maquina virtual, alguien me puede decir si esto es posible? Estoy utlizando
KVM y al crear la máquina virtual en la opción del procesador selecciono
"Copy host CPU configuration". Pero parece no tomar los cambios, ya que el
tipo de procesador me aparece como un Broadwell pero yo tengo un Haswell,
si selecciono la opción de Haswell el hypervisor si ve un procesador
Haswell pero no ve la bandera VMX por lo que cuando trato de encender una
VM me dice que la virtualizacion no esta activada en la configuración del
CPU.

Saludos

Daniel Ortiz Gutiérrez
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] NICs order

[Mauricio Tavares]

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 HWADDR attribute in
>> /etc/sysconfig/network-scripts/ifcfg-etc{0,1}, but after rebooting,
>> order is the same...
>>
>> How can I solve it?
>>
>> Thanks.
>
> You could put the MAC addresses in /etc/udev/rules.d/60-net.rules, e.g.:
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", 
> NAME="eth0"
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", 
> NAME="eth1"
>
>
> But that never worked reliably for me, no matter what I tried.
>
  That is interesting to know. I have not run Centos 7 in a
machine with multiple ports yet, but on 6 blowing up
/etc/udev/rules.d/60-net.rules would make it select the interfaces by
the same order as the MAC.

UPDATE: I just checked my Centos 6 box and it uses
/etc/udev/rules.d/70-persistent-net.rules but in my Centos 7 vm, I
only see a different file altogether

[raub@duckwitch ~]$ ls -l /etc/udev/rules.d/
total 0
-rw-r--r-- 1 root root 0 Jul 25  2014 80-net-name-slot.rules
[raub@duckwitch ~]$



> In the end I had to use different names instead of eth0 and eth1, like:
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", 
> NAME="nic0"
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", 
> NAME="nic1"
>
>
> And also rename /etc/sysconfig/network-scripts/ifcfg-ethX to ifcfg-nicX and
> modify them accordingly.
>
> HTH,
> --
> Ricardo J. Barberis
> Usuario Linux Nº 250625: http://counter.li.org/
> Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
> Senior SysAdmin / IT Architect - www.DonWeb.com
> ___
> 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] NICs order

[Ricardo J. Barberis]

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}, but after rebooting,
> order is the same...
>
> How can I solve it?
>
> Thanks.

You could put the MAC addresses in /etc/udev/rules.d/60-net.rules, e.g.:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"


But that never worked reliably for me, no matter what I tried.

In the end I had to use different names instead of eth0 and eth1, like:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="nic0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="nic1"


And also rename /etc/sysconfig/network-scripts/ifcfg-ethX to ifcfg-nicX and
modify them accordingly.

HTH,
-- 
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] odoo

[Elio Bastias, Project Managers]

Mauricio,
Ok, de nada si te puedo ayudar, enviame un mail.-
Saludos,

El 30 de enero de 2016, 11:10, Mauricio Pastorini <
mpastor...@soporte-online.cl> escribió:

> Gracias Elio, he estado revisando, finalmente desistí de instalarla versión
> 9 ya que no esta disponible nodejs-clean-css para Centso 6.
>
> ahora trabajando en la versión 8.
>
> El 30 de enero de 2016, 9:44, Elio Bastias, Project Managers <
> elio.bast...@gmail.com> escribió:
>
> > Mauricio,
> > Como estas,
> > Buenos días, desde ARG.
> > Te recomiendo que entres a los foros de la comunidad de ODOO, hay tenes
> > mucho info sobre el tema de implmentación, te lo comento por que me
> pasaba
> > algo similar pero con la DB y lo pude resolver ahí.-
> >
> > Saludos
> >
> > El 26 de enero de 2016, 17:58, Mauricio Pastorini <
> > mpastor...@soporte-online.cl> escribió:
> >
> > > Buenas tardes, tengo un VPS con Centos 6.7 y WHM estoy tratando de
> > instalar
> > > odoo v 9 y tengo problemas con python 2.7 y nodejs-clean-css
> > >
> > > alguna experiencia al respecto. ?
> > >
> > > gracias
> > >
> > > --
> > > *Mauricio Pastorini Torres*
> > > Ingeniero Civil Informático
> > > *Sistemas de Gestión Online Ltda.*
> > > http://www.gestion-online.cl
> > > twitter: *@mauricio1964*
> > > E-Mail: mpastor...@soporte-online.cl 
> > > *+56 9  7439*
> > > ___
> > > CentOS-es mailing list
> > > CentOS-es@centos.org
> > > https://lists.centos.org/mailman/listinfo/centos-es
> > >
> >
> >
> >
> > --
> > Elio Bastias
> > Project Manager
> > Smart - IT
> > |Open Source Innovation | Open Source Communications
> > Estrategia y Management en Comunicaciones e Infraestructurade IT
> >
> > |Gtalk/Mail: consul...@eliobastias.com.ar
> >
>
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

[CentOS] CentOS 7 and network printers: FYI

[m . roth]

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
cups-browsed service.

Which appears to be brand new with 7, and I have not seen any mention of it.

Enabled and started, and the network printers are visible on the cups
localhost web page->printers.

  mark

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

Re: [CentOS] NICs order

[Leroy Tennison]

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 added 
as kernel command line parameters:

net.ifnames=1 and biosdevname=0

I need to add big cautions here, my experience with this is on Ubuntu (where 
it's 70-net.rules) and a hardware platform which has 10 NICs.  
systemd/biosdevname... named the first six NICs 'ens...' and the last four 
'eth...'.  ( I really do wish the developers would stop trying to decide 
what's best for us and leave control in our hands or at least provide 
documentation which is easily findable that allows us to take control back. 
).  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.  I know where to set these parameters on Ubuntu but you'll 
have to find where on CentOS.  Hope this helps.

- Original Message -
From: "Ricardo J. Barberis" 
To: "CentOS mailing list" 
Sent: Monday, February 1, 2016 8:31:42 AM
Subject: Re: [CentOS] NICs order

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}, but after rebooting,
> order is the same...
>
> How can I solve it?
>
> Thanks.

You could put the MAC addresses in /etc/udev/rules.d/60-net.rules, e.g.:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"


But that never worked reliably for me, no matter what I tried.

In the end I had to use different names instead of eth0 and eth1, like:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="nic0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="nic1"


And also rename /etc/sysconfig/network-scripts/ifcfg-ethX to ifcfg-nicX and
modify them accordingly.

HTH,
-- 
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Confidentiality Notice | This email and any included attachments may be 
privileged, confidential and/or otherwise protected from disclosure.  Access to 
this email by anyone other than the intended recipient is unauthorized.  If you 
believe you have received this email in error, please contact the sender 
immediately and delete all copies.  If you are not the intended recipient, you 
are notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7 and network printers: FYI

[Valeri Galtsev]

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:
>
> # NOTE: This file is not part of CUPS. You need to start & enable
> cups-browsed service.
>
> Which appears to be brand new with 7, and I have not seen any mention of
> it.
>
> Enabled and started, and the network printers are visible on the cups
> localhost web page->printers.

Unrelated to the topic, but may be helpful for somebody who uses cups
browsing option. I usually turn off cups browsing. Here is why: someone
brings laptop to our network, and may have one of his/her printers
"shared". Somebody else finds, sets it up, and happily uses it. Till the
first person goes away. Then second person comes to me telling my printer
doesn't work. Which is not my printer, in a sense I can do nothing about
what the second person had done about that printer...

Just my $0.02

Valeri

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

[CentOS] Latest version of kate editor

[H]

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.

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

Re: [CentOS] NICs order

[Gordon Messmer]

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 systemd/udev interface 
renaming feature.  biosdevname=0 disables the biosdevname interface 
renaming feature, which is completely separate.  If you want the 
traditional, non-deterministic Linux interface naming, you must specify 
both.


Also, if you add rules to /etc/udev/rules.d, you should rebuild your initrd.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos