Re: F32 bind9 split dns debug

[Jack Craig]

On Sun, Nov 15, 2020 at 10:50 PM J.Witvliet--- via users <
users@lists.fedoraproject.org> wrote:

> How about: “lsof -i -n  -P”
>

this will do nicely, Thank You!

>
>
> *From: *"Jack Craig" 
> *Date:* Saturday, 14 November 2020 at 21:11:39
> *To: *"Community support for Fedora users" 
> *Subject:* Re: F32 bind9 split dns debug
>
> is there an easier way to verify a port access to internal host besides
> wireshark & tcpdump?
>
> On Sat, Nov 14, 2020 at 11:51 AM Jack Craig 
> wrote:
>
>>
>>
>> On Sat, Nov 14, 2020 at 11:33 AM Jack Craig 
>> wrote:
>>
>>>
>>> this part looked ok to me, but i am not sure.
>>>
>>
>> now seeing higher throughput, but still got...
>>
>> 14-Nov-2020 11:28:20.993 query-errors: info: client @0x7fc8601c9760
>> 52.183.97.231#63450 (linuxlighthouse.com): view external-wan-view: query
>> failed (REFUSED) for linuxlighthouse.com/IN/A at
>> ../../../bin/named/query.c:7270
>> 14-Nov-2020 11:28:21.030 query-errors: info: client @0x7fc8601c9760
>> 20.190.57.96#61806 (www.linuxlighthouse.com): view external-wan-view:
>> query failed (REFUSED) for www.linuxlighthouse.com/IN/A at
>> ../../../bin/named/query.c:7270
>> 14-Nov-2020 11:28:21.047 query-errors: info: client @0x7fc8601c9760
>> 51.143.102.160#49893 (www.linuxlighthouse.com): view external-wan-view:
>> query failed (REFUSED) for www.linuxlighthouse.com/IN/NS at
>> ../../../bin/named/query.c:7270
>>
>> how can i see/test a query's processing between default.log &
>> security.log ?
>> i can see the query, if i could see why it's failing, i'd query this list
>> less. ;)
>>
>> *www.linuxlighthouse.com/IN/NS  at
>> ../../../bin/named/query.c:7270*
>>
>>
>> *i looked at the query.c @7270 but was unable to gleen any useful
>> insight. *
>>
>> *WRT networking, my block of static ip's is from att.com *
>>
>> *i have cascaded routers from att's pace unit to a netgear night hawk
>> that does*
>> *port fwding for 53, 80 443 to the 10.0.0.101 sever.*
>> *i use the firewall on the att rtr limiting to the above ports to pass
>> through.*
>>
>> *the NH logs show connects to 53,80, & 443*
>>
>> *i also cranked debug to 10 in named logging, but so far,...*
>>
>>
>> *lastly, as F32 comes w/iptables, i migrated to nftables. *
>>
>>
>>>
>>>
> Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u
> niet de geadresseerde bent of dit bericht abusievelijk aan u is
> toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht
> te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van
> welke aard ook, die verband houdt met risico's verbonden aan het
> elektronisch verzenden van berichten.
>
> This message may contain information that is not intended for you. If you
> are not the addressee or if this message was sent to you by mistake, you
> are requested to inform the sender and delete the message. The State
> accepts no liability for damage of any kind resulting from the risks
> inherent in the electronic transmission of messages.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: F32 bind9 split dns debug

[Jack Craig]

i am still working to take all this in, Thank You for this time/wisdom...

On Sat, Nov 14, 2020 at 9:12 PM Tim via users 
wrote:

