Re: wayward wayland.

On Fri, 2021-04-23 at 20:24 -0600, home user wrote: > Since my initial install was 8 years ago, I don't remember for > certain how I did it: CD or USB stick. For later on, once you're back working again: Next time you do an install, leave some notes in the /root homespace about what you've done.

Re: machine will not boot after moving root

On Fri, Apr 23, 2021 at 11:17 PM Samuel Sieb wrote: > > On 4/23/21 3:37 PM, Michael Hennebry wrote: > >> With the hard disk only does it find grub and does it display a menu > >> or drop you to the grub> prompt? > > > > I get the grub prompt. > > And this is where you can only see (hd0)? That so

Re: machine will not boot after moving root

On Fri, Apr 23, 2021 at 11:11 PM Samuel Sieb wrote: > His partition list has "extended" on sda4, so it looks like he's correct > about it being BIOS. Yep, I missed that. grub2-install --force /dev/sdXY can work, even though it's not recommended upstream. I think it's still some confusion over

Re: machine will not boot after moving root

On 4/23/21 3:37 PM, Michael Hennebry wrote: On Fri, 23 Apr 2021, Roger Heflin wrote: What is the exact error you are getting? Something along the lines of UUID 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a not found. When are you getting this error? Since you say grub isn't booting from the hard d

Re: machine will not boot after moving root

On 4/23/21 7:39 PM, Chris Murphy wrote: I'm actually betting dollars to donuts that this is a UEFI system, and grub2-install was used, and now it's looking for grub.cfg in the wrong location. His partition list has "extended" on sda4, so it looks like he's correct about it being BIOS. ___

Re: machine will not boot after moving root

On 4/23/21 1:05 PM, Roger Heflin wrote: But if the windows system is gone and you don't care about it, then I would set sda3 to be bootable. The bootable flag is not relevant. rescue it and then grub-install /dev/sda3 but make sure the newuuid is grub needs to be installed to the raw hard d

Re: wayward wayland.

On 4/23/21 9:48 PM, Ed Greshko wrote: That caveat only applied to lightdm.  I'd revert that change now that you'e using gdm. reverted. rebooted. got the gdm login. The GNOME entry re-appeared; the GNOME on Xorg entry disappeared. logged into GNOME. "env | grep -i wayland" returns nothing,

Re: wayward wayland.

