Linked by Eugenia Loli on Fri 12th Dec 2003 06:53 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
More News »
Sponsored Links



By default Slackware's X uses the vesa drivers. Should work most of the time. To setup X you can use one of many config utilities such as xf86cfg (which btw is a completly gui utility)
And no it is not impossible to run the install in an xterm window. Early Slackware and Linux books used serial consoles hooked to another machine to take screenshots for use in publications.
Netconfig runs during the install processes. You can use it later to reconfigure the network or manually edit /etc/rc.d/rc.inetd.conf as most Slackers do. This is all in the (Dated) Slackware Essentials Book.
Now as for the "dependency-resolving package manager". The lack there of is half the the reason why us Slaackers use Slack. Lets try not to get into the hell that is RPM dependacies. Also for updating and installing packages you can use swaret which is included in /extra. It will do dependancy checking.