Re: [CentOS] dhcpcd.conf

[Pete Biggs]

On Mon, 2017-02-13 at 17:57 -0800, Alice Wonder wrote:
> Hi,
> 
> ran into a problem w/ linode hosted VM where IPv6 address changed after 
> they migrated it to a different host.
> 
> They claim I can fix it with
> 
> sed -i 's/slaac private/slaac hwaddr/' /etc/dhcpcd.conf
> 
> However there appears to be no dhcpcd.conf on any of my CentOS 7 systems.
> 
> What is the CentOS 7 equivalent?
> 
CentOS 7 uses dhclient not dhcpc by default as a DHCP client. That in
turn is usually controlled by NetworkManager.

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

[CentOS] CentOS-announce Digest, Vol 144, Issue 4

[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-2017:0269 Critical CentOS 6  java-1.7.0-openjdk Security
  Update (Johnny Hughes)
   2. CESA-2017:0269 Critical CentOS 5  java-1.7.0-openjdk Security
  Update (Johnny Hughes)
   3. CESA-2017:0269 Critical CentOS 7  java-1.7.0-openjdk Security
  Update (Johnny Hughes)


--

Message: 1
Date: Mon, 13 Feb 2017 17:16:15 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2017:0269 Critical CentOS 6
java-1.7.0-openjdk Security Update
Message-ID: <20170213171615.ga22...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2017:0269 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0269.html

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

i386:
5e812e4583b71107b72779cfc77f78c7fdc1a147a56126136f87d14cc3b4efb8  
java-1.7.0-openjdk-1.7.0.131-2.6.9.0.el6_8.i686.rpm
ce382ede1a4eac4ffdba9aa870cc9c06a083749fb40b4d9ca342b17354836553  
java-1.7.0-openjdk-demo-1.7.0.131-2.6.9.0.el6_8.i686.rpm
4ad8906f9df3db8a1812a2b3b326762a9c2a694d6a494eb0e5220b9596d0718c  
java-1.7.0-openjdk-devel-1.7.0.131-2.6.9.0.el6_8.i686.rpm
191ff23c7449d819ca45243beb432c700c66476597fd08c57c39ae8ceda8ffd2  
java-1.7.0-openjdk-javadoc-1.7.0.131-2.6.9.0.el6_8.noarch.rpm
800b7ed498f4b4fd6d0e024652ad05eef8682237fe2349f82a69106a4ca09d54  
java-1.7.0-openjdk-src-1.7.0.131-2.6.9.0.el6_8.i686.rpm

x86_64:
d9381ac7f354a3d066efe9ef1160264309f46c9373c5b28e26365ca3d81dad1a  
java-1.7.0-openjdk-1.7.0.131-2.6.9.0.el6_8.x86_64.rpm
0057a0bbfe965f73222b4806b7be62f4b79507a1c9903ccc5c4daeb65cd1addf  
java-1.7.0-openjdk-demo-1.7.0.131-2.6.9.0.el6_8.x86_64.rpm
7872f4fef9d877d2e9de8d9e1c11cd64e6afaf3620266997706fcdad9d9b196d  
java-1.7.0-openjdk-devel-1.7.0.131-2.6.9.0.el6_8.x86_64.rpm
191ff23c7449d819ca45243beb432c700c66476597fd08c57c39ae8ceda8ffd2  
java-1.7.0-openjdk-javadoc-1.7.0.131-2.6.9.0.el6_8.noarch.rpm
3c2b900af1a17e21b63aab28f034e6026d983cf96e1ffd7231a677e1ada30623  
java-1.7.0-openjdk-src-1.7.0.131-2.6.9.0.el6_8.x86_64.rpm

Source:
bf4fbc5136e1640ade4a455baa073d802fc25f099af1075fd636d3d1484ee9cb  
java-1.7.0-openjdk-1.7.0.131-2.6.9.0.el6_8.src.rpm



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



--

Message: 2
Date: Mon, 13 Feb 2017 17:21:05 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2017:0269 Critical CentOS 5
java-1.7.0-openjdk Security Update
Message-ID: <20170213172105.ga27...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2017:0269 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0269.html

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

i386:
f2fb7e8343760a6cc3535a6124bd71411b20795da0ac056b8361c8826ce9a69e  
java-1.7.0-openjdk-1.7.0.131-2.6.9.0.el5_11.i386.rpm
72c2fee994a496787fe7a8080b0871b0d015c63fc57cf5f2457107620bbb9ac1  
java-1.7.0-openjdk-demo-1.7.0.131-2.6.9.0.el5_11.i386.rpm
2563c40d3b9b9d9ce7787284a8f8808491d4adb7af5ee3a6f9a1daeba47e8012  
java-1.7.0-openjdk-devel-1.7.0.131-2.6.9.0.el5_11.i386.rpm
d4ca35c4e689c276e1f746664e9d9f7fd46a44df643bc7e42a87183473870530  
java-1.7.0-openjdk-javadoc-1.7.0.131-2.6.9.0.el5_11.i386.rpm
c9e4741823aec2cfc8674f0c0bf52d87eca0fb31c5ea682a7d4208d1d2f29928  
java-1.7.0-openjdk-src-1.7.0.131-2.6.9.0.el5_11.i386.rpm

x86_64:
b20918246adb9966adbdcc06306e0863392d4cbf327bdfb570d4ade8bf73  
java-1.7.0-openjdk-1.7.0.131-2.6.9.0.el5_11.x86_64.rpm
e0ce4d7487d50528ea6fffb32c47f5e2405f3863a91b7ca85025b5b86e07ae99  
java-1.7.0-openjdk-demo-1.7.0.131-2.6.9.0.el5_11.x86_64.rpm
f18a46c869e0fe0bda885e6876f117e3a35604ef23a3c7cdc6c71df754d59ab1  
java-1.7.0-openjdk-devel-1.7.0.131-2.6.9.0.el5_11.x86_64.rpm
4a16817c9069a4f5f7d176df443a30e6309bb3551244bfe057054c058b329b70  
java-1.7.0-openjdk-javadoc-1.7.0.131-2.6.9.0.el5_11.x86_64.rpm
1d7b5898fd46ae5a447d7b8116919e8e7e16179b40ea3551c0f2ed62b5d1e22f  
java-1.7.0-openjdk-src-1.7.0.131-2.6.9.0.el5_11.x86_64.rpm

Source:
41d3efcc5b6cccbb9ea0af1bde1b2fc4aab16274d55d26db3e64924068128bc8  
java-1.7.0-openjdk-1.7.0.131-2.6.9.0.el5_11.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.c

Re: [CentOS] CentOS 7, systemd, NetworkMangler, oh, my

[Johnny Hughes]

On 02/13/2017 11:36 AM, peter.winterflood wrote:
> On 13/02/17 16:49, James Hogarth wrote:
>> On 13 February 2017 at 16:17, peter.winterflood
>>  wrote:
>>>
>>>
>>> there's a really good solution to this.
>>>
>>> yum remove NetworkManager*
>>>
>>> chkconfig network on
>>>
>>> service network start
>>>
>>> and yes thats all under fedora 25, and centos 7.
>>>
>>> works like a charm.
>>>
>>> sometimes removing NM leaves resolv.conf pointing to the networkmanager
>>> directory, and its best to check this, and replace your resolv.conf link
>>> with a file with the correct settings.
>>>
>>> sorry if this upsets the people who maintain network mangler, but its
>>> inappropriate on a server.
>>>
>>>
>> This is terribly bad advice I'm afraid ...
>>
>> https://access.redhat.com/solutions/783533
>>
>> The legacy network service is a fragile compilation of shell scripts
>> (which is why certain changes like some bonding or tagging alterations
>> require a full system restart or very careful unpicking manually with
>> ip) and is effectively deprecated in RHEL at this time due to major
>> bug fixes only but no feature work.
>>
>> You really should have a read through this as well:
>>
>> https://www.hogarthuk.com/?q=node/8
>>
>> On EL6 yes NM should be removed on anything but a wifi system but on
>> EL7 unless you fall into a specific edge case as per the network docs:
>>
>> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Networking_Guide/index.html
>>
>>
>> you really should be using NM for a variety of reasons.
>>
>> Incidentally Mark, this had nothing to do with systemd ... I wish you
>> would pick your topics a little more appropriately rather than
>> tempting the usual flames.
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
> 
> James
> 
> This was not A flame at all, but another voice of frustration at the
> ongoing
> 
> adoption of workstation like features of the Redhat OS.
> 
> heres one of the reasons not to use NM in a server
> 
> we use bonding on all our systems
> 
> from that article you posted
> 
> Certain interface bonding configuration options as defined by the
> BONDING_OPTS parameter in the interface's ifcfg file may not be
> compatible with NetworkManager. ( Solution 1249593
>  )
> 
> in fact anyone who has tried to use bonding with NM will know why I
> dislike it.
> 
> thanks for that, article, this next bug had caught me, on an older build
> , now its fixed, but the fix did not go and backfix a broken config.
> 
> When transitioning from NetworkManager to using the network initscript,
> the default gateway parameter in the interface's ifcfg file will be
> depicted as 'GATEWAY0'. In order for the ifcfg file to be compatible
> with the network initscript, this parameter must be renamed to
> 'GATEWAY'. This limitation will be addressed in an upcoming release of
> RHEL7.
> 
> one to watch out for on the removing NM, plus the resolv.conf one.
> 
> Anyway, for anyone else, make you own mind up whether this is good or
> bad advise, test it, and see how your mileage varies, Ive had more
> problems with NM than ive had with initscripts.

That is your opinion .. and there are thousands of engineers from almost
every major Linux distro who disagree with you.

I am personally fine if people want to turn off NM .. but that is not
what any of the Enterprise distros are doing.

Opinions are fine .. I sometimes turn off NM as well .. and for some
cases it is best.

But as Linux installs become more and more complicated and it is not
some individual machines in a rack but clouds, clusters, and containers
with software defined networking and individual segments for specific
applications spread out within the network, only talking to one another
.. etc.  Well, NM will be much more important.

I get it .. but no one needed a hand held cell phone before 1973 and no
one needed a smart phone before 2007.  Now, almost everyone has a smart
cell and land lines are dying.  Technology moves forward.  People want
integrated cloud, container, SDN technology, etc.  Used a VCR or
Cassette Player lately?




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7, systemd, NetworkMangler, oh, my

[m . roth]

Johnny Hughes wrote:

> I get it .. but no one needed a hand held cell phone before 1973 and no
> one needed a smart phone before 2007.  Now, almost everyone has a smart
> cell and land lines are dying.  Technology moves forward.  People want
> integrated cloud, container, SDN technology, etc.  Used a VCR or
> Cassette Player lately?

I have no intention of *ever* getting an annoyaphone - I'm online all day
at work, before I go to work, and most evenings, in front of a *real*
computer. My cell's a flipphone, and I *LOATHE* texts... because the
protocol was developed for freakin' pagers, and after a job 20 years ago,
I don't EVER want that again.

And my land line phone has *much* better voice quality than any cell/mobile.*

And yes, I very happily have my VCR, for all the tapes I have, and a good
dual cassette deck (OK, I do want to burn them to disk... along with my
200-300 vinyl records...oh, that's right, vinyl's coming back. 

  mark, who's older than a lot of you

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

[CentOS] RAID questions

[tdukes]

Hello,

Just a couple questions regarding RAID. Here's thesituation.

I bought a 4TB drive before I upgraded from 6.8 to 7.3. I'm not too far
into this that Ican't start over. I wanted disk space to backup 3 other
machines. I way overestimated what I needed for full, incremental and
image backups with UrBackup.I've used less than 1TB so far. I would like
to add an additional drive to makeit a RAID server.

I may use a PCIe SSD for the boot drive if I can find onecompatible with
my old hardware.

1- Better to go with a hardware RAID (mainboardsupported) or software?

2 - Can an existing drive with data on it be used as aRAID drive without
losing current data?

3 - Can additional drive(s) be added later with a changein RAID level
without current data loss?

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

Re: [CentOS] RAID questions

[John R Pierce]

On 2/14/2017 4:48 PM, tdu...@palmettoshopper.com wrote:

1- Better to go with a hardware RAID (mainboardsupported) or software?


I would only use hardware raid if its a card with battery (or 
supercap+flash) backed writeback cache, such as a megaraid, areca, etc.  
otherwise I would use mdraid mirroring.




2 - Can an existing drive with data on it be used as aRAID drive without
losing current data?


software mdraid will let you add a mirror to an existing disk.or if 
its using LVM, you can mirror in LVM now.



3 - Can additional drive(s) be added later with a changein RAID level
without current data loss?


Only some systems support that sort of restriping, and its a dangerous 
activity (if the power fails or system crashes midway through the 
restriping operation, its probably not restartable, you quite likely 
will lose the whole volume)...with LVM mirroring, you can add more 
pairs of drives as additional mirrors to the volume group.



--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] RAID questions

[Digimer]

On 14/02/17 07:58 PM, John R Pierce wrote:
> On 2/14/2017 4:48 PM, tdu...@palmettoshopper.com wrote:
>> 1- Better to go with a hardware RAID (mainboardsupported) or software?
> 
> I would only use hardware raid if its a card with battery (or
> supercap+flash) backed writeback cache, such as a megaraid, areca, etc. 
> otherwise I would use mdraid mirroring.
> 
> 
>> 2 - Can an existing drive with data on it be used as aRAID drive without
>> losing current data?
> 
> software mdraid will let you add a mirror to an existing disk.or if
> its using LVM, you can mirror in LVM now.

Note; If you're mirroring /boot, you may need to run grub install on
both disks to ensure they're both actually bootable (or else you might
find yourself doing an emergency boot off the CentOS ISO and installing
grub later).