> On Sat, 2020-11-14 at 11:33 -0800, Jack Craig wrote:
> > zone: /var/named/internal
> >
> >
> > internal.  86400 IN SOA ws.linuxlighthouse.com.
> > root.linuxlighthouse.com. 2020101601 86400 3600 604800 86400
> > internal.  86400 IN NS ws.internal.
> > internal.  86400 IN A 108.220.213.121
> > internal.  86400 IN A 10.0.0.1
> > internal.  86400 IN MX 10 mail.internal.
> > mail.internal.  86400 IN A 108.220.213.122
> > ws.internal.  86400 IN A 108.220.213.121
> > ws.internal.  86400 IN A 10.0.0.101
> > ws2.internal.  86400 IN A 10.0.0.102
> > www.internal.  86400 IN A 108.220.213.121
> > www.internal.  86400 IN A 10.0.0.101
>
> Also, what names do you want resolved for internal searches?
>
> If you put a dot at the end of the name (mail.internal. etc), that's
> the whole domain name, it's not going to use it as a hostname suffixed
> with your domain name.  Without a dot, they'll be prefix subdomains.
>
> e.g. For an example.com zone file, an entry like this:
>
> www A   192.168.1.2
>
> will answer queries for: "www.example.com"
>
> But, an entry like this:
>
> www.A   192.168.1.2
>
> would be an answer for a query about: "www"
>
> At least, that's how BIND9 works on my computers.  Though I have read
> that it can handle different kinds of record files, I haven't tried
> them out.
>
> Here's an entire local network domain record on my system:
>
> $ORIGIN .
> $TTL 86400  ; 1 day
> example.lan IN SOA  ns.example.lan hostmaster.example.lan (
> 359; serial
> 300; refresh (5 minutes)
> 900; retry (15 minutes)
> 3600   ; expire (1 hour)
> 1800   ; minimum (30 minutes)
> )
> NS  ns.example.lan.
> A   192.168.1.1
> MX  1 mail.example.lan.
> $ORIGIN example.lan.
> mailA   192.168.1.1
> ns  A   192.168.1.1
> web CNAME   www
> www A   192.168.1.1
>
> Taking that all in line by line.
>
>  * This is the top-level record for this domain (dot origin)
>  * With a 1 day time-to-live for record data.
>  * It's the start of authority record (master records) for an
>example.lan domain name.
>  * Records held at ns.example.lan
>  * Admin contact is hostmas...@example.lan
>  * The serial number is 359 (be sure to increment it any time you
>change any DNS record data).
>  * Check for updated records every 5 minutes (this is a LAN with
>dynamic IPs, so short is okay, here).
>  * If the master server is unresponsive, wait for 15 minutes before
>trying again (keep using your previously cached data).  I haven't
>optimised this setting.
>  * Discard any unrefreshed cached data after 1 hour.
>  * Other DNS servers should cache this data for at least 30 minutes,
>even if they've not been able to refresh it.  Yes, I know it's
>different from the 1 day TTL, I'd been trying to see which figures
>were obeyed, but I don't remember my test results from all those
>years ago.
>  * The domain's NS server is ns.example.lan (note the trailing dot,
>meaning this is the end of this domain name, it's not a suffix to
>add example.lan to the end of it).  Theoretically, I could have just
>written ns by itself, with no dot at the end, and the domain name
>would be appended to it.
>  * The example.lan domain is at 192.168.1.1
>  * Its priority 1 mail exchanger is mail.example.lan (again, note the
>trailing dot)
>  * The following records are subdomains of example.lan (the probably
>redundant origin line).
>  * The mail subdomain (mail.example.lan) is at 192.168.1.1
>  * The ns subdomain (ns.example.lan) is at 192.168.1.1
>  * A web subdomain (web.example.lan) is an alternative for the www
>subdomain
>  * The www subdomain (www.example.lan) is at 192.168.1.1
>
>
>
> --
>
> uname -rsvp
> Linux 3.10.0-1160.2.2.el7.x86_64 #1 SMP Tue Oct 20 16:53:08 UTC 2020 x86_64
>
> Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> I will only get to see the messages that are posted to the mailing list.
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
users 

Re: F32 bind9 split dns debug

[J.Witvliet--- via users]

How about: “lsof -i -n  -P”


From: "Jack Craig" 
mailto:jack.craig.ap...@gmail.com>>
Date: Saturday, 14 November 2020 at 21:11:39
To: "Community support for Fedora users" 
mailto:users@lists.fedoraproject.org>>
Subject: Re: F32 bind9 split dns debug

is there an easier way to verify a port access to internal host besides 
wireshark & tcpdump?

On Sat, Nov 14, 2020 at 11:51 AM Jack Craig 
mailto:jack.craig.ap...@gmail.com>> wrote:


On Sat, Nov 14, 2020 at 11:33 AM Jack Craig 
mailto:jack.craig.ap...@gmail.com>> wrote:

this part looked ok to me, but i am not sure.

now seeing higher throughput, but still got...

14-Nov-2020 11:28:20.993 query-errors: info: client @0x7fc8601c9760 
52.183.97.231#63450 (linuxlighthouse.com): view 
external-wan-view: query failed (REFUSED) for 
linuxlighthouse.com/IN/A at 
../../../bin/named/query.c:7270
14-Nov-2020 11:28:21.030 query-errors: info: client @0x7fc8601c9760 
20.190.57.96#61806 (www.linuxlighthouse.com): 
view external-wan-view: query failed (REFUSED) for 
www.linuxlighthouse.com/IN/A at 
../../../bin/named/query.c:7270
14-Nov-2020 11:28:21.047 query-errors: info: client @0x7fc8601c9760 
51.143.102.160#49893 (www.linuxlighthouse.com): 
view external-wan-view: query failed (REFUSED) for 
www.linuxlighthouse.com/IN/NS at 
../../../bin/named/query.c:7270