On 24/04/2021 11:26, home user wrote: On 4/23/21 9:18 PM, Ed Greshko wrote: 2.  Do you have the file /usr/share/wayland-sessions/gnome.desktop (You've not disabled it) I have it; see below.  I don't know if I've disabled it; how would I check? That question was related to earlier in the thr

Re: wayward wayland.

On 4/23/21 9:18 PM, Ed Greshko wrote: 2.  Do you have the file /usr/share/wayland-sessions/gnome.desktop (You've not disabled it) I have it; see below.  I don't know if I've disabled it; how would I check? That question was related to earlier in the thread in talking about lightdb.  If one a

Re: wayward wayland.

On 24/04/2021 11:09, home user wrote: On 4/23/21 8:48 PM, Ed Greshko wrote: On 24/04/2021 10:42, home user wrote: On 4/23/21 8:28 PM, Ed Greshko wrote: On 24/04/2021 10:24, home user wrote: ... So we're back to the starting questions.  How do I get wayland working in gnome on this workstat

Re: wayward wayland.

On 24/04/2021 11:15, home user wrote: Looking more slowly and closely, I see 2 of mine are more recent than Ed's: qt5-qtwayland-5.15.2-5.fc33.x86_64 (mine) qt5-qtwayland-5.15.2-3.fc33.x86_64 (Ed's) xorg-x11-server-Xwayland-1.20.11-1.fc33.x86_64 (mine) xorg-x11-server-Xwayland-1.20.10-1.fc33.x86

Re: wayward wayland.

On 4/23/21 9:09 PM, home user wrote: On 4/23/21 8:48 PM, Ed Greshko wrote: On 24/04/2021 10:42, home user wrote: On 4/23/21 8:28 PM, Ed Greshko wrote: On 24/04/2021 10:24, home user wrote: ... So we're back to the starting questions.  How do I get wayland working in gnome on this workstatio

Re: wayward wayland.

On 4/23/21 8:48 PM, Ed Greshko wrote: On 24/04/2021 10:42, home user wrote: On 4/23/21 8:28 PM, Ed Greshko wrote: On 24/04/2021 10:24, home user wrote: ... So we're back to the starting questions.  How do I get wayland working in gnome on this workstation?  Am I missing something? If yes, w

Re: on to letsencrypt

This is wonderful ED, Thank YOU!! first tho, a backup of key files... On Fri, Apr 23, 2021 at 7:37 PM Ed Greshko wrote: > On 24/04/2021 10:29, Jack Craig wrote: > > ok, done. now we have, > > > > > > Apr 23 19:25:59 ws.linuxlighthouse.com > named[6483]: usin

Re: wayward wayland.

On 24/04/2021 10:42, home user wrote: On 4/23/21 8:28 PM, Ed Greshko wrote: On 24/04/2021 10:24, home user wrote: ... So we're back to the starting questions.  How do I get wayland working in gnome on this workstation?  Am I missing something? If yes, what? Otherwise, what do I need to do t

Re: wayward wayland.

On 4/23/21 8:28 PM, Ed Greshko wrote: On 24/04/2021 10:24, home user wrote: ... So we're back to the starting questions.  How do I get wayland working in gnome on this workstation?  Am I missing something? If yes, what?  Otherwise, what do I need to do to make wayland available and properly

Re: machine will not boot after moving root

On Fri, Apr 23, 2021 at 2:51 PM Michael Hennebry wrote: > I've read that I need --force to grub2-install onto a partition. That's sufficiently unreliable that upstream GRUB has recommended against it for almost a decade. First, what firmware type is this? [ -d /sys/firmware/efi ] && echo UEFI

Re: on to letsencrypt

On 24/04/2021 10:29, Jack Craig wrote: ok, done. now we have, Apr 23 19:25:59 ws.linuxlighthouse.com named[6483]: using 7 UDP listeners per interface Apr 23 19:25:59 ws.linuxlighthouse.com named[6483]: listening on IPv6 inte

Re: machine will not boot after moving root

On Thu, Apr 22, 2021 at 1:41 PM Michael Hennebry wrote: > > I'm trying to move my root directory from sda5 to sda3. This is much harder to do without LVM or Btrfs. For LVM there's more steps but basically it depends on 'pvmove'. And for Btrfs it's 'btrfs replace' - both are live migrations and so

Re: on to letsencrypt

ok, done. now we have, systemctl status named ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2021-04-23 19:25:59 PDT; 39s ago Process: 6480 ExecSta

Re: wayward wayland.

On 24/04/2021 10:24, home user wrote: On 4/23/21 8:02 PM, Ed Greshko wrote: (my apologies: I replied to him when I meant to reply to the list) On a F33 system installed from Workstation Live the choices would show as GNOME GNOME Classic GNOME on Xorg With the top being walyand. I don't have

Re: wayward wayland.

On 4/23/21 8:02 PM, Ed Greshko wrote: (my apologies: I replied to him when I meant to reply to the list) On a F33 system installed from Workstation Live the choices would show as GNOME GNOME Classic GNOME on Xorg With the top being walyand. I don't have that top entry. Since my initial inst

Re: on to letsencrypt

On 24/04/2021 10:13, Jack Craig wrote: Maybe send your current named.conf?  attaching isnt happening for some reason so i'l need to inline it. it should be exactly as you sent me, pls yell if not so? Ahhh.  the file you sent me contains exactly what it *should not* contain. The fi

Re: on to letsencrypt

On Fri, Apr 23, 2021 at 6:24 PM Ed Greshko wrote: > On 24/04/2021 08:47, Jack Craig wrote: > > since you've been guiding, i have changed only as guided,... rebooting, > ... > > Well, I don't think this is exactly correct. > > As I noted, the incorrect output started on 4/16 > > Apr 16 11:55:33 w

Re: wayward wayland.

On 24/04/2021 09:46, home user wrote: I'm BAAAaaack! I did not stay at the workstation so I don't know if there were any errors, warnings, or messages.  But I found the gdm login screen displaying.  I'm currently logged in to my Fedora user account in GNOME on Xorg and doing this message in Thun

Re: wayward wayland.

On 4/23/21 6:14 PM, home user wrote: On 4/23/21 5:53 PM, Ed Greshko wrote: On 24/04/2021 07:42, home user wrote: On 4/23/2021 4:34 PM, Ed Greshko wrote: If both of those are "yes", would you do as Tim requested and touch /.autorelabel And then reboot with selinux enabled. With or without r

Re: on to letsencrypt

On 24/04/2021 08:47, Jack Craig wrote: since you've been guiding, i have  changed only as guided,... rebooting, ... Well, I don't think this is exactly correct. As I noted, the incorrect output started on 4/16 Apr 16 11:55:33 ws.linuxlighthouse.com named[49681

Re: on to letsencrypt

*post reboot* *systemctl status named* ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2021-04-23 17:51:14 PDT; 5s ago Process: 3507 ExecStartPre=/bin/ba

Re: on to letsencrypt

since you've been guiding, i have changed only as guided,... rebooting, ... On Fri, Apr 23, 2021 at 5:20 PM Ed Greshko wrote: > On 24/04/2021 08:00, Jack Craig wrote: > > ps -ax | grep named > > 1814955 pts/4S+ 0:00 sudo vi /etc/named.conf > > 1814962 pts/4S+ 0:00 /usr/bin/vim

Re: on to letsencrypt

On 24/04/2021 08:00, Jack Craig wrote: ps -ax | grep named 1814955 pts/4    S+     0:00 sudo vi /etc/named.conf 1814962 pts/4    S+     0:00 /usr/bin/vim /etc/named.conf 1815795 ?        Ssl    0:09 /usr/sbin/named -u named -c /etc/named.conf 1825164 pts/0    S+     0:00 grep --color=auto named [

Re: wayward wayland.

On 4/23/21 5:53 PM, Ed Greshko wrote: On 24/04/2021 07:42, home user wrote: On 4/23/2021 4:34 PM, Ed Greshko wrote: Before that. Can you boot again with selinux disabled?  And, if you can, does gdm start? Is this with or without run-level 3? Either way.  If with 3 you'll have to logi

Re: on to letsencrypt

ps -ax | grep named 1814955 pts/4S+ 0:00 sudo vi /etc/named.conf 1814962 pts/4S+ 0:00 /usr/bin/vim /etc/named.conf 1815795 ?Ssl0:09 /usr/sbin/named -u named -c /etc/named.conf 1825164 pts/0S+ 0:00 grep --color=auto named [root@ws named$ [root@ws named$ ncat -l 10

Re: wayward wayland.

On 24/04/2021 07:42, home user wrote: On 4/23/2021 4:34 PM, Ed Greshko wrote: Before that. Can you boot again with selinux disabled?  And, if you can, does gdm start? Is this with or without run-level 3? Either way.  If with 3 you'll have to login from the text prompt and manually sta

Re: wayward wayland.

On 4/23/2021 4:34 PM, Ed Greshko wrote: Before that. Can you boot again with selinux disabled?  And, if you can, does gdm start? Is this with or without run-level 3? If both of those are "yes", would you do as Tim requested and touch /.autorelabel And then reboot with selinux enabled.

Re: on to letsencrypt

On 24/04/2021 07:13, Ed Greshko wrote: On 24/04/2021 06:40, Jack Craig wrote: netstat -nap | grep named tcp        0      0 127.0.0.1:53        0.0.0.0:*             LISTEN      1815795/named tcp        0      0 127.0.0.1:953         0.0.0.0:*      

Re: machine will not boot after moving root

From what I can see with mine 7 places would be about right. Is that uuid the current one for sda3 or the old uuid for sda5? if it is not the one for sda3 that would be an issue. It kind of looks like the *3a uuid is from the bootcd so that would be wrong, if you run the grub2-mkconfig and the g

Re: on to letsencrypt

On 24/04/2021 06:40, Jack Craig wrote: netstat -nap | grep named tcp        0      0 127.0.0.1:53            0.0.0.0:*             LISTEN      1815795/named tcp        0      0 127.0.0.1:953           0.0.0.0:*             LISTEN      1815795/named t

Re: on to letsencrypt

netstat -nap | grep named tcp0 0 127.0.0.1:530.0.0.0:* LISTEN 1815795/named tcp0 0 127.0.0.1:953 0.0.0.0:* LISTEN 1815795/named tcp6 0 0 ::1:53 :::*LISTEN 18157

Re: machine will not boot after moving root

On Fri, 23 Apr 2021, Roger Heflin wrote: What is the exact error you are getting? Something along the lines of UUID 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a not found. With the hard disk only does it find grub and does it display a menu or drop you to the grub> prompt? I get the grub prompt.

Re: wayward wayland.

On 24/04/2021 02:56, home user wrote: On 04/22/2021 10:34 PM, home user wrote: I'm having to use my old windows-7 partition and system for this message. Rebooting to re-enable SELinux It failed. The last 4 lines of boot messages were: [OK] Started Command Scheduler. Started GNOME Dis

Re: machine will not boot after moving root

What is the exact error you are getting? With the hard disk only does it find grub and does it display a menu or drop you to the grub> prompt? If it displays a menu and you select one of them what does it then do? The uuid will also be on the kernelopts line, but if that was the error you would

Re: on to letsencrypt

On 24/04/2021 02:49, Jack Craig wrote: named now comes up just fine. how do i verify the correct binding by interface has been done? The output of sudo netstat -nap | grep named Also, please provide the output of systemctl --no-pager -l status named -- Remind me to ignore comments which

Re: machine will not boot after moving root

The grub rescue mode finds only (hd0), no paritions at all. On Fri, 23 Apr 2021, Roger Heflin wrote: if you are doing the grub-install/grub2-mkconfig from inside the chroot then it should find the correct uuid (if it works like it should). I did stuff in the chroot, but apparently not well.

Re: machine will not boot after moving root

if you are doing the grub-install/grub2-mkconfig from inside the chroot then it should find the correct uuid (if it works like it should). any of the test commands for grub need to be in the chroot otherwise they will think they are the livecd and not do the right thing or show the right thing as

Re: machine will not boot after moving root

On Fri, 23 Apr 2021, Roger Heflin wrote: I assume it is still not bootable. But if the windows system is gone and you don't care about it, then I would set sda3 to be bootable. Did that. Forgot to mention it. rescue it and then grub-install /dev/sda3 but make sure the newuuid is I've rea

Re: machine will not boot after moving root

I assume it is still not bootable. But if the windows system is gone and you don't care about it, then I would set sda3 to be bootable. rescue it and then grub-install /dev/sda3 but make sure the newuuid is in both fstab (you have done that I think) and matches what is in the /boot/grub2/grub.cfg

Re: machine will not boot after moving root

On Fri, 23 Apr 2021, Roger Heflin wrote: If you used rsync to copy from one disk to the other then the uuid would have changed on the new fs as compared to the old fs. I Yup. Needed to change fstab. typically copy /boot the hard crude way (dd) and copy LVM using the LVM tools (pvmove and fr

Re: wayward wayland.

On 04/22/2021 10:34 PM, home user wrote: I'm having to use my old windows-7 partition and system for this message. Rebooting to re-enable SELinux It failed. The last 4 lines of boot messages were: [OK] Started Command Scheduler. Started GNOME Display Manager... Started Hold until

Re: on to letsencrypt

On Wed, Apr 21, 2021 at 7:08 PM Ed Greshko wrote: > On 22/04/2021 04:47, Jack Craig wrote: > > > > i have zone files for llh & reverse zone > > Oh, BTW, there is very little point in defining > > zone "213.220.108.in-addr.arpa" { > type master; > > You only have been assigned

Re: machine will not boot after moving root

If you used rsync to copy from one disk to the other then the uuid would have changed on the new fs as compared to the old fs. I typically copy /boot the hard crude way (dd) and copy LVM using the LVM tools (pvmove and friends) and in both cases that maintains the same UUID on the old and new. Yo

Re: machine will not boot after moving root

On Fri, 23 Apr 2021, Roger Heflin wrote: I am not sure which it needs. If it did not stop windows from booting then it may have updated the wrong thing. It did stop windows from booting. No menu. Nuthin. -- Michael henne...@web.cs.ndsu.nodak.edu "Sorry but your password must contain an u

Re: machine will not boot after moving root

I have BIOS, not UEFI. On Fri, 23 Apr 2021, Roger Heflin wrote: I am not sure which it needs. If it did not stop windows from booting then it may have updated the wrong thing. Windows will not boot either. Try /dev/sda3 it will either work or give you an error in my experience. From wha

Re: machine will not boot after moving root

On 23/04/2021 00:30, Roger Heflin wrote: Nothing in dracut cares about what partition it is on, That is not completely true. The correct file system kernel modules (or what else is needed to access the root partition) have to be included in the intitrd. If the root file system type is changed

Re: wayward wayland.

On 04/23/2021 7:28 AM, Ed Greshko wrote: On 23/04/2021 21:08, home user wrote: My gut tells me the SELinux re-label either never finishedor never started.  The 4 lines that I put into my most recent post came up in under 2 minutes after the grub menu disappeared, and I never saw any hint of ou

Re: machine will not boot after moving root

I am not sure which it needs. If it did not stop windows from booting then it may have updated the wrong thing. Try /dev/sda3 it will either work or give you an error in my experience. What OS does the main boot loader come from and/or is the machine EFI? Something in the main boot loader wil

Re: wayward wayland.

On 23/04/2021 21:08, home user wrote: My gut tells me the SELinux re-label either never finishedor never started.  The 4 lines that I put into my most recent post came up in under 2 minutes after the grub menu disappeared, and I never saw any hint of output from a SELinux relabelling.  So when I t

Re: wayward wayland.

On Fri, 2021-04-23 at 07:08 -0600, home user wrote: > My gut tells me the SELinux re-label either never finished or never > started. The 4 lines that I put into my most recent post came up in > under 2 minutes after the grub menu disappeared, and I never saw any > hint of output from a SELinux

Re: wayward wayland.

On 04/23/2021 12:19 AM, Joe Zeff wrote: On 4/22/21 11:50 PM, Ed Greshko wrote: As you did before, when you have the kernel selection menu hit e.  Then add a 3 to the end of the linux line.  Ctrl-x to continue to single user mode. No, runlevel 3 boots you into a multi-user system with networki