04-11-2009
Quote:
Originally Posted by
pludi
Explore Linux: Grab a copy of any distribution that appeals to you, install it and explore to your hearts desire.
What languages have been used: For the kernel, almost exclusively C and Assembler (as far as I know). Almost all of the system libraries are written in C, too, with a few in C++. As for the rest it's a healthy mix of almost every language out there.
And I too want to remind you of the
Rules, specifically Rule 9, which you agreed to when registering.
What I did was, I got PCLinuxOS as a live cd ISO and burned it. Then I could do anything like edit the code, if you mess up the system, just reboot and your fine.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I need to access files from a specific folder of a Linux system from an another Linux System Remotely.
I know how to, Export a folder on One SCO System & can access the same by using Import via., NFS in the Sco Unix SVR4 System using the scoadmin utility.
Also, I know to use mount -t ... (2 Replies)
Discussion started by: S.Vishwanath
2 Replies
2. UNIX for Dummies Questions & Answers
Here's what I have...
$ vi foo1
- open foo1 and work around for a while. I yank a few lines into a buffer and then :w to save.
Next I :e foo2 to open foo2 and paste my buffer. I :w to save, but I would like to then be able to go directly back into foo1 where I was before I opened foo2. ... (4 Replies)
Discussion started by: djschmitt
4 Replies
3. Windows & DOS: Issues & Discussions
:D mount -t vfat /dev/hda1 /mnt
my dillemma is simple i have psion 5 mx wich is an epoc type machine not only does it only work on windows as far as I know but I have to convert the files (the usual stuff!) sometimes a humen error happens and the files that I want to transfer to the linux drive... (7 Replies)
Discussion started by: moxxx68
7 Replies
4. UNIX for Dummies Questions & Answers
Hi, I am trying to edit sshd_config file through the vi editor.
logged on as a root.
when I try to write the file I get:
Read-only file, not written; use ! to override
when i type :w!, I get:
Error: etc/ssh/sshd_config Permission denied.
I want to change:
#PermitRootLogin no to yes
freeBDS... (6 Replies)
Discussion started by: emosms
6 Replies
5. UNIX for Dummies Questions & Answers
i need to know how files can be transfered from one system to another securely in linux. (9 Replies)
Discussion started by: bibing
9 Replies
6. Shell Programming and Scripting
Hi,
I want to connect to sqlplus through unix. I got the command to do it. But I was getting error:
./executeSQL.ksh: sqlplus: not found
Then when I googled I found that we have to include Oracle Client path in .profile file. I don't know how to do it. Also I don't have permissions to... (2 Replies)
Discussion started by: dips_ag
2 Replies
7. UNIX for Dummies Questions & Answers
Hi, sometimes one wants to edit files while still seeing output of earlier commands in terminal. I've found out that cat test && cat - >> test does the trick for displaying file content and adding lines but I believe I saw a much cooler command that was also able to erase lines from files. I cannot... (6 Replies)
Discussion started by: scarleo
6 Replies
8. AIX
I have a following requirement in production
system 1 : LINUX
User: abcd
system 2: AIX (it is hosting a production DB)
Requirement
user abcd from system 1 should have read access on archive log files created by DB on system 2. The log files are created with permissions 540 by user ora ,... (2 Replies)
Discussion started by: amitnm1106
2 Replies
9. Shell Programming and Scripting
Experts - I have an requirement to gunzip and edit many files in a pair of directories.
I have two scripts that work great when run separately, but I'm having problems
combining the two.
The goal is to gunzip the files found in the first script and pipe them to the
bash/sed script and... (9 Replies)
Discussion started by: timj123
9 Replies
LEARN ABOUT REDHAT
makekdedoc
MAKEKDEDOC(1) KDOC Documentation System MAKEKDEDOC(1)
NAME
makekdedoc -- Generates HTML documentation for KDE libraries using KDOC.
SYNOPSIS
makekdedoc [--rule-file=<rulefile>] [--libdir=<libdir>]
[--outputdir=<outputdir>] [--url=<url>]
[--srcdir=<kdelibs src dir>]
[--kdoc=<path to kdoc>] [<library>...]
makekdedoc --help
DESCRIPTION
This is a perl script that uses KDOC to generate documentation for kdelibs. A "rule" file is used to figure out the libraries to document,
the order in which to document them and the libraries with which each one will be cross-referenced (eg kdeui uses -lkdecore). See "FILES"
for more info.
NOTE: The script assumes that you have already generated a Qt cross-reference using qt2kdoc[1].
OPTIONS
Defaults for each option are in square brackets.
library...
Specify the libraries to document. By default, all libraries defined by the rule file are documented.
--outputdir <path>, -d <path>
The directory where the output will be written. [`cwd`/srcdoc]
--url <url>, -u <url>
The base URL by which the generated docs will be accessed. For example, if your web server is configured to use $HOME/public_html for
your home page, you could set the outputdir to $HOME/public_html/srcdoc and the url to http://myhost/~mylogin/srcdoc. [output dir]
--rule-file <path>, -r <path>
The path to the rule file to use for generating the documentation. [<srcdir>/kdoc.rules]
--libdir <path>, -L <path>
The directory in which the KDOC cross-reference files are stored. [$KDOCLIBS if set, otherwise $HOME/.kdoc]
--kdoc <path>, -k <path>
The path to the kdoc program. [kdoc]
--kdocopt <options>, -p <options>
Extra options to be passed to kdoc.
--srcdir <path>, -b <path>
The path to the kdelibs source, eg "$HOME/baseline/kdelibs". [`cwd`]
--help, -h
Quit with a usage message.
EXAMPLES
makekdedoc --srcdir $HOME/baseline/kdelibs
--outputdir $HOME/public_html/src/kdelibs/
--url "http://www.ph.unimelb.edu.au/~ssk/src/kdelibs"
FILES
Rule file
This file lists the directories in the source directory to document. It also lists the files to document from each directory, and the
libraries with which to cross-reference the generated documentation. Here is a small example that documents two libraries and links the
second to the first.
# makekdedoc rule file
doc_MODULES = eenie meenie
# rules for eenie
eenie_FILES = *.h
eenie_LIBS = -lqt
# rules for meenie
meenie_FILES = a.h b.h
meenie_LIBS = -leenie -lqt
In this example, all files in "eenie/*.h" will be documented then two files from "meenie/" will be documented, in the order declared in
"doc_MODULES".
SEE ALSO
See kdoc[1] and qt2kdoc[1].
VERSION
makekdedoc $Revision: 1.2 $
AUTHOR
The script and this documentation were written by Sirtaj Singh Kang <taj@kde.org> in April 1999.
2.0a54 2000-10-10 MAKEKDEDOC(1)