Re: Kickstart Fedora 30 (aarch64) on Raspberry Pi 3 B+

[Samuel Sieb]

On 5/27/19 10:13 PM, Felix Geschwindner via users wrote:

I managed to boot U-Boot, chain load iPXE (probably not necessary since U-Boot is capable 
enough) but when pulling the regular aarch64 vmlinuz/initrd.gz pxeboot images it just 
errors out with an error saying "Invalid application". My knowledge about the 
kernel/initramfs chain gets blurry here which is why all tries in altering the initrd.gz 
image have failed gloriously.


I don't know much about this, but "Invalid application" suggests that 
iPXE doesn't like the kernel image you're trying to start.  Unless it's 
uboot not liking your iPXE.

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

Re: Fedora 30, BootLoaderSpec and generating entries under /boot/loader/entries

[Chris Murphy]

On Wed, May 22, 2019 at 11:16 AM Kevin Wilson  wrote:
>
> Hi all,
>
> I had installed Fedora 30,  on a dual boot machine which has a second
> partition with Fedora 28.
> Fedora 30  comes by default with a new boot loader spec.
>
> I found under /boot/loader/entries/ the following:
>
> ls /boot/loader/entries/
>
> ec1b8b7719964c8b9a1d8db430c63fd6-0-rescue.conf
> ec1b8b7719964c8b9a1d8db430c63fd6-5.0.9-301.fc30.x86_64.conf0
>
> I want to be able to boot by default into Fedora 28.

There are a couple of ways to do this. I have't tested any of them, so
I'm not sure which is the most reliable. On Fedora 28 do you have
/usr/sbin/grub2-switch-to-blscfg ?

If so, one option is to convert Fedora 28 to use BLS - and then it's
possible for Fedora 28 and Fedora 30 to share a single /boot where all
the kernels and drop-in bootloader .conf files go. The one tricky
thing is, if this is UEFI, we would probably want to make sure Fedora
28 /etc/fstab does not mount the EFI System partition on /boot/efi
because we'll want to prevent the older Fedora 28 EFI bootloader
packages from overwriting the contents of the EFI system partition.
It's fine for the packages to get installed on Fedora 28 though.

Another strategy is to edit the Fedora 30 grub.cfg (strictly speaking
should using either /etc/grub.d/40_custom or /etc/grub.d/41_custom) so
that there is a single "forwarding" entry to Fedora 28's grub menu.
That menu entry uses the GRUB 'configfile' command and points to the
Fedora 28 grub.cfg. Now Fedora 28 goes on updating its grub.cfg
normally.

It should be possible to give this forwarding menu entry a proper
title that can be set as the saved_entry in the grubenv so that GRUB
will use it by default. I know, it seems a little bit Rube Goldberg
but at least it'd all be self-describing.

Thing is, each strategy does differ on the details depending on
firmware type: BIOS or UEFI. On BIOS, the grub.cfg is self contained
in the /boot for that particular version of Fedora. Whereas with UEFI,
the grub.cfg goes on /boot/efi/EFI/fedora/ no matter the Fedora
version, which happens to be on the EFI system partition. So out of
the box, two Fedora bootloaders cannot co-exist on UEFI, F28 will
always try to step on the grub.cfg there, where F30 never updates it.
I'm also not really sure that Fedora 28's GRUB blscfg.mod is getting
all the latest updates and bug fixes. It's going EOL in 5 days.


>
> Is there a way by some utility to generate entries under
> /boot/loader/entries/ for the
> Fedora 28  and choose Fedora 28 as the default ?

Dual Fedoras has never exactly been easy. It requires some esoteric
knowledge of GRUB as well as update and upgrade handling to know the
path of least resistance.

(I say that from a system with six or seven Fedoras on a single Btrfs
volume, each in their own subvolume, and if i want to flip to one of
the others, I just hand edit the menu entry changin the
'rootflags=subvol=root30' to use root29 or root28 or rootraw or
whatever. The gotcha of course is those roots don't necessarily have
matching kernel modules for the /boot kernel + initramfs. Since I'm
using Fedora 30 95% of the time, I just manually 'cp -a --reflink'
copy the latest modules from F30 to the proper location in the rootX
subvolume for the Fedora version I want to boot.)

The nice thing about BLS going forward is with minimal effort it is
possible for Fedora 29, 30, 31 to share a single /boot, they all drop
their kernels, initramfs, and matching bls snippets there, and they
all appear in the same GRUB menu. The one thing to change is
/etc/fstab so older Fedora's doing GRUB updates don't overwrite
/boot/efi/EFI/fedora with old bootloader binaries (not really the end
of the world if it did happen I guess).


