mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
gferg
parent
5092c94eaf
commit
d621b5d6c0
|
|
@ -44,7 +44,7 @@ Revision Control System
|
|||
<author>Al Dev (Alavoor Vasudevan)
|
||||
<htmlurl url="mailto:alavoor@yahoo.com"
|
||||
name="alavoor@yahoo.com">
|
||||
<date>v21.3, 15 July 2001
|
||||
<date>v21.4, 25 Aug 2001
|
||||
<abstract>
|
||||
This document is a "practical guide" to very quickly setup CVS/RCS source code
|
||||
control system. This document has custom shell scripts that are wrappers
|
||||
|
|
@ -224,26 +224,61 @@ and give read, write access to Unix group/user.
|
|||
Also make sure that the directory name of CVSROOT does not contain
|
||||
any blank spaces. For example CVSROOT should not be like '/home/my rootcvs'.
|
||||
<CODE>
|
||||
export CVSROOT=/home/cvsroot
|
||||
mkdir $CVSROOT
|
||||
chmod o-rwx $CVSROOT
|
||||
chmod ug+rwx $CVSROOT
|
||||
</CODE>
|
||||
Now, change the group of $CVSROOT to the group-name of users who want to use CVS sytem.
|
||||
<CODE>
|
||||
chgrp users $CVSROOT
|
||||
</CODE>
|
||||
To initialize the CVS repository and to put in source code files do:
|
||||
<CODE>
|
||||
cvs init
|
||||
bash$ su - root
|
||||
bash# export CVSROOT=/home/cvsroot
|
||||
bash# groupadd --help
|
||||
bash# groupadd cvs
|
||||
bash# useradd --help
|
||||
bash# useradd -g cvs -d /home/cvsroot cvs
|
||||
|
||||
bash# ls -ld $CVSROOT ... (you should see the listing)
|
||||
bash# chmod o-rwx $CVSROOT
|
||||
bash# chmod ug+rwx $CVSROOT
|
||||
|
||||
#To initialize the CVS repository and to put in source code files do:
|
||||
bash# cvs init
|
||||
|
||||
# Add the unix users to the cvs group. Create supplementary groups for users.
|
||||
# Note that you MUST not put any blank spaces after comma seperating the
|
||||
# group names in -G option.
|
||||
# In example below user tom belongs to groups cvs, users and staff and user
|
||||
# johnson belongs to group cvs only.
|
||||
bash# usermod --help
|
||||
bash# usermod -G cvs some_unix_username
|
||||
bash# usermod -G cvs,users,staff tom
|
||||
bash# usermod -G cvs,users,staroffice billclinton
|
||||
bash# usermod -G cvs johnson
|
||||
bash# exit .... (logout of root superuser mode)
|
||||
|
||||
# Login as a user and import files into cvs....
|
||||
bash$ su - billclinton
|
||||
bash$ export EDITOR=/bin/vi
|
||||
bash$ export CVSROOT=/home/cvsroot
|
||||
bash$ export CVSREAD=yes
|
||||
|
||||
# Change directory is a must
|
||||
cd $HOME/my_source_code_dir
|
||||
bash$ cd $HOME/my_source_code_dir
|
||||
|
||||
# Must give vendor tag and revision tag
|
||||
cvs import my_source_code_dir V1_0 R1_0
|
||||
cvs import my_source_code_dir Vendor1_0 Rev1_0
|
||||
|
||||
# For example I did:
|
||||
bash$ cd $HOME/foobar
|
||||
bash$ cvs import foobar Vendor1_0 Rev1_0
|
||||
|
||||
# A sample testing and verification:
|
||||
bash$ cd $HOME/foobar
|
||||
bash$ cvs checkout myfoo.java
|
||||
</CODE>
|
||||
|
||||
<bf>TROUBLESHOOTING:</bf> When doing checkout it says module is unknown. It
|
||||
is a common mistake not to change directory while doing cvs import. You
|
||||
<bf><it>MUST change directory</it></bf> to the
|
||||
source-code-directory and then do cvs import. For example:
|
||||
<code>
|
||||
bash$ cd $HOME/foobardir
|
||||
bash$ cvs import foobardir Vendor1_0 Rev1_0
|
||||
</code>
|
||||
<!--
|
||||
*******************************************
|
||||
************ End of Section ***************
|
||||
|
|
@ -824,23 +859,24 @@ will look like local folder on MS Windows. See the next section for
|
|||
<p>
|
||||
It is <bf>VERY STRONGLY recommended</bf> that you use
|
||||
<url name="Samba(on cdrom samba*.rpm)" url="http://www.samba.org">
|
||||
and a PC X Server on MS Windows 95/NT.
|
||||
and a VNC viewer (or PC X Server) on MS Windows 95/NT.
|
||||
With samba the Unix/Linux CVS server will be like a <bf>file server</bf>.
|
||||
By using Samba the remote directory on Unix
|
||||
will look like a local folder on MS Windows on the local disk.
|
||||
Install samba*.rpm on Unix/Linux server(which has the CVS repository) and install
|
||||
the PC X server on
|
||||
MS Windows 95/NT/2000 desktop. Using a PC X server you can easily log on to the
|
||||
the VNC viewer (or PC X server) on
|
||||
MS Windows 95/NT/2000 desktop. Using a VNC (or PC X server) you can easily log on to the
|
||||
Unix box and check-out/check-in the files. And you can use tools like
|
||||
Java Visual Cafe or Java JBuilder on MS Windows to edit the files located in Unix/Linux
|
||||
folder(via samba).
|
||||
After editing, you can check-in the files to Unix thru PC X-server.
|
||||
After editing, you can check-in the files to Unix through VNC or PC X-server.
|
||||
|
||||
Advantages of using CVS on Linux/Unix via MS Windows are:
|
||||
<itemize>
|
||||
<item> Only one single Linux File server (CVS server) can serve many MS Windows clients.
|
||||
<item> A Linux file server (CVS) is very robust, secure and reliable
|
||||
<item> Only one UPS (uninterrupted power supply) battery is required for a linux server.
|
||||
<item> Linux can serve as MS Windows folder through Samba package.
|
||||
<item> A Linux file server (CVS) supports centralised backups via tools like
|
||||
<url name="Arkeia, Bru" url="http://www.aldev.8m.com">
|
||||
mirrors at
|
||||
|
|
@ -865,8 +901,17 @@ and dust free. Small room keeps the cooling/heating costs down.
|
|||
<item> A Linux file server (CVS) provides security via Unix groups and user id authentication
|
||||
</itemize>
|
||||
|
||||
The following PC X servers are available:
|
||||
The best tool for remote access is VNC. The VNC is lightweight and is
|
||||
much better than the PC X servers. <bf><it>The VNC is very strongly recommended
|
||||
over PC X server</it></bf>. The remote access methods available are:
|
||||
<itemize>
|
||||
<item>VNC (Virtual Network Computing) at <url url="http://www.uk.research.att.com/vnc">
|
||||
VNC is not an X-server but can display the remote Unix on Windows.
|
||||
VNC is the best tool in the market for remote access, it is very lightweight and
|
||||
is a very powerful software.
|
||||
|
||||
<p>
|
||||
The following PC X servers are available:
|
||||
<item> Low cost, best and small size (3 MB) <url url="http://www.microimages.com"> and
|
||||
click on "X-Server (MI/X) for Windows"
|
||||
<item> Humming bird eXceed 14 MB <url url="http://www.hummingbird.com">
|
||||
|
|
@ -881,10 +926,6 @@ There are more than 2 dozen vendors for X servers for Windows:
|
|||
University resources:
|
||||
<item> University listings <url url="http://www.et.byu.edu/support/pc/xterm.html">
|
||||
<item> Floppy based PC "X server" <url url="http://mirriwinni.cse.rmit.edu.au/~brad/co338/sem1/floppy.html">
|
||||
|
||||
<p> Alternatives to X servers:
|
||||
<item>VNC (Virtual Network Computing) at <url url="http://www.uk.research.att.com/vnc">
|
||||
VNC is not an X-server but can display the remote Unix on Windows.
|
||||
</itemize>
|
||||
<!--
|
||||
*******************************************
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
<title>LILO mini-HOWTO
|
||||
<author>Miroslav "Misko" Skoric, <tt/m.skoric@eunet.yu/
|
||||
<date>v3.5, 13 May 2001
|
||||
<date>v3.6, 26 August 2001
|
||||
<abstract>
|
||||
<nidx>linux loader windows nt 2000 boot</nidx>
|
||||
LILO is the most used <bf/Li/nux <bf/Lo/ader for the x86 flavour of
|
||||
|
|
@ -25,7 +25,7 @@ This version of Lilo mini-HOWTO is based on work of Cameron Spitzer
|
|||
(<tt>cls@truffula.sj.ca.us</tt>) and Alessandro Rubini
|
||||
(<tt>rubini@linux.it</tt>). There is also a contribution from Tony Harris
|
||||
(<tt>tony@nmr.mgh.harvard.edu</tt>). Well, I have used materials from
|
||||
the authors mentioned - without changes - and added some pointers
|
||||
the authors mentioned - <bf>without changes</bf> - and added some pointers
|
||||
related to configuring LILO for using with Windows NT and Windows 2000.
|
||||
More detailed information about the activation of Windows NT/2000 from LILO
|
||||
menu, you may find in <tt>Linux+WinNT</tt> mini-HOWTO.
|
||||
|
|
@ -407,7 +407,7 @@ kernel image nothing special is needed, but you need version 18 or
|
|||
newer of Lilo. If your installation is older, you should upgrade your
|
||||
Lilo package.
|
||||
|
||||
<sect1>How to boot Windows NT from Lilo menu
|
||||
<sect1>How to boot Windows NT from 'LILO boot:' menu
|
||||
|
||||
<p>
|
||||
Here I will give you an order of routines you have to do if you want
|
||||
|
|
@ -491,13 +491,14 @@ to have both Linux and NT entries under Lilo menu:
|
|||
|
||||
</itemize>
|
||||
|
||||
<sect1>How to boot Windows 2000 from Lilo menu
|
||||
<sect1>How to boot Windows 2000 from 'LILO boot:' menu
|
||||
|
||||
<p>
|
||||
Well, you may use the same procedure as described above.
|
||||
I suggest you to read <tt>Linux+WinNT</tt> mini-HOWTO that also talks
|
||||
about booting Windows 2000, which is installed on the same part of disk
|
||||
where Windows NT was <em>before</em>. There you'll find many useful details.
|
||||
where Windows NT was <em>before</em>. There you'll find many useful details
|
||||
regarding various Linux+WinNT/2000/98 combinations.
|
||||
|
||||
|
||||
<sect>Installing <tt/hdc/ to Boot as <tt/hda/ and Using <tt>bios=</tt>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
<title>Linux+WindowsNT mini-HOWTO
|
||||
<author>Miroslav "Misko" Skoric, <tt/m.skoric@eunet.yu/
|
||||
<date>v2.6, 13 May 2001
|
||||
<date>v2.7, 26 August 2001
|
||||
<abstract>
|
||||
<nidx>linux loader windows nt 2000 boot</nidx>
|
||||
This mini-HOWTO covers some ways on how to install both Linux
|
||||
|
|
@ -666,6 +666,70 @@ process shouldn't change too much, if any.
|
|||
</itemize>
|
||||
|
||||
|
||||
<sect>HOW TO INSTALL WINDOWS 2000 <em>BESIDE</em> LINUX AND WINDOWS 98
|
||||
|
||||
<p>
|
||||
<em>Notice: When I say 'beside Linux and Windows 98', I mean of
|
||||
Linux and Windows 98 that <bf>already</bf> work together, so they were
|
||||
installed earlier, <bf>before</bf> we made a decission to add
|
||||
Windows 2000. One of the machines I use at work, has both Linux
|
||||
and Win98. They both load from under LILO menu.
|
||||
</em>
|
||||
|
||||
<p>
|
||||
Actually, it is not a very big problem to install Windows 2000 on a
|
||||
computer where another Windows is running. In my case, it is Windows 98
|
||||
so I just put 2000's CD into the drive. After it recognized that an
|
||||
'older' version of Windows was running on my machine, it offered me
|
||||
either to upgrade it to 2000 or to install W2k as the 'clean'
|
||||
installation. At first, I tried to upgrade my Windows 98 to W2k, in
|
||||
order to get a very similar combination that I have at home (described
|
||||
in previous chapter). But, some hardware and software compatibility
|
||||
issues were reported (I mean, some of my components wouldn't stay
|
||||
fully operational if I just did an upgrade).
|
||||
|
||||
<p>
|
||||
When saw that, I considered to try the 'fresh' installation of W2k,
|
||||
<em>beside</em> Win98 and Linux. Happily, I recently installed another
|
||||
HD into the box, so I did not need to handle the first disk, where Win98
|
||||
and Linux were living. Actually, the main reason to add the second disk
|
||||
was that the first one got almost full. If I wanted to install the third
|
||||
operating system on the first disk, I'd have to clean it well. So, when
|
||||
W2k's Setup asked for the location to be installed, I told it to use
|
||||
the second disk, repartition it and format it as the NTFS file system
|
||||
(just to mention that my Win98 was FAT32 and Linux was ext2).
|
||||
|
||||
<p>
|
||||
After an hour or so, W2k's installation was finished. During the setup
|
||||
procedure, it re-started the system a couple of times. When it was
|
||||
about to do that for the first time, I was curious if it would re-write
|
||||
the MBR, where LILO resides (actually, in the previous chapter, I have
|
||||
mentioned that W2k's installation was likely to re-write the MBR).
|
||||
Interestingly, it did not do that this time, so I continued to see
|
||||
'LILO boot:' on the screen. But, a *new* thing has appeared after LILO:
|
||||
the Windows 2000 boot loader, that in turn offered not only to load W2k but
|
||||
a 'Windows' (ie. my old Win98) too.
|
||||
|
||||
<p>
|
||||
Well, depending on which operating system I like to start, the procedure
|
||||
might slightly differ, but it is easy. No problem at all. For example:
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
|
||||
<item>If I like to load my Linux, then LILO boot is the "cross-road".
|
||||
At this point, the 'linux' entry should either be chosen or set as
|
||||
default in <bf>/etc/lilo.conf</bf>;
|
||||
|
||||
<item>If I like to load Windows, then the other entry under LILO
|
||||
boot should either be chosen or set to be default. After it is done,
|
||||
Windows 2000 boot loader should appear on the screen. On that point,
|
||||
I have two choices: W2k and W98. The rest is easy, both Windozes
|
||||
start from there happily.
|
||||
|
||||
</itemize>
|
||||
|
||||
|
||||
<sect>FURTHER INFORMATION
|
||||
|
||||
<p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue