On Tue, Apr 11, 2017 at 01:40:21AM -0700, Alice Wonder wrote:
> Hello list -
>
> http://unix.stackexchange.com/questions/90035/how-to-set-dns-resolver-in-fedora-using-network-manager
>
> That says it works for CentOS 5 and I *suspect* the methods there (3 listed)
> would work, but what is the bes
On 04/11/2017 07:09 PM, Keith Keller wrote:
On 2017-04-11, Gordon Messmer wrote:
You also don't have the flexibility to replace the kernel. Or glibc.
But you do, don't you? It'll take you months to replace them, or years
to rewrite, but you*can* do it.
The same is true of systemd, which
On Tue, April 11, 2017 9:09 pm, Keith Keller wrote:
> On 2017-04-11, Gordon Messmer wrote:
>>
>> You also don't have the flexibility to replace the kernel. Or glibc.
>
> But you do, don't you? It'll take you months to replace them, or years
> to rewrite, but you *can* do it.
I agree. We had on
On 2017-04-11, Gordon Messmer wrote:
>
> You also don't have the flexibility to replace the kernel. Or glibc.
But you do, don't you? It'll take you months to replace them, or years
to rewrite, but you *can* do it. That is the freedom that open source
software provides that proprietary OSes do
On Tue, Apr 11, 2017 at 05:11:25PM -0500, Valeri Galtsev wrote:
>
> On Tue, April 11, 2017 4:41 pm, Warren Young wrote:
> > On Apr 11, 2017, at 11:28 AM, Scott Robbins wrote:
> >>
> >> (though they're talking of trying OpenRC)
> >
> > Not just talking. TrueOS, neé PC-BSD, now runs on OpenRC.
>
On Tue, Apr 11, 2017 at 3:58 PM, H wrote:
> On 3/13/2017 1:09 PM, Nux! wrote:
>>
>> yum -y install
>> http://mirrors.coreix.net/elrepo/elrepo/el6/x86_64/RPMS/kmod-jfs-0.0-1.el6.elrepo.x86_64.rpm
>>
>> (that's for 64bit, adjust the url accordingly for 32bit)
>>
>> it won't hose your system
>> Nux!
We are running into an issue relating to snmpd and the temporary partitions
created in /run/user/ so any insight by someone with magical
net-snmp skills would be much appreciated.
Our monitoring app walks all our servers.
We modify /etc/snmp/snmpd.conf on all our servers to just have one line:
roc
Hi, I would like to see this addressed.
I found more information on the issue at
https://kb.isc.org/article/AA-01183/0/Linux-connection-tracking-and-DNS.html
Is there a firewalld solution to this issue?
On 04/11/2017 11:05 AM, Chris Adams wrote:
One additional DNS server note: you should dis
Am 11.04.2017 um 19:17 schrieb Nicolas Kovacs :
>
> Le 11/04/2017 à 19:09, John R Pierce a écrit :
>> do you mean 'authoritative DNS server' ?
>
> Yes.
Totally off-topic, but it hits my mind right now. We are receiving a big
amount of version queries on our public dns infra from a broad range o
Thank you, installed it and it worked fine. Now I am looking for the same for
CentOS 7... It did not look like you have that in your repository?
On 3/13/2017 1:09 PM, Nux! wrote:
yum -y install
http://mirrors.coreix.net/elrepo/elrepo/el6/x86_64/RPMS/kmod-jfs-0.0-1.el6.elrepo.x86_64.rpm
(that
> Also, in case you're ever interested, I've written a script that
> generates suitable IPv4-based filenames for pre-default usage:
>
>https://github.com/heinlein/pxehex
gethostip ... I simply rebuilt the relevant C5 rpms for C6,
system-config-netboot and system-config-netboot-cmd, IIRC.
On Tue, April 11, 2017 4:41 pm, Warren Young wrote:
> On Apr 11, 2017, at 11:28 AM, Scott Robbins wrote:
>>
>> (though they're talking of trying OpenRC)
>
> Not just talking. TrueOS, neé PC-BSD, now runs on OpenRC.
>
> So let me tell you about how my recent TrueOS server upgrade broke
> virtual
On Apr 11, 2017, at 11:28 AM, Scott Robbins wrote:
>
> (though they're talking of trying OpenRC)
Not just talking. TrueOS, neé PC-BSD, now runs on OpenRC.
So let me tell you about how my recent TrueOS server upgrade broke virtually
all of my services on the TrueOS server, roached the X config
> > > .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d
> > > .../pxelinux.cfg/01-88-99-aa-bb-cc-dd
> > > .../pxelinux.cfg/C0A8025B
> > > .../pxelinux.cfg/C0A8025
> > > .../pxelinux.cfg/C0A802
> > > .../pxelinux.cfg/C0A80
> > > .../pxelinux.cfg/C0A8
> > > .../pxelinux.cfg
On 11/04/17 17:02, Bruce Ferrell wrote:
> On 04/11/2017 07:50 AM, Andrew Holway wrote:
>>> I'd much rather have a bash script to look at-- and manually step
>>> through.
>>
>> Is that a joke? Bash is an almighty impenetrable nightmare. I've been
>> doing
>> *nix for nearly 10 years and *still*
On 4/11/2017 2:01 PM, Bruce Ferrell wrote:
Whatever openether.org is, it sounds buggy.
there's no such domain.there's a softether.org, which is a VPN
package, and some kinda github.com/openether which appears to be
Ethereum blockchain based distributed computing related.
--
john r pie
Similar. When user jobs can run for a couple of months you can't just
do a reboot every few days. Yum makes doing updates easy, but that can
bring another problem: I've seen people do "yum update" multiple times
and not realise that they need to reboot.
On 11/04/17 19:23, Pete Biggs wrote:
>
>>
On 04/11/2017 01:33 PM, m.r...@5-cent.us wrote:
Pete Biggs wrote:
We've been using pxeboot to pull up a menu, to build or rebuild
machines for years. We have this new server, and it fails. Times out.
What's happening is that it tries in this order
.../pxelinux.cfg/b8945908-d6a6-41a9
Pete Biggs wrote:
>
>>We've been using pxeboot to pull up a menu, to build or rebuild
>> machines for years. We have this new server, and it fails. Times out.
>> What's happening is that it tries in this order
>> .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d
>> .../pxelinux
>We've been using pxeboot to pull up a menu, to build or rebuild
> machines for years. We have this new server, and it fails. Times out.
> What's happening is that it tries in this order
> .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d
> .../pxelinux.cfg/01-88-99-aa-bb-cc-
On Tue, April 11, 2017 1:23 pm, Pete Biggs wrote:
>
>>
>> Years uptime, wow! What do you do when security update for kernel or
>> glibc
>> is released? These come as often as once every 45 days in my
>> observation.
>>
> They're non-exposed hosts doing very specific things - think internal
> netwo
>
> Years uptime, wow! What do you do when security update for kernel or glibc
> is released? These come as often as once every 45 days in my observation.
>
They're non-exposed hosts doing very specific things - think internal
network with an air-gap to the internet.
P.
One additional DNS server note: you should disable firewalld for any DNS
server, caching or authoritative. If you need firewalling, use straight
iptables.
The reason is that firewalld always enables connection state tracking
(at least as far as I can tell), and that should never be used in front
On Tue, April 11, 2017 12:43 pm, Pete Biggs wrote:
>
>> I just read through this thread, and I must say I'm a bit worried, to
>> the point that I'm asking myself: is CentOS still as reliable as it was?
>
> Yes.
>
>> This is not a rhetorical question, but a real one. On my Slackware
>> servers, I'm
Here are two articles on DNS that I wrote for Opensource.com.
Introduction to the Domain Name System (DNS)
https://opensource.com/article/17/4/introduction-domain-name-system-dns
Build your own DNS name server on Linux
https://opensource.com/article/17/4/build-your-own-name-server
I hope th
Le 11/04/2017 à 19:43, Pete Biggs a écrit :
> Look, CentOS is a RHEL clone, RH make money out of this and they aren't
> going to produce an OS that is flaky. If they did, no one would use it.
That was my initial thought. Thanks for confirming it.
Cheers,
Niki
--
Microlinux - Solutions informat
Le 11/04/2017 à 19:34, Gordon Messmer a écrit :
> 1: Change the "listen-on" settings to bind to network interfaces:
>
> - listen-on port 53 { 127.0.0.1; };
> - listen-on-v6 port 53 { ::1; };
> + listen-on port 53 { any; };
> + listen-on-v6 port 53 { any; };
>
> 2: Allow ex
> I just read through this thread, and I must say I'm a bit worried, to
> the point that I'm asking myself: is CentOS still as reliable as it was?
Yes.
> This is not a rhetorical question, but a real one. On my Slackware
> servers, I'm hosting a few dozen websites, various platforms for schools
On Tue, 2017-04-11 at 01:40 -0700, Alice Wonder wrote:
> Hello list -
>
> http://unix.stackexchange.com/questions/90035/how-to-set-dns-resolver
> -in-fedora-using-network-manager
>
> That says it works for CentOS 5 and I *suspect* the methods there (3
> listed) would work, but what is the best w
On 04/11/2017 10:36 AM, Gordon Messmer wrote:
On 04/11/2017 10:16 AM, Nicolas Kovacs wrote:
I just read through this thread, and I must say I'm a bit worried, to
the point that I'm asking myself: is CentOS still as reliable as it was?
Yes. I've been very happy with release 7 across hundreds o
If you are looking for a recursive resolver, I would highly recommend
unbound.
If you are looking for an authoritative DNS server, I would highly
recommend NSD.
I run both and find both extremely easy to configure and maintain.
Both are available from the EPEL repositories.
I stopped using
On 04/11/2017 10:16 AM, Nicolas Kovacs wrote:
I just read through this thread, and I must say I'm a bit worried, to
the point that I'm asking myself: is CentOS still as reliable as it was?
Yes. I've been very happy with release 7 across hundreds of servers and
dozens of configurations.
On 04/11/2017 10:05 AM, Nicolas Kovacs wrote:
Is there a*reliable* more or less quick & dirty tutorial on how to get
BIND up and running as a primary public nameserver, with the default
configuration as a starting point?
1: Change the "listen-on" settings to bind to network interfaces:
-
On 4/11/2017 10:17 AM, Nicolas Kovacs wrote:
Le 11/04/2017 à 19:09, John R Pierce a écrit :
do you mean 'authoritative DNS server' ?
Yes.
I've not run bind on c7 yet, but on c6, I just edit /etc/named.conf and
create /var/named/master/$zonename then do a 'reload' of the named
service. no
On Tue, Apr 11, 2017 at 12:11:19PM -0400, Jonathan Billings wrote:
> I feel like this conversation has reached the "lets just keep
> repeating FUD about systemd" stage and probably won't progress in a
> useful direction.
>
> Maybe we should just jump right to the end that we always have each
> tim
Le 11/04/2017 à 19:09, John R Pierce a écrit :
> do you mean 'authoritative DNS server' ?
Yes.
--
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Web : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
_
Le 11/04/2017 à 18:11, Jonathan Billings a écrit :
> Maybe we should just jump right to the end that we always have each
> time this comes up. systemd is the death of linux and you're leaving
> for FreeBSD/devuan/whatever. Lets just move along now.
I've been using CentOS 5.x almost exclusively f
On 4/11/2017 10:05 AM, Nicolas Kovacs wrote:
I just installed CentOS 7 on a public server. I'd like to setup BIND as
a primary DNS server for a few domains.
do you mean 'authoritative DNS server' ?
--
john r pierce, recycling bits in santa cruz
__
Hi,
I just installed CentOS 7 on a public server. I'd like to setup BIND as
a primary DNS server for a few domains.
Until now, all my public machines were running Slackware Linux, and
setting up BIND on a Slackware machine is relatively easy. In its out of
the box configuration, it has a bone-hea
On 04/11/2017 09:48 AM, Leroy Tennison wrote:
Interesting that you should cite Stallman because freedom is an issue here,
we've been reduced to Microsoft when it comes to init. We've lost most of our
flexibility with no option to choose piecemeal what we want and don't want.
You also don't
On Tue, Apr 11, 2017 at 09:24:11AM -0700, Bruce Ferrell wrote:
> Well, sorta yes and sorta no Jonathan. Yes, in that I've moved my
> personal systems to Linux distros that don't use systemd.
>
> No in the it's not "FUD"... The complaints about the code and
> development are facts. Not alternati
Interesting that you should cite Stallman because freedom is an issue here,
we've been reduced to Microsoft when it comes to init. We've lost most of our
flexibility with no option to choose piecemeal what we want and don't want.
- Original Message -
From: "Andrew Holway"
To: "centos"
On Tue, 11 Apr 2017, m.r...@5-cent.us wrote:
Hi, folks,
We've been using pxeboot to pull up a menu, to build or rebuild
machines for years. We have this new server, and it fails. Times out.
What's happening is that it tries in this order
.../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab8
Interesting, I'm going to have to look into this.
- Original Message -
From: "Jonathan Billings"
To: "centos"
Sent: Tuesday, April 11, 2017 8:32:49 AM
Subject: Re: [CentOS] OT: systemd Poll
On Tue, Apr 11, 2017 at 08:02:56AM -0500, Leroy Tennison wrote:
> This does concern me, another p
Hi, folks,
We've been using pxeboot to pull up a menu, to build or rebuild
machines for years. We have this new server, and it fails. Times out.
What's happening is that it tries in this order
.../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d
.../pxelinux.cfg/01-88-99-aa-bb-
On 04/11/2017 09:11 AM, Jonathan Billings wrote:
On Tue, Apr 11, 2017 at 09:02:45AM -0700, Bruce Ferrell wrote:
How about over 30 and it took me a week? No, I don't carry a CS
degree or cert of any kind either, just some high school.
For me, systemd has been an absolute nightmare of unexpected
On Tue, 2017-04-11 at 12:11 -0400, Jonathan Billings wrote:
Maybe we should just jump right to the end that we always have each
> time this comes up. systemd is the death of linux and you're leaving
> for FreeBSD/devuan/whatever. Lets just move along now.
+1
__
I found this:
http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase5-419410.html
On Tue, 11 Apr 2017, Ian Diddams wrote:
Curring a long story short...
we had a centos 5 server running jboss 6 and jboss 4.2.3GA
because of centois 5 EOL TPTB have decr
Curring a long story short...
we had a centos 5 server running jboss 6 and jboss 4.2.3GA
because of centois 5 EOL TPTB have decreed this server needs migratiung to a
Centos 7 server
But... the hboss 4.2.3GA jboss app uses java 1.5.0 (_22 FTWT).
I can't *(unsurprisingly!) find java 1.5.0 under y
On Tue, Apr 11, 2017 at 09:02:45AM -0700, Bruce Ferrell wrote:
> How about over 30 and it took me a week? No, I don't carry a CS
> degree or cert of any kind either, just some high school.
>
> For me, systemd has been an absolute nightmare of unexpected reboots
> and non-transparently broken pro
On 04/11/2017 07:50 AM, Andrew Holway wrote:
I'd much rather have a bash script to look at-- and manually step through.
Is that a joke? Bash is an almighty impenetrable nightmare. I've been doing
*nix for nearly 10 years and *still* am unable to read anything vaguely
complicated in bash where
>
> most scripts are perfectly clear.
This is the Richard Stallman assumption:
He assumes that the average normal person is able to program Fortran 77 and
Lisp and are able to spend inordinate amounts of time debugging and getting
obscure OSS software packages working because using Skype and oth
Andrew Holway wrote:
>>
>> I'd much rather have a bash script to look at-- and manually step
>> through.
>
Same here.
>
> Is that a joke? Bash is an almighty impenetrable nightmare. I've been
> doing *nix for nearly 10 years and *still* am unable to read anything
vaguely
> complicated in bash wher
Jonathan Billings wrote:
> On Tue, Apr 11, 2017 at 08:02:56AM -0500, Leroy Tennison wrote:
>> This does concern me, another post referred to the heavy-handed way
>> in which systemd has been implemented and I totally agree. "You
>> will conform" - no exceptions. What I fear is that we will lose t
>
> I'd much rather have a bash script to look at-- and manually step through.
Is that a joke? Bash is an almighty impenetrable nightmare. I've been doing
*nix for nearly 10 years and *still* am unable to read anything vaguely
complicated in bash whereas I can write fairly decent python after 6
On 04/11/2017 09:10 AM, Leroy Tennison wrote:
Another huge concern: It breaks, someone else has to fix it because it's in the
C source - after it reaches a high enough priority. At least with scripts you
could conceivably hack it. From what I've read there is some ability to get
systemd to d
On Tue, April 11, 2017 8:12 am, James B. Byrne wrote:
>
> On Sun, April 9, 2017 00:39, Anthony K wrote:
>> According to "Arthur Schopenhauer":
>>
>> "All truth passes through three stages.
>> First, it is ridiculed.
>> Second, it is violently opposed.
>> Third, it is accepted as bei
On 04/11/2017 07:42 AM, m...@tdiehl.org wrote:
On Tue, 11 Apr 2017, ken wrote:
And I have to wonder, why in /usr/lib/systemd/system/ is there a file
named -.slice ?? Didn't anyone see a problem with this...? or
countless possible problems? Doesn't instill confidence.
Well wonder no more!! S
On Tue, Apr 11, 2017 at 08:02:56AM -0500, Leroy Tennison wrote:
> This does concern me, another post referred to the heavy-handed way
> in which systemd has been implemented and I totally agree. "You
> will conform" - no exceptions. What I fear is that we will lose the
> ability to control the na
Leroy Tennison writes:
> Another huge concern: It breaks, someone else has to fix it because it's in
> the C source - after it reaches a high enough priority. At least with
> scripts you could conceivably hack it. From what I've read there is some
> ability to get systemd to defer to a script,
On Sun, April 9, 2017 00:39, Anthony K wrote:
> According to "Arthur Schopenhauer":
>
> "All truth passes through three stages.
> First, it is ridiculed.
> Second, it is violently opposed.
> Third, it is accepted as being self-evident."
>
> I must admit that I skipped through the fi
Another huge concern: It breaks, someone else has to fix it because it's in the
C source - after it reaches a high enough priority. At least with scripts you
could conceivably hack it. From what I've read there is some ability to get
systemd to defer to a script, I'm going to have to become an
And to add to the issues concerning consistency, what if you have a fail over
unit and you're replicating configuration (i.e. NIC), you really prefer that
NIC names remain the same. Given the hardware morass underneath all of this,
the only safe choice (regardless of whether you use systemd, in
> er, I meant to add that the 09: seems to correspond with the enp9s* and the
> 0a: seems to correspond with the enp10s*
I wrote myself a little script that uses /sys/class/net, ethtool and lspci to
identify which interface corresponds to which bus slot/lspci entry.
On 04/11/2017 05:39 AM, Alice Wonder wrote:
On 04/11/2017 05:30 AM, Jonathan Billings wrote:
On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote:
And *why* random NIC names? Quick, you've got servers from 5
manufacturers, of different ages... what's the NIC going to be
called? Do
names
On 04/11/2017 05:30 AM, Jonathan Billings wrote:
On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote:
And *why* random NIC names? Quick, you've got servers from 5
manufacturers, of different ages... what's the NIC going to be called? Do
names like enp5s0 offer any convenience to *anyone*
> But the consistent device naming in Linux comes from slot index
> numbers, physical location and even the MAC (if so configured), and
> not what driver it uses.
>
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.h
On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote:
> > And *why* random NIC names? Quick, you've got servers from 5
> > manufacturers, of different ages... what's the NIC going to be called? Do
> > names like enp5s0 offer any convenience to *anyone* not a hardware
> > engineer?
>
> As so
On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote:
> > And *why* random NIC names? Quick, you've got servers from 5
> > manufacturers, of different ages... what's the NIC going to be called? Do
> > names like enp5s0 offer any convenience to *anyone* not a hardware
> > engineer?
>
> As so
> And *why* random NIC names? Quick, you've got servers from 5
> manufacturers, of different ages... what's the NIC going to be called? Do
> names like enp5s0 offer any convenience to *anyone* not a hardware
> engineer?
As someone else had stated, it's not related to SystemD but
Fedora/RHEL has ch
On Tue, 11 Apr 2017, ken wrote:
And I have to wonder, why in /usr/lib/systemd/system/ is there a file named
-.slice ?? Didn't anyone see a problem with this...? or countless possible
problems? Doesn't instill confidence.
Well wonder no more!! Simply look it up in the man pages. It is docume
On Tue, Apr 11, 2017 at 12:03 PM, Alice Wonder wrote:
> From the man page that does tell it not to mess with /etc/resolv.conf -
> thank you. That will work.
>
> On 04/11/2017 02:21 AM, anax wrote:
>
>> Hi Alice
>> man NetworkManager.conf
>>
>> in /etc/NetworkManager/NetworkManager.conf
>>
>>
From the man page that does tell it not to mess with /etc/resolv.conf -
thank you. That will work.
On 04/11/2017 02:21 AM, anax wrote:
Hi Alice
man NetworkManager.conf
in /etc/NetworkManager/NetworkManager.conf
dns=none
*snip*
___
Cen
Hi Alice
man NetworkManager.conf
in /etc/NetworkManager/NetworkManager.conf
dns=none
suomi
On 04/11/2017 10:40 AM, Alice Wonder wrote:
Hello list -
http://unix.stackexchange.com/questions/90035/how-to-set-dns-resolver-in-fedora-using-network-manager
That says it works for CentOS
On 04/10/2017 08:13 PM, Bruce Ferrell wrote:
On 04/10/2017 03:20 PM, Pete Biggs wrote:
I must admit that I skipped through the first and second stages - I
never found creating init scripts a joy and instead opted to write my
own scripts that I launched via inittab. As such, I welcomed the
simpl
Hello list -
http://unix.stackexchange.com/questions/90035/how-to-set-dns-resolver-in-fedora-using-network-manager
That says it works for CentOS 5 and I *suspect* the methods there (3
listed) would work, but what is the best way with NetworkManager to set
it up to use the localhost for DNS ?
76 matches
Mail list logo
