similar to: OT: systemd Poll - So Long, and Thanks for All the fish.

On 04/20/2017 05:55 PM, Warren Young wrote: > ... I find that most hardware is ready to fall over by the time the > CentOS that was installed on it drops out of support anyway. > ... James' point isn't the hardware cost, it's the people cost for retraining. In many ways the Fedora treadmill is easier, being that there are many more smaller jumps than the huge leap from C6

On Apr 20, 2017, at 7:33 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: > > When a vendor ... fundamentally changes the way the administration > of an operating system is presented I?ve gotten the sense from this other part of the thread that the answer to my question, ?What are you moving to?? is FreeBSD. If you think FreeBSD system administration hasn?t changed over the

On Apr 24, 2017, at 7:53 AM, Lamar Owen <lowen at pari.edu> wrote: > > James' point isn't the hardware cost, it's the people cost for retraining. Unless you?ve hired monkeys so that you must train them to do their tasks by rote, that is a soft cost, not a hard cost. If you?ve hired competent IT staff, they will indeed need some time to work out the differences, but they

On 09/04/17 14:39, Anthony K wrote: > > So, at which stage are you in w/ regards to adopting systemd? Are you > still ridiculing it, violently opposed to it, or have you mellowed to it? Thanks for all those that responded. systemd still appears to be a sore topic. systemd is still coping a whole lot of ridicule but not so violent opposition. Can't say I understand why, but you

On Wed, Apr 19, 2017 at 5:21 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: > > On Mon, April 17, 2017 17:13, Warren Young wrote: > >> >> Also, I???ll remind the list that one of the *prior* times the systemd >> topic came up, I was the one reminding people that most of our jobs >> summarize as ???Cope with change.?? >> > > At some point

On 04/15/2017 04:46 AM, Pete Biggs wrote: > Not wishing to extend this thread further, but ... > >> There are conspiracy theories out there that the NSA is involved with >> bringing systemd to Linux so they can have easy access to *"unknown"* >> bugs - aka backdoors - to all Linux installations using systemd *[1]*. > They're conspiracy theories, and

> Indeed. I think the assertion "OSS is somehow safer because of community > audit" is a logical fallacy. How would one go about "auditing" in the first > place? There are tools to audit source code for problems - OSS is safer *because* the source is available and can be audited. > Even if the various Intelligence agencies are not injecting > vulnerabilities

> > There is no doubt that most security agencies have a long list of zero- >> day exploits in their toolbox - I would hazard to suggest that they >> wouldn't be doing their job if they didn't! But I seriously doubt they >> would commission exploitable code in something that is openly >> auditable. >> >> P. >> > > P., I used to think

On Mon, April 17, 2017 17:13, Warren Young wrote: > > Also, I???ll remind the list that one of the *prior* times the systemd > topic came up, I was the one reminding people that most of our jobs > summarize as ???Cope with change.??? > At some point 'coping with change' is discovered to consume a disproportionate amount of resources for the benefits obtained. In my sole

Not wishing to extend this thread further, but ... > There are conspiracy theories out there that the NSA is involved with > bringing systemd to Linux so they can have easy access to *"unknown"* > bugs - aka backdoors - to all Linux installations using systemd *[1]*. They're conspiracy theories, and that's it. The bottom line is that in general people don't like

It's amazing what you can learn in a few days... Having just found out that Queen Elizabeth has a great sense of humor, it has now emerged that Kevin Fleming - a man who (both with and without his moustache) has been an amazing contributor and influencer in the Asterisk project is set to move on to a new challenge outside the project - but still within the realms of Open Source. Kevin has

Hi list, what solution do you use for virtualizzation? thanks in advance.

On 04/26/2016 07:44 AM, mxs kolo wrote: > Now reporduced with 100% > 1) create contrainer with memory limit 1Gb > 2) run inside simple memory test allocator: > #include <malloc.h> > #include <unistd.h> > #include <memory.h> > #define MB 1024 * 1024 > int main() { > int total = 0; > while (1) { > void *p = malloc( 100*MB ); >

Anyone had any experience getting puppet to update multiple OS''s on a single server? For example, for a set of blades Network booting from a primary server, the OS for each blade would be stored on the primary server. For example: /pxe/host1/<normal OS directory structure> /pxe/host2/<normal OS directory structure> ..... /pxe/hostn/<normal OS directory structure> Can

Greetings, We have purchased an IBM BladeCenter and I am in the process of testing Linux installation on these things (boot off SAN i.e. qla2300 driver, not using internal drives). My distro of choice is Debian, however, since I'm really not interested in trying to hand compile all the drivers, I decided to try CentOS (which I'm so far very impressed with). On boot, as with the

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 name, MAC address association at some future > point because "no one

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 documented after all!! Hummm, lets see: (vcliff pts2) # grep Documentation=

I know this is systemd-punching day, but at least get your information straight. On Mon, Apr 10, 2017 at 03:38:03PM -0400, m.roth at 5-cent.us wrote: >Why change names, such as rpc-idmapd to > nfs-idmapd? Unrelated to systemd, as far as I can tell. Fedora adopted new names that made more sense, and it was incorporated into RHEL7. >And I've just been fighting today, because I

On Sunday 21 September 2014 11:09:14, Michael S. Tsirkin wrote: > On Thu, Sep 18, 2014 at 09:18:37PM +0200, Stefan Fritsch wrote: > > On Monday 01 September 2014 09:37:30, Michael S. Tsirkin wrote: > > > Why do we need INT#x? > > > How about setting IRQF_SHARED for the config interrupt > > > while using MSI-X? You'd have to read ISR to check that the >

On Sunday 21 September 2014 11:09:14, Michael S. Tsirkin wrote: > On Thu, Sep 18, 2014 at 09:18:37PM +0200, Stefan Fritsch wrote: > > On Monday 01 September 2014 09:37:30, Michael S. Tsirkin wrote: > > > Why do we need INT#x? > > > How about setting IRQF_SHARED for the config interrupt > > > while using MSI-X? You'd have to read ISR to check that the >