Is the Grub Customizer a no, no?

[all41]

He that complies against his will
Is of his own opinion still
Which he may adhere to, yet disown,
For reasons to himself best known

[Pjotr]

You follow your own advice, I follow my own understanding, alright?

Right. In my finest Italian: basta!

[Sir Charles]

You follow your own advice, I follow my own understanding, alright?

Right. In my finest Italian: basta!

Buono, ciao ragazzo!

[Sir Charles]

He that complies against his will
Is of his own opinion still
Which he may adhere to, yet disown,
For reasons to himself best known

His reason might be this,
the content of hisproxifiedScripts:

Code: Select all

#! /bin/sh
set -e

# grub-mkconfig helper script.
# Copyright (C) 2006,2007,2008,2009,2010  Free Software Foundation, Inc.
#
# GRUB is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# GRUB is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with GRUB.  If not, see <http://www.gnu.org/licenses/>.

prefix="/usr"
exec_prefix="/usr"
datarootdir="/usr/share"
ubuntu_recovery="1"
quiet_boot="1"
quick_boot="1"
gfxpayload_dynamic="1"
vt_handoff="1"

. "${datarootdir}/grub/grub-mkconfig_lib"

export TEXTDOMAIN=grub
export TEXTDOMAINDIR="${datarootdir}/locale"

CLASS="--class gnu-linux --class gnu --class os"
SUPPORTED_INITS="sysvinit:/lib/sysvinit/init systemd:/lib/systemd/systemd upstart:/sbin/upstart"

if [ "x${GRUB_DISTRIBUTOR}" = "x" ] ; then
  OS=GNU/Linux
else
  case ${GRUB_DISTRIBUTOR} in
    Ubuntu|Kubuntu)
      OS=`grep GRUB_TITLE /etc/linuxmint/info | awk -F = '{print $2}'`
      ;;
    *)
      OS="${GRUB_DISTRIBUTOR} GNU/Linux"
      ;;
  esac
  CLASS="--class $(echo ${GRUB_DISTRIBUTOR} | tr 'A-Z' 'a-z' | cut -d' ' -f1|LC_ALL=C sed 's,[^[:alnum:]_],_,g') ${CLASS}"
fi