>> 3 - Can additional drive(s) be added later with a changein RAID level
>> without current data loss?
> 
> Only some systems support that sort of restriping, and its a dangerous
> activity (if the power fails or system crashes midway through the
> restriping operation, its probably not restartable, you quite likely
> will lose the whole volume)...with LVM mirroring, you can add more
> pairs of drives as additional mirrors to the volume group.
> 
> 


-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] RAID questions

[John R Pierce]

On 2/14/2017 5:08 PM, Digimer wrote:

Note; If you're mirroring /boot, you may need to run grub install on
both disks to ensure they're both actually bootable (or else you might
find yourself doing an emergency boot off the CentOS ISO and installing
grub later).


I left that out because the OP was talking about booting from a seperate 
SSD, and only mirroring his data drive.



--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] RAID questions

[Digimer]

On 14/02/17 08:12 PM, John R Pierce wrote:
> On 2/14/2017 5:08 PM, Digimer wrote:
>> Note; If you're mirroring /boot, you may need to run grub install on
>> both disks to ensure they're both actually bootable (or else you might
>> find yourself doing an emergency boot off the CentOS ISO and installing
>> grub later).
> 
> I left that out because the OP was talking about booting from a seperate
> SSD, and only mirroring his data drive.

Ah, ok, that makes sense.

