Just a heads up about hostname --ip-address(s) usage

Default install of Mageia has ipv6 address for localhost
$ cat /etc/hosts
127.0.0.1 localhost
::1 localhost

and ipv6 is enabled.

In all my scripts I use Node_ip=$(hostname --ip-address)
which work well in a fully configured setup.

Coding logic from
$ hostname --help | grep ip-address
-i, --ip-address addresses for the host name
-I, --all-ip-addresses all addresses for the host

suggests -i is better than -I because I just want the one address.
I know some systems can be configured to have more than one address
so I did not want -I output.

So, I am running in a VirtualBox guest, with dynamic addressing
and the -i takes 10 seconds to return a value.
fe80::a00:27ff:fe32:71e%enp93 10.0.2.15

whereas -I immediately returns 10.0.2.15. No idea why the long delay.
Going to assume is a "feature" for a clean install because I have
ipv6 disabled everywhere on the host machine and routers.

Glad I only have to modify 15 scripts and since I am using geany as
my editor, it should take about a minute to make the changes.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 26/7/20 6:04 am, Bit Twister wrote:

Just a heads up about hostname --ip-address(s) usage

Default install of Mageia has ipv6 address for localhost
$ cat /etc/hosts
127.0.0.1 localhost
::1 localhost

and ipv6 is enabled.

I have an abiding suspicion about the consistency of "default" installs.

I checked with my "Network Centre" and Disable IPv6 is NOT checked

But!

~]$ cat /etc/hosts
# generated by drakhosts
127.0.0.1 localhost.localdomain localhost
192.168.1.100 unimatrix.cryptid.test unimatrix
192.168.1.200 prnt.cryptid.test prnt
192.168.1.220 phone.cryptid.test phone
192.168.1.254 gateway.cryptid.test gateway
203.123.68.185 wangate.cryptid.test wangate
203.123.90.241 routerwan.cryptid.test router

No IPv6 mentioned

Mileage obviously varies and my installation no longer default :-|

PS
I still haven't created better names for those address since we spent
those several days pounding it all into shape, and into my head :-)

--
faeychild
Running plasmashell 5.15.4 on 5.6.14-desktop-2.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sun, 26 Jul 2020 12:51:53 +1000, faeychild wrote:

On 26/7/20 6:04 am, Bit Twister wrote:

Just a heads up about hostname --ip-address(s) usage

Default install of Mageia has ipv6 address for localhost
$ cat /etc/hosts
127.0.0.1 localhost
::1 localhost

and ipv6 is enabled.

I have an abiding suspicion about the consistency of "default" installs.

I checked with my "Network Centre" and Disable IPv6 is NOT checked

But!

~]$ cat /etc/hosts
# generated by drakhosts
127.0.0.1 localhost.localdomain localhost
192.168.1.100 unimatrix.cryptid.test unimatrix

No IPv6 mentioned

I am going to spend any time looking it but I am curious how to setup /etx/hosts.

Was all your hosts input through MCC or some other method?

When doing the install, was it clean or upgrade?

And last question, during install did you pick static or
dynamic (dhcp) when configuring the nic?


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 26/7/20 6:09 pm, Bit Twister wrote:

I am going to spend any time looking it but I am curious how to setup /etx/hosts.

Questions have triggered some, as usual vague, memories.

Was all your hosts input through MCC or some other method?

NO I think it was done manually with a text editor

When doing the install, was it clean or upgrade?

Clean install from ISO

And last question, during install did you pick static or
dynamic (dhcp) when configuring the nic?

According to network centre
DHCP is manual configuration.

An even more unreliable impression is that the IPv6 local entry in
etc/hosts was deliberately removed during the networking building exercise.


regards
--
faeychild
Running plasmashell 5.15.4 on 5.6.14-desktop-2.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sun, 26 Jul 2020 22:29:29 +1000, faeychild wrote:

On 26/7/20 6:09 pm, Bit Twister wrote:

Was all your hosts input through MCC or some other method?

NO I think it was done manually with a text editor
Clean install from ISO

Just a guess, you forgot you had removed the ipv6 stuff 8=)