how can i see/test a query's processing between default.log & security.log ?
i can see the query, if i could see why it's failing, i'd query this list less. 
;)

www.linuxlighthouse.com/IN/NS at 
../../../bin/named/query.c:7270

i looked at the query.c @7270 but was unable to gleen any useful insight.

WRT networking, my block of static ip's is from att.com

i have cascaded routers from att's pace unit to a netgear night hawk that does
port fwding for 53, 80 443 to the 10.0.0.101 sever.
i use the firewall on the att rtr limiting to the above ports to pass through.

the NH logs show connects to 53,80, & 443

i also cranked debug to 10 in named logging, but so far,...

lastly, as F32 comes w/iptables, i migrated to nftables.




Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet 
de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u 
verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat 
aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband 
houdt met risico's verbonden aan het elektronisch verzenden van berichten.

This message may contain information that is not intended for you. If you are 
not the addressee or if this message was sent to you by mistake, you are 
requested to inform the sender and delete the message. The State accepts no 
liability for damage of any kind resulting from the risks inherent in the 
electronic transmission of messages.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Not enough swap space for hibernation

[Chris Murphy]

On Fri, Nov 13, 2020 at 11:10 PM Samuel Sieb  wrote:
>
> On 11/13/20 9:39 PM, Tim via users wrote:
> > On Fri, 2020-11-13 at 21:24 +0530, Sreyan Chakravarty wrote:
> >> I have no idea why this is happening when I have 8GB of free swap space :
> >>
> >> $  free -h
> >>totalusedfree  shared  buff/cache   
> >> available
> >> Mem:  7.7Gi   1.6Gi   4.1Gi   269Mi   2.0Gi   
> >> 5.6Gi
> >> Swap: 8.0Gi  0B   8.0Gi
> >>
> >> My RAM is also 8GB.
> >
> > The old recommendation always was to have *MORE* swap space than RAM.
>
> That's a good point.  The memory usage is quite low at that point, but
> if he ever ended up using swap space, there could easily not be enough
> to hibernate.  However, it should work in this current case.

Hibernation is pretty complicated. What should happen is the kernel
evicts dirty pages to swap in order to free up 50% RAM. Then the
kernel uses that free memory to create the hibernation image and
compress it and then it gets written into swap. So there are some
opportunities for it to fail.

There's a bunch of tests to do to help narrow down the problem.
https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html

Note that swapfiles on Btrfs additionally need an offset boot parameter added.
https://bugzilla.kernel.org/show_bug.cgi?id=202803#c9


-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Grub2 Boot Menu Hidden in Fedora 33

[Chris Murphy]

On Sun, Nov 15, 2020 at 5:14 AM Stephen Morris  wrote:
>
> On 15/11/20 12:26 pm, Andre Robatino wrote:
> > I have a BIOS Fedora 33-only laptop, and "grub2-editenv - unset 
> > auto_hide_menu" worked on that.
> That's interesting. I am running F33 in a VM in VMware Player and for me
> that command did nothing, whereas it worked fine in F32.


What do you get for

grub2-editenv list



-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fstrim for ESP on SSDs

[Chris Murphy]

On Sun, Nov 15, 2020 at 9:34 AM Jorge Fábregas  wrote:
>
> Hi,
>
> I've been running with the fstrim.timer for years and recently noticed
> that my ESP partition always reports the same amount for trimmed blocks
> (512MB). It appears fstrim doesn't support FAT32 filesystems?

FAT supports discards since kernel ~4.19.

fstrim doesn't have file system specific support, it directly calls
FITRIM() ioctl and the kernel handles the file system specifics.

>Should I
> use the "discard" option in fstab for /boot/efi ?

> I know it's not a big issue since we seldom write the ESP after
> installation except for /boot/efi/EFI/fedora/grubenv after updates (or
> perhaps shim updates) but I'm wondering...

Yeah I don't think you need to consider it too much.


-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: systemd-resolved breakage

[Tom H]

On Sun, Nov 15, 2020 at 10:15 AM Anthony F McInerney
 wrote:


> Can someone explain why systemd-resolved needs to symlink
> /etc/resolv.conf to 4(or more) different places, instead of just
> having those 'detected things' as options in
> /etc/systemd/resolved.conf ?

The different symlinks/files provide different options.

/etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf
so
/etc/resolv.conf has "127.0.0.53" and "search"
resolved forwards queries to the upstream server