-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] RAID questions

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of John R
> Pierce
> Sent: Tuesday, February 14, 2017 8:13 PM
> To: centos@centos.org
> Subject: Re: [CentOS] RAID questions
> 
> On 2/14/2017 5:08 PM, Digimer wrote:
> > Note; If you're mirroring /boot, you may need to run grub install on
> > both disks to ensure they're both actually bootable (or else you might
> > find yourself doing an emergency boot off the CentOS ISO and
> > installing grub later).
> 
> I left that out because the OP was talking about booting from a seperate
SSD,
> and only mirroring his data drive.
> 
Thanks!!

I'm only considering a SSD drive due to the lack of 3.5 drive space. I have
unused 5.25 bays but I'd have to get an adapter.

I probably don't need to go the RAID 10 route. I just need/would like some
kind of redundancy for backups. This is a home system but over the years due
to HD, mainboard, power supply failures, I have lost photos, etc, that can
never be replaced. Backing up gigabytes/terabytes of data to cloud storage
would be impractical due to bandwidth limitations.

Just looking for a solution better than what I have. A simple mirror is more
than I have now. I'd like to add another drive for redundancy and go from
there.

What should I do?

TIA

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

Re: [CentOS] CentOS 7, systemd, NetworkMangler, oh, my

[Alice Wonder]

