Thanks to everyone. It gives me a path to go research.
On Tue, Jul 15, 2014 at 10:52 PM, Blake Dunlap wrote:
> The term you want to search for is subinterface. I'm not strong in Deb
> so I can't really help much further, except that it looked to me like
> googling for "linux mint subinterface" g
I have no knowledge of Linux Mint, but in CentOS this is done in
/etc/sysconfig/network-scripts. Create a file for each NIC or virtual
interface. The first will probably already be there called ifcfg-eth0. Add
ifcfg-eth0:1,ifcfg-eth0:2,
and so on. The real NIC will have a hardware address
(HW
Back when Slackware was a 0.9.6 or so, I set up virtual ethernet
connections. So I had eth0, eth0:1 eth0.2 eth0.3 etc.
But I can't figure out how I did that. Also need to set different
routing for each.
Suggestions on how to do it or where to RTFM (Read The Fine Manual)
are appreciated.
Situati
On 07/15/2014 03:36 PM, Blake Dunlap wrote:
Saying puppet is for people who can't rsync a bash script
is like saying DNS is for people who can't rsync a hosts file.
-Blake
sh! I'm trying to kill off an /etc/hosts file from the retiring
server. Don't give me away! :)
Howard
--
The advantage of puppet is the ongoing control, and object dependency
management opposed to deploy once user automation like a bash script /
ks script. Saying puppet is for people who can't rsync a bash script
is like saying DNS is for people who can't rsync a hosts file.
They both have their use
Yeah it's a tough call. You mentioned that you don't do this very often,
but when you DO have to setup new systems, you also said that the scripts
are out of date almost immediately. So now, every time you provision a new
set of boxes, you have to also manage a code base.
Payroll was always the bi
On 07/15/2014 03:16 PM, Wesley Duffee-Braun wrote:
not to go too far into the weeds, but I'm not sure I agree with "puppet
is for people that can't rsync" and while I get the gist of that
statement, having a standard toolkit (puppet, chef, whathaveyou) scales
much better. It's the "who will run o
not to go too far into the weeds, but I'm not sure I agree with "puppet is
for people that can't rsync" and while I get the gist of that statement,
having a standard toolkit (puppet, chef, whathaveyou) scales much better.
It's the "who will run our shit if you get hit by a bus" situation. or the
"l
On 7/15/14 3:56 PM, Howard White wrote:
On 07/15/2014 02:51 PM, Kent Perrier wrote:
Have you looked at installing cobbler and letting that take care of the
details?
Just wondering.
In the best of all worlds, I would have [ puppet | chef | spacewalk |
cobbler | wtf ]. I'm a one-handed-wallpa
On 07/15/2014 02:51 PM, Kent Perrier wrote:
Have you looked at installing cobbler and letting that take care of the
details?
Just wondering.
In the best of all worlds, I would have [ puppet | chef | spacewalk |
cobbler | wtf ]. I'm a one-handed-wallpaper-hanger here...
Howard
--
--
You r
Have you looked at installing cobbler and letting that take care of the
details?
Just wondering.
On Tue, Jul 15, 2014 at 2:48 PM, Howard White wrote:
> On 07/15/2014 02:07 PM, Howard White wrote:
>
>> ARG!!! Surely this is old news to somebody out there -- PLEASE!
>>
>> We've been installing
On 07/15/2014 02:07 PM, Howard White wrote:
ARG!!! Surely this is old news to somebody out there -- PLEASE!
We've been installing operating systems via PXE here a long time. We
are retiring our CentOS 5 (.8 32 bit) tftpboot server and I am just now
breaking in (or down...) the replacement Cent
ARG!!! Surely this is old news to somebody out there -- PLEASE!
We've been installing operating systems via PXE here a long time. We
are retiring our CentOS 5 (.8 32 bit) tftpboot server and I am just now
breaking in (or down...) the replacement CentOS 6 (.5 64 bit) tftpboot
server. I've go
13 matches
Mail list logo
