SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It has installed fine, but when i started it, i ran into a problem. The /etc/defaults/grub file in the grub2 slackbuild package was spitting out a "sed" error. so i had to customize the file a little bit.
Edit as follows (in line 8):
From ->
Code:
GRUB_DISTRIBUTOR="$( sed s/Slackware /Slackware-/ /etc/slackware-version )"
I am uploading the package as well as the source/slackbuild .xz file. In case anyone is interested in trying it out.
If it works properly, I will think about posting it to slackbuilds.org.
here is a sample of my /etc/defaults/grub file, if anyone wants to have a look.
Code:
# If you change this file, run grub-mkconfig -o /boot/grub/grub.cfg
# afterwards to update /boot/grub/grub.cfg.
GRUB_DEFAULT="2"
#GRUB_HIDDEN_TIMEOUT="0"
GRUB_HIDDEN_TIMEOUT_QUIET="false"
GRUB_TIMEOUT="15"
GRUB_DISTRIBUTOR="$( cat /etc/slackware-version 2>/dev/null || echo Slackware )"
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_VIDEO_BACKEND="vbe"
GRUB_GFXMODE="1366x768x24"
GRUB_GFXPAYLOAD_LINUX="1366x768x24"
GRUB_TERMINAL_OUTPUT="gfxterm"
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"
# Uncomment to disable generation of recovery mode menu entrys
#GRUB_DISABLE_LINUX_RECOVERY="true"
GRUB_SAVEDEFAULT="false"
GRUB_BACKGROUND="/boot/slackware.jpg"
export GRUB_COLOR_NORMAL="white/black"
export GRUB_COLOR_HIGHLIGHT="red/black"
If you want to build the the Package, you will need the following extra dependencies:
sorry I can't help you on that one, but I just try to hang on with my own incomprehension.
Quote:
Originally Posted by slackd
As the title suggests. I use grub on my laptop. Being spoilt by the grub-customizer package in ubuntu, I wanted the same in Slackware.
What do you mean by "spoilt"? Does it work for you in Ubuntu? - I use Mint for the most part (Mint 12 and 13), which is supposed to be Ubuntu-like, and I'm being fooled by grub-customizer.
Well, I can tune the settings the way I like, and obviously they get stored somewhere, because when I run grub-customizer again at a later time, I see my previous settings again. But they're not reflected by the actual GRUB behavior.
Whether I play around with video resolution, colors, or the GRUB wallpaper, or even the items I wish to be displayed or omitted from the GRUB menu, all that has no effect on the two PCs I used to try grub-customizer. So wherever that program stores its settings - it's not GRUB's configuration file /etc/default/grub.
Maybe grub-customizer only works with GRUB legacy?
@Doc CPU: Changing options in /etc/default/grub will not change the behavior of Grub unless you notify Grub of the changes with
Code:
sudo update-grub
yes, I know that, thanks.
Quote:
Originally Posted by TobiSGD
I would think that a program that is meant to customize Grub does this automatically, but maybe it does not.
The point is that /etc/default/grub remained totally unaffected when I tried to get somewhere with grub-customizer. Neither the file contents nor its timestamp was changed. And yes, of course grub-customizer was executed with root privileges, so it should be able to write to the config file. Obviously it saved its settings somewhere else.
Editing the grub config file manually and issuing "update-grub" after that works fine, and always has.
Sorry about the late reply but I was working on a project presentation for my summer internship
Seems like your question has been partly been answered, but to clarify your second question. Grub Customizer stores its settings in /etc/grub.d/*_*_proxy files.. see the following >
Code:
[02:50:59] root@SamBox:~ # ls -l /etc/grub.d/
total 76
-rwxr-xr-x 1 root root 7617 Jun 28 05:03 00_header
-rwxr-xr-x 1 root root 259 Jun 29 12:03 10_grub-customizer_menu_color_helper
-rwxr-xr-x 1 root root 844 Jun 30 15:44 11_linux_proxy
-rwxr-xr-x 1 root root 203 Jun 30 15:44 12_custom_proxy
-rwxr-xr-x 1 root root 1018 Jun 30 15:44 13_linux_proxy
-rwxr-xr-x 1 root root 10054 Jun 25 23:16 14_linux_xen
-rwxr-xr-x 1 root root 216 Jun 25 23:16 15_custom
-rwxr-xr-x 1 root root 10054 Jun 30 15:33 16_linux_xen
-rwxr-xr-x 1 root root 203 Jun 30 15:44 17_os-prober_proxy
-rwxr-xr-x 1 root root 183 Jun 30 15:44 18_custom_proxy
-rwxr-xr-x 1 root root 216 Jun 30 15:33 19_custom
-rw-r--r-- 1 root root 483 Jun 25 23:16 README
drwxr-xr-x 2 root root 4096 Jun 30 15:44 bin
drwxr-xr-x 2 root root 4096 Jun 30 15:44 proxifiedScripts
Any changes you make in the /etc/default/grub file also remains true and is applied when you run
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.