/etc/resolv.conf is a symlink to /usr/lib/systemd/resolv.conf
so
/etc/resolv.conf has "127.0.0.53"
resolved forwards queries to the upstream server

/etc/resolv.conf is a symlink to /run/systemd/resolve/resolv.conf
so
/etc/resolv.conf has "upstream server" and "search"
resolved only creates this file as if it were "resolvconf"

/etc/resolv.conf is a file
so
resolved uses the configured "server" and "search" as its "upstream
server" and "search"

I doubt that anyone would want resolved to create/modify the symlinks
depending on "/etc/systemd/resolved.conf".

Sam's idea of using the "alternatives" infrastrucure would be better.
But that would create other problems.

Assume that you're using networkd and resolved. If you install
NetworkManager, the preferred, higher-priority alternative'll be
"/run/NetworkManager/resolv.conf" whether you want it or not.


> Also spotted this on the Arch Wiki
>
> "systemd-resolved will work out of the box with a network manager
> using /etc/resolv.conf. No particular configuration is required
> since systemd-resolved will be detected by following the
> /etc/resolv.conf symlink. This is going to be the case with
> systemd-networkd or NetworkManager."

Sure, but this isn't the problem here. When you upgrade from F32 to
F33, the systemd post-install script enables resolved and creates a
resolved symlink.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

fstrim for ESP on SSDs

[Jorge Fábregas]

Hi,

I've been running with the fstrim.timer for years and recently noticed
that my ESP partition always reports the same amount for trimmed blocks
(512MB). It appears fstrim doesn't support FAT32 filesystems?  Should I
use the "discard" option in fstab for /boot/efi ?

I know it's not a big issue since we seldom write the ESP after
installation except for /boot/efi/EFI/fedora/grubenv after updates (or
perhaps shim updates) but I'm wondering...

Thanks.

-- 
Jorge
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: F32 UEFI reboot complete OK if 'cold/hard'; but 'warm/soft' reboot hangs after Grub menu entry is selected ?

[PGNet Dev]

On 11/15/20 5:23 AM, Roger Heflin wrote:

Does the kernel post any messages?


nope


you might try removing quiet and see if anything shows up at all,


those^ results are withOUT 'quiet' ...
specifically, WITH 'try-some-massively-overkill-debugging-first',

  rd.systemd.show_status=1 rd.shell=1 rd.auto=1 rd.udev.log_priority=debug 
rd.debug=1 rd.break systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on 
systemd.log_level=debug debug showopts noquiet print_fatal_signals=1 loglevel=8 
initcall_debug

and serial-console enabled/monitored.


if nothing at all does


nope. complete 'radio silence'.  not a peep after selecting the grub menu entry 
after a soft-reboot.


then something
must be broken really early which would likely make it a firmware
issue.


likely.  tho, i'm not entirely clear on what could be getting borked in a 
soft-reboot case that's NOT an issue in the hard-reboot case. and doesn't seem 
to appear as a problem in the running environment.


There are options you can specify on the kernel line that will force a
hard/cold boot when you do a reboot, and setting that option is
probably the easiest solution.  I think it is boot=cold but at the
moment the machine I have to set that on to get it to work on reboots
is off so I cannot double check.


here,

  https://www.kernel.org/doc/html/v5.8/admin-guide/kernel-parameters.html

i see only

reboot=

not

boot=

I've already tried any/all combinations of 'reboot=' options.

I've also tried the usual assortment of acpi= options ; to no avail.

I can't get it to FAIL to RE-boot; in all soft cases, e.g. 'shutdown -r now', I 
_do_ get a reboot, back to the grub menu ... and it's there, and only there, 
that it freezes / goes silent on soft-reboot.


A bios update might fix it, but if the boot=cold does it, then I would
just set that.  The option is I believe designed for this sort of
issue.


BIOS is latest available; which _is_ a bit old.

I've cleared/reflashed ... no effect.

(Re)booting the machine with different OSs (Win10, Ubu20, OpensuseTW) all work 
without problem; both in the soft- and hard-reboot cases.

So, here, it's Fedora-specific; It's 'local' to my F32 install on this machine; 
elusive, atm :-/

If I can just manage to get _some_ sort of useful logging at that stage ...
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: F32 UEFI reboot complete OK if 'cold/hard'; but 'warm/soft' reboot hangs after Grub menu entry is selected ?

[Roger Heflin]

I am going to guess a "warm" reboot does not leave some piece of
critical hardware in a correct state (either to work, or that some
driver and/or grub needs/expects) and so something fails early.

Does the kernel post any messages? you might try removing quiet and
see if anything shows up at all, if nothing at all does then something
must be broken really early which would likely make it a firmware
issue.

