- GO INSTALLPKG INSTALL
- GO INSTALLPKG UPDATE
- GO INSTALLPKG SOFTWARE
- GO INSTALLPKG PASSWORD
GO INSTALLPKG PASSWORD
This allows you to block brute force password attacks on ssh.
GO INSTALLPKG INSTALL
Make sure to read the readme's and info files for any dependancies you need to install first.Ī strongly recommended package is DenyHosts. Sbopkg will allow you to sync with the repository, and allow you to search slackbuilds, and build them, downloading the source as required, and then install them.
To create and install packages not included with slackware, you may find sbopkg useful. See the slackware documentation project for info about setting up and running slackware.
GO INSTALLPKG SOFTWARE
httpd (apache), sendmail, mysql (mariadb), saslauthd once you have configured the various server software config files. You will also need to remember this change when merging config files after any further security updates to sshĪnd make executable the rc.
GO INSTALLPKG UPDATE
If you want to be able to log in directly as root (with password) you will need to update /etc/ssh/sshd_config by changing the #PermitRootLogin prohibit-password line to Since security updates which came out in early 2016, the default for sshd is to block root password logins. Rsync -azP -delete ::/pub/slackware/slackware-14.2/patches/packages/ /slackdisk/patches/packagesĪt any later time which will fetch all the security updated packages to your local drive, where you can then review (and install) them. Now to format the new partition ext3 (for ext2, just miss out the -j )
Finally press w to write the changes and quit fdisk. Accept the default start position and end position, then press t and then 2 and then 82 to set the second partition as a swap file. accept the default start position, and for the size + XGB where X is (storage purchased) - (2 x system RAM) in GB. type fdisk -l to check the drive of the virtual machine. To avoid having to sudo everything type sudo su. partitioning drives and obtaining the install files Partitioning the drive When you are happy with the virtual disk allocation, you can get back to the xen-shell prompt and continue.įor this install we are assuming at least 10GB of space allocated to the first virtual disk /dev/xvda To view and change the arrangement of virtual drives made up out of your purchased disk space. This installation guide ignores /dev/xdb entirely. xvda (the main amount) and xvdb (an amount equal to the ram you have allocated) for swap. Log in to xen shell (using putty from windows, or ssh from linux or mac)īy default bitfolk allocate two virtual disks for your virtual machine. If you have less than 15gb or more of storage you will not be able to retain the installation packages on your virtual drive, there simply isn't enough space. That is left to you in the usual slackware way. The space used can obviously be reduced by not installing things like X, or servers that are not going to be used, but this how-to doesn't assume what you will or won't use. The default recommended install for slackware is everything except for kdei, ref for which you usually just install your locale. Installing Slackware 14.2 (32bit) on a bitfolk vps Before you start 1.7.3 Protecting your ssh login from hackers. Configuring grub and network so pygrub can boot your os Recording network settings and changing init to handle the xen console 1.3.3 Because we are not using the slackware main setup installer, we will have to manually do a little bit of extra configuration. 1.3.2 Setting up the file structure and getting the install files. partitioning drives and obtaining the install files 1 Installing Slackware 14.2 (32bit) on a bitfolk vps. This was done on my older sw 12.2 installation which I always *experiment* on before I actually do it on my main install.Īs a footnote, I had been using the 3 version 3.0 oracle (or is it Sun?) and now I have the newer Apache Open Office 3.4 - but first I used Kpackage to remove the 3.0 PACKAGE that I had installed from some time ago, then I proceeded with the Apache OO version 3. I use slackware 12.2 on my main box as I prefer KDE 3.5.10 to KDE 4.x and I had to update my glibc but other than that, it was just a matter of getting those rpm's converted to tgz mainly. I had missed this part myself and had also been launching directly from /opt/./.soffice but just saw a youtube video of a guy doing this on a Vector Linux box and he simply converted the 'redhat' menu rpm to tgz and installed that and it gave him his /usr/bin/3 files he needed AND it even put the links in his Kmenu iirc - you should be able to figure it out. Sure, now you need to go back to where you unpacked the tar.gz and find the dir named desktop-integration, here is ls
0 kommentar(er)
