• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About iNSEM

  • Rank

Contact Methods

  • ICQ
  1. I'd suggest removing the KDM (KDE Display Manager) package. If you still want to keep it installed but don't want it launched on boot, disable it from your init boot process.
  2. apt-get into it. use a custom compiled kernel. regular debian because it wont be as bloated a knoppix or ubuntu are (they are desktop distros). the end.
  3. i suggest ubuntu linux, kubuntu linux, or knoppix. those will probably work straight up.
  4. I don't know about your video card situation but on everything else... iptables for linux firewall. You ext3 as your linux file system because it is rock fucking solid. ext2 is one of the most reliable fs's ever and version 3 adds journal support. If people bother you about "benchmark" performance of ext3 versus other journal based file systems it's hog wash. You wont know a difference. Even on server's with a lot of disk access it works really well. And if you want good file system sercurity use windows xp and take advantage of the encrypted file system features. Linux supports encrypted fs for ext3 as well. do it for linux as well. password protect lilo or grub for booting. but in reality geeking out about FS security on your box is pointless. A) if you really are doing things which warrent that type of physical security (yes fs encryption is part of physical security b/c it is to protect against mounting a drive/parititions on a non-native boot system/machine), then you shouldn't even be keeping such sensitive data on machines you can be traced to. and i doubt A is the case.
  5. For a *nix server you should have multiple parititions for most data points on the file system. Generally I do the following: Filesystem Size Used Avail Use% Mounted on /dev/hda1 16M 5.6M 8.9M 39% /boot /dev/hda2 342M 218M 107M 68% / /dev/hda3 15G 8.1G 6.0G 58% /home /dev/hda5 2.3G 371M 1.9G 17% /var /dev/hda6 137M 4.1M 126M 4% /tmp /dev/hda7 919M 816M 57M 94% /usr It's important to do this so you can have corruptions of portions of your hd without it affection the entire system. Also if you run out of space in a particular mount point it wont affect everything else on the system. /boot needs to be small because it only holds your kernel, and if you use GRUB those config files for it. /home is where we make all users web space, and it is where everyone subsequently stores their data. If we run out of space in /home it wont affect mail, logs, mysql data which is stored in /var (on a debian system). We keep our http root in /home with a specific user and keep all of it's logs there as well. In case someone attempts to something to Apache and it creates excessive logs, it wont overflow to anything. /var is for mysql, mail, logs etc etc. /tmp so we our tmp files dont become too many and take space away from var and home. /usr holds the src dir and applications. this doesn't really every change in size on a server. You have all the apps you need installed and your kernel src's there. Again helps keep things seperate. The above drive is about 20gigs. Just remember: most of your space should go to /home, then to /var. And the least amount to /boot. This works well for us and should for you as well. ALSO, use a journal file system. If for some reason the box restarts, power goes out, power supply issues etc, you want it to be able to skip the fsck on boot so your services come back. ext3 performance is fine for even the most traffic entensive systems and it builds on the stability of ext2 by just adding journaling.
  6. /etc/lilo.conf needs to be edited to represent the new kernel. after editing run lilo if you use grub uhh... edit the /boot/grub/ files then run the appropriate grub command to update. heh, i can't remember the details of grub. see the man pages. if that doesn't work. be more specific with what happens etc when you boot.
  7. plan 9 is a real time os developed at the old bell labs. don't bother with it.
  8. i'm going with the easy answer here. setup your linux box to do dhcp. dhcp-client - DHCP Client dhcp3-client - DHCP Client pump - BOOTP and DHCP client for automatic IP configuration udhcpc - very small DHCP client dhcpcd - DHCP client for automatically configuring IPv4 networking. hope that helps.
  9. "Shhh, wait... Is someone on the line?"
  10. Debian. apt-get into it tons of packages, tons of supported architectures. you know it's stable.
  11. top - shows a breakdown of mem usage, cpu usage, running apps and what resources they are using, and how many apps are running/sleep etc ps ax (no hyphon anymore, it was depreciated) lists running processes ps ax |grep processname shows just those matching the grep string read the top man pages.
  12. sorry if this is flaming, but that doesn't make any sense. i call bullshit and am going to ask you to not troll. if you seriously think that 'linux' on a(ny) 'hp laptop' is actually the problem i'm going to have to ask for a detailed explaination that would help the thread starter with their problem. ps- i'm not a mod, i just dun like trolling.
  13. email address: it will be in the headers. screen name: you need to have someone direct connect to you and then watch inbound/outbound connections. and numerous other methods are available...
  14. REMEMBER! If you are setting up a dns server you MUST have it registered with your registrar so the root servers can "glue" it's cname to it's IP. for example: is glued to Withouth that, to put it simply, things will not work right. I don't know your use but maybe a caching server might be best.
  15. First I'll start with a quote: "Only two types of users use a GUI: PowerUsers, and newbies. And you are not a PowerUser." The way i really learned bash and using linux in tty was not installing any gui packages and forcing myself to learn how to do everything i wanted via the command line. here are a list of things you can do via "text mode": Aol Instant Messenger via pork or naim. Both support irc and yahoo msngr's as well. web sites via lynx or links. mp3 playing. video if you setup realplayer or whatever you use as your player to launch xserver with no desktop environment and just that app. programming: vi, elvis, emacs network tools ssh, email, irc etc Anyways... You can do most everything. It takes some patience and a want to learn. But if you do you will certainly be thankful in the long run. In fact I think i'm ready to do it again ;P AND REMEMBER! alt+f2,f3,f4 etc for multiple sessions!