There are options you can specify on the kernel line that will force a
hard/cold boot when you do a reboot, and setting that option is
probably the easiest solution.  I think it is boot=cold but at the
moment the machine I have to set that on to get it to work on reboots
is off so I cannot double check.

A bios update might fix it, but if the boot=cold does it, then I would
just set that.  The option is I believe designed for this sort of
issue.

On Sat, Nov 14, 2020 at 3:00 PM PGNet Dev  wrote:
>
> I've built up an older box (ASRock J1900D2Y mobo), on Fedora32 + kernel 
> 5.8.18 + grub 2.04 (from F32 pkgs), booting UEFI.
>
> I can cold boot -- or hard reboot -- the box, and it boots to desktop with no 
> problems.
> Afaict, everything's up & running without issue.
>
> But,
>
> on SOFT reboot -- via either `shutdown -r now` or `systemctl start 
> reboot.target`,
> the system DOES start the reboot.
> UEFI boot passes to grub menu as usual, latest kernel is selected, and then 
> ...
> ... nothing.
>
> Just sits there.  No further error logging, or progress -- even at serial 
> console with kernel/systemd debug logging turned up.
>
> A cold, power-cycling reboot immediately fixes the problem -- e.g., after an 
> IPMI 'Reset', the system again boots fine.
>
> Since cold boot is OK, seems kernel & initrd are ok.
>
> Since the issue arises only AFTER grub menu's in the picture, it doesn't seem 
> that BIOS/UEFI should be involved in any way.
>
> Any hints as to where to dig around next? Or suggestions how to workaround?
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Grub2 Boot Menu Hidden in Fedora 33

[Stephen Morris]

On 15/11/20 12:26 pm, Andre Robatino wrote:

I have a BIOS Fedora 33-only laptop, and "grub2-editenv - unset auto_hide_menu" 
worked on that.
That's interesting. I am running F33 in a VM in VMware Player and for me 
that command did nothing, whereas it worked fine in F32.


regards,
Steve
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Grub2 Boot Menu Hidden in Fedora 33

[Stephen Morris]

On 15/11/20 1:20 am, Tom Horsley wrote:

On Sat, 14 Nov 2020 16:00:38 +1100
Stephen Morris wrote:


In Fedora 33 is the only way to get the menu to permanently display to
edit /etc/grub.d/12_menu_auto_hide and change the timeout_style and
timeout settings within the else condition for the fastboot check? I
currently have the menu permanently displayed as a result of making this
modification.

Yep. I've had a "big hammer" I've used for a while, run automatically
after dnf to reapply any changes I've made to system files I'm
not intended to edit. Fixing the grub scripts so not a single one
can ever set hide to true is one of my big hammer changes :-).

https://tomhorsley.com/game/Mjolnir.html
Thanks Tom. I did find an article on the net that appeared to be from 
the designer of this process, where he provided a method to display the 
menu without needing to edit any files, but that only worked for the 
next boot. Apparently the process has now been designed to only display 
the menu if the last boot failed.


regards,
Steve
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: systemd-resolved breakage

[Anthony F McInerney]

On Sat, 14 Nov 2020 at 19:35, Sam Varshavchik  wrote:

> Anthony F McInerney writes:
>
> >Note that the selected mode of operation for this file is
> detected
> > fully automatically, depending on whether /etc/resolv.conf is a symlink
> to
> >/run/systemd/resolve/resolv.conf or lists 127.0.0.53 as DNS
> server.
>
> Again: why does anything have to be "detected fully automatically"?
>
> We've had a mechanism for controlling symlinks for an eternity:
> alternatives.
>
> I cannot see any valid technical argument against having /etc/resolv.conf
> managed by alternatives. If systemd-resolved wishes to have the highest
> alternatives priority, and thus ends up being the resolver by default,
> that's fine.
>
> Does anyone have an argument /against/ having /etc/resolv.conf managed
> via
> alternatives? What can't you do with alternatives that you can with the
> current ham-fisted approach, where someone has to go out of their way to
> figure out how to switch to network manager-provided resolv.conf?
>
>
>
Can someone explain why systemd-resolved needs to symlink /etc/resolv.conf
to 4(or more) different places, instead of just having those 'detected
things' as options in /etc/systemd/resolved.conf ?

Also spotted this on the Arch Wiki

*"systemd-resolved* will work out of the box with a network manager
 using
/etc/resolv.conf. No particular configuration is required since
*systemd-resolved* will be detected by following the /etc/resolv.conf symlink.
This is going to be the case with systemd-networkd
 or NetworkManager
."
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org