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.
Seriously, orbea is correct that trying to get Void's grub to work with a non-Void kernel is still a Void issue. We don't know what software is included with Void (unless some of us have run it, which I haven't) and it'd be best to get OS specific instructions on how to make Void's grub properly recognize and boot another kernel. You wouldn't go to a Windows forum trying to get Windows to be recognized in Void's bootloader, would you?
I really don't see why this is an issue at all period.
anybody has two or more Linux (and windows) installed on a HARD DRIVE, one only one Linux can be used to run update-grub, through update-grub it gets the default kernel that every other system uses to boot its own system. regardless of how many different kernels are in /boot.
that is obvious that something some where within each Linux it has to have something to tell grub which is the default kernel to use because I have more then one kernel in both Linux Installs and that grub is picking them up and when I boot into a different Linux it does not get confused as to which kernel to use.
OR
when that Linux is booted then within that system it has to have somewhere to tell it to use only one kernel, that would be it's the default kernel to use out of all of the kernels within /boot
because having more then one kernel in /boot and some part of each system has to have some how to know which kernal to get out of all of the kernels in /boot.
either way each system has to have a way to tell itself which Kernel in /boot is the default kernel to use, out of all of the kernels within /boot
so therefore how is it strictly a VOID linux problem only based on the fact that I am using that ones grub to boot off of?
Quote:
As for building a kernel, it is as simple as:
Code:
make bzImage modules
make modules_install
I just missed that make modules_install part, and all of that other part in that page is just ????? I have no idea what for
Quote:
Code:
cp arch/x86_64/boot/bzImage /boot/vmlinuz-4.8.6
that part is done.
Quote:
If you went with a generic kernel, you would need to then generate an initrd based off the output of /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.8.6. Then updating your bootloader to see the new kernel (and possibly initrd). As said above, since you aren't using Slackware's bootloader, it would be best to ask in the Void forum how to update the Slackware entry to use a new kernel in the Void bootloader.
RIGHT THERE you hit the nail on the head: -> right there -> generate a initrd
that is where i got my error at then posted this, just adding the other stuff to try and kill more then one bird at a time. thinking it all has to be tied together some how to get slack to use that new kernal so I could test it out, seeings how i cannot get LILO to do what it is suppose to be able to multi-boot.
when I ran this
Quote:
mkinitrd -c -k 4.8.3 -m ext4
that is when it bitched at me about noting in /lib/modules/ with 4.8.3
that is when I looked in it to see what is in it and seen all of this
then look in the source for 4.8.3 and seen it did not match ... so ooooooooo going back to the start again ... like a dog chasing his tail... your turn....
AND I cannot get into Slack for at least another aprox one hour to run that make modules_install to see if that will fix that last part in order to run mkinitrd
I would suggest to just use lilo, seriously if you want help configuring grub in void linux ask a void linux specific place. This is not a slackware problem.
what, this you mean THIS SUGGESTION????? USE LILO
well tell me then how do I add an different system three more to be exact for lilo to boot all of them???????
No, in your huge post about getting lilo to work in Slackware.
Quote:
Originally Posted by BW-userx
I really don't see why this is an issue at all period.
anybody has two or more Linux (and windows) installed on a HARD DRIVE, one only one Linux can be used to run update-grub, through update-grub it gets the default kernel that every other system uses to boot its own system. regardless of how many different kernels are in /boot.
that is obvious that something some where within each Linux it has to have something to tell grub which is the default kernel to use because I have more then one kernel in both Linux Installs and that grub is picking them up and when I boot into a different Linux it does not get confused as to which kernel to use.
True. Only one bootloader can be used unless you intend to chainload (which I had also mentioned in the lilo thread, but you never commented on it, so I assumed you didn't want to use it). But, just as you wouldn't go to a Windows forum when your Void's grub won't boot Windows, you shouldn't come to a Slackware forum and expect that we know what's going on with Void's grub. That grub is likely a different version than Slackware's and/or possibly has patches or additional software that Slackware doesn't have (I remember you complaining in a previous bootloader thread that Slackware's grub didn't contain some grub command/script you expected it to have).
Quote:
Originally Posted by BW-userx
when that Linux is booted then within that system it has to have somewhere to tell it to use only one kernel, that would be it's the default kernel to use out of all of the kernels within /boot
because having more then one kernel in /boot and some part of each system has to have some how to know which kernal to get out of all of the kernels in /boot.
either way each system has to have a way to tell itself which Kernel in /boot is the default kernel to use, out of all of the kernels within /boot
Any Linux bootloader should be able to support multiple kernels for one distro.
Quote:
Originally Posted by BW-userx
so therefore how is it strictly a VOID linux problem only based on the fact that I am using that ones grub to boot off of?
Because Void's grub is not necessarily the same grub that Slackware uses. As I said above, it could be a different version or it could contain patches or scripts that Slackware's doesn't.
Quote:
Originally Posted by BW-userx
I just missed that make modules_install part, and all of that other part in that page is just ????? I have no idea what for
that part is done.
Well, the make modules_install part was even in the section you copied But we do all miss the obvious sometimes. I've definitely had those moments before.
Quote:
Originally Posted by BW-userx
RIGHT THERE you hit the nail on the head: -> right there -> generate a initrd
An initrd should only be needed if you're basing your kernel off a generic config. If you compile all the needed drivers into the kernel instead of modules, no initrd is needed (except for a few exceptions, like using lvm or encryption).
Quote:
Originally Posted by BW-userx
seeings how i cannot get LILO to do what it is suppose to be able to multi-boot.
lilo is more than capable of multi-boot. It just doesn't have utilities like grub to make things easier (supposedly... but I haven't used grub enough to know). lilo requires you to edit a conf file and if it is wrong, it can lead you to failed boots. But, when it's right, it works beautifully.
Quote:
Originally Posted by BW-userx
when I ran this that is when it bitched at me about noting in /lib/modules/ with 4.8.3
that is when I looked in it to see what is in it and seen all of this
then look in the source for 4.8.3 and seen it did not match ... so ooooooooo going back to the start again ... like a dog chasing his tail... your turn....
AND I cannot get into Slack for at least another aprox one hour to run that make modules_install to see if that will fix that last part in order to run mkinitrd
If you didn't do make modules_install, where did the directories in /lib/modules/4.8.3/ come from? Have you had other 4.8.3 kernel compilations on this install?
No, in your huge post about getting lilo to work in Slackware.
True. Only one bootloader can be used unless you intend to chainload (which I had also mentioned in the lilo thread, but you never commented on it, so I assumed you didn't want to use it). But, just as you wouldn't go to a Windows forum when your Void's grub won't boot Windows, you shouldn't come to a Slackware forum and expect that we know what's going on with Void's grub. That grub is likely a different version than Slackware's and/or possibly has patches or additional software that Slackware doesn't have (I remember you complaining in a previous bootloader thread that Slackware's grub didn't contain some grub command/script you expected it to have).
Any Linux bootloader should be able to support multiple kernels for one distro.
Because Void's grub is not necessarily the same grub that Slackware uses. As I said above, it could be a different version or it could contain patches or scripts that Slackware's doesn't.
Well, the make modules_install part was even in the section you copied But we do all miss the obvious sometimes. I've definitely had those moments before.
An initrd should only be needed if you're basing your kernel off a generic config. If you compile all the needed drivers into the kernel instead of modules, no initrd is needed (except for a few exceptions, like using lvm or encryption).
lilo is more than capable of multi-boot. It just doesn't have utilities like grub to make things easier (supposedly... but I haven't used grub enough to know). lilo requires you to edit a conf file and if it is wrong, it can lead you to failed boots. But, when it's right, it works beautifully.
If you didn't do make modules_install, where did the directories in /lib/modules/4.8.3/ come from? Have you had other 4.8.3 kernel compilations on this install?
Good luck
sooo you remember that lilo problem I posted about huh... whatever happened to altimers? lol
I am not a dummy but some of this stuff does confuse me.ah on that where did the 4.8.3 come from well when I looked and did not see it, and only seen the 2.x.x for the install. I just mimicked it and mkdir 4.8.3 then looked in to source to copy it from there into that dir and that is where everything went huh??? so I posted in here.
and so here we are .. sorry if I am sounding like an ass on this stuff....
now they have just put out a 4.8.4 updated kernel and damn that list is long.
what is the basic rule of thumb for saying y or n or m on every stinking question?
I know my basic hardware on my motherboard then their is all of these other questions about shit I don't even know what it is, and some stuff I have a slight idea to what it is but do I really need it, I have no idea.
that is why on that other one I just selected M for most everything trying to play it safe. this time I am just saying Y to everything. which is mad crazy HUGE ...
anyways I hacked it so that slack had no choice but to boot the 4.8.3 by moving everything into a different directory I made on root, leaving only everything to do with 4.8.3 then ran Void update-grub then booted got kernel panic
Code:
kernel panic not syncing VFS unable to mount root fs on unknown-block (8,1)
I have no idea what (8,1) is I only have two hdd's partitioned with 4 on one and 3 on the other one neither one has 8 ... If that is what it is referring to.
as far as that lilo thing to me at that time the grub seemed like the fastest easiest way to go, then I found that part out about no one uses the same grub, fu*K what the f*** is that ... learning the hard way on that one.
I could have sworn I've duel booted on lilo with slack and void before too a while back, but too I remember I put grub on slack and used that so maybe that is why it dual booted with VOID .. anyways.
I just went to one system, VOID, then slack went 14.2 so I figured I 'd check it out again. I kind of like it - but all of that typing to install everything ...
anyways I am at point one again. I over wrote that initrd I didn't name it customxxx when I did it. but Slack is still booting off of HUGE so I don't know About that if i needed it or not for HUGE ...
Now I am planing on just compiling that latest one 4.8.4 so I can see if I can get that because I have not actually made progress here anyways ... so it only a few hours to get that made. then try this again.
missing that step started this post, but it looks like I'd of posted on this anyways by still not getting anywhere with this kernel....
Code:
root@SlackDaddy & src >> $ls
linux-4.4.23 linux-4.8.3 linux-4.8.4
root@SlackDaddy & src >> $ln -s linux-4.4.23 linux
root@SlackDaddy & src >> $mkinitrd -c -k 4.4.2 -m ext4
ERROR: No /lib/modules/4.4.2 kernel modules tree found for kernel "4.4.2"
root@SlackDaddy & src >> $mkinitrd -c -k 4.4.23 -m ext4
OK: /lib/modules/4.4.23/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/4.4.23/kernel/fs/mbcache.ko added.
OK: /lib/modules/4.4.23/kernel/fs/ext4/ext4.ko added.
36556 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
sooo you remember that lilo problem I posted about huh... whatever happened to altimers? lol
Of course I remember it. I spent a lot of time trying to help you fix your problem and it wasn't that long ago.
Quote:
Originally Posted by BW-userx
I am not a dummy but some of this stuff does confuse me.ah on that where did the 4.8.3 come from well when I looked and did not see it, and only seen the 2.x.x for the install. I just mimicked it and mkdir 4.8.3 then looked in to source to copy it from there into that dir and that is where everything went huh??? so I posted in here.
Ok, so you manually created the 4.8.3 directory and copied directories out of the source folder? That makes a bit more sense. Luckily, you now know you can just run make modules_install to get everything where it should be.
Quote:
Originally Posted by BW-userx
now they have just put out a 4.8.4 updated kernel and damn that list is long.
what is the basic rule of thumb for saying y or n or m on every stinking question?
I know my basic hardware on my motherboard then their is all of these other questions about shit I don't even know what it is, and some stuff I have a slight idea to what it is but do I really need it, I have no idea.
that is why on that other one I just selected M for most everything trying to play it safe. this time I am just saying Y to everything. which is mad crazy HUGE ...
This is one of the difficult things about building a custom kernel. Pat (and other distro maintainers) takes a lot of time to get the kernel configured as it is in Slackware. Generally, you can just follow the suggestion ("if unsure, say X") in the HELP portion of that section. This is also why it's generally recommended to use a good config as a start rather than starting from a completely blank slate. Then you can run make old-config to go through just the new stuff.
Quote:
Originally Posted by BW-userx
anyways I hacked it so that slack had no choice but to boot the 4.8.3 by moving everything into a different directory I made on root, leaving only everything to do with 4.8.3 then ran Void update-grub then booted got kernel panic
Code:
kernel panic not syncing VFS unable to mount root fs on unknown-block (8,1)
I have no idea what (8,1) is I only have two hdd's partitioned with 4 on one and 3 on the other one neither one has 8 ... If that is what it is referring to.
If you compiled things as modules but then didn't install those modules and then create an initrd, then it certainly would prevent you from booting, because it probably didn't have the required things built in the kernel, so it didn't know how to load the filesystem containing the OS.
Quote:
Originally Posted by BW-userx
as far as that lilo thing to me at that time the grub seemed like the fastest easiest way to go, then I found that part out about no one uses the same grub, fu*K what the f*** is that ... learning the hard way on that one.
I could have sworn I've duel booted on lilo with slack and void before too a while back, but too I remember I put grub on slack and used that so maybe that is why it dual booted with VOID .. anyways.
I just went to one system, VOID, then slack went 14.2 so I figured I 'd check it out again. I kind of like it - but all of that typing to install everything ...
While lilo is certainly capable of handling your setup, it wouldn't be worth it to address it again. It'd be much easier to stick with your current bootloader and figure out how to get that to update properly. Unfortunately, as I said before, I don't use grub, so I can't help out with that.
Quote:
Originally Posted by BW-userx
anyways I am at point one again. I over wrote that initrd I didn't name it customxxx when I did it. but Slack is still booting off of HUGE so I don't know About that if i needed it or not for HUGE ...
Technically, there's no such thing as a huge or generic kernel. They are just tags used by Patrick in Slackware to label whether a kernel has all drivers compiled into the kernel (huge) or as modules (generic). If you based your kernel off a huge config, then depending on what changes you made, you might still not have the required drivers compiled into the kernel and they exist as modules. If that is the case, then you do need an initrd. However, even if all that stuff is compiled into the kernel, using an initrd won't harm anything, so you can use one no matter what type of config you use.
Quote:
Originally Posted by BW-userx
Now I am planing on just compiling that latest one 4.8.4 so I can see if I can get that because I have not actually made progress here anyways ... so it only a few hours to get that made. then try this again.
missing that step started this post, but it looks like I'd of posted on this anyways by still not getting anywhere with this kernel....
Code:
root@SlackDaddy & src >> $ls
linux-4.4.23 linux-4.8.3 linux-4.8.4
root@SlackDaddy & src >> $ln -s linux-4.4.23 linux
root@SlackDaddy & src >> $mkinitrd -c -k 4.4.2 -m ext4
ERROR: No /lib/modules/4.4.2 kernel modules tree found for kernel "4.4.2"
root@SlackDaddy & src >> $mkinitrd -c -k 4.4.23 -m ext4
OK: /lib/modules/4.4.23/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/4.4.23/kernel/fs/mbcache.ko added.
OK: /lib/modules/4.4.23/kernel/fs/ext4/ext4.ko added.
36556 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
their I fixed that possible problem
thanks
I would highly recommend using Slackware's mkinitrd_command_generator.sh script I posted earlier (found under /usr/share/mkinitrd/). It will help you determine a proper mkinitrd command. It would contain more than just the module for your filesystem (it also sets the filesystem and the root partition, in addition to loading several other modules). Here's an example of what it output on my computer:
Of course I remember it. I spent a lot of time trying to help you fix your problem and it wasn't that long ago.
Ok, so you manually created the 4.8.3 directory and copied directories out of the source folder? That makes a bit more sense. Luckily, you now know you can just run make modules_install to get everything where it should be.
This is one of the difficult things about building a custom kernel. Pat (and other distro maintainers) takes a lot of time to get the kernel configured as it is in Slackware. Generally, you can just follow the suggestion ("if unsure, say X") in the HELP portion of that section. This is also why it's generally recommended to use a good config as a start rather than starting from a completely blank slate. Then you can run make old-config to go through just the new stuff.
If you compiled things as modules but then didn't install those modules and then create an initrd, then it certainly would prevent you from booting, because it probably didn't have the required things built in the kernel, so it didn't know how to load the filesystem containing the OS.
While lilo is certainly capable of handling your setup, it wouldn't be worth it to address it again. It'd be much easier to stick with your current bootloader and figure out how to get that to update properly. Unfortunately, as I said before, I don't use grub, so I can't help out with that.
Technically, there's no such thing as a huge or generic kernel. They are just tags used by Patrick in Slackware to label whether a kernel has all drivers compiled into the kernel (huge) or as modules (generic). If you based your kernel off a huge config, then depending on what changes you made, you might still not have the required drivers compiled into the kernel and they exist as modules. If that is the case, then you do need an initrd. However, even if all that stuff is compiled into the kernel, using an initrd won't harm anything, so you can use one no matter what type of config you use.
I would highly recommend using Slackware's mkinitrd_command_generator.sh script I posted earlier (found under /usr/share/mkinitrd/). It will help you determine a proper mkinitrd command. It would contain more than just the module for your filesystem (it also sets the filesystem and the root partition, in addition to loading several other modules). Here's an example of what it output on my computer:
Personally, I'll change the output at the end to list my kernel version in it, so I would change it to be /boot/initrd-3.18.24.gz.
I did run make old-config to go through just the new stuff. their is a lOT of new stuff in that listings. I was already close to 35 minutes into it by just hitting y to everything and it still was not done before I did a Ctrl+C to kill it.
I just ran it regular like so it would over write that other one, mkinitrd -c -k 3.18.24 -f ext4
that HUGE was just me making reference to Slackware's HUGE everything compiled in it kernel, because I was saying yes to everything. there fore it is a larger Kernel. hence HUGE
as far a the kernel panic I did everything over after installing modules, and making a initrd using the shell script and using version numbers. then booted it again and still had a kernel panic.
I did run make old-config to go through just the new stuff. their is a lOT of new stuff in that listings. I was already close to 35 minutes into it by just hitting y to everything and it still was not done before I did a Ctrl+C to kill it.
Yes, it can be quite the process to go with a newer kernel than Slackware supports. You could try using make olddefconfig, which will use the default value for any new items in the kernel, but that could prevent support for things that the developers haven't enabled by default (like updated drivers). But, I guess you could always go through the menus later and verify everything you need enabled is enabled.
Quote:
Originally Posted by BW-userx
as far a the kernel panic I did everything over after installing modules, and making a initrd using the shell script and using version numbers. then booted it again and still had a kernel panic.
You would need to make sure the new kernel and initrd are referenced properly in grub. But I don't know what you need to do that since I'm not familiar with grub.
Yes, it can be quite the process to go with a newer kernel than Slackware supports. You could try using make olddefconfig, which will use the default value for any new items in the kernel, but that could prevent support for things that the developers haven't enabled by default (like updated drivers). But, I guess you could always go through the menus later and verify everything you need enabled is enabled.
make olddefconfig they do have some new CPU governor items and other things I seen I'd like to add, but a lot of that stuff is, in my guess, for someone running Linux as a server, a lot of Networking items and then their is all of that other, "it's all greek to me" stuff in there as well I'd seen.
Quote:
You would need to make sure the new kernel and initrd are referenced properly in grub. But I don't know what you need to do that since I'm not familiar with grub.
by the way I did it grub had no choice in the matter, I moved everything else into a different directory. Adding that I might not have giving the kernel what it needed I have no idea. that is why I went to saying yes on the 4.8.4 kernel with everything to make sure it had everything, knowing that it is over kill.
then looked at the clock and decided it is too late in the day for this, as I was still working on the list. so I kill'ed it for another day.
how do I clean this up so I can run this to completion?
Code:
userx@SlackDaddy & linux-4.8.4 >> $make -j 8
HOSTCC scripts/kconfig/conf.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
scripts/kconfig/Makefile:37: recipe for target 'silentoldconfig' failed
make[2]: *** [silentoldconfig] Error 1
Makefile:545: recipe for target 'silentoldconfig' failed
make[1]: *** [silentoldconfig] Error 2
SYSTBL arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h
SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_32.h
SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_64.h
SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_x32.h
make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'. Stop.
make: *** Waiting for unfinished jobs....
userx@SlackDaddy & linux-4.8.4 >> $
I am guessing I have no idea. Maybe it is looking at a file in /boot because i deleted the other 4.8.4 and unzipped it again and tried it again, and got this error again. I killed a make oldconfig session the other day, Ctrl+C . That is the only thing I can think of that it is talking about make: *** Waiting for unfinished jobs....
[MOD]
OR
when it asked me to name the config somewhere in that menu it gave me an option to name it so I named it config-4.8.4 so now it does not see it. *** Configuration file ".config" not found! BUT
Code:
/home/userx/bin/linux-4.8.4/.config-4.8.4
maybe you could share with me what command line argument to make it use that one
userx@Voided.1 & ~ >> $sudo update-grub
Generating grub configuration file ...
Found background: /usr/share/void-artwork/splash.png
Found linux image: /boot/vmlinuz-4.8.4_1
Found initrd image: /boot/initramfs-4.8.4_1.img
Found linux image: /boot/vmlinuz-4.8.3_1
Found initrd image: /boot/initramfs-4.8.3_1.img
Found linux image: /boot/vmlinuz-4.7.10_1
Found initrd image: /boot/initramfs-4.7.10_1.img
Found linux image: /boot/vmlinuz-4.7.9_1
Found initrd image: /boot/initramfs-4.7.9_1.img
Found linux image: /boot/vmlinuz-4.7.8_1
Found initrd image: /boot/initramfs-4.7.8_1.img
Found linux image: /boot/vmlinuz-4.7.6_1
Found initrd image: /boot/initramfs-4.7.6_1.img
Found linux image: /boot/vmlinuz-4.0.5_2
Found initrd image: /boot/initramfs-4.0.5_2.img
Found Slackware Linux (Slackware 14.2) on /dev/sda1
Found Windows 10 (loader) on /dev/sdb1
Found Void Linux 64 on /dev/sdb3
done
userx@Voided.1 & ~ >> $sudo reboot
Whoa! Why are you creating a symbolic link between the 32bit and 64bit kernels?
Are you trying to build a 32bit or 64bit kernel? Based on what you're building, you should only copy that kernel (32bit would be in the x86 folder and 64bit would be in the x86_64 folder).
Here's all you need to do to build a kernel after you've configured it as you desired (based on a 64bit kernel... if that's different, switch the x86_64 to x86).
Code:
make bzImage modules
make modules_install
cp arch/x86_64/boot/bzImage /boot/vmlinuz-4.8.4
$(/usr/share/mkinitrd/mkinitrd_command_generator.sh -r -k 4.8.4 -a "-o /boot/initrd-4.8.4.gz")
Everything else is not needed and can be left out for simplicity. You can remove other kernels, if needed, so grub will pick this up properly. If it doesn't work, then it is one of two issues... 1. your kernel isn't configured properly for your machine, or 2. grub on Void isn't set up properly for the new kernel. Unfortunately, until you know you're configuring grub properly, there's no easy way to determine whether the issue is grub or your kernel config (at least not that I'm familiar with).
Last edited by bassmadrigal; 10-23-2016 at 07:39 PM.
Reason: Fixed kernel version
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
But we do all miss the obvious sometimes. I've definitely had those moments before.
