-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Luis.F.Correia wrote: > Hi Greg, > >> -----Original Message----- > <snip> >> I am real short of time too. However, I look forward to >> revising some of documentation files for the LEAF wiki. So >> with a little vim regex tricks, this page >> http://leaf.cvs.sourceforge.net/*checkout*/leaf/doc/howto/LRP- >> Serial-HOWTO.txt?revision=1.1.1.1 >> became http://leaf.wiki.sourceforge.net/Serial+Link+Configuration >> >> Regards, >> Greg > > Did you had to create an entry in the HOWTO page or it did appear > there magicly? > > Luis
Almost magically. Login to SF with your SF userid. I started on the main page. I hit the edit button, then I immediately hit the Use Text Editor button at the bottom of the page on the right hand side. My preference is to use the powerful wikitext language verses a graphical interface. Greg finds a mouse slow at times verses using [[]] == ==, etc. Where I wanted to start a new page I typed in a word or phrase but, then enclosed them in square brackets i.e. [[LEAF]] If you look at the history of a page you will see that Mike made the word just LEAF, when he first created the page. Once I had the phrase in [[]], then I saved the page. When I viewed the changed page, I could click on the LEAF word and start creating new content. If you can count to five, then you can use a wiki. Links are create with two [[ on either side ]] =my word= creates the headings. ==my indented word== creates a subheading. If you look at http://leaf.wiki.sourceforge.net/space/changes then in a way you can analogously think of reading the documentation commits mailing list. Each page has a history link so you can look at the diffs of a page. With a wiki it is more important to type in an idea; save it; revise it; and hope others will help edit the page(s) that you author than slowly ponder an idea in private before committing a change. If egos are put aside, then community edited content will build real fast. The text of the page is listed below as a "Use the force and read the source" example. The SF wiki has a little different spin on its wiki engine than what I normally use. There's still some clean up to do on some of the pages. That's where I start cutting the content page into a local editor like vim and regex changes as required. For example, once I had established the LEAF page, I went back to a few pages and used :%s/LEAF/[[&]]/gc or :1,$ s/LEAF/[[LEAF]]/gc to add the wiki page link references back to the LEAF page. If you know some html, then you will understand that [[]] creates an href and = creates H1 tags, == H2, === H3, etc. Firefox rocks with wikis because you can install spell check extensions and use them in the web browser text area. I like http://www.svarteper.com/ff/aspellfox/ because I use aspell. You can also use your editor's spell checker--vim 7 now comes with one built in--or command link tools such as aspell check mytemp_text_file.txt before pasting the text back into the wiki page text area. Since there is built in CVS like features, don't be bashful. Hit the edit button and try a few changes. You can always cancel your change, etc. The page history for the serial page is located here http://leaf.wiki.sourceforge.net/page/history/Serial+Link+Configuration You will see that I just spell checked the document. Just like CVS commit comments, I always try to add an edit comment at the bottom of the page. Here's the links that Mike provided http://www.wiki.sourceforge.net/help http://www.wiki.sourceforge.net/wikitext http://www.wiki.sourceforge.net/image+tags Please look at the wikitext page to see more of the syntax. I'll be happy to try and help with any other questions that you have. Regards, Greg This [[LEAF]] [[Serial Link Configuration|Serial HOWTO]] covers using a serial wire link to your [[LEAF]] box so that the connection replaces the VGA card and keyboard normally used as the primary user interface for maintaining a working [[LEAF]] system. =Disclaimers= The procedure described works for me on my test systems. Your mileage may vary. Absolutely no guarantees are made about the accuracy or suitability of the procedures described below. I cannot be responsible if you accidentally destroy a working [[LEAF]] system, or even if you just wind up wasting an evening or weekend trying to get things working. <grin> It is assumed you are smart enough to adapt some of the commands to your particular environment. For example, if this HOWTO says to perform the command: [[code]] echo "Hello World" > /dev/ttyS0 [[code]] and you are trying to use the COM2 serial port, you would actually type something like: [[code]] echo "Hello World" > /dev/ttyS1 [[code]] This document is being placed in the public domain. You may feel free to copy, use, modify, record, transmit, archive, fold, spindle, or mutilate this document in any way you see fit. =Conventions= For clarity, commands you should type in, filenames, screen output, and other such items are either on their own line: Like this or enclosed in single quotes 'Like this'. You should not type in the single quotes when entering commands or filenames, or expect them to be on screen output. =Configuring a serial terminal as you primary interface= ==Before You Get Started== You will need a few things, so try to track them all down before you get started. I have tried to collect most of the files needed on my web site at http://lrp.steinkuehler.net 1) A serial terminal (duh). If you don't have a serial terminal, there's not much to help you in the rest of this HOWTO. You can also use a PC running a serial terminal program (that's what I do). 2) A seral cable approprate for connecting your [[LEAF]] box to your serial terminal. This is typically a 'null modem' cable. I used a combination of a 9 pin straight-through cable, a null modem adapter, and a gender changer (with 2 female plugs) for my setup. I got all the parts at Radio-Shack...we don't have Fry's here in Kansas :< ==Getting Started== It is assumed at this point that your [[LEAF]] box is configured and working properly. If this is not the case, you should stop here and get your [[LEAF]] box working with a keyboard and monitor. 1) Connect your [[LEAF]] box to the serial terminal. You can use any standard serial ports on your [[LEAF]] box (I used COM1, or /dev/ttyS0). 2) Set your terminal to 9600 buad ([[LEAF]] defaults to 9600 buad...you can use a faster baud rate later, when you configure the serial settings). 2) Test the basic connection by typing the following on your [[LEAF]] console [[code]] echo "Hello World" > /dev/ttyS0 [[code]] 3) If you're lucky, you will see "Hello World" show up on your serial. If everything is connected properly but the two ends disagree on baud rate, you may see some strange looking characters. If you don't see anything, you can try to figure out why, or you can forge ahead, but be prepared for problems later. =Configuring A Serial Terminal= 1) Get to the lrcfg menu by logging in or running 'lrcfg' 2) Edit the /etc/inittab file (lrcfg menu 2-3) 3) There is an example entry for a serial terminal already: [[code]] #T1:23:respawn:/sbin/getty -L ttyS1 19200 vt100 [[code]] 4) Simply uncomment this line to enable a console session on COM2. If you would rather use COM1, change the line to the following (note the two items that changed): [[code]] T0:23:respawn:/sbin/getty -L ttyS0 19200 vt100 ^^ ^^^^^ [[code]] 5) Adjust the baud rate setting (19200) or terminal type (vt100) as necessary 6) Save the file <alt>-w and exit <alt>-q 7) Edit the /etc/securetty file (lrcfg menu 2-5) 8) Add ttyS0 (and/or ttyS1 as appropriate) to the list 9) Save the file <alt>-w and exit <alt>-q 10) Backup the /etc package (lrcfg menu b-2) At this point, you should get a login prompt on the serial terminal the next time you reboot, and you should be able to log in as root from the serial terminal. You might want to try this before continuing, to verify everything is working properly. =Configuring Kernel Messages To Display On The Serial Terminal= If you rebooted and tested your serial terminal, you noticed nothing appeared on the serial terminal until the [[LEAF]] system was completely booted and ready for a user to log in. Now it's time to get the kernel boot messages to display on the serial terminal, as well. I strongly suggest you reboot to test you setup before continuing. Fix anything that is broken before you play with the kernel booting. 1) Mount the boot disk [[code]] mount -t msdos /dev/boot /mnt [[code]] 2) Edit syslinux.cfg [[code]] ae /mnt/syslinux.cfg [[code]] 3) Add the following to the end of the append= line (which should be long and wrapped around your display). Make sure there is a space in front of the first console=, and a space between the two settings, as shown. [[code]] append=... console=tty0 console=ttyS0,19200n8 [[code]] 4) This displays kernel messages on both the virtual terminal tty0 (your VGA/keyboard combo), and ttyS0 (COM1), with ttyS0 being the 'primary' console because it is listed last. You can also add more consoles, if you like, and they will all recieve the kernel boot messages. The primary console will get some output (mainly from the linuxrc script) that does not show up on the other console(s). 5) Save the file <alt>-w and exit <alt>-q 6) Reboot Hopefully everything went well, and you can now unplug the monitor and keyboard from your [[LEAF]] system. =Resources= Here are some useful [[LEAF]] related links: http://lrp.steinkuehler.net/ http://www.c0wz.com/ http://linuxrouter.sourceforge.net/ http://www.linuxrouter.org/ http://beta-linuxrouter.razorsedge.com/ http://lrp.plain.co.nz/ http://wpkgate.kc.com.my.cpwright.com/lrp/ =Attribution= The [[Serial Link Configuration]] document was originally written by [[http://sourceforge.net/users/cstein/|Charles Steinkuehler]] and with recent wiki updates by [[http://sourceforge.net/users/dr_kludge/|Dr. Kludge]]. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFF/4yRxyxe5L6mr7IRAiY1AJ9M7LaPs0w7xJUEFQLfDL1CJteQWACfdVoj Hblr4JTtNoWVlop3V3ukkDE= =UCiT -----END PGP SIGNATURE----- ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