And last question, during install did you pick static or
dynamic (dhcp) when configuring the nic?

According to network centre
DHCP is manual configuration.

Right answer to Wrong question. :)

During clean install, you had to either take network configuration or
configure it.

If you did not get into the Network Configuration screen then yes
DHCP is correct.

Which brings up this observation. I would have thought if using static
ip addresses in /etc/hosts. then the nic should be configured static.

FYI for any lurkers, during network installs picking static instead of
dhcp will automagically halfway configure your static settings if you
have more than one connection.

No idea if with one nic, it will do the full configuration.
Experience taught me I should configure second connection first, then
configure the Internet nic last.


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 27/7/20 12:00 am, Bit Twister wrote:

NO I think it was done manually with a text editor
Clean install from ISO

Just a guess, you forgot you had removed the ipv6 stuff 8=)

Yes That's where the unsettling vague memories are suggesting

And last question, during install did you pick static or
dynamic (dhcp) when configuring the nic?

According to network centre
DHCP is manual configuration.

Right answer to Wrong question. :)

During clean install, you had to either take network configuration or configure it.

Ahh!
During the install I click through the setup and accept the defaults

If you did not get into the Network Configuration screen then yes
DHCP is correct.

Which brings up this observation. I would have thought if using static
ip addresses in /etc/hosts. then the nic should be configured static.

I think so, but since our meddling we raised it to

192.168.1.100 still static

Initially the only setting in /etc/host was the nic and local- prob IPv6
the other stuff was included later. I think it all started when I
decided to network the printer. The we added gateways and router addresses.