On 02/14/2017 06:49 AM, Johnny Hughes wrote:



But as Linux installs become more and more complicated and it is not
some individual machines in a rack but clouds, clusters, and containers
with software defined networking and individual segments for specific
applications spread out within the network, only talking to one another
.. etc.  Well, NM will be much more important.


All due respect, when we drop KISS it is rarely a good thing.

Issue I am dealing with right now - all my VMs with linode are CentOS 7.

Three of them are nameservers, I have to run my own because some of my 
sites - I use certificate authorities but do not trust them, DNSSEC with 
DANE is a must, and with DNSSEC the only way to make sure I'm the only 
one with access to the private signing key is to manage the zone files 
myself.


One of the VMs (in London data center) was recently migrated to a 
different machine, I think because of a bad fan in the server.


NSD never properly came up. After investigation, it is because the IPv6 
address changed.


Trying to figure out why the IPv6 address changed has been a nightmare.

Linode support suspects the reason is because the VM is using slaac 
private to request the IP address instead of slaac hwaddr - and 
suggested that I change the /etc/dhcpcd.conf file.


Well CentOS 7 doesn't use that, and trying to figure out where in the 
mess of /etc/sysconfig/network-scripts the problem is occurring has 
caused me much frustration.


Why the bleep can't stuff like this be simple KISS with simple key=value 
configuration files?


