Responses to Coming changes in impending MX 25 release.

[siamhie]

Thanks Siamhie, post 173 holds a more extensive explanation as to why.

(which I don't get, but that is fine, I got my answer to 'where is it' )

That's what I get for living on the West Coast US. Comments are posted while I'm still... ...

[Eadwine Rose]

*chuckles* If you'd used the unread posts link on the top right you would have seen them.

[siamhie]

*chuckles* If you'd used the unread posts link on the top right you would have seen them.

I probably should start doing that instead of diving into the Newest Posts section when I get on the forums.


Just an FYI for everyone. Debian 13 is systemd and I'm not sure when that happened (I rarely keep up).
I knew that their Gnome was systemd in 12 when I was troubleshooting audio issues back then in MX.


Debian 13 XFCE


Debian 13 KDE

[bradhamilton]

Thanks for the link - when I went there, this caught my eye:

"systemd hangs on startup or shutdown
Sometimes it is necessary to investigate why systemd hangs on startup or on reboot/shutdown."

Huh????? Do the Debian devs consider this to be a standard "feature"? If so, then that's another data point *against* using systemD - if it was a bug, or even a "feature", it should have been either fixed or "enhanced" - by removing the "feature".

: - )

It is software. Software has bugs. Software can do funny things. There are talking points for and against, and the Debian wiki also contains this article: https://wiki.debian.org/Debate/initsystem/systemd

I've decided to bite the bullet, and boot KDE MX23 with systemD, as an experiment - unless something(s) go terribly awry, I'll stick with it until the first point release of MX25.

[alcornoqui]

Congrats to the team and community!

After reading the thread I have a few questions on upgrading. First, my recollection, mostly from asqwerth:

- Besides all the reassurances the others have given you, my advice would be that if and when you want to move to MX25, install it FRESH and get a properly set up default system. Don't try to use the unsupported, warning-laden way of carrying out an in-place upgrade of your existing MX23 install to turn it into MX25.

- The installer allows you to do a fresh install of MX25 with the option of preserving your /home

- Before you do your fresh install, use the MX tool called "User Installed Programs" to save a list of the programs in MX23 that you installed yourself (ie, they didn't come with as default with MX23). Save that uip file elsewhere.

- After you have done your fresh install of MX25 preserving home, you can open up User Installed Programs in your new MX25 install, feed it that saved uip file, and it will help you install with a single command most of what you had installed in MX23.

- Exceptions:
1.flatpaks [anyway, once you are in MX25, there could be a newer native version of the program that works well for you so you might not need the flatpak version anymore ]
2. native programs from MX23/Debian12 repos that are no longer found in the MX25/Debian 13 repos
3. things you manually installed from external deb files.

And my questions:

I have 7 MX-23 machines (not all mine, some of relatives), and I plan to upgrade them gradually. Until now I've done it without reinstalling (with perfect results, btw), but this time I want to install fresh, as adviced.

Regarding UEFI vs BIOS, does the installer offer a choice or do we have to do some previous partitioning in a machine that is UEFI capable but is currently partitioned/formatted for BIOS? I seem to remember some hand-holding by the installer but I'm not sure. What I know is some of my machines boot to UEFI and some don't, and again, I'd like to make sure to select UEFI if possible this time.

I've checked https://mxlinux.org/wiki/system/uefi/ and the manual but still not fully sure...

Now, some of the machines don't have separate /home partition: Will the "Preserve /home" option work in that case? If not, what would you recommend doing?

And just to be sure, is it expected that most stuff works after a fresh install preserving /home or problems are frequent? Which are the most frequent?

Thanks for the great work, awesome distro!

[siamhie]

I've decided to bite the bullet, and boot KDE MX23 with systemD, as an experiment - unless something(s) go terribly awry, I'll stick with it until the first point release of MX25.

I commented (page 15 post #147) that I've been booting systemd with no issues. My media server requires systemd.

All the desktop ISO's (MX-19,MX-21,MX-23) I install (XFCE, KDE and fluxbox) are booted to systemd and I've never run into an issue with the preinstalled software.

[bradhamilton]

I've decided to bite the bullet, and boot KDE MX23 with systemD, as an experiment - unless something(s) go terribly awry, I'll stick with it until the first point release of MX25.

I commented (page 15 post #147) that I've been booting systemd with no issues. My media server requires systemd.

All the desktop ISO's (MX-19,MX-21,MX-23) I install (XFCE, KDE and fluxbox) are booted to systemd and I've never run into an issue with the preinstalled software.

Great! Your previous post(s) as well as @AK-47's, have prompted me to take the plunge. My experiment will probably last for a few months (waiting for the first MX25 point release), or "deal-breakers", whichever comes first; but I wonder if the "shim" is currently "protecting" me from issues.

I don't do anything really fancy, so I don't expect issues - wait and see...

[ghunter]

SNIP

Code: Select all

tools:apt,apt-get,synaptic

drifting off topic ...I know but I am surprised you do not like nala as the faster package tool?

Code: Select all

inxi -SIa
System:
  Host: box Kernel: 6.14.10-2-liquorix-amd64 arch: x86_64 bits: 64
    compiler: gcc v: 12.2.0 parameters: audit=0 intel_pstate=disable
    amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.14.10-2-liquorix-amd64
    root=/dev/sda1 ro quiet
  Desktop: IceWM v: 3.3.1 vt: 7 dm: LightDM v: 1.32.0
    Distro: MX-23.6_fluxbox_x64 Libretto October 15 2023 base: Debian GNU/Linux
    12 (bookworm)
Info:
  Processes: 302 Uptime: 17m wakeups: 1 Memory: 61.71 GiB
  used: 1.52 GiB (2.5%) Init: SysVinit v: 3.06 runlevel: 5 default: graphical
  tool: systemctl Compilers: gcc: 12.2.0 alt: 12 Packages: pm: dpkg pkgs: 1668
  libs: 898 tools: apt,apt-get,nala pm: rpm pkgs: 0 Shell: Bash v: 5.2.15
  running-in: lxterminal inxi: 3.3.26

[siamhie]

SNIP

Code: Select all

tools:apt,apt-get,synaptic

drifting off topic ...I know but I am surprised you do not like nala as the faster package tool?

I had literally installed it 5 minutes before the screenshot and wanted to show the init section. I hadn't gotten around to setting it up.

[daemonspudguy]

Is the way systemd-shim worked literally impossible to get working with cgroups v2 or would it require more effort than the maintainer was willing to put in? I'm guessing the former but I just want to know for sure.