In comp.os.linux.networking
(E-Mail Removed):
> I have 6 machines running Linux in 3 different versions. I have not
> networked with it, instead use MSWindows on peer to peer.
> But I have read parts of several MSCE books and this has helped me
> understand problems with transferring files to NTFS OS's. This is a
> major problem between and among different OS's and file systems. I am
> looking for a universal, maybe fat 16 but it is so limited.
You can use smb (samba) over the network, Linux can mount smbfs
natively. Fat32/vfat is the easiest for local data.
> I also want to know if you can download rpms or other drivers or
> applications like OpenOffice, or kernel patches or new kernels into a
> Win XP computer running under Win 2000 server and loading onto a Lexar
> jump drive in fat 16 and the work in Linux, or do they somehow get
> messed up for example Mac files will not read off a dos formated floppy
> unless you have a reader of Dos files installed in Mac. But so if you
> download to a fat16 jump drive will a driver work in Mac>>see I've got
> the same questions about Linux.
Should be no problem, text files need to be run through dos2unix
to be corrected.
> Or can you burn an ISO boot disk in Windows(?) and it work to boot
> Linux when the file was downloaded into the Windows(?) OS and file
> system?
Should be no problem.
> I would like a book that tells what to do in a kernel panic, or in
> repair mode in bootup or installation...never have found this
> documented and don't think it is in man pages.
There's no general advice for any problem that might happen, you
need to get used to the basics and learn how to debug problems.
Try a google search for "Linux rute tutorial".
> What I like about linux is its stability, it actually keeps the MSWin
> machines calmer and not crashing. I suspect this is because of the way
> Linux/Unix allocates resources of the computer, but I don't know.
> Maybe a good RHCE book would explain this.
Not really, one reason is it was developed by people who belief
in what they are doing.
> There is a lot to know about any OS or Server system, and you can't
> just screw up a network to try and figure if you can fix it. So how
Why not? Remove bash and try to fix the system. Look at problems
people are asking for on usenet and try to resolve them. Don't
reply until you are really sure you understood how to solve the
problem. Unsure why you used coln, can't really see how your
questions are network related.
[..]
BTW
Please read this before posting anything else:
http://cfaj.freeshell.org/google
--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo
(E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 340: We'll fix that in the next (upgrade, update,
patch release, service pack).