LQWiki - User contributions [en]

Talk:General programming tips

2004-03-23T22:21:06Z

TRauMa: layout

I created this page to give the seeking visitor something to start with: a language independent philosophy of programming and a feeling for which languages are common, without going into greater detail. Comments?

:Call it "General programming overview"?
:Still, it's a useful idea.
:[[User:Chalupamaster92|Chalupamaster92]] 19:40, Mar 7, 2004 (EST)

----------

The pascal and basic entries are a bit lengthy. I didn't include them in the first place because they aren't that important to this particular wiki and I wanted to concentrate on the languages/tools you are likely to find on your system (or, Joe Averages linux box). What do you think about shortening them/making them more fitting to the general style (what lang, when used, where to find). [[User:TRauMa|TRauMa]] 17:19, Mar 23, 2004 (EST)

Talk:General programming tips

2004-03-23T22:19:39Z

TRauMa: Rearranging discussion chronologically, call for input on pascal/basic

I created this page to give the seeking visitor something to start with: a language independent philosophy of programming and a feeling for which languages are common, without going into greater detail. Comments?

Call it "General programming overview"?

Still, it's a useful idea.

[[User:Chalupamaster92|Chalupamaster92]] 19:40, Mar 7, 2004 (EST)

---

The pascal and basic entries are a bit lengthy. I didn't include them in the first place because they aren't that important to this particular wiki and I wanted to concentrate on the languages/tools you are likely to find on your system (or, Joe Averages linux box). What do you think about shortening them/making them more fitting to the general style (what lang, when used, where to find). [[User:TRauMa|TRauMa]] 17:19, Mar 23, 2004 (EST)

Managing sessions

2004-03-06T05:02:20Z

TRauMa:

Managing Sessions

* chvt - switches the display to the specified virtual terminal.
* login - prompts the user for username and password.
* logout - exists the current session and displays the login screen.
* rlogin - enables you to establish a user session on another computer connected to the LAN. Deprecated, safety-hazard. Use [[ssh]] instead.
* shutdown - Shuts down the system.
* startx - This shell script, enables you to start a X session.
* tty - Displays the number of the terminal device that is currently in use.
* [[xdm]], [[kdm]], [[gdm]] - Starting the X (KDE, Gnome) Display Manager
* xterm - Starts the xterm terminal emulation program. requires the X window system.
* screen - Terminal multiplexer. This is somewhat like a virtual terminal, only much more powerful.
* nohup - Prevents programs from getting killed on logout.

Source distributions

2004-03-06T04:54:20Z

TRauMa: type (grr)

----

'''Description:'''

Source based distributions enable the more experienced user to have a considerable degree of control over their system. Compiling and optimizing software for your particular hardware can bring noticeable performance improvements - however, compiling software can be a lengthy process. Another benefit of compiling a package instead of installing a prebuild binary is that some packages have optional parts in them with optional dependencies on other packages, which can be only selected at compile time. If you rely on prebuild packages, you can't make those selections any more. Usually the package maintainer chooses to switch all these options on, something which leads to the so called "dependency hell".

For more information on the various Source based distributions, click on the links below.

''This article is a [[LinuxQuestions.org_Wiki:stub_articles|stub]] and needs to be finished. [[LinuxQuestions.org_Wiki:plunging_forward|Plunge forward]] and [[LinuxQuestions.org_Wiki:How_to_edit_a_page|help it grow]] !''
 
----

'''Links:'''

*[[Gentoo]]
*[[Source_Mage]]
*[[Linux_From_Scratch]]
*[[Slackware]]

Source distributions

2004-03-06T04:53:20Z

TRauMa: added info bout optional (compile time) features

----

'''Description:'''

Source based distributions enable the more experienced user to have a considerable degree of control over their system. Compiling and optimizing software for your particular hardware can bring noticeable performance improvements - however, compiling software can be a lengthy process. Another benefit of compiling a package instead of installing a prebuild binary is that some packages have optional parts in them with optional dependencies on other packages, which can be only selected at compile time. If you rely on prebuild packages, you can't make those selections any more. Usually the packe maintainer chooses to switch all these options on, something which leads to the so called "dependency hell".

