Theres a separate article dedicated to doing a full system upgrade which you should definitely read first. Alors que les systèmes BSD comme DragonFly BSD ont la réputation d’être réservés aux serveurs, ils peuvent servir de bureau pour ceux qui sont à l’aise avec les concepts Unix, en particulier pour les personnes qui ont de l’expérience avec les distros Linux techniques comme Slackware, Gentoo, ou Arch. Is there a better way to make this happen? (without upgrading the base system? it has so many finely tuned things running that I don't want to mess with the rest of the setup). slackpkg update slackpkg install-new slackpkg upgrade-all slackpkg clean-system It is always recommended to read the latest ChangeLogs and UPGRADING.TXT (found on the HTTP/ FTP mirrors for each version) before doing any major system upgrades. Having scoured the net for later Samba binaries for Slackware 12 and gotten precisely nowhere, I decided that maybe I could compile the blessed thing. My suggestion is, dont be scared from the console, its your friend. root/slackware/a/tar-.tgz installpkg /root/slackware/a/xz-.tgz. The installpkg, removepkg, and upgradepkg utilities all take the name of an application as an argument and install, remove, or upgrade them, respectively. You might find that you need to refer to a few things after the upgrade process is. One really needs 'pkg install', 'pkg upgrade' and 'pkg remove'. Apart from pkgtool, Slackware has tools that will help you install, remove, and upgrade packages. The Samba wiki has a couple of hacks for the registry and also seems to suggest a version later than 3.3 (though not in so many words) Using the package manager is quite easy, I have never felt a need for a pkg GUI. I'm a newbie on Slackware (I usually dwell in Ubuntu) so I may be going about this the wrong way but this is what I've done so far: If it is, it's a simple one liner, but if not, it's simple enough to either write a wrapper script or copy the script to /usr/local/sbin/mkinitrd_command_generator.sh and make the necessary changes.I'm trying to upgrade the Samba server on a Slackware 12 box to serve as PDC for Windows 7 32bit machines (it now has a 3.0.3 and does the job for Win XP machines, but 7 refuses to join the domain - I'm posting this after having tried a few dozen hacks on the windows registry). installpkg(8) handles installation of new packages. The administrator of that machine can examine the output of that command and determine if it is correct after reading the theory about how the initrd needs to be built. Also, the ability to upgrade packages is only offered through the command line utilities. Mkinitrd -c -k 3.14.10-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L It should emit a string like this (your system will probably give different # /usr/share/mkinitrd/mkinitrd_command_generator.sh -r The following command will save you the headache of figuring this out all The script will recognize your kernel version, root partitionĪnd filesystem, it will find out if you are using LUKS and/or LVM and willĭetermine what kernel modules your initrd needs to mount the root filesystem. Your Slackware configuration and make a smart suggestion about the 'mkinitrd'Ĭommand you have to type in order to create an initrd.gz with all the bells The mkinitrd package in Slackware 14.0 (and on) ships with a script called After all of that it shows you the /usr/share/mkinitrd/mkinitrd_command_generator.sh command which you can use to generate the command that you need to build the initrd. README_CRYPT.TXT in the root of the distribution describes how to do this, step by step, including the relevant theory so you know what you're doing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |