Unetbootin is a sweet Open Source utility. It allows you to boot into an os without having to burn a cd. I've been using it for CentOS 5.6 installs. From the unetbootin home page-
http://unetbootin.sourceforge.net/
UNetbootin allows you to create bootable Live USB drives for Ubuntu, Fedora, and other Linux distributions without burning a CD. It runs on Windows, Linux, and Mac OS X. You can either let UNetbootin download one of the many distributions supported out-of-the-box for you, or supply your own Linux .iso file if you've already downloaded one or your preferred distribution isn't on the list.
UNetbootin can create a bootable Live USB drive, or it can make a "frugal install" on your local hard disk if you don't have a USB drive. It loads distributions either by downloading a ISO (CD image) files for you, or by using an ISO file you've already downloaded.
"The unexamined life is not worth living." --Socrates--
Saturday, July 30, 2011
Thursday, July 21, 2011
Screen
The GNU Screen command is a powerful and versatile utility. It allows system administrators, developers, and everybody else to work more efficiently. The following article by Steve ‘Ashcrow’ Milner and Anderson Silva provides a very good explanation of what it does and how to use it.
http://magazine.redhat.com/2007/09/27/a-guide-to-gnu-screen/
The same way tabbed browsing revolutionized the web experience, GNU Screen can do the same for your experience in the command line. GNU Screen allows you to manage several interactive shell instances within the same “window.” By using different keyboard shortcuts, you are able to shuffle through the shell instances, access any of them directly, create new ones, kill old ones, attach and detach existing ones.
Instead of opening up several terminal instances on your desktop or using those ugly GNOME/KDE-based tabs, Screen can do it better and simpler.
Not only that, with GNU Screen, you can share sessions with others and detach/attach terminal sessions. It is a great tool for people who have to share working environments between work and home.
By adding a status bar to your screen environment, you are able to name your shell instances on the fly or via a configuration file called .screenrc that can be created on the user’s home directory.
Installing
Installing Screen on a Fedora or Red Hat® Enterprise Linux® 5 system is quite easy with yum, assuming you have sudo access.
Login as root:
su # enter root password
Use yum to install it:
yum install screen
Enter your password. After a few minutes (depending on your network connection), Screen will be installed. But before you start playing around with it, let’s look at how to do some basic configuration.
Customizing the configuration file
Screen keeps its configuration file in the same vein that many applications do: in a dot file in your user’s home directory. This file is aptly named .screenrc. In my experience, most people use ~/.screenrc to do two things:
Make a hardstatus line. This is basically a line at the bottom of the screen that lists your current terminal and all opened ones. It can also display the system clock and the hostname.
Default screens on startup. It’s quite nice to have your IRC connection, mail client, and default SSH connections auto-start for you!
The lines below are numbered for reference. Your config file should not have numbered lines.
1 hardstatus alwayslastline
2 hardstatus string '%{= kG}[ %{G}%H %{g}][%= %{=kw}%?%-Lw%?%{r}(%{W}%n*%f%t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}][%{B}%Y-%m-%d %{W}%c %{g}]'
3
4 # Default screens
5 screen -t shell1 0
6 screen -t shell2 1
7 screen -t server 2 ssh me@myserver
On lines 1 and 2, you are setting the hardstatus. Line 1 makes the hardstatus always show up as the last line. Line 2 is about what will be shown in the hardstatus line. In this case you will see something like so at the bottom:
As you change screens, you will see the parentheses move around the active screen.
Line 4 is a comment, as it starts with #. Lines 5-7 are all screen statements in the following format:
screen -t NameOfScreen ScreenNumber ShellCommand
Shortcuts
The following are some of the most used shortcuts that lets you navigate through your screen environment. Note that unless modified by your .screenrc, by default every screen shortcut is preceded by Ctrl+a. Note that these shortcuts are case-sensitive.
0 through 9 – Switches between windows
Ctrl+n – Switches to the next available window
Backspace – Switches to the previous available
Ctrl+a – Switches back to the last window you were on
A – Changes window session name
K – Kills a window session
c – Creates a new window
[ - Then use arrows to scroll up and down terminal
Find out about more shortcuts in Screen's man pages. In your terminal, run: man screen.
Sharing a session with others
Another great application of Screen is to allow other people to login to your station and to watch the work you are doing. It is a great way to teach someone how to do things on the shell.
Setup to allow screen to be shared
As root: chmod u+s /usr/bin/screen (Screen has to be SUID if you want to share a term between two users.)
Note: SUID allows an executable to be run by the owner of that file, instead of with the user's own permission. There are some security concerns when doing this, so use this tip at your own discretion.
chmod 755 /var/run/screen
Log out of root, and run Screen as the user who is going to share the session:
screen
Press Ctrl+a, then type :multiuser on and press Enter.
Press Ctrl+a, then type :acladd steve (”steve” is the username of the person who will connect to your screen session).
Connecting to the shared screen:
SSH into the workstation that you are going to watch the screen session on.
On your terminal type: screen -x anderson/ (”anderson” is the username of the person who is sharing the screen session. You need the / at the end.).
And now both users (from the host and guest) will be sharing a screen session and can run commands on the terminal.
Working from multiple locations
Let's say you have a screen session open at work with X number of windows on it. Within those screens you may be running an IRC client, an SSH connection to the web server, and your favorite text-based email client. It's 5 p.m. and you have to go home, but you still have work left to do.
Without Screen you would probably go home, VPN into your company's network, and fire up all the shells you need to keep working from home. With Screen, life gets a little easier.
You can simply SSH into your workstation at work and list your available screen sessions with the command:
screen -ls
And connect to the sessions you were running at work with the command:
screen -x screen_session_name
This way screen will let you pick things up exactly from where you left off.
Applications to make Screen your window manager
Now that you have seen what Screen can do for you, you probably are wondering how to make it your main interaction point, like a terminal window manager.
Let's start with IRC, a very common and popular chat system. Instead of using a graphical client like Pidgin, install Irssi. Irssi sports a slick console interface, tons of add-ons and scripts, and can be enhanced with Perl. It's even theme-able!
Another important part of any user's setup is email. Today most people use graphical clients such as Thunderbird, Evolution, or Sylpheed. My favorite client happens to run in a terminal: Mutt. While Mutt isn't the easiest client in the world to set up, it sure is a joy to use. You can even use your favorite console text editor for doing emails.
Speaking of favorite text editors, there is a good chance that you work on some code projects or configurations. Instead of using gedit/kedit or powering up a heavy IDE such as Eclipse, you can pick up on Vim. Vim is a powerful text editor which, as is stated on the Vim website, could be considered an entire IDE in itself and sports syntax coloring in over 200 programming languages. If Vim doesn't fit your style, there is always emacs, nano, or JOE.
Now all you need you need to do is edit your ~/.screenrc to meet your needs.
My ~/.screenrc looks like the following:
1 hardstatus alwayslastline
2 hardstatus string '%{= kG}[ %{G}%H %{g}][%= %{=
kw}%?%-Lw%?%{r}(%{W}%n*%f %t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}][%{B}
%Y-%m-%d %{W}%c %{g}]‘
3
4 # Default screens
5 screen -t shell1 0
6 screen -t shell2 1
7 screen -t server 2 sh me@myserver
8 screen -t IRC 7 irssi
9 screen -t Mail 8 mutt
http://magazine.redhat.com/2007/09/27/a-guide-to-gnu-screen/
The same way tabbed browsing revolutionized the web experience, GNU Screen can do the same for your experience in the command line. GNU Screen allows you to manage several interactive shell instances within the same “window.” By using different keyboard shortcuts, you are able to shuffle through the shell instances, access any of them directly, create new ones, kill old ones, attach and detach existing ones.
Instead of opening up several terminal instances on your desktop or using those ugly GNOME/KDE-based tabs, Screen can do it better and simpler.
Not only that, with GNU Screen, you can share sessions with others and detach/attach terminal sessions. It is a great tool for people who have to share working environments between work and home.
By adding a status bar to your screen environment, you are able to name your shell instances on the fly or via a configuration file called .screenrc that can be created on the user’s home directory.
Installing
Installing Screen on a Fedora or Red Hat® Enterprise Linux® 5 system is quite easy with yum, assuming you have sudo access.
Login as root:
su # enter root password
Use yum to install it:
yum install screen
Enter your password. After a few minutes (depending on your network connection), Screen will be installed. But before you start playing around with it, let’s look at how to do some basic configuration.
Customizing the configuration file
Screen keeps its configuration file in the same vein that many applications do: in a dot file in your user’s home directory. This file is aptly named .screenrc. In my experience, most people use ~/.screenrc to do two things:
Make a hardstatus line. This is basically a line at the bottom of the screen that lists your current terminal and all opened ones. It can also display the system clock and the hostname.
Default screens on startup. It’s quite nice to have your IRC connection, mail client, and default SSH connections auto-start for you!
The lines below are numbered for reference. Your config file should not have numbered lines.
1 hardstatus alwayslastline
2 hardstatus string '%{= kG}[ %{G}%H %{g}][%= %{=kw}%?%-Lw%?%{r}(%{W}%n*%f%t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}][%{B}%Y-%m-%d %{W}%c %{g}]'
3
4 # Default screens
5 screen -t shell1 0
6 screen -t shell2 1
7 screen -t server 2 ssh me@myserver
On lines 1 and 2, you are setting the hardstatus. Line 1 makes the hardstatus always show up as the last line. Line 2 is about what will be shown in the hardstatus line. In this case you will see something like so at the bottom:
As you change screens, you will see the parentheses move around the active screen.
Line 4 is a comment, as it starts with #. Lines 5-7 are all screen statements in the following format:
screen -t NameOfScreen ScreenNumber ShellCommand
Shortcuts
The following are some of the most used shortcuts that lets you navigate through your screen environment. Note that unless modified by your .screenrc, by default every screen shortcut is preceded by Ctrl+a. Note that these shortcuts are case-sensitive.
0 through 9 – Switches between windows
Ctrl+n – Switches to the next available window
Backspace – Switches to the previous available
Ctrl+a – Switches back to the last window you were on
A – Changes window session name
K – Kills a window session
c – Creates a new window
[ - Then use arrows to scroll up and down terminal
Find out about more shortcuts in Screen's man pages. In your terminal, run: man screen.
Sharing a session with others
Another great application of Screen is to allow other people to login to your station and to watch the work you are doing. It is a great way to teach someone how to do things on the shell.
Setup to allow screen to be shared
As root: chmod u+s /usr/bin/screen (Screen has to be SUID if you want to share a term between two users.)
Note: SUID allows an executable to be run by the owner of that file, instead of with the user's own permission. There are some security concerns when doing this, so use this tip at your own discretion.
chmod 755 /var/run/screen
Log out of root, and run Screen as the user who is going to share the session:
screen
Press Ctrl+a, then type :multiuser on and press Enter.
Press Ctrl+a, then type :acladd steve (”steve” is the username of the person who will connect to your screen session).
Connecting to the shared screen:
SSH into the workstation that you are going to watch the screen session on.
On your terminal type: screen -x anderson/ (”anderson” is the username of the person who is sharing the screen session. You need the / at the end.).
And now both users (from the host and guest) will be sharing a screen session and can run commands on the terminal.
Working from multiple locations
Let's say you have a screen session open at work with X number of windows on it. Within those screens you may be running an IRC client, an SSH connection to the web server, and your favorite text-based email client. It's 5 p.m. and you have to go home, but you still have work left to do.
Without Screen you would probably go home, VPN into your company's network, and fire up all the shells you need to keep working from home. With Screen, life gets a little easier.
You can simply SSH into your workstation at work and list your available screen sessions with the command:
screen -ls
And connect to the sessions you were running at work with the command:
screen -x screen_session_name
This way screen will let you pick things up exactly from where you left off.
Applications to make Screen your window manager
Now that you have seen what Screen can do for you, you probably are wondering how to make it your main interaction point, like a terminal window manager.
Let's start with IRC, a very common and popular chat system. Instead of using a graphical client like Pidgin, install Irssi. Irssi sports a slick console interface, tons of add-ons and scripts, and can be enhanced with Perl. It's even theme-able!
Another important part of any user's setup is email. Today most people use graphical clients such as Thunderbird, Evolution, or Sylpheed. My favorite client happens to run in a terminal: Mutt. While Mutt isn't the easiest client in the world to set up, it sure is a joy to use. You can even use your favorite console text editor for doing emails.
Speaking of favorite text editors, there is a good chance that you work on some code projects or configurations. Instead of using gedit/kedit or powering up a heavy IDE such as Eclipse, you can pick up on Vim. Vim is a powerful text editor which, as is stated on the Vim website, could be considered an entire IDE in itself and sports syntax coloring in over 200 programming languages. If Vim doesn't fit your style, there is always emacs, nano, or JOE.
Now all you need you need to do is edit your ~/.screenrc to meet your needs.
My ~/.screenrc looks like the following:
1 hardstatus alwayslastline
2 hardstatus string '%{= kG}[ %{G}%H %{g}][%= %{=
kw}%?%-Lw%?%{r}(%{W}%n*%f %t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}][%{B}
%Y-%m-%d %{W}%c %{g}]‘
3
4 # Default screens
5 screen -t shell1 0
6 screen -t shell2 1
7 screen -t server 2 sh me@myserver
8 screen -t IRC 7 irssi
9 screen -t Mail 8 mutt
Saturday, July 16, 2011
CentOS
I've been building a number of servers lately. The operating system is CentOS, the Community Enterprise Operating system. CentOS is open source, free, solid, and basically Redhat Enterprise Linux without a price tag. Here's the description from the website-
CentOS is an Enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor. CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. (CentOS mainly changes packages to remove upstream vendor branding and artwork.) CentOS is free.
CentOS is developed by a small but growing team of core developers. In turn the core developers are supported by an active user community including system administrators, network administrators, enterprise users, managers, core Linux contributors and Linux enthusiasts from around the world.
CentOS is an Enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor. CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. (CentOS mainly changes packages to remove upstream vendor branding and artwork.) CentOS is free.
CentOS is developed by a small but growing team of core developers. In turn the core developers are supported by an active user community including system administrators, network administrators, enterprise users, managers, core Linux contributors and Linux enthusiasts from around the world.
Saturday, July 2, 2011
Dokuwiki
Dokuwiki, http://www.dokuwiki.org/dokuwiki, is a great open source wiki application. It's built using PHP and is great for small to medium sized workgroups.
DokuWiki is a standards compliant, simple to use Wiki, mainly aimed at creating documentation of any kind. It is targeted at developer teams, workgroups and small companies. It has a simple but powerful syntax which makes sure the datafiles remain readable outside the Wiki and eases the creation of structured texts. All data is stored in plain text files – no database is required.
Download Dokuwiki here-http://www.splitbrain.org/projects/dokuwiki
***************************************
Dokuwiki install on Ubuntu 11.04
Follow instructions here-http://www.dokuwiki.org/install:ubuntu
dowloaded dokuwiki-2011-05-25a.tgz to //home/yourname/Downloads
sudo su
cd /opt/lampp/htdocs
cp /home/yourname/Downloads/dokuwiki-2011-05-25a.tgz .
tar xvf dokuwiki-2011-05-25a.tgz
sudo mv dokuwiki-2011-05-25a.tgz dokuwiki
--Before continuing, you must identify the user and group running your apache process--
One way is to run this command-
egrep -i 'user|group' /opt/lampp/etc/httpd.conf and look for the values of:
User daemon
Group daemon
Using the User:Group values, change the dokuwiki permissions-
chown -R daemon:daemon dokuwiki(www-data:www-data or nobody: could also be used)
chmod -R g+w dokuwiki
Start lampp if not running
/opt/lampp/./lampp start
Test if wiki is running-
http://127.0.0.1/dokuwiki/doku.php
Finish installing-
http://127.0.0.1/dokuwiki/install.php
Wiki Name-My Ubuntu Wiki
Super User:jdoe
Real Name:John Doe
Email:myname@gmail.com
Password:password
***********************************
Dokuwiki install on Fedora Linux
How to install dokuwiki and get it running with Xampp
your new wiki=
http://localhost/dokuwiki/doku.php
http://127.0.0.1/dokuwiki/doku.php
http://rcfedora/dokuwiki/doku.php
(http://blog.ourmanpann.com/xampp/)
or
another helpful link
http://www.dokuwiki.org/install:permissions#how_to_set_permissions
download dokuwiki tar file
mv it to /opt/dokuwki-2009-12-25
untar it-tar -zxvf dokuwki-2009-12-25.tgz
sudo mv dokuwiki-2009-02-14 /opt/lampp/htdocs
cd /opt/lampp/htdocs/
chmod -R g+w dokuwiki-2009-02-14/
sudo chown -R nobody dokuwiki-2009-02-14/
sudo ln -s dokuwiki-2009-02-14 dokuwiki
If installed correctly and apache is running, you should be able display this page to complete setting up
the wiki-
http://127.0.0.1/dokuwiki/install.php
**********************
Dokuwiki install on Windows Vista.
INSTALL STEPS-
Download dokuwiki tarball from
http://www.splitbrain.org/projects/dokuwiki
file name dokuwiki-2011-05-25a.tgz
Use 7zip to extract dokuwiki-2011-05-25a.tgz
Copy new dokuwiki-2011-05-25a.tgz directory to c:\xampp
Rename dokuwiki-2011-05-25a.tgz directory to dokuwiki
Open browser, go to http://127.0.0.1/dokuwiki/install.php
Enter values-
Wiki Name
My Wiki
Superuser
me
Real Name
Me
Email
somebody@gmail.com
Password
mypassword
Enter Wiki name, super user, real name, password, and make security choices. Click finish link.
Wiki should now be working.
Test-
start xampp
then navigate to wiki
http://127.0.0.1/dokuwiki/doku.php
Wiki installed in
c:\xampp\htdocs\dokuwiki
************************************
Dokuwiki install on MAC 10.6 OSX
Follow instructions here-http://www.dokuwiki.org/install:macosx
Download dokuwiki-2011-05-25a.tgz
from
http://www.splitbrain.org/projects/dokuwiki
to your MAC. It will be stored here-
//home/yourname/Downloads
Enable PHP in Apache and Allow Directory Accesses
Backup httpd.conf:
$ sudo cp /private/etc/apache2/httpd.conf /private/etc/apache2/httpd.conf.bak
Edit httpd.conf:
$ sudo vi /private/etc/apache2/httpd.conf
Make the following changes to httpd.conf:
CHANGE:
#LoadModule php5_module
TO:
LoadModule php5_module
Download dokuwiki-yyyy-mm-dd.tgz (assuming to ~/Downloads)
Unpack downloaded file, move to appropriate location, and change ownership:
$ cd ~/Downloads && tar -zxvf dokuwiki-yyyy-mm-dd.tgz
$ mv dokuwiki-yyyy-mm-dd ~/Sites/dokuwiki
$ cd ~/Sites/dokuwiki
$ sudo chown -R www data conf lib/plugins
Start Personal Web Sharing in System Preferences → Sharing
You should now be able to run the installer at http://localhost/~your_username/dokuwiki/install.php
Answer questions from install.php and then your new Wiki will be created here-
http://127.0.0.1/~yourname/dokuwiki/doku.php
Wiki Name-MAC Wiki
Superuser-me
Real Name-First Last
Email-me@somewhere.com
Password-mypassword
MAC System Preferences/Sharing/Web Sharing
Place check mark next to Web Sharing.
your personl website, in the Sites folder in your home folder, is available at-
http://192.xxx.xxx.xxx/~yourname/
your computer's website is available at this address-
http://192.xxx.xxx.xxx
DokuWiki is a standards compliant, simple to use Wiki, mainly aimed at creating documentation of any kind. It is targeted at developer teams, workgroups and small companies. It has a simple but powerful syntax which makes sure the datafiles remain readable outside the Wiki and eases the creation of structured texts. All data is stored in plain text files – no database is required.
Download Dokuwiki here-http://www.splitbrain.org/projects/dokuwiki
***************************************
Dokuwiki install on Ubuntu 11.04
Follow instructions here-http://www.dokuwiki.org/install:ubuntu
dowloaded dokuwiki-2011-05-25a.tgz to //home/yourname/Downloads
sudo su
cd /opt/lampp/htdocs
cp /home/yourname/Downloads/dokuwiki-2011-05-25a.tgz .
tar xvf dokuwiki-2011-05-25a.tgz
sudo mv dokuwiki-2011-05-25a.tgz dokuwiki
--Before continuing, you must identify the user and group running your apache process--
One way is to run this command-
egrep -i 'user|group' /opt/lampp/etc/httpd.conf and look for the values of:
User daemon
Group daemon
Using the User:Group values, change the dokuwiki permissions-
chown -R daemon:daemon dokuwiki(www-data:www-data or nobody: could also be used)
chmod -R g+w dokuwiki
Start lampp if not running
/opt/lampp/./lampp start
Test if wiki is running-
http://127.0.0.1/dokuwiki/doku.php
Finish installing-
http://127.0.0.1/dokuwiki/install.php
Wiki Name-My Ubuntu Wiki
Super User:jdoe
Real Name:John Doe
Email:myname@gmail.com
Password:password
***********************************
Dokuwiki install on Fedora Linux
How to install dokuwiki and get it running with Xampp
your new wiki=
http://localhost/dokuwiki/doku.php
http://127.0.0.1/dokuwiki/doku.php
http://rcfedora/dokuwiki/doku.php
(http://blog.ourmanpann.com/xampp/)
or
another helpful link
http://www.dokuwiki.org/install:permissions#how_to_set_permissions
download dokuwiki tar file
mv it to /opt/dokuwki-2009-12-25
untar it-tar -zxvf dokuwki-2009-12-25.tgz
sudo mv dokuwiki-2009-02-14 /opt/lampp/htdocs
cd /opt/lampp/htdocs/
chmod -R g+w dokuwiki-2009-02-14/
sudo chown -R nobody dokuwiki-2009-02-14/
sudo ln -s dokuwiki-2009-02-14 dokuwiki
If installed correctly and apache is running, you should be able display this page to complete setting up
the wiki-
http://127.0.0.1/dokuwiki/install.php
**********************
Dokuwiki install on Windows Vista.
INSTALL STEPS-
Download dokuwiki tarball from
http://www.splitbrain.org/projects/dokuwiki
file name dokuwiki-2011-05-25a.tgz
Use 7zip to extract dokuwiki-2011-05-25a.tgz
Copy new dokuwiki-2011-05-25a.tgz directory to c:\xampp
Rename dokuwiki-2011-05-25a.tgz directory to dokuwiki
Open browser, go to http://127.0.0.1/dokuwiki/install.php
Enter values-
Wiki Name
My Wiki
Superuser
me
Real Name
Me
somebody@gmail.com
Password
mypassword
Enter Wiki name, super user, real name, password, and make security choices. Click finish link.
Wiki should now be working.
Test-
start xampp
then navigate to wiki
http://127.0.0.1/dokuwiki/doku.php
Wiki installed in
c:\xampp\htdocs\dokuwiki
************************************
Dokuwiki install on MAC 10.6 OSX
Follow instructions here-http://www.dokuwiki.org/install:macosx
Download dokuwiki-2011-05-25a.tgz
from
http://www.splitbrain.org/projects/dokuwiki
to your MAC. It will be stored here-
//home/yourname/Downloads
Enable PHP in Apache and Allow Directory Accesses
Backup httpd.conf:
$ sudo cp /private/etc/apache2/httpd.conf /private/etc/apache2/httpd.conf.bak
Edit httpd.conf:
$ sudo vi /private/etc/apache2/httpd.conf
Make the following changes to httpd.conf:
CHANGE:
#LoadModule php5_module
TO:
LoadModule php5_module
Download dokuwiki-yyyy-mm-dd.tgz (assuming to ~/Downloads)
Unpack downloaded file, move to appropriate location, and change ownership:
$ cd ~/Downloads && tar -zxvf dokuwiki-yyyy-mm-dd.tgz
$ mv dokuwiki-yyyy-mm-dd ~/Sites/dokuwiki
$ cd ~/Sites/dokuwiki
$ sudo chown -R www data conf lib/plugins
Start Personal Web Sharing in System Preferences → Sharing
You should now be able to run the installer at http://localhost/~your_username/dokuwiki/install.php
Answer questions from install.php and then your new Wiki will be created here-
http://127.0.0.1/~yourname/dokuwiki/doku.php
Wiki Name-MAC Wiki
Superuser-me
Real Name-First Last
Email-me@somewhere.com
Password-mypassword
MAC System Preferences/Sharing/Web Sharing
Place check mark next to Web Sharing.
your personl website, in the Sites folder in your home folder, is available at-
http://192.xxx.xxx.xxx/~yourname/
your computer's website is available at this address-
http://192.xxx.xxx.xxx
Subscribe to:
Posts (Atom)