You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

the server definitely is pushing out the folders, as I do get the nfs server mounted to the computers var directory.

and i just loaded in Suse using the same exact folder..so I know it's good. i rebooted the nfs server to make sure it saw all the folder contents etc. tho i dont want suse on that pc, but just did it to verify that gnu/linux likes the card, computer,nfs server etc.

I used eric's / alien bob's script to rsync slack 10.2 and just copied over all the files and folders into my nfs export folder.

Ain't I supposed to point the installer to the folder "slackware" which is the one that contains all of the sections with appropriate packages a thru y?

The installer mentions to point it to where the 'a3' disk is, I dont even see that.

I could have sworn that I had tried that way b4 out of desperation, and I thought it had failed, but it's working right now as I type this LOL

thanks cw

in case any1 needs, or wants to add, or comments:

-boot up w/the slackware 10.2 cd - i used the bare.i (default kernel) for this install. you're kernel needs may be different, hit F2 for list of kernels.

-then log in as 'root'

-then type 'pcmcia' to activate the pcmcia port. slackware does work with the old 'yenta-socket' which gnu/linux has declared 'depracated' if you don't have a pcmcia slot, you don't need to do this part.

-then type 'network'. if you know your net-card's name, as I did you just type "P 8139too" where 8139too is my network card. The "P" means probe, I'm telling the installer to 'probe' card type '8139too' and if it see's it, then it will load modules for me.

,,,,If you don't know your NIC, you will need to put the 'network.dsk' onto a floppy disk prior to beginning this setup/install process. It's a boot disk with drivers, and will seek out your card for you. It's located in the 'bootdisks' section on all of the slakware mirrors. Slackware's documentation on how to get it on a diskette is accurate (not old) i found.

-then you enter slackware installer, add & format your swap.

-then add & format the '/' target position.

-add any other linux partitions.

-now your 'fstab' is setup for linux partitions.

-now back at the main installer screen, choose "NFS" as installation source. enter in the IP addresses as prompted. When prompted for folder location on the nfs server it's like cw said:

/folder-that-nfs-exported-on-your-lan/slackware-10.2/slackware

this assumes you used eric/alien bob's 'rsync' script that he has titled for slackware-current and changed it to do version 10.2 for you and it downloads the 'rysnc' slackware to the above location as shown.

you're looking for the 'nfs' to be mounted for you by slackware's nfs installer to /var/log/mount and you see the IP of the server echoed there on screen, that means no errors, and you tell the nfs mount wizard, no I dont need to re-enter my nfs info, I'm working.

- then choose your packages...and let her rip baby.

--final thoughts as I don't know if you can, or how to do the following:

*these days could we 'mount' our downloaded iso's on the nfs and use them?
*can we put cd's into the nfs server and copy over the contents.

if anyone has any input on these final thoughts post them here ? or link to separate thread

--final thoughts as I don't know if you can, or how to do the following:

*these days could we 'mount' our downloaded iso's on the nfs and use them?
*can we put cd's into the nfs server and copy over the contents.

if anyone has any input on these final thoughts post them here ? or link to separate thread

Hi,

I see no reason that prevents you from mounting a cd on the server and share the mount via the /etc/exports on the server.

You could even mount the iso on the loop device on the server.

I would probably copy the iso(s) to the HD on the server and share that mount point via /etc/exports.

The only problem I could foresee would be the cd mount share. When you have multiple install cd(s) the exchange physically for the cd would present a problem. You could use a jukebox cd (multiple cd platters) but the handling of cd exchange may trouble the install.

I really think the copy of iso(s) to the HD and mounting with the loop device the better option.

If you have GBs' of memory you could create a large ramdisk and copy the iso there to share as a mount point. The speed would be the advantage here.

As far as I know, the Slackware DVDs are not official, but are made the same way that the CDs are, so there should be no problems using them

About mounting CDs and ISOs and sharing them over NFS, I have done both, and have had no problems. In fact, that is how I install Slackware now, for the most part. I boot the target machine with the floppies, then do a NFS install against my server which is sharing out the mounted ISO of the latest Slackware-current.