For more information on the various Source based distributions, click on the links below.

''This article is a [[LinuxQuestions.org_Wiki:stub_articles|stub]] and needs to be finished. [[LinuxQuestions.org_Wiki:plunging_forward|Plunge forward]] and [[LinuxQuestions.org_Wiki:How_to_edit_a_page|help it grow]] !''
 
----

'''Links:'''

*[[Gentoo]]
*[[Source_Mage]]
*[[Linux_From_Scratch]]
*[[Slackware]]

Talk:Programming tips & tricks

2004-03-06T04:46:05Z

TRauMa:

Love the ifconfig>grep>awk command! But it's not necessary to be root on my box - I don't think my perms are screwed up, but it's possible.

[[User:Digiot|Digiot]] 17:26, Mar 1, 2004 (EST)

----

Me again. This section seems kind of sparse. Is it maybe due to people not wanting to just plop down any old tip in the middle of nowhere? What do folks think of the idea of moving 'scripting' over here as 'shell scripting' and coming up with some more subcategories. I know it seems paradoxical to categorize very little content, but maybe that'll shake loose some tips from folks.

?

[[User:Digiot|Digiot]] 01:41, Mar 5, 2004 (EST)

----

That's a pretty big maybe Digiot. But having shell scripting here would be nice. How about letting folks jot down other tips too. I mean not restricting folks to just Programming. Maybe tips about using some GUI tool and things like that.

What say?

[[User:Linuxlala|Linuxlala]]

----

Given that this page/subject will grow in time, one possibility would be to have category links to separate pages for each programming language rather than having all the content on one page - you could of course bring some order to a page with ''sections'' and a ''T.O.C'' - however, even a T.O.C can become excessively large after some time - so , much as we're going to ''only'' have main categories on the Applications page, we should only have main category links on this page - candidates would be C/C++/Java/Python/Perl/BASH_scripting etc etc etc etc etc, plenty of scope for other categories aswell...

[[User:Skyline|Skyline]] 09:42, Mar 5, 2004 (EST)

----

I think the IP trick should go under networking. If anyone agrees, please move it there. BTW: I have gentoo and debian stable, neither has any permissions screwed up, and the ifconfig works.
[[User:Koody|Koody]]
----

Please place entries in order. We probably should have done inverse order but, unless and until there's a general change, let's keep it in order. I agree - a simple usage of ifconfig doesn't require root - only that sbin be on your path or that you give the full path.

Looks like I'm late to the discussion as far as the rest. Sure, gone for it! ;)

[[User:Digiot|Digiot]] 21:18, Mar 5, 2004 (EST)

----

What about it now? Sorry for changing right away, but I only remembered to look here after I already had changed the page.

[[User:TRauMa|TRauMa]] 23:46, Mar 5, 2004 (EST)

Programming tips & tricks

2004-03-06T04:40:17Z

TRauMa: some beautification, added java

Talk:General programming tips

2004-03-06T04:36:08Z

TRauMa: Call for comments

General programming tips

2004-03-06T04:33:40Z

TRauMa: typo

== Unix Philosophy ==

