User Tools

Site Tools


vps_-_slackware

bluepisw.jpg

Slackware setup on SDF VPS service

login to vps3 or vps9.sdf.org

prompt> ssh uid@vps9.sdf.org

u/p is the same you use on the sdf cluster.
VPS Maintenance Shell for slackwarexx (205.166.94.xxx)
no stats collected.

[c] - Connect to your console
[l] - list your status
[r] - reset or start
[s] - Force Shutdown (not an OS shutdown)
[t] - toggle your Operating System
[i] - Switch your VPS ID (multiple VPS members only)
[x] - Clean install (destroys data)
[p] - Change your vps.sdf.org password
[u] - View current interface statistics
[U] - View all recorded interface statistics
[q] - Disconnect

[26-Jan-26 02:37:10] Command:

on the menu press t for toggle then choose slackware

again on the menu press x for clean install
wait for the system to copy over a clean install.

When you finally finish and it tells you to continue

press r to start then

press c for console

system should load…

once you see the slackware login:

login as root / r00tr00t

once you login run passwd and change the root password.

when you are done changing your password;

you need to blacklist and modprobe some modules

echo "blacklist 8139too" >> /etc/modprobe.d/blacklist.conf
echo "/sbin/modprobe 8139cp" >> /etc/rc.d/rc.modules.local
reboot
you may run netconfig or set thing up manually i will use netconfig in this example
as root run netconfig and it will ask you about hostname, domain, then it will ask you 
to either use static or dhcp since sdf only gives you one ip dhcp should be fine.
once that is done you need to edit /etc/rc.d/rc.inet1.conf and add the following
IFNAME[0]="eth126"
as if you notice when you run ifconfig -a it will show a eth126 so you have to tell the network script 
that you want to use eth126 and not eth0
once that is done you can either reboot or manually run sh /etc/rc.d/rc.inet1
and you should see:
root@vps:~# sh /etc/rc.d/rc.inet1
Polling for DHCP server on interface eth126:
eth126: adding address fe80::86c1:2161:1cfb:c782
eth126: waiting for carrier
eth126: carrier acquired
DUID 00:01:00:01:31:09:99:ea:aa:00:00:d1:09:29
eth126: IAID 00:d1:09:29
eth126: soliciting a DHCP lease
eth126: offered 205.166.94.xx from 205.166.94.24
eth126: leased 205.166.94.xx for 3600 seconds
eth126: adding route to 205.166.94.0/24
eth126: adding default route via 205.166.94.1
forked to background, child pid 1077
root@vps:~#

and you should be able to ping and nslookup

lets test:

root@vps:~# ping -c 1 google.com && nslookup google.com
PING google.com (142.250.73.78) 56(84) bytes of data.
64 bytes from pnseaa-am-in-f14.1e100.net (142.250.73.78): icmp_seq=1 ttl=120 time=1.65 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.656/1.656/1.656/0.000 ms
Server:         205.166.94.24
Address:        205.166.94.24#53

Non-authoritative answer:
Name:   google.com
Address: 142.250.73.78

root@vps:~#

now that networking is done we can go on to updating to slackware 15.0.

Upgrade to Slackware 15.0

vps_-_slackware.txt · Last modified: by cpet