why does my MX-17's grub say it is MX-18?

[lonesomepoint]

I have been trying MX-17 in the last couple of days, and I only now paid close attention to the GRUB menu. MX-18, it says for my new installation. 18? I was pretty sure I didn't install 18, and I certainly wasn't trying to; but went back and checked the ISO. The file is labeled MX 17. Unless I somehow mislabeled it (changing MX 17 to 18 would be an odd mistake even for me), my MX-17 upgrade has installed a GRUB menu that labels it MX-18. Has anyone else seen this happen? Just an odd curiosity. I guess I can edit the menu...

[Eadwine Rose]

Can you post the quick system info in MX Tools?

[dolphin_oracle]

mx-17 updates to mx-18 automatically, except for the kernel and a few extra packages.

[lonesomepoint]

Oh, I see...it updates to MX-18. Well, that tears it: I don't want to criticize, but I'm not interested in going closer to the bleeding edge. I'll go back to MX-16, unless you have left it easy to turn off the automatic update--I suppose you probably did?

Here is my quick system info, anyway:

System:
Host: T420 Kernel: 4.15.0-1-686-pae i686 bits: 32 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18_386 Continuum March 12 2017
base: Debian GNU/Linux 9 (stretch)
Machine:
Type: Laptop System: LENOVO product: 4177QGU v: ThinkPad T420
serial: <filter>
Mobo: LENOVO model: 4177QGU serial: <filter> UEFI [Legacy]: LENOVO
v: 83ET76WW (1.46 ) date: 07/05/2013
Battery:
ID-1: BAT0 charge: 57.7 Wh condition: 57.8/71.3 Wh (81%)
model: SANYO 42T4763 status: Unknown
CPU:
Topology: Dual Core model: Intel Core i3-2310M bits: 64 type: MT MCP
arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 16746
Speed: 1609 MHz min/max: 800/2100 MHz Core speeds (MHz): 1: 862 2: 947
3: 853 4: 855
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile x86/MMX/SSE2
v: 3.3 Mesa 18.2.6 direct render: Yes
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k4.15.0-1-686-pae
Network:
Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e
v: 3.2.6-k port: 4080 bus ID: 00:19.0
IF: eth0 state: down mac: <filter>
Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
v: kernel port: efa0 bus ID: 03:00.0
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 178.37 GiB used: 66.11 GiB (37.1%)
ID-1: /dev/sda vendor: Hitachi model: HTS725016A9A364 size: 149.05 GiB
ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Fit size: 29.32 GiB
Partition:
ID-1: / size: 14.70 GiB used: 5.00 GiB (34.0%) fs: ext4 dev: /dev/sda7
ID-2: /home size: 11.69 GiB used: 3.53 GiB (30.2%) fs: ext4 dev: /dev/sda3
ID-3: swap-1 size: 5.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5
Sensors:
System Temperatures: cpu: 44.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2181
Repos:
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://la.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
Processes: 204 Uptime: 14m Memory: 7.79 GiB used: 1.02 GiB (13.1%)
Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12

inxi: 3.0.29

[richb]

Please paste code text beween code-tags ( [code] text goes here [/code] ) rather than quote tags. It is the </> at the top of the post block.

MX 18 is still based on Debian Stable, not bleeding edge.

[dolphin_oracle]

nope, its automatic.

although the bulk of the change is the kernel and the new graphics stack. and a new gimp.

we almost called is 17.2

[lonesomepoint]

About this Quick System Update: this is the first time I've used it, and unless I'm wrong, is it just inxi -F? I once asked how to identify my version, and someone told me to use inxi -F. I did that just before I read your responses, because I wanted to make sure this was indeed MX-18; and I notice the inxi -F output appears the same as Quick System Update.

[dolphin_oracle]

About this Quick System Update: this is the first time I've used it, and unless I'm wrong, is it just inxi -F? I once asked how to identify my version, and someone told me to use inxi -F. I did that just before I read your responses, because I wanted to make sure this was indeed MX-18; and I notice the inxi -F output appears the same as Quick System Update.

yeah, its inxi with enabled some of the options. -Fxrz in this case. and it copies the report to your clipboard for pasting into the forum.

[BitJam]

Oh, I see...it updates to MX-18. Well, that tears it: I don't want to criticize, but I'm not interested in going closer to the bleeding edge. I'll go back to MX-16, unless you have left it easy to turn off the automatic update--I suppose you probably did?

The update was automatic because the Debian repo we use did not change. The way MX works is you can safely and stably keep updating your system with updates like what you are doing. IMO, what you have now, MX-17 updated to MX-18 is the most stable and best supported version of MX you can run. It is based on Debian Stable which is considered to be very very stable.

When the Debian Stable repo changes then you cannot upgrade from one version of MX to another. You need to do a re-install. This is explained in MX Repos section of our About Page. We do not make this change for you automatically.

MX is not on the bleeding edge. It is based on Debian Stable (which is the antithesis of bleeding edge). We then curate a collection of packages backported to Debian Stable. We try to give you the best of both worlds. The stability of Debian Stable combined with a hand picked selection of newer packages that have been backported from Debian Testing (and tested, of course). This is what you were running before upgrades brought you up to date with MX-18; it is what you are running now after your system was up to date with MX-18.

Perhaps it was a mistake for us to change the name from MX-17 to MX-18. We did it because an upgraded MX-17 is pretty much the same as an MX-18 system and we thought changing to the MX-18 name would make support easier because we would know better what system we were dealing with. Again, when the Debian Stable repo changes, we don't do this and in order to upgrade you will need to re-install. We do try to support our older systems (like MX-16) with security updates and so on but IMO if you are looking for stability, you are better off with the most recent MX. Unlike what Robert Frost might say, in the computer world, you are usually best off with the road most taken.

[asqwerth]

It's just a name or label, given because a new refreshed iso was released.

It won't matter to existing mx17 users.

If MX hadn't released a new iso at all and just continued to service and maintain mx17 by offering updates and backported programs like Gimp 2.10, and also told existing users there were additional new artwork packages and updated kernels users could install if they wished, that would be mx18 in all but name.