> Or should I disable the boot loader spec in order to boot to Fedora 28
> on this machine ?

I'm not sure that really helps get you closer to what you want. Anyway
it's best if you tell us what your plan is for Fedora 28 going EOL
this week. Are you making Fedora 30 primary in the near future? Or are
you going to upgrade the Fedora 28 installation to Fedora 29? That
sorta matters strategy wise. Maybe.



-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Kickstart Fedora 30 (aarch64) on Raspberry Pi 3 B+

[Felix Geschwindner via users]

Hi Fedora community,

Fedora on RPI is AMAZING and I'm working on a project to automate provisioning 
for a Raspberry Pi cluster. This would add a ton of CI capabilities and 
convenience. It would also take the edge of the nuisance that RPIs eat SD cards 
like I eat Oreos.
Right now the process is pretty manual:

1. Put SD card in secondary machine
2. DD Fedora's minimal aarch64 image onto SD card
3. Grow partition
4. Put SD card back
5. Boot
6. Go through initial setup
7. Update all packages
8. Continue with regular config and host management

This requires being physically in front of the RPIs (and provisioning machine) 
and involves a lot of hand holding.

I'd like to make this process as headless as possible so that re-kicking a RPI 
is as easy as "setting a flag", rebooting and waiting for the RPI to come back 
up freshly installed.
Right now I have the following path in mind how this could potentially work:

The network interface of the RPI3B+ is capable of PXE booting, yay! So I'm 
thinking something along the lines of:

1. DHCP
2. Load files through TFTP (bootcode.bin -> start_x.elf -> DTB(?) -> 
u-boot.bin/IPXE -> kernel -> initramfs)
3. Boot kernel/initramfs which fires up Anaconda
4. Install Fedora normally
5. Use %post to copy device tree files to /boot and do other things necessary 
to make the RPI boot

If this worked, provisioning would be as easy as:

(0. Create DHCP reservation)
1. SD card into RPI
2. Turn on RPI
3. Login via SSH/VNC/etc.

I managed to boot U-Boot, chain load iPXE (probably not necessary since U-Boot 
is capable enough) but when pulling the regular aarch64 vmlinuz/initrd.gz 
pxeboot images it just errors out with an error saying "Invalid application". 
My knowledge about the kernel/initramfs chain gets blurry here which is why all 
tries in altering the initrd.gz image have failed gloriously.

If we can make this possible I'd be happy to turn it into a Wiki page so that 
others can extend their RPI environment with unattended provisioning.

Happy memorial to everyone celebrating and thank you for your interest!
Vascko
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: is grubby a dumb software?

[Chris Murphy]

On Sun, May 26, 2019 at 11:14 PM François Patte
 wrote:
>
> > 5. BLS installation by default !?

https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault



>
> ???
>
> Moreover my system uses raid-1 + lvm
>
> Do you mean that grubby --- which seems to be the grub configuration
> tool chosen by fedora --- cannot handle my installation? What can I do:
> change to another distrib?

Fedora 30, both new installations and upgrades from Fedora 28/29, has
GRUB bootloaderspec enabled by default.

grubby isn't used during kernel upgrades anymore, there are scripts in
the kernel package that create a bootloader file for that kernel and
is dropped into /boot/loader/entries - and then a GRUB blscfg.mod
module parses the drop-in scripts in /boot/loader/entries to create
the GRUB menu. This means the grub.cfg is static, is no longer either
recreated or modified.

And it should support raid1 + LVM. If it's not, it's a bug and should be fixed.

Anyway, you can include the following information. Ideally attach it
all to a detailed bug report describing the problem, but you can use
fpaste, pastebine, Google Drive, or Nextcloud URL for your files:

# blkid
# efibootmgr -v
# rpm -qa | grep grub2
# fdisk -l /dev/sdX##where X is the device node for boot & root partitions