So for now, that particular nameserver is only IPv4 until I figure it 
out, and modifying the network scripts to try and figure out how to fix 
it raises my blood pressure because if a modification causes the IPv4 
not to work, recovering becomes a real PITA.

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

Re: [CentOS] CentOS 7, systemd, NetworkMangler, oh, my

[Alice Wonder]

On 02/14/2017 08:40 PM, Alice Wonder wrote:

On 02/14/2017 06:49 AM, Johnny Hughes wrote:



But as Linux installs become more and more complicated and it is not
some individual machines in a rack but clouds, clusters, and containers
with software defined networking and individual segments for specific
applications spread out within the network, only talking to one another
.. etc.  Well, NM will be much more important.


All due respect, when we drop KISS it is rarely a good thing.

Issue I am dealing with right now - all my VMs with linode are CentOS 7.

Three of them are nameservers, I have to run my own because some of my
sites - I use certificate authorities but do not trust them, DNSSEC with
DANE is a must, and with DNSSEC the only way to make sure I'm the only
one with access to the private signing key is to manage the zone files
myself.

One of the VMs (in London data center) was recently migrated to a
different machine, I think because of a bad fan in the server.

NSD never properly came up. After investigation, it is because the IPv6
address changed.

Trying to figure out why the IPv6 address changed has been a nightmare.

Linode support suspects the reason is because the VM is using slaac
private to request the IP address instead of slaac hwaddr - and
suggested that I change the /etc/dhcpcd.conf file.

Well CentOS 7 doesn't use that, and trying to figure out where in the
mess of /etc/sysconfig/network-scripts the problem is occurring has
caused me much frustration.

Why the bleep can't stuff like this be simple KISS with simple key=value
configuration files?

So for now, that particular nameserver is only IPv4 until I figure it
out, and modifying the network scripts to try and figure out how to fix
it raises my blood pressure because if a modification causes the IPv4
not to work, recovering becomes a real PITA.
___


As far as me not trusting certificate authorities - I read a Netcraft 
report a year ago or so that estimated about 100 fraudulent TLS 
certificates that browsers accept as valid are issued every month.


PKI is seriously broken, it depends upon trusting certificate 
authorities that have repeatedly demonstrated they put profit over 
proper validation before issuing certificates.


DNSSEC + DANE is the only viable solution, and DANE really only is 
secure when you know no one else has access to the private KSK ans ZSK 
and that pretty much means running your own authoritative nameservers, 
where a stable IP address is a must and VMs like what linode offers are 
the most cost effective way of making sure you have enough in 
geographically diverse locations.


It's a shame that Network Manager makes things so difficult, dhcp is how 
VM hosting service assign the IP addresses and they really shouldn't change.


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

Re: [CentOS] RAID questions

[Andreas Benzler]

Am Dienstag, den 14.02.2017, 20:21 -0500 schrieb Digimer:
> On 14/02/17 08:12 PM, John R Pierce wrote:
> > On 2/14/2017 5:08 PM, Digimer wrote:
> >> Note; If you're mirroring /boot, you may need to run grub install on
> >> both disks to ensure they're both actually bootable (or else you might
> >> find yourself doing an emergency boot off the CentOS ISO and installing
> >> grub later).
> > 
> > I left that out because the OP was talking about booting from a seperate
> > SSD, and only mirroring his data drive.
> 
> Ah, ok, that makes sense.
> 
What we did test out and use on huge centos file system servers is 

http://relax-and-recover.org/

Rear put you working kernel, needed kernel for your machine for example,
onto usb or iso.  A Bare-metal copy of you base system for recovery
disaster can copy back over another value.

Sincerely

Andy


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