LinuxQuestions.org
Visit Jeremy's Blog.
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 01-30-2019, 04:11 AM   #2731
GazL
Senior Member
 
Registered: May 2008
Posts: 4,952
Blog Entries: 15

Rep: Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559

initrd is needed under certain circumstances (LUKS/LVM/RAID rootfs being some of the primary ones).

While an initrd may not be required on an individual host level, at the distro level it seems quite reasonable to say: "If some of the users will need one, then lets just use one for everyone, whether it's strictly needed or not, and keep things consistent".


early firmware loading also being another one, which is more important than it used to be post spectre/meltdown.
 
5 members found this post helpful.
Old 01-30-2019, 01:18 PM   #2732
timsoft
Member
 
Registered: Oct 2004
Location: scotland
Distribution: slackware 13.1,13.37,14.0,14.1,14.2 64 and 32bit and arm
Posts: 320

Rep: Reputation: 86
i must confess I always use huge, and if i compile my own kernels I include the fs support (ext2/3/4) etc. to avoid having to create an initrd, so I'm greatful for those "huge" kernels. it does follow the KISS principle, and if you have very limited ram and don't want to do your own kernel, you can still use what is available.
 
1 members found this post helpful.
Old 01-30-2019, 01:33 PM   #2733
ZhaoLin1457
Member
 
Registered: Jan 2018
Posts: 238

Rep: Reputation: 205Reputation: 205Reputation: 205
I don't think that is something in common between the initrd usage and not following whatever KISS principles.

And regarding the memory consumption, the default "huge" kernel is rather memory wasteful, because the allocated memory for initrd is freed after switching to real root, if I understand right from what other distributions says.

Last edited by ZhaoLin1457; 01-30-2019 at 01:34 PM.
 
1 members found this post helpful.
Old 01-30-2019, 02:39 PM   #2734
Nobby6
LQ Newbie
 
Registered: Jul 2012
Posts: 16

Rep: Reputation: Disabled
Quote:
Originally Posted by GazL View Post
initrd is needed under certain circumstances (LUKS/LVM/RAID rootfs being some of the primary ones).

While an initrd may not be required on an individual host level, at the distro level it seems quite reasonable to say: "If some of the users will need one, then lets just use one for everyone, whether it's strictly needed or not, and keep things consistent".


early firmware loading also being another one, which is more important than it used to be post spectre/meltdown.
Fair enough, but if I was betting person, most people would be ignorant of teh fact and not need it.
I've always used hardware RAID, even at home since 2000ish, so I admit not looking into it, but, if it goes in an initrd image, then surely it can be used in boot kernel, I cant imagine linux in 2019 needing it for software RAID, but.. as vI said I admit ignorance in software RAID.
 
Old 01-30-2019, 03:12 PM   #2735
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 890

Rep: Reputation: Disabled
Hi,
Quote:
Originally Posted by GazL View Post
early firmware loading also being another one, which is more important than it used to be post spectre/meltdown.
Although I'm initrd fan, sometime ago somebody emailed me that it is possible to load microcode with the huge kernel.
There will come the day I'll investigate it ;-)

--
Best regards,
Andrzej Telszewski
 
Old 01-30-2019, 03:27 PM   #2736
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,705

Rep: Reputation: Disabled
Quote:
Originally Posted by atelszewski View Post
Hi,

Although I'm initrd fan, sometime ago somebody emailed me that it is possible to load microcode with the huge kernel.
There will come the day I'll investigate it ;-)
you can just load the microcode in place of the initrd, like (excerpt from lilo.conf)
Code:
image = /boot/vmlinuz-huge
  initrd = /boot/intel-ucode.cpio
  root = /dev/sda1
  label = Linux
  read-only
 
2 members found this post helpful.
Old 01-30-2019, 03:48 PM   #2737
ZhaoLin1457
Member
 
Registered: Jan 2018
Posts: 238

Rep: Reputation: 205Reputation: 205Reputation: 205
But, but, but /boot/intel-ucode.cpio is still an initrd, which by its own existence and usage, defeats the claim that you can load the microcode without an initrd.