Include these files:
/etc/fstab
/etc/default/grub
/boot/efi/EFI/fedora/grub.cfg or /boot/grub2/grub.cfg
/boot/efi/EFI/fedora/grubenv or /boot/grub2/grubenv
/boot/loader/entries/*   ## all of them




-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: F30 Grub2-mkconfig and Grub2-install not Working Correctly?

[Chris Murphy]

On Mon, May 27, 2019 at 10:37 PM Chris Murphy  wrote:
>
> On Thu, May 23, 2019 at 5:08 AM Tom H  wrote:
> >
> > I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> > "/etc/default/grub" _should_ (given the variable's name) allow
> > "grub2-mkconfig" give you an upstream-style "grub.cfg".
>
>
> It is also necessary to
> # dnf install grubby-deprecated
>
> I'm not sure how long that deprecated package will be maintained, so I
> don't recommend reverting this change, instead it's better to move
> forward, file bugs, and make it better.

Explanation: This package is the real grubby. The grubby package in
F30 is a wrapper script that has far less functionality and is there
just to help people familiar with grubby commands for changing kernel
boot behavior like boot parameters and default kernel. But if you
revert to the old way, you need the real grubby provided by the
grubby-deprecated package, because that's what rewrites the grub.cfg
when new kernels are installed and old kernels are removed.

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: F30 Grub2-mkconfig and Grub2-install not Working Correctly?

[Chris Murphy]

On Thu, May 23, 2019 at 5:08 AM Tom H  wrote:
>
> I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> "/etc/default/grub" _should_ (given the variable's name) allow
> "grub2-mkconfig" give you an upstream-style "grub.cfg".


It is also necessary to
# dnf install grubby-deprecated

I'm not sure how long that deprecated package will be maintained, so I
don't recommend reverting this change, instead it's better to move
forward, file bugs, and make it better.


-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora & MIDI - recommendations request [solved]

[Seth Kenlon]

Interesting. I haven't had to stop Pulse for my music work in years
(but admittedly haven't worked on Fedora in a while, opting for the
stability of Slackware and RHEL; maybe this apparent regression
confirms my bias). Any way, glad you got it working!

On Tue, May 28, 2019 at 5:18 AM Max Pyziur  wrote:
>
> On Sat, 25 May 2019, Seth Kenlon wrote:
>
> > For a MIDI file to produce sound out of Rosegarden (and probably most
> > DAWs) you do have to assign the MIDI file an instrument.
> >
> > If the MIDI file is composed for General MIDI, you have to assign
> > General MIDI to the track containing the MIDI file you are trying to
> > play. I haven't used Timidity++ directly in a long while, but if I
> > remember correctly, General MIDI is the default for it (although you
> > can swap out instrument sets in timidiity.cfg). So in other words,
> > while it *is* the default behaviour of Timidity to use General MIDI
> > mappings in order to produce sound from a MIDI file, that is *not* the
> > default for Rosegarden (et. al) because a DAW sort of expects you to
> > assign your own instruments.
> >
> > If you are assigning an instrument (in Track Parameters) to the track
> > in Rosegarden, then I'd look at your sound output settings. I imagine
> > Rosegarden is sending sound output to something other than the
> > speakers or headphones you expect to hear output from. The way I check
> > for that is from the outside in: check all my physical cable
> > connections, then my sound settings in pavuctl (Sound Settings in
> > Gnome), then check JACK sound mappings, and then finally check
> > Rosegarden sound mapping.
>
> Thank you for this.
>
> I now can plug in a USB MIDI hardward controller (Akai LPK25) and open
> Rosengarden, and get sound output. I also can load a MIDI file (found on
> some MIDI archive) into Rosengarden, and it plays.
>
> Not all Fedora-installed MIDI-related is functioning for me.
>
> But combined that's a start and gets me to the next set of obstacles.
>
> The critical set of instructions and web source that got me through this
> is
> Ted's Linux MIDI Guide
> http://tedfelix.com/linux/linux-midi.html
>
> There's some explanation; critically Pulseaudio impedes MIDI functionality
> and needs to be shutdown at the user level. The webpage provides a bash
> init.d-style StartStopStatus script. It needs a bit of modification for
> things such as the location the recommended soundfont.
>
> The webpage also provides examples of commands to use for diagnostic
> purposes.
>
> fyi,
>
> MP
>
> > On Sat, May 25, 2019 at 9:43 AM Samuel Sieb  wrote:
> >>
> >> On 5/24/19 6:32 AM, Max Pyziur wrote:
> >>> I then began working through your Rosengarden item. I connected my USB
> >>> MIDI controller ((Akai LPK25).
> >>>
> >>> Started jackd, then qjacktl, and then Rosengarden.
> >>>
> >>> I loaded a MIDI file, pushed "play," and I get no sound. That's where I
> >>> get stuck.
> >>>
> >>> As I mentioned, I can work w MuseScore, Transcribe!, Audacity, strip
> >>> audio from videos using ffmpeg, etc.
> >>>
> >>> So, it seems that there are some services that need to be
> >>> enabled/started or disabled/stopped to move further here.
> >>
> >> Try installing qsynth (gui for fluidsynth).  Connect it to the midi port.
> >>
> >> I helped my son setup rosegarden to play around with some composing, so
> >> I know it works.
> >> ___
> >> users mailing list -- users@lists.fedoraproject.org
> >> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >> 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://getfedora.org/code-of-conduct.html
> > 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://getfedora.org/code-of-conduct.html
> 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archive

Re: F28, openvpn, NetworkManager

[Jack Craig]

On Mon, May 27, 2019 at 6:42 AM Mike Wright 
wrote:

> On 5/26/19 10:59 PM, Jack Craig wrote:
>
> >  , then vpn comes and
> >  > default route is now pointed at the vpn.
> >  >
> >  > and this process in reverse on shutdown...
>
> What I've seen is two additional, more specific, default routes added:
> 0.0.0.0/1 and 128.0.0.0/1, which cover the entire ipv4 address space. By
> doing it this way the new routes can be deleted and the original default
> route remains.  This works because a more specific route trumps the less
> specific route (0.0.0.0).
>
> Unfortunately, I can't remember who adds/removes those routes but I
> suspect it is NM.
>

i think you are right, ...

[ws:root:/etc/sysconfig/network-scripts]# grep "ip route add" *



> Good travels on your adventure,
>

Thx!

:m
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora & MIDI - recommendations request [solved]

[Max Pyziur]

On Sat, 25 May 2019, Seth Kenlon wrote:


For a MIDI file to produce sound out of Rosegarden (and probably most
DAWs) you do have to assign the MIDI file an instrument.

If the MIDI file is composed for General MIDI, you have to assign
General MIDI to the track containing the MIDI file you are trying to
play. I haven't used Timidity++ directly in a long while, but if I
remember correctly, General MIDI is the default for it (although you
can swap out instrument sets in timidiity.cfg). So in other words,
while it *is* the default behaviour of Timidity to use General MIDI
mappings in order to produce sound from a MIDI file, that is *not* the
default for Rosegarden (et. al) because a DAW sort of expects you to
assign your own instruments.

If you are assigning an instrument (in Track Parameters) to the track
in Rosegarden, then I'd look at your sound output settings. I imagine
Rosegarden is sending sound output to something other than the
speakers or headphones you expect to hear output from. The way I check
for that is from the outside in: check all my physical cable
connections, then my sound settings in pavuctl (Sound Settings in
Gnome), then check JACK sound mappings, and then finally check
Rosegarden sound mapping.


Thank you for this.

I now can plug in a USB MIDI hardward controller (Akai LPK25) and open 
Rosengarden, and get sound output. I also can load a MIDI file (found on 
some MIDI archive) into Rosengarden, and it plays.


Not all Fedora-installed MIDI-related is functioning for me.

But combined that's a start and gets me to the next set of obstacles.

The critical set of instructions and web source that got me through this 
is

Ted's Linux MIDI Guide
http://tedfelix.com/linux/linux-midi.html

There's some explanation; critically Pulseaudio impedes MIDI functionality 
and needs to be shutdown at the user level. The webpage provides a bash 
init.d-style StartStopStatus script. It needs a bit of modification for 
things such as the location the recommended soundfont.


The webpage also provides examples of commands to use for diagnostic 
purposes.


fyi,

MP


On Sat, May 25, 2019 at 9:43 AM Samuel Sieb  wrote:


On 5/24/19 6:32 AM, Max Pyziur wrote:

I then began working through your Rosengarden item. I connected my USB
MIDI controller ((Akai LPK25).

Started jackd, then qjacktl, and then Rosengarden.

I loaded a MIDI file, pushed "play," and I get no sound. That's where I
get stuck.

As I mentioned, I can work w MuseScore, Transcribe!, Audacity, strip
audio from videos using ffmpeg, etc.

So, it seems that there are some services that need to be
enabled/started or disabled/stopped to move further here.


Try installing qsynth (gui for fluidsynth).  Connect it to the midi port.

I helped my son setup rosegarden to play around with some composing, so
I know it works.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
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://getfedora.org/code-of-conduct.html
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: F30 Grub2-mkconfig and Grub2-install not Working Correctly?

[ja]

On Mon, 2019-05-27 at 19:10 +0200, Tom H wrote:
> > On 23/5/19 9:07 pm, Tom H wrote:
> > > I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> > > "/etc/default/grub" _should_ (given the variable's name) allow
> > > "grub2-mkconfig" give you an upstream-style "grub.cfg".
> > 
> > Thanks Tom, "/etc/default/grub" had a setting of
> > "GRUB_ENABLE_BLSCFG=true" which I changed from "true" to "false"
> > and that enabled the original grub2-mkconfig style menu. So
> > everything is now good.
> 
> Good. You're welcome.
> 
> [ But the BLS way is nice too. If you have the time, you should set up
> a VM and check it out. ]
> 
+1

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

Re: F30 Grub2-mkconfig and Grub2-install not Working Correctly?

[Tom H]

> On 23/5/19 9:07 pm, Tom H wrote:
>>
>> I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
>> "/etc/default/grub" _should_ (given the variable's name) allow
>> "grub2-mkconfig" give you an upstream-style "grub.cfg".
>
> Thanks Tom, "/etc/default/grub" had a setting of
> "GRUB_ENABLE_BLSCFG=true" which I changed from "true" to "false"
> and that enabled the original grub2-mkconfig style menu. So
> everything is now good.

Good. You're welcome.

[ But the BLS way is nice too. If you have the time, you should set up
a VM and check it out. ]
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: F28, openvpn, NetworkManager

[Mike Wright]

On 5/26/19 10:59 PM, Jack Craig wrote:



On Sun, May 26, 2019 at 10:52 PM Ed Greshko > wrote:


On 5/27/19 1:38 PM, Jack Craig wrote:
 >
 >
 > On Sun, May 26, 2019 at 10:17 PM Ed Greshko
mailto:ed.gres...@greshko.com>
 > >>
wrote:
 >
 >     On 5/27/19 12:17 PM, Jack Craig wrote:
 >     > i thought what i read was after nm brings up the vpn, only
then is the default
 >     route to
 >     > vpn created. more, its torn down first on shutdown.
 >     >
 >     > i'm thinking along this line, ...
 >     >
 >     > https:

xpect
what should happen is that after each interface comes up via NM a
default route
 > is set to it
 > so eth0 up, default route to , say, 10.0.0./24
 , then vpn comes and
 > default route is now pointed at the vpn.
 >
 > and this process in reverse on shutdown...


What I've seen is two additional, more specific, default routes added:
0.0.0.0/1 and 128.0.0.0/1, which cover the entire ipv4 address space. By 
doing it this way the new routes can be deleted and the original default 
route remains.  This works because a more specific route trumps the less 
specific route (0.0.0.0).


Unfortunately, I can't remember who adds/removes those routes but I 
suspect it is NM.


Good travels on your adventure,
:m
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: F30 Grub2-mkconfig and Grub2-install not Working Correctly?

[Stephen Morris]

On 23/5/19 9:07 pm, Tom H wrote:

On Thu, May 23, 2019 at 11:12 AM Stephen Morris
 wrote:

On 23/5/19 3:49 pm, Tom H wrote:

On Thu, May 23, 2019 at 12:55 AM Stephen Morris
 wrote:

I have upgraded from F29 to F30 via the recommenced dnf method. I
have Fedora running in a vm under vmware player. Grub2-mkconfig
and grub2-install no longer seem to generate the grub menu as
they did under F29, the menu seems to be that generated by grubby
(it could be that turning off the suppression of sub-menu
creation is now being ignored). Looking at /boot/grub2/grub.cfg I
cannot see any references in there to kernels, so I have attached
the file for reference. Am I missing something or is the
functionality now different, /boot/grub2/grub.cfg is where I have
always written the grub.cfg via this process?

You have

insmod blscfg
blscfg

on lines 128-129.

So grub's setting up a generic BLS grub.cfg and you should have
your kernel specifications in "/boot/loader/entries/*.conf".

Does "/boot/grub2/i386-pc/blscfg.mod" exist on your system?

IIRC, the common bugs page recommends "configfile
/boot/grub2/grub.cfg.rpmsave" or "configfile
//grub2/grub.cfg.rpmsave"
(depending on whether "/boot" is a separate filesystem) at the
grub prompt to use the previous grub.cfg.

Is it documented anywhere how to switch the system back to using,
in my case, /boot/grub2/grub.cfg to provide the kernel menu
structure via grub2-mkconfig and grub2-install as it was in
previous versions of Fedora?

I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
"/etc/default/grub" _should_ (given the variable's name) allow
"grub2-mkconfig" give you an upstream-style "grub.cfg".


Thanks Tom, "/etc/default/grub" had a setting of 
"GRUB_ENABLE_BLSCFG=true" which I changed from "true" to "false" and 
that enabled the original grub2-mkconfig style menu. So everything is 
now good.



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://getfedora.org/code-of-conduct.html
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: is grubby a dumb software?

[stan via users]

On Sun, 26 May 2019 23:32:35 -0700
Samuel Sieb  wrote:

>  From that URL, BLS = Boot Loader Specification.
> Instead of having a monolithic grub config file, there are individual 
> files describing each boot option.

Thanks, I just came back to correct my answer, and see that you have
done that for me.  :-)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org