Slackware 12
in [Slackware]
|
Prev: Coming gotchya
Next: Blown hard-drive and motherboard!
From: GangGreene on 12 Jan 2010 11:19 Douglas Mayne wrote: > On Tue, 12 Jan 2010 08:54:42 -0500, GangGreene wrote: > >> Douglas Mayne wrote: >> >>> On Mon, 11 Jan 2010 15:13:50 -0500, GangGreene wrote: >>> >>>> Aaron W. Hsu wrote: >>>> >>>>> On Mon, 11 Jan 2010 08:59:28 -0500, GangGreene >>>>> <GangGreen(a)invalid.com> wrote: >>>>> >>>>>> I just need to finish up on changing the kernel from huge to >>>>>> generic, smp setting up my wireless, and enabling kdm on boot and >>>>>> then I am good. BTW does the generic kernel have pae enabled? If >>>>>> not I can change it and recompile, I don't think it will be any >>>>>> trouble. >>>>> >>>>> Make sure that you check out the README in /boot about initrds. That >>>>> pretty much explains how a generic kernel works. Most things are >>>>> compiled as modules, and I've never had to recompile the generic >>>>> kernel proper to get what I wanted. There is also a helper script >>>>> that will show you how to build the initrd by automatically scanning >>>>> your system and generating the command for you. >>>>> >>>>> Aaron W. Hsu >>>>> >>>>> >>>>> >>>> Did not find the helper script to build the initrd. Do you know which >>>> package it is in? >>>> >>> mkinitrd-xx >>>> >>>> I'll fetch it by force ;) >>>> >>> No need to force it. Try this: >>> >>> $ grep mkinitrd /var/log/packages/* >>> >>> That's an "old chesnut" in the Slackware world, and yields this line >>> (among others): >>> /var/log/packages/mkinitrd-1.3.4-i486-3:sbin/mkinitrd >>> >>> >> Must be in thirteen the grep didn't find it >> > That is probably telling you the package is not installed. Other checks: > $ ls /var/log/packages/mkinitrd* > > Also, > $ man mkinitrd > > Or as root: > # which mkinitrd > > It is strange that it is missing because mkinitrd is in the "a" package > group, and you should have opted to install almost everything in that > group. AFAIK, mkinitrd is the Slackware tool for making an initrd, going > back a long way in the version history. For Slackware 12.2, the package > was initially released in the "slackware/a" package group, as version: > mkinitrd-1.3.2-i486-4.tgz > > It has been updated in the "patches/packages/" as of Dec 2008 to version: > mkinitrd-1.3.3-i486-1_slack12.2.tgz > > > This was noted in the Changelog: > <begin changelog snippet> > +--------------------------+ > Thu Dec 18 12:40:56 CST 2008 > patches/packages/mkinitrd-1.3.3-i486-1_slack12.2.tgz: > Fixed a few bugs in the previous mkinitrd package: > If a kernel version is requested with the -k option and modules are > needed to build the initrd, exit with an error if no matching > /lib/modules/ tree is > present. Usually an incorrect kernel version was supplied. > Thanks to Eric Hameleers. > <snip> > <end changelog> > I did a full install, the mkinitrd-xx is what I couldn't find the package was installed
From: Peter Chant on 12 Jan 2010 16:05 GangGreene wrote: > Did not find the helper script to build the initrd. > Do you know which package it is in? > > I'll fetch it by force ;) Personally though initrd seems like a good idea in practice, when I rebuild a kernel I run away from it as quickly as possible. I build the new drivers and filesystems into the kernel rather than use modules and simply ignore it. Much less fiddling. Pete -- http://www.petezilla.co.uk
From: Mikhail Zotov on 13 Jan 2010 15:37 On Sun, 10 Jan 2010 19:34:11 -0500 GangGreene <GangGreen(a)invalid.com> wrote: .... > 3. Package management > > Package repositories? > Package development HOWTOS? Check links at http://slackworld.berlios.de/links.html > I want to package some things like B43 firmware etc. > Looking for Wine package. Slackbuilds.org have both. -- Mikhail
From: onebuck on 19 Jan 2010 20:25 On Jan 12, 10:19 am, GangGreene <GangGr...(a)invalid.com> wrote: > Douglas Mayne wrote: > > On Tue, 12 Jan 2010 08:54:42 -0500, GangGreene wrote: > > >> Douglas Mayne wrote: > > >>> On Mon, 11 Jan 2010 15:13:50 -0500, GangGreene wrote: > > >>>> Aaron W. Hsu wrote: > > >>>>> On Mon, 11 Jan 2010 08:59:28 -0500, GangGreene > >>>>> <GangGr...(a)invalid.com> wrote: > > >>>>>> I just need to finish up on changing the kernel from huge to > >>>>>> generic, smp setting up my wireless, and enabling kdm on boot and > >>>>>> then I am good. BTW does the generic kernel have pae enabled? If > >>>>>> not I can change it and recompile, I don't think it will be any > >>>>>> trouble. > > >>>>> Make sure that you check out the README in /boot about initrds. That > >>>>> pretty much explains how a generic kernel works. Most things are > >>>>> compiled as modules, and I've never had to recompile the generic > >>>>> kernel proper to get what I wanted. There is also a helper script > >>>>> that will show you how to build the initrd by automatically scanning > >>>>> your system and generating the command for you. > > >>>>> Aaron W. Hsu > > >>>> Did not find the helper script to build the initrd. Do you know which > >>>> package it is in? > > >>> mkinitrd-xx > > >>>> I'll fetch it by force ;) > > >>> No need to force it. Try this: > > >>> $ grep mkinitrd /var/log/packages/* > > >>> That's an "old chesnut" in the Slackware world, and yields this line > >>> (among others): > >>> /var/log/packages/mkinitrd-1.3.4-i486-3:sbin/mkinitrd > > >> Must be in thirteen the grep didn't find it > > > That is probably telling you the package is not installed. Other checks: > > $ ls /var/log/packages/mkinitrd* > > > Also, > > $ man mkinitrd > > > Or as root: > > # which mkinitrd > > > It is strange that it is missing because mkinitrd is in the "a" package > > group, and you should have opted to install almost everything in that > > group. AFAIK, mkinitrd is the Slackware tool for making an initrd, going > > back a long way in the version history. For Slackware 12.2, the package > > was initially released in the "slackware/a" package group, as version: > > mkinitrd-1.3.2-i486-4.tgz > > > It has been updated in the "patches/packages/" as of Dec 2008 to version: > > mkinitrd-1.3.3-i486-1_slack12.2.tgz > > > This was noted in the Changelog: > > <begin changelog snippet> > > +--------------------------+ > > Thu Dec 18 12:40:56 CST 2008 > > patches/packages/mkinitrd-1.3.3-i486-1_slack12.2.tgz: > > Fixed a few bugs in the previous mkinitrd package: > > If a kernel version is requested with the -k option and modules are > > needed to build the initrd, exit with an error if no matching > > /lib/modules/ tree is > > present. Usually an incorrect kernel version was supplied. > > Thanks to Eric Hameleers. > > <snip> > > <end changelog> > > I did a full install, the mkinitrd-xx is what I couldn't find > the package was installed Hi, Head over to; http://www.linuxquestions.org/questions/slackware-14/ You'll find a lot of users along with helpful information. Gary (aka onebuck)
From: GangGreene on 20 Jan 2010 06:16
onebuck wrote: > On Jan 12, 10:19�am, GangGreene <GangGr...(a)invalid.com> wrote: >> Douglas Mayne wrote: >> > On Tue, 12 Jan 2010 08:54:42 -0500, GangGreene wrote: >> >> >> Douglas Mayne wrote: >> >> >>> On Mon, 11 Jan 2010 15:13:50 -0500, GangGreene wrote: >> >> >>>> Aaron W. Hsu wrote: >> >> >>>>> On Mon, 11 Jan 2010 08:59:28 -0500, GangGreene >> >>>>> <GangGr...(a)invalid.com> wrote: >> >> >>>>>> I just need to finish up on changing the kernel from huge to >> >>>>>> generic, smp setting up my wireless, and enabling kdm on boot and >> >>>>>> then I am good. BTW does the generic kernel have pae enabled? �If >> >>>>>> not I can change it and recompile, I don't think it will be any >> >>>>>> trouble. >> >> >>>>> Make sure that you check out the README in /boot about initrds. >> >>>>> That pretty much explains how a generic kernel works. Most things >> >>>>> are compiled as modules, and I've never had to recompile the >> >>>>> generic kernel proper to get what I wanted. There is also a helper >> >>>>> script that will show you how to build the initrd by automatically >> >>>>> scanning your system and generating the command for you. >> >> >>>>> Aaron W. Hsu >> >> >>>> Did not find the helper script to build the initrd. Do you know >> >>>> which package it is in? >> >> >>> mkinitrd-xx >> >> >>>> I'll fetch it by force ;) >> >> >>> No need to force it. Try this: >> >> >>> $ grep mkinitrd /var/log/packages/* >> >> >>> That's an "old chesnut" in the Slackware world, and yields this line >> >>> (among others): >> >>> /var/log/packages/mkinitrd-1.3.4-i486-3:sbin/mkinitrd >> >> >> Must be in thirteen the grep didn't find it >> >> > That is probably telling you the package is not installed. Other >> > checks: $ ls /var/log/packages/mkinitrd* >> >> > Also, >> > $ man mkinitrd >> >> > Or as root: >> > # which mkinitrd >> >> > It is strange that it is missing because mkinitrd is in the "a" package >> > group, and you should have opted to install almost everything in that >> > group. AFAIK, mkinitrd is the Slackware tool for making an initrd, >> > going back a long way in the version history. For Slackware 12.2, the >> > package was initially released in the "slackware/a" package group, as >> > version: mkinitrd-1.3.2-i486-4.tgz >> >> > It has been updated in the "patches/packages/" as of Dec 2008 to >> > version: mkinitrd-1.3.3-i486-1_slack12.2.tgz >> >> > This was noted in the Changelog: >> > <begin changelog snippet> >> > +--------------------------+ >> > Thu Dec 18 12:40:56 CST 2008 >> > patches/packages/mkinitrd-1.3.3-i486-1_slack12.2.tgz: >> > Fixed a few bugs in the previous mkinitrd package: >> > If a kernel version is requested with the -k option and modules are >> > needed to build the initrd, exit with an error if no matching >> > /lib/modules/ tree is >> > present. �Usually an incorrect kernel version was supplied. >> > Thanks to Eric Hameleers. >> > <snip> >> > <end changelog> >> >> I did a full install, the mkinitrd-xx is what I couldn't find >> the package was installed > > Hi, > > Head over to; http://www.linuxquestions.org/questions/slackware-14/ > > You'll find a lot of users along with helpful information. > > Gary (aka onebuck) The information looks good Thank you |