Tom Horsley writes:
On Tue, 25 Jan 2022 18:43:19 -0500
Sam Varshavchik wrote:
> 2) Stuff that crammed down everyone's throat, for various non-technical
> reasons and, otherwise, they have no technical merit of advantage that
> anyone can identify and point to.
At least NM had a reasonably vali
On Tue, 25 Jan 2022 18:43:19 -0500
Sam Varshavchik wrote:
> 2) Stuff that crammed down everyone's throat, for various non-technical
> reasons and, otherwise, they have no technical merit of advantage that
> anyone can identify and point to.
At least NM had a reasonably valid reason - wireless
Patrick O'Callaghan writes:
Perhaps not impossible, but certainly more difficult. I attribute this
to the poor quality of much documentation. Gone are the good ol' days
of UNIX when everything was in the man pages (as long as you had the
patience to read them). Many tools nowadays don't even ha
Tom Horsley writes:
Not all of it though, there were still a few more things for google
to turn up (like setting bridge.stp making it start 100 times faster).
I do have a server with a bridge and a hosted VM that uses it. The server
predated the existence of NetworkManager. At some point in
Every so often I have to boot Linux into single-user mode. I do this by
waiting for the Grub2 menu, selecting the desired kernel, and pressing
'e'. Then I select the 'linux' statement, add '1' to the end of
the line, and boot with .
This still works fine, but since upgrading to Fedora 34 I've
On Jan 25, 2022, at 12:03, Patrick O'Callaghan wrote:
>
>
> Perhaps not impossible, but certainly more difficult. I attribute this
> to the poor quality of much documentation. Gone are the good ol' days
> of UNIX when everything was in the man pages (as long as you had the
> patience to read the
On Tue, 25 Jan 2022 13:05:48 -0800
Samuel Sieb wrote:
> When
> was the last time you tried to use it?
A few years ago no doubt. It wasn't just the OK button. Value fields
I wanted to type in were inactive, etc. This is one of my many
objections to "helpful" GUI tools. At least the command line
t
On 1/25/22 12:52, Tom Horsley wrote:
On Tue, 25 Jan 2022 12:46:47 -0800
Samuel Sieb wrote:
It
allows you to create and edit any type of network interface
Only if the "OK" button isn't grayed out.
There is no OK button now. But I do remember a long time ago that there
was a field (I think
On Tue, 25 Jan 2022 12:46:47 -0800
Samuel Sieb wrote:
> It
> allows you to create and edit any type of network interface
Only if the "OK" button isn't grayed out.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to u
On 1/25/22 06:28, Tom Horsley wrote:
On Mon, 24 Jan 2022 19:17:06 -0800
Samuel Sieb wrote:
Install "nm-connection-editor" and it's easy.
Not remotely correct unless perhaps you are the author and know
what the gibberish it presents means. All my attempts to use it
mostly left me with all the
On 1/25/22 11:48, Thomas Cameron wrote:
I forgot to mention - disabling systemd-resolved does not make the
system get the reverse DNS assigned hostname. It's just set to "fedora."
Actually, I was incorrect! It said "fedora" as the hostname until I
logged in at the console. Then the hostname
On 1/24/22 09:50, Petr Menšík wrote:
One key difference might be enabled systemd-resolved by default in
Fedora 34, but it is not in RHEL9. I think it should not be related
directly. But could it?
What does hostnamectl report after installation? What it thinks the
hostname is? Would the behaviour
On 1/24/22 09:50, Petr Menšík wrote:
One key difference might be enabled systemd-resolved by default in
Fedora 34, but it is not in RHEL9. I think it should not be related
directly. But could it?
What does hostnamectl report after installation? What it thinks the
hostname is? Would the behaviour
On Tue, 2022-01-25 at 09:24 -0500, Tom Horsley wrote:
> > But there's just one problem. If you need to do a basic task, like
> > that, you
> > have absolutely no clue where to begin.
>
> Without google, linux itself would be impossible :-)
Perhaps not impossible, but certainly more difficult.
> Am 25.01.2022 um 15:30 schrieb James Szinger :
>
> On Tue, 25 Jan 2022 01:48:24 +0100
> Peter Boy wrote:
>
>> ...
>>
>> Konfiguration is much easier and it causes less system load. The only
>> disadvantage is that the VMs cannot communicate directly with the
>> host. But it is usually bette
In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to
"nobody" even though the names and numeric IDs are the same on the server and
client. The messages logged are of the form:
"name '@local' does not map into domain 'localdomain'"
I have no nfs-idmapd ser
On Tue, 25 Jan 2022 01:48:24 +0100
Peter Boy wrote:
> If you want your VMs to have access to the public network, then you
> have to share the host's public interface. The most convenient option
> is mac-vlan and to avoid a bridge. You don’t need to configure the
> host interface, but just the VMs
On Mon, 24 Jan 2022 19:17:06 -0800
Samuel Sieb wrote:
> Install "nm-connection-editor" and it's easy.
Not remotely correct unless perhaps you are the author and know
what the gibberish it presents means. All my attempts to use it
mostly left me with all the controls disabled and no hint
of what i
On Mon, 24 Jan 2022 21:20:50 -0500
Sam Varshavchik wrote:
> But there's just one problem. If you need to do a basic task, like that, you
> have absolutely no clue where to begin.
Without google, linux itself would be impossible :-). I got most of
that from a google search when led me here:
htt
19 matches
Mail list logo
