A short FAQ on Trinux
6c8847332c7a955c9df193dd74580339aeb9b5612d3570f54763a477230583a1<html>
<head>
<title>Trinux FAQ (tentative)</title>
</head>
<body bgcolor="white">
<center>
<h1>Trinux FAQ</h1></center>
<hr>
<B>MAILING LISTS</B>
<p>The following mailing lists are available courtesy of Sourceforge:
<li><a href="http://lists.sourceforge.net/mailman/listinfo/trinux-talk">Trinux-talk</a> - the best place to ask questions or get help
<li><a href="http://lists.sourceforge.net/mailman/listinfo/trinux-news">Trinux-news</a> - keep up with the latest releases
<p>
<B>OTHER RESOURCES</B>
<li>Visit the SourceForge <a href="http://sourceforge.net/bugs/?group_id=3301">bug racking tool</a> to report problems/fixes. Trinux 0.7x is the only "supported" version.
<li>There are also <a href="http://sourceforge.net/forum/?group_id=3301">Web based Forums</a> available, but I don't check these as often as the mailing lists
<p><FONT color="red">
<CENTER>most everything below pertains to older versions and needs to be updated</CENTER></FONT>
<hr><p>
<b>ANNOYING STUFF</b>
<ol>
<b><li>When I exit Trinux with either a CTRL-D or exit, Trinux dies and says something about a Kernel panic, unable to mount VFS. What gives?</b>
<ul>
<li>Right now, Trinux does not use getty's or runlevels, so it won't respawn new shells. <font color="red">The solution:</font> Don't do that!!!
</ul>
<b><li>I can't stop pinging (or using tcpdump for that matter). CTRL-C doesn't seem to work. HELP!!!</b>
<ul>
<li>Yes, we know. This is a problem with kernel 2.2.x that we haven't been able to solve. I think it's something related to raw socket (oddly enough), but Matt Cerha thinks it has to do with keyboard mapping. He's also volunteered to provide the person that fixes this bug with a cool <a href="http://www.openbsd.org">OpenBSD</a> T-shirt. <font color="red">The fix:</font> Use X-Windows (and Xterms) because it doesn't seem to affect non-console shells as bad. It also seems to be more of a problem with ash than bash.</ul>
<b><li>When will you add mouse support to X-windows?</b>
<ul>
<li>Probably never. If you really want to use a mouse, you'll have to recompile your own kernel and add serial/PS2 support. If the truth be told, disabling mouse support was the only way I'd even agree to include X with Trinux. Why, pray tell, would you need a mouse anyway? Answer that!
</ul>
<b><li>This evilwm thing is great, but when will there be packages for KDE or GNOME?
<ul>
<li>The same answer as #3, except there's no probably about it. As it hints at in the previous question, the only purpose for X in Trinux is multiple Xterms. I would not be opposed to a libgtk+ package so that nmapfe, gfcc, nessus, or cheops could be included, but desktop environments???! KDE is too slow and GNOME is too unstable. Besides, then we'd have to start including sound card support in the kernel... ; </ul>
</ol>
<b>IMPORTANT STUFF</b>
<ol>
<b><li>What are package dependencies and which one's do I need to know about?</b>
<ul>
<li><b>misclibs</b> - required for most packages including nmap, ipgrab, X
<li><b>termcap</b> - required for any packages that use terminal stuff
<li><b>ncurses</b> - required for any packages that use terminfal stuff
<li><b>pthreads</b> - required for ntop and hunt
<li><b>slang</b> - required for lynx
<li><b>libz</b> - required for lynx
</ul>
<b><li>How do I enable non-US keyboard support?</b>
<ul>
<li>Make sure you load the <b>keymap.gz</b> package and create the file <i>/conf/keymap</i> on the boot floppy. If you put the two-letter country code used by loadkeys you won't be prompted for your country every time you boot. See the script <i>/etc/init.d/keymap</i> for details on how the keymap is loaded.
</ul>
<b><li>Help, I've created a new package, but every time I run the program I get a segmentation fault?!
<ul>
<li>Did you compile your package on RedHat 6.0? Trinux is built on RedHat 5.2 and the binaries are linked against glibc 2.06.
</ul>
</ol>
</body>
</html>
© 2022 Packet Storm. All rights reserved.
%7Cutmcsr%3D(direct)%7Cutmcmd%3D(none)){kind=small}
Follow us on Twitter
Follow us on Facebook
Subscribe to an RSS Feed