That the kernel is capable to load multiple (concatenated) initrds, that's entirely another story.

Last edited by ZhaoLin1457; 01-30-2019 at 03:49 PM.
 
Old 01-30-2019, 03:53 PM   #2738
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,705

Rep: Reputation: Disabled
to be precise, I was replying to the above "it is possible to load microcode with the huge kernel".
 
1 members found this post helpful.
Old 01-30-2019, 05:39 PM   #2739
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,510

Rep: Reputation: 228Reputation: 228Reputation: 228
No more interest in no more initrd.

I built a custom kernel this morning. That is something I hadn't done in maybe 4 years. I just really got tired of building an initrd on each kernel upgrade. I was really tired of kernel upgrades in current. I blacklisted those things and all its parts.

I took out loads of stuff from the generic kernel, especially for embedded and stuff I was sure about. I also used the latest stable release - 4.20.5. That way, I won't be tempted to upgrade so often.

The only boo-boo was not building the nvidia driver for the second kernel. The three finger salute sent me back to correct that self-inflicted bludgeoning.

So far, everything works, and it seems to have shaved about 20 seconds. I'm too lazy to go back and time that again.
 
Old 01-31-2019, 01:55 AM   #2740
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,501
Blog Entries: 2

Rep: Reputation: 339Reputation: 339Reputation: 339Reputation: 339
Thumbs up

Quote:
Originally Posted by mlangdn View Post
No more interest in no more initrd.

I built a custom kernel this morning. That is something I hadn't done in maybe 4 years. I just really got tired of building an initrd on each kernel upgrade. I was really tired of kernel upgrades in current. I blacklisted those things and all its parts.

I took out loads of stuff from the generic kernel, especially for embedded and stuff I was sure about. I also used the latest stable release - 4.20.5. That way, I won't be tempted to upgrade so often.

The only boo-boo was not building the nvidia driver for the second kernel. The three finger salute sent me back to correct that self-inflicted bludgeoning.

So far, everything works, and it seems to have shaved about 20 seconds. I'm too lazy to go back and time that again.
I was just about to ask what happened to roll your own people
 
1 members found this post helpful.
Old 01-31-2019, 01:55 PM   #2741
qunying
Member
 
Registered: Jun 2002
Distribution: Slackware
Posts: 156

Rep: Reputation: 88
Please update the libimobiledevice from the git HEAD in https://github.com/libimobiledevice/libimobiledevice.

The current version was released 4 years ago and does not work on newer iOS and iTunes:
https://github.com/libimobiledevice/...ice/issues/380
 
2 members found this post helpful.
Old 01-31-2019, 03:13 PM   #2742
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,109

Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
glibc-2.29

release notes --> https://sourceware.org/ml/libc-annou.../msg00000.html
sources --> http://ftp.gnu.org/gnu/glibc/glibc-2.29.tar.xz
 
Old 01-31-2019, 04:49 PM   #2743
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,574
Blog Entries: 1

Rep: Reputation: 1891Reputation: 1891Reputation: 1891Reputation: 1891Reputation: 1891Reputation: 1891Reputation: 1891Reputation: 1891Reputation: 1891Reputation: 1891Reputation: 1891
Mesa 18.3.3

The release notes,

https://www.mesa3d.org/relnotes/18.3.3.html

Last edited by cwizardone; 01-31-2019 at 05:31 PM.
 
Old 02-01-2019, 02:59 AM   #2744
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,501
Blog Entries: 2

Rep: Reputation: 339Reputation: 339Reputation: 339Reputation: 339
kernel got 5.0 ?
 
Old 02-01-2019, 06:49 AM   #2745
_gin
Member
 
Registered: Aug 2012
Distribution: Slackware64-14.2
Posts: 89

Rep: Reputation: Disabled
Qt 5.12.1

http://blog.qt.io/blog/2019/02/01/qt-5-12-1-released/
http://download.qt.io/official_relea...-5.12.1.tar.xz

Last edited by _gin; 02-01-2019 at 06:52 AM.
 
1 members found this post helpful.
  


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
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

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

All times are GMT -5. The time now is 07:08 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