If you are familiar with programming under different operating systems than linux, you may notice subtle differences regarding the philosophy of the system. A good introductionary read is the free book by Eric S. Raymond, [http://www.catb.org/~esr/writings/taoup/ "The Art of Unix Programming"], particulary the chapter about the [http://www.catb.org/~esr/writings/taoup/html/ch01s06.html "Unix philosophy"].

== Available languages ==
If you wonder about what languages you can expect to be already installed on a typical linux, here is a short list:

* [[C/C_plus_plus_tips|C]]: From linux kernel to utilities, many of the binaries on a typical linux system are written in C. You can expect the C standard library on every [[POSIX]] conforming system, and a C compiler on most of them.

* [[C/C_plus_plus_tips|C++]]: Many of the larger open source projects are written in C++, and again you will find the standard library on virtually every system, and more often than not a compiler.

* [[Java_tips|Java]]: There are many systems with the Java Runtime Enviroment installed, but low footprint server enviroments sometimes omit it.

* [[Bash_tips|Shell]]: Every linux system has a shell which you can write programs for, the famous shell scripts. Most popular are bash and csh, which understand a common syntax subset, but sometimes differ greatly.

* [[Perl_tips|Perl]]: If the typical shell script wont do, the most widespread scripting language used is perl. It is widely deployed and used for many purposes.

* [[Python_tips|Python]]: Though not as common as perl, most distributions install python by default, some of them even rely on it for their base system.

Of course it shouldn't be difficult to install development tools for your favourite language, and usually the user won't notice which language you wrote the software in, at least if it's compiled (and not interpreted).

General programming tips

2004-03-06T04:31:42Z

TRauMa: Some quick overview about programing on linux

== Unix Philosophy ==

If you are familiar with programing under different operating systems than linux, you may notice subtle differences regarding the philosophy of the system. A good introductionary read is the free book by Eric S. Raymond, [http://www.catb.org/~esr/writings/taoup/ "The Art of Unix Programming"], particulary the chapter about the [http://www.catb.org/~esr/writings/taoup/html/ch01s06.html "Unix philosophy"].

== Available languages ==
If you wonder about what languages you can expect to be already installed on a typical linux, here is a short list:

* [[C/C_plus_plus_tips|C]]: From linux kernel to utilities, many of the binaries on a typical linux system are written in C. You can expect the C standard library on every [[POSIX]] conforming system, and a C compiler on most of them.

* [[C/C_plus_plus_tips|C++]]: Many of the larger open source projects are written in C++, and again you will find the standard library on virtually every system, and more often than not a compiler.

* [[Java_tips|Java]]: There are many systems with the Java Runtime Enviroment installed, but low footprint server enviroments sometimes omit it.

* [[Bash_tips|Shell]]: Every linux system has a shell which you can write programs for, the famous shell scripts. Most popular are bash and csh, which understand a common syntax subset, but sometimes differ greatly.

* [[Perl_tips|Perl]]: If the typical shell script wont do, the most widespread scripting language used is perl. It is widely deployed and used for many purposes.

* [[Python_tips|Python]]: Though not as common as perl, most distributions install python by default, some of them even rely on it for their base system.

Of course it shouldn't be difficult to install development tools for your favourite lamguage, and usually the user won't notice which language you wrote the software in, at least if it's compiled (and not interpreted).

User talk:TRauMa

2004-03-06T03:42:47Z

TRauMa:

If you want to talk to me, here is the place.

User:TRauMa

2004-03-06T03:39:20Z

TRauMa:

A wiki where you have to login to post is no real wiki.

Remote desktop connection

2004-03-06T03:36:21Z

TRauMa: typo

[[ssh]] - SSH (secure shell) is one of the best remote login clients and servers. SSH can be used for a terminal or console session (a command prompt) like Telnet, but can also be configured to "tunnel" X-Windows applications as well. This would allow a user to, for example, log in to a remote system and launch a graphical application and have the application appear on the users system. In such a scenario, the application would appear but NOT the full desktop environment (such as Gnome or KDE).

[[VNC]] - VNC is not as secure as ssh, but is easier to use and configure. VNC is designed primarily to forward an entire GUI environment (including Gnome or KDE if they are in use).

[[XDMCP]] - XDMCP allows remote logins through an X display manager such as Gnome's GDM (so long as the option is enabled). While insecure, this can still be useful on trusted networks where you want to create a simple terminal to your main desktop.

[[Telnet]] - Telnet was one of the earliest attempts at remote administration. It is now considered inherently insecure (it sends everything in clear text) and largely obsolete, but may have some niche uses on trusted networks. Telnet provides only a console session with no capability of forwarding X-Windows applications or GUI environments.

[[rdesktop]] - RDesktop is a Linux client that can attach to a Windows Terminal Server or to the built in Remote Desktop capability of Windows 2000 and Windows XP. It is ideal for many who prefer to work from a Linux system, but who have an occasional need to access a Windows machine. RDesktop replicates the full Windows desktop in a window within Linux.