On 1/20/22 20:10, Thomas Cameron wrote:
I made a quick video of the difference between F35 and RHEL 8.5.
https://youtu.be/KuvqInOg1u8
Skip to about the 1:30 mark to see the difference between F35 and RHEL
8.5. I've seen the hostname assigned by reverse DNS with every version
of RHEL since
On 1/20/22 20:30, Tim via users wrote:
On Thu, 2022-01-20 at 19:45 -0600, Thomas Cameron wrote:
OK, so this is weird. I just kickstarted a F35 VM. When it booted
up, its hostname was host156.tc.camerontech.com, as I expected it to
be.
The /etc/hostname file is blank - it just has a single
On Thu, 2022-01-20 at 19:45 -0600, Thomas Cameron wrote:
> OK, so this is weird. I just kickstarted a F35 VM. When it booted
> up, its hostname was host156.tc.camerontech.com, as I expected it to
> be.
>
> The /etc/hostname file is blank - it just has a single empty line.
>
> After I rebooted
On 1/20/22 19:43, Thomas Cameron wrote:
On 1/20/22 19:40, Tom Horsley wrote:
I never once had that happen. And I installed hundreds of virtual
machines
with different releases for different distros for testing at work.
It has worked this way for YEARS. Is your environment set up with
On 1/20/22 19:17, Thomas Cameron wrote:
On 1/17/22 15:30, Petr Menšík wrote:
I think it might make more sense to correctly detect hostname during
installation. If you define hostname on installation from network, it
should be kept. I expect it should keep the same hostname during
reboots. I
On 1/20/22 19:40, Tom Horsley wrote:
I never once had that happen. And I installed hundreds of virtual machines
with different releases for different distros for testing at work.
It has worked this way for YEARS. Is your environment set up with
working forward and reverse DNS?
I just tested
On Thu, 20 Jan 2022 19:20:22 -0600
Thomas Cameron wrote:
> But this is the behavior Linux has used for years and years. If you set
> your hostname to localhost.localdomain, say via a kickstart script or a
> golden image you use to spin up dozens of instances, previous versions
> of Fedora
On 1/17/22 14:29, Sam Varshavchik wrote:
It should be possible to hack up a script that gets run when an IP
address is assigned that does a reverse IP lookup and sets the hostname.
However that should be done in a manner that does not permanently save
the hostname so that it gets reverted to
On 1/17/22 15:30, Petr Menšík wrote:
I think it might make more sense to correctly detect hostname during
installation. If you define hostname on installation from network, it
should be kept. I expect it should keep the same hostname during
reboots. I think only diskless terminals may want
On 1/17/22 04:27, Tim via users wrote:
I sort-of go along with that. If you've set a hostname, there's sense
in it not getting changed. On the other hand, if you use a DHCP server
to centrally manage the allocation of addresses, you might also want it
(or your DNS server) to control hostnames.
On 1/17/22 01:42, Peter Boy wrote:
I was already afraid that I had overlooked something essential. :-)
The default configuration rather follows the opposite principle. The
hostname should be well defined and independent of changing IP
addresses. I guess the only way will be to determine the
On 1/18/22 04:10, Petr Menšík wrote:
dhcp server of libvirt is dnsmasq. It would provide hostnames when it
has matching dhcp-record with IP and name (and hwaddr). With libvirt,
that would be set by in network
configuration xml. I think it should use also /etc/hosts of the host.
But dnsmasq can
On 19Jan2022 20:32, ToddAndMargo wrote:
>into a variable
>
>X=$(curl -s ipinfo.io -o -)
That is robust (well, it loses trailing whitespace).
>But I lose all my line feeds when I
>echo -e $X
>How do I get my line feeds back?
Quotes.
echo -e "$X"
Unquoted it is broken into "words"
On 1/19/22 21:59, Todd Zullinger wrote:
ToddAndMargo via users wrote:
I am trying to get
curl -s ipinfo.io -o -
into a variable
X=$(curl -s ipinfo.io -o -)
But I lose all my line feeds when I
echo -e $X
How do I get my line feeds back?
Quote the variable. You don't need
On Thu, Jan 20, 2022 at 5:01 AM Patrick Dupre wrote:
> When I run octave with
>
> pkg load symbolic
> and
> syms x
> I
> get
> Symbolic pkg v2.9.0: Traceback (most recent call last):
> File "", line 28, in
> AttributeError: '_PrintFunction' object has no attribute '__globals__'
> Traceback
On Thu, 20 Jan 2022 at 08:01, Patrick Dupre wrote:
> Hello,
>
> When I run octave with
>
> pkg load symbolic
> and
> syms x
> I
> get
> Symbolic pkg v2.9.0: Traceback (most recent call last):
> File "", line 28, in
> AttributeError: '_PrintFunction' object has no attribute '__globals__'
>
On Thu, 20 Jan 2022 13:00:56 +0100
Patrick Dupre wrote:
> When I run octave with
>
> pkg load symbolic
> and
> syms x
> I
> get
> Symbolic pkg v2.9.0: Traceback (most recent call last):
> File "", line 28, in
[cut]
> It seems that it is an identified bug, due to sympy
Is there a Fedora
Hello,
When I run octave with
pkg load symbolic
and
syms x
I
get
Symbolic pkg v2.9.0: Traceback (most recent call last):
File "", line 28, in
AttributeError: '_PrintFunction' object has no attribute '__globals__'
Traceback (most recent call last):
File "", line 1, in
File "", line 12, in
Hey All,
I would like to invite all of you to participate in the Kernel 5.16
Test week is happening from 2022-01-23 to 2022-01-29. It's
fairly simple, head over to the wiki [0] and read in detail about the
test week and simply run the test case mentioned in[1] and enter your
results.
As usual,
19 matches
Mail list logo