Can you remember that week taken out of your life :-(

I could reset the nic automagically and see what it selects.??

FYI for any lurkers, during network installs picking static instead of
dhcp will automagically halfway configure your static settings if you
have more than one connection.

No idea if with one nic, it will do the full configuration.
Experience taught me I should configure second connection first, then configure the Internet nic last.

It's a little like the graphics driver - does one install it during or after. Some odd things can go on.


--
faeychild
Running plasmashell 5.15.4 on 5.6.14-desktop-2.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Mon, 27 Jul 2020 09:04:50 +1000, faeychild wrote:

On 27/7/20 12:00 am, Bit Twister wrote:

I could reset the nic automagically and see what it selects.??

I'll suggest you are sending a DHCP lease with /etc/hosts value and
the router being half smart returns the address.

It's a little like the graphics driver - does one install it during or after. Some odd things can go on.

Personally I prefer loading default driver, install all updates, reboot
backup system, then dink with the driver.

If install is not a network install, I won't even enable the nic after configuring it.

Less variables in the mix makes for less chance of a problem.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 27/7/20 10:57 am, Bit Twister wrote:

Personally I prefer loading default driver, install all updates, reboot backup system, then dink with the driver.

I just do the basic install with nouveau driver, then reboot, then
install the nvidia drive and leave it to settle for a while.
I may reboot a couple of times to read the kernel messages.

I update sometime later

Then I do battle with the printer

If install is not a network install, I won't even enable the nic after configuring it.

With the ISO install the procedure states that the nic has been
successfully setup and asks you wish to establish a connection.

Less variables in the mix makes for less chance of a problem.

I haven't tried a network install. I have more faith in the ISO.
At least I have all the necessary files and do not depend on the
internet connection


What is the process if the network install falls over?
Can it be restarted without drama?


--
faeychild
Running plasmashell 5.15.4 on 5.6.14-desktop-2.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Mon, 27 Jul 2020 11:58:21 +1000, faeychild wrote:

On 27/7/20 10:57 am, Bit Twister wrote:

If install is not a network install, I won't even enable the nic after
configuring it.

With the ISO install the procedure states that the nic has been
successfully setup and asks you wish to establish a connection.

Yep, and once enabled, somewhere in the back of my brain I have to remember
to answer no to the question of doing the updates during the install.

With that enabled you have an install needing no updates on your first
boot after install.

Less variables in the mix makes for less chance of a problem.

I haven't tried a network install. I have more faith in the ISO.

I hear that, but when working with clean Cauldon installs, there
is no classic iso until alpha/beta are generated.

They are currently trying to generate a beta, check mirror of choice /mageia/iso/cauldron/ for your classic hard media isos.

For the net_install iso look in
/mageia/distrib/cauldron/x86_64/install/images/
for your desired net install iso. Size usually less than 100 meg is size.

At least I have all the necessary files and do not depend on the
internet connection

What is the process if the network install falls over?
Can it be restarted without drama?

Yes. For instance if you glance at https://pkgsubmit.mageia.org/
very much you might notice an Upload in progress for xx whatever

I check for that anytime to do updates or new installs, because that
can change packages lists hurting your chances of a transient database
or package dependency

Depending on where the failure occurs you are sent back to the package selection menu or during install you get the normal failure selections.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 27/7/20 3:52 pm, Bit Twister wrote:

Yep, and once enabled, somewhere in the back of my brain I have to remember to answer no to the question of doing the updates during the install.

With that enabled you have an install needing no updates on your first
boot after install.

After sitting by until all the updates go in, only to find an error with
the install when one finally gets to reboot - jams keyboard throughout monitor.

I came close!!

I haven't tried a network install. I have more faith in the ISO.

I hear that, but when working with clean Cauldon installs, there
is no classic iso until alpha/beta are generated.

Bleeding edge stuff is a vastly different approach

Yes. For instance if you glance at https://pkgsubmit.mageia.org/
very much you might notice an Upload in progress for xx whatever

I had this bookmarked and had forgotten its existence

Depending on where the failure occurs you are sent back to the package selection menu or during install you get the normal failure selections.

Good to know for confidence levels


regards
--
faeychild
Running plasmashell 5.15.4 on 5.6.14-desktop-2.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Tue, 28 Jul 2020 14:42:28 +1000, faeychild wrote:

On 27/7/20 3:52 pm, Bit Twister wrote:

Yep, and once enabled, somewhere in the back of my brain I have to remember >> to answer no to the question of doing the updates during the install.

With that enabled you have an install needing no updates on your first
boot after install.

After sitting by until all the updates go in, only to find an error with
the install when one finally gets to reboot - jams keyboard throughout monitor.

I came close!!

That leaves me with some confusion. Was the attempt a network install of Cauldron or Official.

If Production, that is a definite bug report needed. I would suggest a
bug report if cauldron if you are not going to indicate the problem
in the dev mail list.

Bleeding edge stuff is a vastly different approach

Not if using a media iso instead of network install. :)

Yes. For instance if you glance at https://pkgsubmit.mageia.org/
very much you might notice an Upload in progress for xx whatever

I had this bookmarked and had forgotten its existence

I hear that. Stuff like that I put on my personal web page


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 28/7/20 11:35 pm, Bit Twister wrote:

That leaves me with some confusion. Was the attempt a network install of Cauldron or Official.

Just speculating, Bits.
I stick with official
I've never attempted a network install. My reticence dates from the bad
old days of monthly download limits. Even downloading the latest ISO was
a dent in the allowance so I was only going to do it once.

At least with the ISO I had all the files to mess with and single
download costs.
Alternatively several attempts with a dodgy network download or
installation would have crippled the allowance for a month.

Even with the ISO I remember the occasional reboot after installing
would fail with a message about X or X11 failure and be presented with a
virtual terminal and no idea what to do next..
So I would reinstall from the DVD, reinstalling from the network just
wasn't on

Things are just so much easier due to the hard work of many anonymous
unsung programers

regards




--
faeychild
Running plasmashell 5.15.4 on 5.6.14-desktop-2.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Wed, 29 Jul 2020 15:42:07 +1000, faeychild wrote:

On 28/7/20 11:35 pm, Bit Twister wrote:

That leaves me with some confusion. Was the attempt a network install of
Cauldron or Official.

Just speculating, Bits.
I stick with official
I've never attempted a network install. My reticence dates from the bad
old days of monthly download limits. Even downloading the latest ISO was
a dent in the allowance so I was only going to do it once.

Ok, just wanted to see where you was.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)