LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-11-2018, 12:50 PM   #16
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,727

Rep: Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740

the only reason for an initrd are the file system drivers, at least for me.
back the days I always rebuild the generic-smp, but with extX drivers inbuild, than I did not need the initrd
today I use the huge kernel, it works. initrd is too stressful, creating it gives me nothing than work and a wast of time.
 
Old 04-11-2018, 01:56 PM   #17
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238
I use exclusively the generic/generic-smp. From starts.

In fact, I do not remember preciselly how looks the native installer, as I use the hard way (literally: manual installation), and having an external USB hard-drive of 500GB, hosting both x86 and x86_64 installations (in different partitions, of course) including local mirrors, with everything kept up2date.

I do not know why, but I feel that the combination of generic(-smp) and initrd works better.

Last edited by Darth Vader; 04-11-2018 at 03:09 PM.
 
Old 04-11-2018, 02:45 PM   #18
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,592

Rep: Reputation: 6009Reputation: 6009Reputation: 6009Reputation: 6009Reputation: 6009Reputation: 6009Reputation: 6009Reputation: 6009Reputation: 6009Reputation: 6009Reputation: 6009
Quote:
Originally Posted by a4z View Post
the only reason for an initrd are the file system drivers, at least for me.
back the days I always rebuild the generic-smp, but with extX drivers inbuild, than I did not need the initrd
today I use the huge kernel, it works. initrd is too stressful, creating it gives me nothing than work and a wast of time.
For a 'normal' no-frills installation, you don't need an initrd if you are happy with a huge kernel.
In case you want to use RAID, LVM or LUKS, you are required to use an initrd.
 
Old 04-11-2018, 02:51 PM   #19
Ne01eX
Member
 
Registered: Mar 2018
Location: Ekaterinburg region, Ural, Russian Federation
Distribution: Slackware, RTK GNU/Linux
Posts: 173

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by Didier Spaier View Post
If not in Slackware 15.0, at least in the next version there won't be a huge kernel anymore anyway, so better be prepared.
Time for saving kernel-configs?
 
Old 04-11-2018, 03:07 PM   #20
chemfire
Member
 
Registered: Sep 2012
Posts: 230

Rep: Reputation: Disabled
I pretty much use the generic kernels and an initrd. Installing a new initrd with elilo is easier and safer than ever. Just build the image mount the vfat filesystem under /boot if its not already and and go.

This is super nice too because typically you can copy the system to any, including very different machines and with an initrid update and maybe a few deletes of things under /etc/udev/persistent.... its good to go.
 
Old 04-11-2018, 03:47 PM   #21
Ne01eX
Member
 
Registered: Mar 2018
Location: Ekaterinburg region, Ural, Russian Federation
Distribution: Slackware, RTK GNU/Linux
Posts: 173

Original Poster
Rep: Reputation: 22
...if your not using proprietary drivers, such as NVidia. :-D :-D :-D
 
Old 04-11-2018, 05:34 PM   #22
TheTKS
Member
 
Registered: Sep 2017
Location: The deep south... of Canada
Distribution: Slackware, Xubuntu, elementary, OpenBSD, Puppy, TinyCore
Posts: 55

Rep: Reputation: Disabled
Huge kernel going away some day?

Quote:
Originally Posted by Didier Spaier View Post
If not in Slackware 15.0, at least in the next version there won't be a huge kernel anymore anyway, so better be prepared.
Didier, thanks for the heads up. Trying generic is on my ďsome dayĒ list, but Iíve had no great reason not to just run huge. If itís going to go away in the next version or two, Iíll go figure out how to do it with grub, although on reading the instructions it doesnít sound like thereís much to it, if everything goes smoothly.

Has anyone here ever had trouble switching to generic?
 
Old 04-11-2018, 06:18 PM   #23
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,204

Rep: Reputation: 1863Reputation: 1863Reputation: 1863Reputation: 1863Reputation: 1863Reputation: 1863Reputation: 1863Reputation: 1863Reputation: 1863Reputation: 1863Reputation: 1863
Quote:
That's I'm wondering why people use the initrd and modules in general, if can immediately create the monolith for youself.
I use the generic kernel and an initrd to reduce RAM usage. Also, although I have never seen it, apparently it has been reported that the huge kernel can suffer from conflicts on certain hardware. It is faster to build an initrd than to create a monolith with additional options.
 
Old 04-12-2018, 02:08 PM   #24
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 753
Blog Entries: 3

Rep: Reputation: 235Reputation: 235Reputation: 235
Quote:
Originally Posted by Alien Bob View Post
I see no reason for myself to modify the generic kernel configuration these days. I used to compile custom kernels a lot but I am exclusively using Slackware's default generic configs now, combined with an initrd, done so for years.
If i feel like running a patched kernel once in a while (usually the postfactum patches for me), i'll copy over the currently running generic config to build from, then adjust the few new options for what the patches provide. Other than that i'll also use the generic config with no changes if i feel like compiling the latest mainline kernel.
 
Old 04-12-2018, 05:51 PM   #25
ttk
Member
 
Registered: May 2012
Location: Sebastopol, CA
Distribution: Slackware64
Posts: 816
Blog Entries: 26

Rep: Reputation: 1083Reputation: 1083Reputation: 1083Reputation: 1083Reputation: 1083Reputation: 1083Reputation: 1083Reputation: 1083
I exclusively use the 64-bit huge smp kernel.

Slackware's stability is a key feature to me. By using the same kernel binary as some other Slackware users, I am less likely to have bugs in my systems' kernels that other people do not find.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
"a/kernel-generic-4.4.11-i586-1.txz" --> 486 support dropped at last? anscal Slackware 16 05-27-2016 11:04 PM
why the sound of "huge" kenerl is better that the "generic" kernel ? sdrkyj Slackware 2 02-06-2014 10:44 AM
Why "magic number "2.6.38 SMP mod_unload" should be "2.6.38 SMP" " ? rpatel Linux - Kernel 0 10-16-2012 03:35 AM
13.0 64 bit just Huge & Generic, no "smp" kernels installed acummings Slackware 2 10-01-2009 09:59 AM
Confused about "generic" vs. "386" linux kernel SaintDanBert Linux - Software 6 09-29-2009 11:51 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:43 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration