http://www.linuxquestions.org/questions/blog.php?u=329740 LinuxQuestions.org offers a free Linux forum where Linux newbies can ask questions and Linux experts can offer advice. Topics include security, installation, networking and much more. en Tue, 24 Nov 2009 22:32:58 GMT vBulletin 60 http://e1h7.simplecdn.net/lqcdn/images/questions/images/misc/rss.jpg http://www.linuxquestions.org/questions/blog.php?u=329740 http://www.linuxquestions.org/questions/blog.php?b=1627 Sat, 21 Feb 2009 14:56:32 GMT Generating password is simple:

password8.sh:
[code]
#!/bin/sh
cat /dev/urandom| tr -dc '0-9a-zA-Z!@#$%^&*_+-'|head -c 8;echo
[/code]
This script generates 8 characters long password.
To change number of characters, replace 8 with other number.
'0-9a-zA-Z!@#$%^&*_+-' defines character set used in password. If you need another charset, change this string to suit your needs. ]]> ErV http://www.linuxquestions.org/questions/blog.php?b=1627 http://www.linuxquestions.org/questions/blog.php?b=1485 Wed, 31 Dec 2008 00:33:57 GMT [SIZE="5"][b]Making slackware packages from source[/b][/SIZE]

I'm posting this because some people have problems with making packages from source code, and howto where I learned how to do it isn't available anymore.

[color=red][b]WARNING![/b][/color]:
1) howto is pretty short and doesn't dive into details too much (although I initially thought about overview of commonly used build systems).
2) This doesn't work for all packages, only for most of them. Method is not universal
3) This stuff is written for people that don't like Slackbuilds, or want to compile software without slackbuild. If you simply want to install program as fast as possible, search for compiled package on [url]www.linuxpackages.net[/url], or search for slackbuild on [url]www.slackbuilds.org[/url].

[SIZE="4"][b]Requirements[/b][/size]
This method will work only if following conditions are met:
1) program package contains ./configure script.
2) Makefile produced by ./configure contains word [i]DESTDIR[/i] (case-sensitive).
Seems pretty restrictive, but, fortunately, this covers 95% of all available linux software.

If there is no ./configure, or makefile doesn't have "DESTDIR" inside, this will not work. (there are exceptions from that rule, of course, but explaing them will take too much space)

[SIZE="4"][b]Short explanation[/b][/SIZE]
In this example I assume that we have extracted our package, and right now are within source code directory, where ./configure script is located. In example our program has name "programname" and version "programversion". When compiling your own package, replace "programname" and "programversion" with values you need.

Most software can be turned into slackware package using this sequence:
1) ./configure
2) make
3) mkdir pkg
4) make DESTDIR=`pwd`/pkg install
5) cd pkg
6) su
7) makepkg programname-programversion-1xyz.tgz
8) chown [color=red]me[/color].users ./programname-programversion-1xyz.tgz (instead of "me" use your user name)
9) mv ./programname-programversion-1xyz.tgz ..
10) cd ..
11) rm -r pkg
12) Ctrl+D (exits "su")

If package meets requirements mentioned before, this sequence will create slackware package for you.

[SIZE="4"][b]How it works[/b][/SIZE]
1) "./configure" - configures package according to our system.
2) "make" - compiles package.
3) "mkdir pkg" - creates directory called "pkg" within same directory where ./configure is located. This "pkg" directory will be used to
store files that will be put into package.
4) "make DESTDIR=`pwd`/pkg install":
This tells to the "make" command to install package as if "pkg" subdirectory (that we created in current directory) were root "/" folder.
"`pwd`" inserts output of "pwd" command into current command line. DESTDIR is a variable used inside makefile. DESTDIR specify the root of installations, and because GNU make allows to override some variables during compilation, we can change it, and say that "pkg" subdirectory is a root of installation.
5) "cd pkg" we are going into "pkg" subdirectory.
6) "su" (enter password here) - changing privilegies to root, because makepkg (which is used to create packages) won't work with other privilegies.
7) "makepkg programname-programversion-1xyz.tgz" This creates slackware package [b][i]without description[/i][/b]. Answer "yes" to all questions (well, unless it doesn't suit your needs). Also, notice "1xyz" part of the filename instead of numbers. When you build custom packages, you need to be able to distinguish them from stock packages. To do that, instead of standard numbers numbers, use custom signature, something like "1abc", "2abc", etc. Use whatever combination you want (I use number + my nickname), as long as you can distinguish your package from packages made by other people.
8) "chown me.users ./programname-programversion-1xyz.tgz" Created package has "root.root" owner. If we want to be able later to move it somewhere, we need to change owner to our user ID.
9) "mv ./programname-programversion-1xyz.tgz .." We are moving our package into the source directory - i.e. one level up.
10) "cd .." Going one level up. (back into directory with "configure")
11) "rm -r pkg" we are cleaning up and removing our pkg subdirectory.
12) "Ctrl+D" - this equivalent to "exit" command which ends "su" session.

[size=4][b]Done[/b][/size]
Now you have your slackware package.
If something doesn't work, or you don't understand something, ask it on slackware forums.

Hope this will be useful. ]]> ErV http://www.linuxquestions.org/questions/blog.php?b=1485 http://www.linuxquestions.org/questions/blog.php?b=1355 Mon, 01 Dec 2008 03:29:41 GMT Okay, I've just got through another flamewar, so I decided to write a some info about answering questions without wasting too much time in the process. The content is based on personal experience, my own point of view, and isn't supposed to be absolute truth or something. I also don't expect someone to agree with me. Recommendations are written in random order, and are supposed to prevent wasting too much time typing replies, or breaking your keyboard too quickly.
Beware! Some people probably might find this thing offensive.

The recommendations are based on following assumptions:
1) You want to help other people to solve their problem.
2) You don't want to spend many hours per day doing that.
3) You want to get satisfaction from giving out info - i.e. people should be grateful, or discussion should be interesting.
4) You do not want to live on the forum, just post answers to some threads.
5) You don't want to have a bad mood after helping someone.

Ok, here are recommendations:

0) Always remember that you can ignore other people instead of trying to reason with them. By "ignoring" I mean ignore list, which is located at [url]http://www.linuxquestions.org/questions/profile.php?do=ignorelist[/url] very handy feature.
1) Never participate in threads about religion. There were many of those, and when there is a clash between believers and atheists (or simply followers of different religions), no matter which side you take, you'll never prove to "them" that you are right. Also, your opponents will never prove you that you are wrong. The thread will eventually degrade into pillow-fight, and someone will close it.
2) Never post in "Linux vs Windows" threads. Yes, this is tempting, but should be avoided. Such threads either never ends or many of them eventually degrade into flamewar. Which side "wins" in case of flamewar depends on forum, but in most cases, moderators win. Providing non-biased info in such threads is difficult, and sometimes leads to disappointment - especially when you discover that someone asked the question you already answered in details one year ago in the same thread.
3) If are feeling too emotional while typing a reply, do not type a reply. If you were offended, report incident to moderators. If you are angry, go outside and take a walk. If you don't like someone, ignore him or her (by adding into ignore list). Being furious or simply emotional causes too much typing. And too much typing means too much time wasted.
4) When someone posts something that doesn't fit into your system of beliefs, and it enrages you, do not try to explain something to that guy/girl, ignore him/her. If he posted something gross, then report it to moderators. To my experience, trying to explain something to someone who don't want to listen is #1 cause of wasting time on the internet. This applies to the choice of distribution, operating system, religion, some questions about women, and so on. Same principle applies to trolls or any person that pisses your off.
5) Do not reply in the threads started by spammers. They don't read it.
6) When replying to "newbie" section, try to keep your replies extremely short, but informational. It is tempting to overwhelm newbie with the amount of things you know, but this guy might not need it. He might be simply interested how to watch DVD, and not in the mood for linux history lesson or detailed comparison of all available dvd-players.
7) When you realize that you started to type extremely long, detailed instructions about "how to do something in linux", stop, put keyboard away, take a deep breath, relax, and then try to find howto on the subject you were writing about. There is high chance that someone already wrote what you were going to write right now, so you'll be reinventing wheel. If there is a howto on the subject, post a link to it or quote it (but still provide link). This will make howto more widespread and will save time for other people.
8) When you found a good howto or manual, and want to put a link to them in reply, consider quoting them. Websites sometimes disappear, and seeing dead link 3 years later (and answering same thing again) isn't much fun. If the source of article doesn't look "stable" enough, quote good portion of it (but still provide link). If website is unlikely to disappear, then link should be enough.
9) If you really pissed someone off, and was unable to pacify that person within small amount of replies (1..3), consider ignoring that person. This is because when someone thinks that you are "evil person that hates all people" (no matter what were your intentions, what did you post, how friendly you were, people might think that about you), you can waste considerable amount of time reasoning with that person and explaining your position. If you started such "clarification conversation", observe person's reaction, and if person is unlikely to change attitude quickly, don't waste your time. Some people can be reasoned with, some can't.
10) When you see newbie poster (which has 1 message on the forum) with a short question (literally short - one statement with poor punctuation, small amount of info, etc), and you want to write really long answer, stop, and think about it again. Poster might be "fly by homework question author" - i.e. he will ask question, and then mysteriously disappear, while other people will waste their time explaining things to him and writing huge replies for few weeks. Not all newbies magically disappear, but you should consider that possibility.
11) Don't do other people's homework, they normally won't truly appreciate it, and this will spoil your mood and take your time. I.e. if the guy asked how to make some script, do not engage in 3 hours of googling, researching and testing just to make that script for him, because in the end his "thanks" might not satisfy you. To my experience, answers that were written with little effort (link to howto, article) generate more positive emotional feedback (for you - i.e. you'll feel more happy) when people say "thanks" than answers where you spend hours to find solution. Making other people's homework makes sense only if the problem is extremely interesting for you and you really like to solve complicated problems. Notice, that even if you solved problem you still can choose not to provide info to the OP, if you think he is too lazy or didn't do his homework.
12) Do not live on the forums. If you are checking forums for new messages every 3 minutes and looking for _any_ discussion to participate in, and occasionally attempt to derail existing threads, then you should probably turn off computer and go jogging, watch the movie, take dog for a walk, or do anything that is fun, takes at least hour and doesn't involve computers. Helping people is fine, forums are good, but, unfortunately, for some people participating in such discussion is a bit addictive. And when you start spending too much time on the forums, quality of your answers decreases.

Now this is it. I hope this information will be useful for someone. ]]> ErV http://www.linuxquestions.org/questions/blog.php?b=1355