On Sat, 2019-10-05 at 15:59 -0400, Lamar Owen wrote:
> Frontpanel, 256 words (12-bit words), and paper tape. But I also never
> had that straight-8 on the net, either, but, via uucp, I did have the
> T6K on Usenet.
My second machine was 9 bits = 8 + parity. 10 years later I was working
on 36
On 10/5/19 2:14 PM, Always Learning wrote:
Technically [the new automobile] was never an "upgrade" but a brand new and
alternative
system.
...
The automobile was originally billed in many areas as the 'horseless
carriage,' an upgrade.
Luxury. Try running on a 32k single processor computer,
On 10/5/19 11:29 AM, Stephen John Smoogen wrote:
...
On the other hand, most of the idea that the old config scripts were
deterministic and imperative was built on a large amount of hacks to
try and make it so. Having spent more time than I want dealing with
systems which seem to be just like
On Fri, 2019-10-04 at 11:17 -0400, Lamar Owen wrote:
> On 10/4/19 10:40 AM, Valeri Galtsev wrote:
> > Do not make any changes [in the program] unless they are absolutely
> > necessary.
Especially with production programs.
> Take the transition from horse and buggy to automobile for instance.
>
> On Oct 5, 2019, at 10:29 AM, Stephen John Smoogen wrote:
>
> On Fri, 4 Oct 2019 at 18:11, Japheth Cleaver wrote:
>>
>> On 10/4/2019 8:17 AM, Lamar Owen wrote:
>>> On 10/4/19 10:40 AM, Valeri Galtsev wrote:
My impression is younger generation doesn't value rules that
programmers
On Fri, 4 Oct 2019 at 18:11, Japheth Cleaver wrote:
>
> On 10/4/2019 8:17 AM, Lamar Owen wrote:
> > On 10/4/19 10:40 AM, Valeri Galtsev wrote:
> >> My impression is younger generation doesn't value rules that
> >> programmers were following 2-3 decades ago. One of which is:
> >>
> >> Do not make
On 10/4/2019 8:17 AM, Lamar Owen wrote:
On 10/4/19 10:40 AM, Valeri Galtsev wrote:
My impression is younger generation doesn't value rules that
programmers were following 2-3 decades ago. One of which is:
Do not make any changes [in the program] unless they are absolutely
necessary.
I have
On Fri, Oct 04, 2019 at 08:27:08AM -0400, Phelps, Matthew wrote:
> Also, we have 150+ machines with fixed IP addresses, always-on connections,
> and no wireless. Having NetworkManager do seemingly random things is not
> desirable.
I mention this every time people bash NetworkManager on servers.
On 10/4/19 5:55 PM, Lamar Owen wrote:
> On 10/4/19 11:39 AM, Ljubomir Ljubojevic wrote:
>> ...
> I've kludged together a solution for those times here by using the NAT
> connection, but then running an OpenVPN client on the guest to an
> OpenVPN server with layer-2 adjacency to those sorts of
On Thu, 2019-10-03 at 15:14 -0400, Jerry Geis wrote:
> > > systemctl status network
>
> AT BOOT:
> ● network.service - LSB: Bring up/down networking
>Loaded: loaded (/etc/rc.d/init.d/network; generated)
>Active: inactive (dead)
> Docs: man:systemd-sysv-generator(8)
>
> After:
On 10/4/19 11:39 AM, Ljubomir Ljubojevic wrote:
...
I have VM in NAT mode mostly these days, but sometimes I need bridged
network to recognize some hardware on the network, Mikrotik WiFi routers
or printers so I need ability to go to bridge.
I've kludged together a solution for those times
On 2019-10-04 10:27, Lamar Owen wrote:
On 10/4/19 11:02 AM, Ljubomir Ljubojevic wrote:
...
It is OK if your KVM host is on LAN cable that never is disconnected
or power goes down. But I have a laptop I use first at work where I
use LAN and then at home where I use WLAN only, and suspending
On 10/4/19 5:27 PM, Lamar Owen wrote:
> On 10/4/19 11:02 AM, Ljubomir Ljubojevic wrote:
>> ...
>> It is OK if your KVM host is on LAN cable that never is disconnected
>> or power goes down. But I have a laptop I use first at work where I
>> use LAN and then at home where I use WLAN only, and
On 10/4/19 11:02 AM, Ljubomir Ljubojevic wrote:
...
It is OK if your KVM host is on LAN cable that never is disconnected
or power goes down. But I have a laptop I use first at work where I
use LAN and then at home where I use WLAN only, and suspending laptop
is same as disconnecting LAN,
On 10/4/19 4:59 PM, Stephen John Smoogen wrote:
> On Fri, 4 Oct 2019 at 10:41, Valeri Galtsev wrote:
>>
>>
>>
>> On 2019-10-04 08:03, Chris Adams wrote:
>>> Once upon a time, Ljubomir Ljubojevic said:
Bridge for VM's is main reason I hate NM.
>>
>> +1
>>
>> My impression is younger
On 10/4/19 10:40 AM, Valeri Galtsev wrote:
My impression is younger generation doesn't value rules that
programmers were following 2-3 decades ago. One of which is:
Do not make any changes [in the program] unless they are absolutely
necessary.
I have in the past agreed with this assessment
On 10/4/19 4:42 PM, Lamar Owen wrote:
> On 10/4/19 10:00 AM, Ljubomir Ljubojevic wrote:
>> On 10/4/19 3:03 PM, Chris Adams wrote:
>>> ...
>>> See the NetworkManager-config-server package.
>> Ahh, thanks. I was wondering about it but never investigated.
> H.
> Description :
> This adds a
On Fri, 4 Oct 2019 at 10:41, Valeri Galtsev wrote:
>
>
>
> On 2019-10-04 08:03, Chris Adams wrote:
> > Once upon a time, Ljubomir Ljubojevic said:
> >> Bridge for VM's is main reason I hate NM.
>
> +1
>
> My impression is younger generation doesn't value rules that programmers
> were following
On 10/4/19 10:00 AM, Ljubomir Ljubojevic wrote:
On 10/4/19 3:03 PM, Chris Adams wrote:
...
See the NetworkManager-config-server package.
Ahh, thanks. I was wondering about it but never investigated.
H.
Description :
This adds a NetworkManager configuration file to make it behave more
On 2019-10-04 08:03, Chris Adams wrote:
Once upon a time, Ljubomir Ljubojevic said:
Bridge for VM's is main reason I hate NM.
+1
My impression is younger generation doesn't value rules that programmers
were following 2-3 decades ago. One of which is:
Do not make any changes [in the
On 10/4/19 3:03 PM, Chris Adams wrote:
> Once upon a time, Ljubomir Ljubojevic said:
>> Bridge for VM's is main reason I hate NM. I now mess with both NM and
>> br0 controled by network because I use Windows VM on my laptop. As soon
>> as you disconnect LAN cable your eth and bridge connection
Once upon a time, Ljubomir Ljubojevic said:
> Bridge for VM's is main reason I hate NM. I now mess with both NM and
> br0 controled by network because I use Windows VM on my laptop. As soon
> as you disconnect LAN cable your eth and bridge connection are gone and
> stupid KVM can not recover and
On 10/4/19 2:27 PM, Phelps, Matthew wrote:
> On Fri, Oct 4, 2019 at 6:26 AM Jim Perrin wrote:
>
>>
>>
>> On 10/3/19 2:42 PM, Jerry Geis wrote:
>>> I have need to use the old network-scripts and not NetworkManager.
>>
>> Why? I'd like to understand more about the use case where this is a
>>
On 10/4/19 2:08 PM, Mike Litoris via CentOS wrote:
> On 10/4/19 12:27 PM, Jim Perrin wrote: Why? I'd like to understand more
> about the use case where this is a requirement.I'd say for the sake of
> simplicity...Why complicate things with NM when you only need to set an IP
> ?The ifconfig
On Fri, Oct 4, 2019 at 6:26 AM Jim Perrin wrote:
>
>
> On 10/3/19 2:42 PM, Jerry Geis wrote:
> > I have need to use the old network-scripts and not NetworkManager.
>
> Why? I'd like to understand more about the use case where this is a
> requirement.
>
>
>
One example we have is qemu virtual
On 10/4/19 12:27 PM, Jim Perrin wrote: Why? I'd like to understand more
about the use case where this is a requirement.I'd say for the sake of
simplicity...Why complicate things with NM when you only need to set an IP ?The
ifconfig files were great.Why is the choice, to use or not to use NM,
On 10/3/19 2:42 PM, Jerry Geis wrote:
I have need to use the old network-scripts and not NetworkManager.
Why? I'd like to understand more about the use case where this is a
requirement.
--
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
On 10/3/19 9:57 PM, Paul Heinlein wrote:
> On Thu, 3 Oct 2019, Jerry Geis wrote:
>
systemctl status network
>>
>>
>> AT BOOT:
>> ● network.service - LSB: Bring up/down networking
>> Loaded: loaded (/etc/rc.d/init.d/network; generated)
>> Active: inactive (dead)
>> Docs:
Am 03.10.2019 um 21:14 schrieb Jerry Geis:
Contents of ifcfg-eth0
# Generated by parse-kickstart
TYPE="Ethernet"
DEVICE="eth0"
UUID="6ada23ed-d1ad-4f37-935c-86163fe61e7b"
ONBOOT="yes"
BOOTPROTO="dhcp"
IPV6INIT="yes"
Why is it not starting at boot ?
Thanks,
Jerry
Set
NM_CONTROLLED=no
On Thu, 3 Oct 2019, Jerry Geis wrote:
systemctl status network
AT BOOT:
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; generated)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
After: service network restart
● network.service
>> systemctl status network
AT BOOT:
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; generated)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
After: service network restart
● network.service - LSB: Bring up/down networking
On Thu, Oct 03, 2019 at 02:42:54PM -0400, Jerry Geis wrote:
> I have need to use the old network-scripts and not NetworkManager.
> I did yum install network-scripts, I have ifcfg-eth0 set for ONBOOT=yes
> but it is not starting on boot.
> What have I missed ?
systemctl status network
--
Matthew
I have need to use the old network-scripts and not NetworkManager.
I did yum install network-scripts, I have ifcfg-eth0 set for ONBOOT=yes
but it is not starting on boot.
What have I missed ?
Jerry
___
CentOS mailing list
CentOS@centos.org
33 matches
Mail list logo