# loop-AES arranges things so that /dev/loop/X can be our root device, but
# the initrds that Linux uses don't like that.
case ${GRUB_DEVICE} in
  /dev/loop/*|/dev/loop[0-9])
    GRUB_DEVICE=`losetup ${GRUB_DEVICE} | sed -e "s/^[^(]*(\([^)]\+\)).*/\1/"`
    # We can't cope with devices loop-mounted from files here.
    case ${GRUB_DEVICE} in
      /dev/*) ;;
      *) exit 0 ;;
    esac
  ;;
esac

if [ "x${GRUB_DEVICE_UUID}" = "x" ] || [ "x${GRUB_DISABLE_LINUX_UUID}" = "xtrue" ] \
    || ! test -e "/dev/disk/by-uuid/${GRUB_DEVICE_UUID}" \
    || uses_abstraction "${GRUB_DEVICE}" lvm; then
  LINUX_ROOT_DEVICE=${GRUB_DEVICE}
else
  LINUX_ROOT_DEVICE=UUID=${GRUB_DEVICE_UUID}
fi

case x"$GRUB_FS" in
    xbtrfs)
	rootsubvol="`make_system_path_relative_to_its_root /`"
	rootsubvol="${rootsubvol#/}"
	if [ "x${rootsubvol}" != x ]; then
	    GRUB_CMDLINE_LINUX="rootflags=subvol=${rootsubvol} ${GRUB_CMDLINE_LINUX}"
	fi;;
    xzfs)
	rpool=`${grub_probe} --device ${GRUB_DEVICE} --target=fs_label 2>/dev/null || true`
	bootfs="`make_system_path_relative_to_its_root / | sed -e "s,@$,,"`"
	LINUX_ROOT_DEVICE="ZFS=${rpool}${bootfs}"
	;;
esac

title_correction_code=

if [ -x /lib/recovery-mode/recovery-menu ]; then
    GRUB_CMDLINE_LINUX_RECOVERY=recovery
else
    GRUB_CMDLINE_LINUX_RECOVERY=single
fi
if [ "$ubuntu_recovery" = 1 ]; then
    GRUB_CMDLINE_LINUX_RECOVERY="$GRUB_CMDLINE_LINUX_RECOVERY nomodeset"
fi

if [ "$vt_handoff" = 1 ]; then
  for word in $GRUB_CMDLINE_LINUX_DEFAULT; do
    if [ "$word" = splash ]; then
      GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT \$vt_handoff"
    fi
  done
fi

linux_entry ()
{
  os="$1"
  version="$2"
  type="$3"
  args="$4"

  if [ -z "$boot_device_id" ]; then
      boot_device_id="$(grub_get_device_id "${GRUB_DEVICE}")"
  fi
  if [ x$type != xsimple ] ; then
      case $type in
	  recovery)
	      title="$(gettext_printf "%s, with Linux %s (%s)" "${os}" "${version}" "$(gettext "${GRUB_RECOVERY_TITLE}")")" ;;
	  init-*)
	      title="$(gettext_printf "%s, with Linux %s (%s)" "${os}" "${version}" "${type#init-}")" ;;
	  *)
	      title="$(gettext_printf "%s, with Linux %s" "${os}" "${version}")" ;;
      esac
      if [ x"$title" = x"$GRUB_ACTUAL_DEFAULT" ] || [ x"Previous Linux versions>$title" = x"$GRUB_ACTUAL_DEFAULT" ]; then
	  replacement_title="$(echo "Advanced options for ${OS}" | sed 's,>,>>,g')>$(echo "$title" | sed 's,>,>>,g')"
	  quoted="$(echo "$GRUB_ACTUAL_DEFAULT" | grub_quote)"
	  title_correction_code="${title_correction_code}if [ \"x\$default\" = '$quoted' ]; then default='$(echo "$replacement_title" | grub_quote)'; fi;"
	  grub_warn "$(gettext_printf "Please don't use old title \`%s' for GRUB_DEFAULT, use \`%s' (for versions before 2.00) or \`%s' (for 2.00 or later)" "$GRUB_ACTUAL_DEFAULT" "$replacement_title" "gnulinux-advanced-$boot_device_id>gnulinux-$version-$type-$boot_device_id")"
      fi
      echo "menuentry '$(echo "$title" | grub_quote)' ${CLASS} \$menuentry_id_option 'gnulinux-$version-$type-$boot_device_id' {" | sed "s/^/$submenu_indentation/"
  else
      echo "menuentry '$(echo "$os" | grub_quote)' ${CLASS} \$menuentry_id_option 'gnulinux-simple-$boot_device_id' {" | sed "s/^/$submenu_indentation/"
  fi      
  if [ "$quick_boot" = 1 ]; then
      echo "	recordfail" | sed "s/^/$submenu_indentation/"
  fi
  if [ x$type != xrecovery ] ; then
      save_default_entry | grub_add_tab
  fi

  # Use ELILO's generic "efifb" when it's known to be available.
  # FIXME: We need an interface to select vesafb in case efifb can't be used.
  if [ "x$GRUB_GFXPAYLOAD_LINUX" = x ]; then
      echo "	load_video" | sed "s/^/$submenu_indentation/"
  else
      if [ "x$GRUB_GFXPAYLOAD_LINUX" != xtext ]; then
	  echo "	load_video" | sed "s/^/$submenu_indentation/"
      fi
  fi
  if ([ "$ubuntu_recovery" = 0 ] || [ x$type != xrecovery ]) && \
     ([ "x$GRUB_GFXPAYLOAD_LINUX" != x ] || [ "$gfxpayload_dynamic" = 1 ]); then
      echo "	gfxmode \$linux_gfx_mode" | sed "s/^/$submenu_indentation/"
  fi

  echo "	insmod gzio" | sed "s/^/$submenu_indentation/"
  echo "	if [ x\$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi" | sed "s/^/$submenu_indentation/"

  if [ x$dirname = x/ ]; then
    if [ -z "${prepare_root_cache}" ]; then
      prepare_root_cache="$(prepare_grub_to_access_device ${GRUB_DEVICE} | grub_add_tab)"
    fi
    printf '%s\n' "${prepare_root_cache}" | sed "s/^/$submenu_indentation/"
  else
    if [ -z "${prepare_boot_cache}" ]; then
      prepare_boot_cache="$(prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | grub_add_tab)"
    fi
    printf '%s\n' "${prepare_boot_cache}" | sed "s/^/$submenu_indentation/"
  fi
  if [ x"$quiet_boot" = x0 ] || [ x"$type" != xsimple ]; then
    message="$(gettext_printf "Loading Linux %s ..." ${version})"
    sed "s/^/$submenu_indentation/" << EOF
	echo	'$(echo "$message" | grub_quote)'
EOF
  fi
  if test -d /sys/firmware/efi && test -e "${linux}.efi.signed"; then
    sed "s/^/$submenu_indentation/" << EOF
	linux	${rel_dirname}/${basename}.efi.signed root=${linux_root_device_thisversion} ro ${args}
EOF
  else
    if [ x"$GRUB_FORCE_PARTUUID" = x ]; then
        sed "s/^/$submenu_indentation/" << EOF
        linux	${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${args}
EOF
    else
        sed "s/^/$submenu_indentation/" << EOF
        linux	${rel_dirname}/${basename} root=PARTUUID=${GRUB_FORCE_PARTUUID} ro ${args}
EOF
    fi
  fi
  if test -n "${initrd}" && [ x"$GRUB_DISABLE_INITRD" != xtrue ]; then
    # TRANSLATORS: ramdisk isn't identifier. Should be translated.
    if [ x"$quiet_boot" = x0 ] || [ x"$type" != xsimple ]; then
      message="$(gettext_printf "Loading initial ramdisk ...")"
      sed "s/^/$submenu_indentation/" << EOF
	echo	'$(echo "$message" | grub_quote)'
EOF
    fi
    sed "s/^/$submenu_indentation/" << EOF
	initrd	${rel_dirname}/${initrd}
EOF
  fi
  sed "s/^/$submenu_indentation/" << EOF
}
EOF
}

machine=`uname -m`
case "x$machine" in
    xi?86 | xx86_64)
	list=`for i in /boot/vmlinuz-* /vmlinuz-* /boot/kernel-* ; do
                  if grub_file_is_not_garbage "$i" ; then echo -n "$i " ; fi
              done` ;;
    *) 
	list=`for i in /boot/vmlinuz-* /boot/vmlinux-* /vmlinuz-* /vmlinux-* /boot/kernel-* ; do
                  if grub_file_is_not_garbage "$i" ; then echo -n "$i " ; fi
	     done` ;;
esac

case "$machine" in
    i?86) GENKERNEL_ARCH="x86" ;;
    mips|mips64) GENKERNEL_ARCH="mips" ;;
    mipsel|mips64el) GENKERNEL_ARCH="mipsel" ;;
    arm*) GENKERNEL_ARCH="arm" ;;
    *) GENKERNEL_ARCH="$machine" ;;
esac

prepare_boot_cache=
prepare_root_cache=
boot_device_id=
title_correction_code=

cat << 'EOF'
function gfxmode {
	set gfxpayload="${1}"
EOF
if [ "$vt_handoff" = 1 ]; then
  cat << 'EOF'
	if [ "${1}" = "keep" ]; then
		set vt_handoff=vt.handoff=7
	else
		set vt_handoff=
	fi
EOF
fi
cat << EOF
}
EOF

# Use ELILO's generic "efifb" when it's known to be available.
# FIXME: We need an interface to select vesafb in case efifb can't be used.
if [ "x$GRUB_GFXPAYLOAD_LINUX" != x ] || [ "$gfxpayload_dynamic" = 0 ]; then
  echo "set linux_gfx_mode=$GRUB_GFXPAYLOAD_LINUX"
else
  cat << EOF
if [ "\${recordfail}" != 1 ]; then
  if [ -e \${prefix}/gfxblacklist.txt ]; then
    if hwmatch \${prefix}/gfxblacklist.txt 3; then
      if [ \${match} = 0 ]; then
        set linux_gfx_mode=keep
      else
        set linux_gfx_mode=text
      fi
    else
      set linux_gfx_mode=text
    fi
  else
    set linux_gfx_mode=keep
  fi
else
  set linux_gfx_mode=text
fi
EOF
fi
cat << EOF
export linux_gfx_mode
EOF

# Extra indentation to add to menu entries in a submenu. We're not in a submenu
# yet, so it's empty. In a submenu it will be equal to '\t' (one tab).
submenu_indentation=""

is_top_level=true
while [ "x$list" != "x" ] ; do
  linux=`version_find_latest $list`
  case $linux in
    *.efi.signed)
      # We handle these in linux_entry.
      list=`echo $list | tr ' ' '\n' | grep -vx $linux | tr '\n' ' '`
      continue
      ;;
  esac
  gettext_printf "Found linux image: %s\n" "$linux" >&2
  basename=`basename $linux`
  dirname=`dirname $linux`
  rel_dirname=`make_system_path_relative_to_its_root $dirname`
  version=`echo $basename | sed -e "s,^[^0-9]*-,,g"`
  alt_version=`echo $version | sed -e "s,\.old$,,g"`
  linux_root_device_thisversion="${LINUX_ROOT_DEVICE}"

  initrd=
  for i in "initrd.img-${version}" "initrd-${version}.img" "initrd-${version}.gz" \
	   "initrd-${version}" "initramfs-${version}.img" \
	   "initrd.img-${alt_version}" "initrd-${alt_version}.img" \
	   "initrd-${alt_version}" "initramfs-${alt_version}.img" \
	   "initramfs-genkernel-${version}" \
	   "initramfs-genkernel-${alt_version}" \
	   "initramfs-genkernel-${GENKERNEL_ARCH}-${version}" \
	   "initramfs-genkernel-${GENKERNEL_ARCH}-${alt_version}"; do
    if test -e "${dirname}/${i}" ; then
      initrd="$i"
      break
    fi
  done

  config=
  for i in "${dirname}/config-${version}" "${dirname}/config-${alt_version}" "/etc/kernels/kernel-config-${version}" ; do
    if test -e "${i}" ; then
      config="${i}"
      break
    fi
  done

  initramfs=
  if test -n "${config}" ; then
      initramfs=`grep CONFIG_INITRAMFS_SOURCE= "${config}" | cut -f2 -d= | tr -d \"`
  fi

  if test -n "${initrd}" ; then
    gettext_printf "Found initrd image: %s\n" "${dirname}/${initrd}" >&2
  elif test -z "${initramfs}" ; then
    # "UUID=" and "ZFS=" magic is parsed by initrd or initramfs.  Since there's
    # no initrd or builtin initramfs, it can't work here.
    linux_root_device_thisversion=${GRUB_DEVICE}
  fi

  if [ "x$is_top_level" = xtrue ] && [ "x${GRUB_DISABLE_SUBMENU}" != xy ]; then
    linux_entry "${OS}" "${version}" simple \
    "${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_LINUX_DEFAULT}"

    submenu_indentation="$grub_tab"
    
    if [ -z "$boot_device_id" ]; then
	boot_device_id="$(grub_get_device_id "${GRUB_DEVICE}")"
    fi
    # TRANSLATORS: %s is replaced with an OS name
    echo "submenu '$(gettext_printf "Advanced options for %s" "${OS}" | grub_quote)' \$menuentry_id_option 'gnulinux-advanced-$boot_device_id' {"
    is_top_level=false
  fi

  linux_entry "${OS}" "${version}" advanced \
              "${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_LINUX_DEFAULT}"
  for supported_init in ${SUPPORTED_INITS}; do
    init_path="${supported_init#*:}"
    if [ -x "${init_path}" ] && [ "$(readlink -f /sbin/init)" != "${init_path}" ]; then
      linux_entry "${OS}" "${version}" "init-${supported_init%%:*}" \
		  "${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_LINUX_DEFAULT} init=${init_path}"
    fi
  done
  if [ "x${GRUB_DISABLE_RECOVERY}" != "xtrue" ]; then
    linux_entry "${OS}" "${version}" recovery \
                "${GRUB_CMDLINE_LINUX_RECOVERY} ${GRUB_CMDLINE_LINUX}"
  fi

  list=`echo $list | tr ' ' '\n' | fgrep -vx "$linux" | tr '\n' ' '`
done

# If at least one kernel was found, then we need to
# add a closing '}' for the submenu command.
if [ x"$is_top_level" != xtrue ]; then
  echo '}'
fi

echo "$title_correction_code"

[Sir Charles]

Admission of missunderstanding regarding the location of "proxified" scripts and the original non-proxified ones

In one of previous posts where I reproduced large part of Daniel Richter's description of Grub Customizer
viewtopic.php?f=90&t=261622&start=100

it reads:

After all, if my understanding of the whole thing is correct, they are what the are, proxies, the original scripts are intact in /etc/grub.d otherwise it would have been impossible for GC to revert the changes.

while it should read:

After all, if my understanding of the whole thing is correct, they are what the are, proxies, the original scripts are intact in
/etc/grub.d/backup/etc_grub_d/ otherwise it would have been impossible for GC to revert the changes.

[Pjotr]

Today, I've written a detailed analysis of my test with Grub Customizer, with five new and (hopefully) clarifying screenshots:
https://sites.google.com/site/easylinuxtipsproject/gc

Spoiler: don't use Grub Customizer.

[sdibaja]

@Pjotr
Good article, thanks.
-
your page on fixing Grub appears to be pretty comprehensive, I will keep it for reference.
https://sites.google.com/site/easylinuxtipsproject/grub
perhaps it will help me get my BSD recognized in Grub.

[Pjotr]

@Pjotr
Good article, thanks.
-
your page on fixing Grub appears to be pretty comprehensive, I will keep it for reference.
https://sites.google.com/site/easylinuxtipsproject/grub
perhaps it will help me get my BSD recognized in Grub.

You're welcome!

Years ago, when I was testing PC-BSD, I added this in /etc/grub.d/40_custom:

Code: Select all

menuentry "PC-BSD" {
set root='(hd0,3)'
chainloader +1
} 

And then of course sudo update-grub.

If you change hd0,3 into what fits your situation, you might be able to get your BSD into the Grub menu after all....

Back on topic: just to make this clear, I mean no disrespect towards Daniel Richter, who is the author of Grub Customizer. I have no doubt that he's a highly skilled programmer and very good at his job. It's just that I think that GC is based on a fundamentally wrong technical concept.

[Sir Charles]

It's just that I think that GC is based on a fundamentally wrong technical concept.

That's what you think.

And if you truely care for the wellbeing of MInt users, please stop calling them "victims" as you do in your article. The Linux world does not need a "Saviour".

And expressing yourself in such an alarmist and condescending way, shows only your disregard for those you are trying to save.
This might look personal. Be my guest, take it like that since I for one don't like to be called "victim" and of what a tool called Grub Customizer. I don't think anybody does.

I think anyone who is interested of learning the working of GC should use it. I have used it, and have observed what it does, what changes it makes until finally, I learned how to do those changes myself without GC. And for that learning experience I am indebted utterly to it's maker Daniel Richter.

Anyone visiting this forums knows that any Linux system can break anytime with an innocent looking package update. That a Linux system can be broken right out of the box. Just look at all these threads, inundated with things that were wrong right from the start,or things that went wrong for some reason or other.

I would say, if you can afford a partition or two to dedicate to experimenting, just do it! Keep one system safe and stable, learn how to repair your bootloader so you won't be locked out then start making and breaking to your heart desire unless you want the "Good Advice" come down to you from "Above".

So enjoy your setup today, because tomorrow when you push that power button, you might see your surprised in many cases terrified face in a black screen looking back at you. No matter how much "silly bling-bling" according to some people here, you have put on your Grub, remember, you are just a victim. Maybe of a tool called Grub Customizer. Or you are just victimized by reading an article treating you as one.

[MrEen]

This is the Newbie Questions section of the forum and the topic was started by a newbie. I think the advice from the very experienced users for a newbie to avoid GC is VERY rational. Decreasing the chances of needing to reinstall the OS most likely decreases the chances the newbie gives up on Linux in frustration.

[Pjotr]

@Marziano: I have better ways to spend my time than to address ignorant annoying babble, mate. Have fun.

[Sir Charles]

This is the Newbie Questions section of the forum and the topic was started by a newbie. I think the advice from the very experienced users for a newbie to avoid GC is VERY rational. Decreasing the chances of needing to reinstall the OS most likely decreases the chances the newbie gives up on Linux in frustration.

You are absolutely right. i apologize for my part of the whole thing.

[daniel]

Seems like some things were understood wrong:
1) the contents of "proxifiedScripts" are not containing any contents of grub customizer. These are the original scripts, moved from /etc/grub.d (for example: /etc/grub.d/10_linux becomes /etc/grub.d/proxifiedScripts/linux after modifying any menuentry of this script).
2) the revert button of grub customizer isn't using the backup folder. The backup folder is just there for the user to restore it easier. Grub customizer loads all grub scripts (proxifiedScripts as well as scripts on /etc/grub.d) on startup and this way it knows the default menuentries of each script. Generally the revert button does nothing more than the user can do manually by using the up/down/rename/remove button - it's just a comfort function. So if you swap a linux kernel entry, you'll get the proxifiedScripts. If you swap it back, then it's moved back to /etc/grub.d/10_linux and the proxifiedScripts folder is completely removed.

If you have better solutions... then tell me. But no, I won't write to /boot/grub/grub.cfg directly or putting everything into /etc/grub.d/40_custom. These are the *really* bad ways because they are either temporary changes that have to be repeated every time you update the system or you lose all the dynamic functionality of grub (means: new kernels wont be inserted anymore, for example).

The discussion about needfulness is useless. It's like discussing about taste...

[Sir Charles]

Daniel! your presence is very much appreciated. Thank you for stepping by. I thought last time you were here you clarified a whole lot of things.

Misunderstanding on my part seems to be the cold,crude fact of the matter. What was missing the whole time here was an explanation as to what's going on with and in GC. And nobody but you has provided that kind of explanation here so far.

[G-Mo]

This has been an interesting post. I learned considerably about the Grub process. I made a large mistake reading backup folder mod dates where Daniel had to recheck the function. Sorry about that. The /etc/grub.d/ directory does indeed hold the original files upon installation. Making changes after the install did not overwrite them as I suggested. Basically I forgot how currently that I had installed GC thinking the backup files were getting overwritten during use. Thus, the current dates. Nope, those were the original install dated files (1/10/18) and when GC changes are made, they remain 1/10.

I started into Mint reading tips and tricks guides like this one: https://www.techsupportalert.com/conten ... dition.htm This page recommends the GC installation and ease of use. I still think it's valid and I have no intent of dropping it and will install it on the new SSD system. I think true admins with enterprise setups may have concerns but if asked, I remain a fan of the utility.

Thanks to Daniel for engaging, and sorry to others who I may have further confused. New guys - Hate 'em!

[anobody]

I have used it for a couple of years and the only problem I have had is changing the boot wallpaper. I have 2 drives with 4 OS's dual boots on them and it list them all for me to make my selection. It is installed on only my SSD mint and Win10 drive and the other HD has 2 different Linux OS's. I make sure that I have it to boot to the last boot in order to not have to wait on Windows to update. Hope this helps

[tovian]

I think true admins with enterprise setups may have concerns but if asked, I remain a fan of the utility.

+1

This thread has really been more of a "Much Ado About Nothing".
The more you fool around with sensitive/critical elements of an operating system the more likely you are to bork something... especially if you don't know what you are doing and are not covering your tracks (backing up). That's nothing new, and it doesn't matter if you use an easy utility or your bare-metal Hex-editor.

This thread has additional value as it may provide some insight into who is truly technically capable versus who is merely a mouthpiece. I try to steer clear of people with closed minds who think they ALREADY have all the answers. That's NOT a recommendation... it's just my very personal opinion.

[Sir Charles]

This thread has really been more of a "Much Ado About Nothing".

Maybe, maybe not. Personally, I realized how wrong I were about, not the functionalities of Grub Customizer, but it's functioning. Thanks to the input from Daniel Richter, the developer of the Grub Customizer, I for one have a much better understanding of how it functions now.

Not knowing and asking is not dumb. Not knowing and not asking is. But when you ask relevant and specific questions and you are given irrelevant, nonsensical answers, that's just ridiculous.

[Pjotr]

But when you ask relevant and specific questions and you are given irrelevant, nonsensical answers, that's just ridiculous.

May I ask which answers in this thread you consider to be both irrelevant and nonsensical?

[Sir Charles]

All that won't explain HOW the tool does what it does.