Linux Help
guides forums blogs
Home Desktops Distributions ISO Images Logos Newbies Reviews Software Support & Resources Linuxhelp Wiki

Welcome Guest ( Log In | Register )



Advanced DNS Management
New ZoneEdit. New Managment.

FREE DNS Is Back

Sign Up Now
2 Pages V   1 2 >

lussumo
Posted on: Apr 27 2004, 10:52 AM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I figure I'll take this thing one step at a time. So yesterday I apt-get'ed snort.

Today I recieved an email from cron.daily with a snort report that was completely empty.

So there was some configuration I missed or something. I did some digging and found this page where they say that snort for woody is outdated and buggy and that I should instead use this:

http://people.debian.org/~ssmeenk/snort-stable-i386/

I put that into my sources.lst file and it failed to connect to it.

I must have entered it wrong in the sources.lst file. What is the format I should be using to add that to the sources.lst file?
  Forum: Technical Support · Post Preview: #12300 · Replies: 2 · Views: 2,211

lussumo
Posted on: Apr 25 2004, 11:28 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Okay, so I finally got iptables working and logging everything it drops.

So what do I do now? Sit here hoping everything is working just fine?

I was thinking I should probably set up some kind of web interface for looking at the dropped packets and then set up rules to explicitly drop packets from particular ips if they keep hounding me.

I did some digging in packages.debian.org and didn't see much that seemed to suit my purposes. I apt-get'ed fwlogwatch and the results of running that program are pretty unimpressive. It pulled ONE ip from the log (there are already TONS of dropped packets and I've only had iptables working properly for a day or so).

Does anyone have any suggestions for iptable log analysis?

Any other suggestions for steps to take security-wise?
  Forum: Technical Support · Post Preview: #12237 · Replies: 2 · Views: 2,211

lussumo
Posted on: Apr 25 2004, 11:23 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Yeah, I finally got it working with the help of some tech support ppl...

I had to restart /etc/init.d/klogd and it started logging just fine.
  Forum: Technical Support · Post Preview: #12236 · Replies: 9 · Views: 5,238

lussumo
Posted on: Apr 23 2004, 11:47 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Here's mine (it's debian woody)

CODE
#  /etc/syslog.conf    Configuration file for syslogd.
#
#      For more information see syslog.conf(5)
#      manpage.

#
# First some standard logfiles.  Log by facility.
#

auth,authpriv.*      /var/log/auth.log
*.*;auth,authpriv.none  -/var/log/syslog
#cron.*    /var/log/cron.log
daemon.*      -/var/log/daemon.log
kern.*    -/var/log/kern.log
lpr.*    -/var/log/lpr.log
mail.*    -/var/log/mail.log
user.*    -/var/log/user.log
uucp.*    /var/log/uucp.log

#
# Logging for the mail system.  Split it up so that
# it is easy to write scripts to parse these files.
#
mail.info      -/var/log/mail.info
mail.warn      -/var/log/mail.warn
mail.err      /var/log/mail.err

# Logging for INN news system
#
news.crit      /var/log/news/news.crit
news.err      /var/log/news/news.err
news.notice      -/var/log/news/news.notice

#
# Some `catch-all' logfiles.
#
*.=debug;
    auth,authpriv.none;
    news.none;mail.none    -/var/log/debug
*.=info;*.=notice;*.=warn;
    auth,authpriv.none;
    cron,daemon.none;
    mail,news.none  -/var/log/messages

#
# Emergencies are sent to everybody logged in.
#
*.emerg    *

#
# I like to have messages displayed on the console, but only on a virtual
# console I usually leave idle.
#
#daemon,mail.*;
#    news.=crit;news.=err;news.=notice;
#    *.=debug;*.=info;
#    *.=notice;*.=warn    /dev/tty8

# The named pipe /dev/xconsole is for the `xconsole' utility.  To use it,
# you must invoke `xconsole' with the `-file' option:
#
#    $ xconsole -file /dev/xconsole [...]
#
# NOTE: adjust the list below, or you'll go crazy if you have a reasonably
#      busy site..
#
daemon.*;mail.*;
    news.crit;news.err;news.notice;
    *.=debug;*.=info;
    *.=notice;*.=warn    |/dev/xconsole
  Forum: Technical Support · Post Preview: #12221 · Replies: 9 · Views: 5,238

lussumo
Posted on: Apr 23 2004, 09:43 AM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I don't have a /etc/init.d/syslog file.
I've got /etc/init.d/sysklogd, but that doesn't have a status option.

It has {start|stop|reload|restart|force-reload|reload-or-restart}

I tried /etc/init.d/sysklogd restart, and it said:

Stopping system log daemon: syslogd.
Starting system log daemon: syslogd.

I assume that means it *was* running all along - if that is what you were getting at...

I did that about an hour ago, and there is still nothing logged for iptables and the kern.log is still empty.
  Forum: Technical Support · Post Preview: #12194 · Replies: 9 · Views: 5,238

lussumo
Posted on: Apr 23 2004, 07:32 AM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I've just noticed that my kern.log is totally empty, too.
Is that normal?
  Forum: Technical Support · Post Preview: #12191 · Replies: 9 · Views: 5,238

lussumo
Posted on: Apr 23 2004, 07:13 AM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I don't know, robert.
I think the way I've set up my rules should work just fine and the real issue is that it's not logging into any files because of some other non-rules based issue. But why debate? Here's my ruleset...

CODE
#!/bin/sh
#
# Make this executable with
# chmod 700 iptables-rules
# execute with ./iptables-rules

# save typing & confusion with variables

IP_LOCAL=***.***.***.*** (commented out for obvious reasons)
IPTABLES=/sbin/iptables
test -x $IPTABLES || exit 5

case "$1" in
start)
echo -n "Loading Packet Filters"

# SETUP -- stuff necessary for any bastion host

# Load kernel modules first
# modprobe ip_tables

# Flush active rules and custom tables
$IPTABLES --flush
$IPTABLES --delete-chain

# Set default deny policies for all three default chains
$IPTABLES -P INPUT DROP
$IPTABLES -P FORWARD DROP
$IPTABLES -P OUTPUT DROP

# Give free reign to the loopback interfaces, ie. local
# processes may connect to other processes' listening ports.
$IPTABLES -A INPUT -i lo -j ACCEPT
$IPTABLES -A OUTPUT -o lo -j ACCEPT

# Do some rudimentary anti-IP-spoofing drops.
# ie. Drop any source IP address which is impossible.
$IPTABLES -A INPUT -s 255.0.0.0/8 -j LOG --log-prefix "Spoofed source IP"
$IPTABLES -A INPUT -s 255.0.0.0/8 -j DROP
$IPTABLES -A INPUT -s 0.0.0.0/8 -j LOG --log-prefix "Spoofed source IP"
$IPTABLES -A INPUT -s 0.0.0.0/8 -j DROP
$IPTABLES -A INPUT -s 127.0.0.0/8 -j LOG --log-prefix "Spoofed source IP"
$IPTABLES -A INPUT -s 127.0.0.0/8 -j DROP
$IPTABLES -A INPUT -s 192.168.0.0/8 -j LOG --log-prefix "Spoofed source IP"
$IPTABLES -A INPUT -s 192.168.0.0/8 -j DROP
$IPTABLES -A INPUT -s 172.16.0.0/8 -j LOG --log-prefix "Spoofed source IP"
$IPTABLES -A INPUT -s 172.16.0.0/8 -j DROP
$IPTABLES -A INPUT -s 10.0.0.0/8 -j LOG --log-prefix "Spoofed source IP"
$IPTABLES -A INPUT -s 10.0.0.0/8 -j DROP

# The following will NOT interfere with local inter-process traffic, whose
# packets have the source IP of the local loopback interface, eg 127.0.0.1
$IPTABLES -A INPUT -s $IP_LOCAL -j LOG --log-prefix "Spoofed source IP"
$IPTABLES -A INPUT -s $IP_LOCAL -j DROP

# Tell netfilter that all TCP sessions do indeed begin with SYN
$IPTABLES -A INPUT -p tcp ! --syn -m state --state NEW -j LOG --log-prefix "Stealth scan attempt?"
$IPTABLES -A INPUT -p tcp ! --syn -m state --state NEW -j DROP

# The packet filtering policies

# INBOUND POLICY
# (applies to packets entering our network interface from the network, and addressed to this host)

# Accept inbound packets that are part of previously OK'd sessions
$IPTABLES -A INPUT -j ACCEPT -m state --state ESTABLISHED,RELATED

# Accept inbound packets which initiate SSH sessions
$IPTABLES -A INPUT -p tcp -j ACCEPT --dport 22 -m state --state NEW

# Accept inbound packets which initiate HTTP Sessions
$IPTABLES -A INPUT -p tcp -j ACCEPT --dport 80 -m state --state NEW

# Accept inbound packets which initiate SMTP Sessions
$IPTABLES -A INPUT -p tcp -j ACCEPT --dport 25 -m state --state NEW

# Accept inbound packets which initiate IMAP SSL (mail) Sessions
$IPTABLES -A INPUT -p tcp -j ACCEPT --dport 993 -m state --state NEW

# Log and drop anything not accepted above
$IPTABLES -A INPUT -j LOG --log-prefix "Dropped by default (INPUT):"
$IPTABLES -A INPUT -j DROP

# OUTBOUND POLICY
# (applies to packets sent to the network interface (NOT loopback) from local processes)

# If it's part of an approved connection, let it out
$IPTABLES -I OUTPUT 1 -m state --state RELATED,ESTABLISHED -j ACCEPT

# Allow outbound DNS queries (eg. to resolve IPs in logs)
$IPTABLES -A OUTPUT -p udp --dport 53 -m state --state NEW -j ACCEPT
$IPTABLES -A OUTPUT -p tcp --dport 53 -m state --state NEW -j ACCEPT

# Allow outbound http requests
$IPTABLES -A OUTPUT -p tcp --dport 80 -m state --state NEW -j ACCEPT

# Allow outbound SMTP sessions (eg. to send mail)
$IPTABLES -A OUTPUT -p tcp --dport 25 -m state --state NEW -j ACCEPT

# Log & drop anything not accepted above (if for no other reason, for troubleshooting)
$IPTABLES -A OUTPUT -j LOG --log-prefix "Dropped by default (OUTPUT):"
$IPTABLES -A OUTPUT -j DROP

# Log & drop ALL incoming packets destined anywhere but here.
# (We already set hte default FORWARD policy to DROP. But this is yet another free, reassuing redundancy)
$IPTABLES -A FORWARD -j LOG --log-prefix "Attempted FORWARD? Dropped:"
$IPTABLES -A FORWARD -j DROP

;;

wide_open)
echo -n "DANGER!! Unloading Packet Filters!!"
$IPTABLES --flush
$IPTABLES -P INPUT ACCEPT
$IPTABLES -P FORWARD ACCEPT
$IPTABLES -P OUTPUT ACCEPT
;;

lockout)
echo -n "Unloading all fw rules, leaving default drop policies"
$IPTABLES --flush
;;

status)
echo -n "Querying iptables status (via iptables --list)..."
$IPTABLES --line-numbers -v --list
;;

*)
echo "Usage: $0 {start|lockout|wide_open|status}"
exit 1
;;
esac
  Forum: Technical Support · Post Preview: #12190 · Replies: 9 · Views: 5,238

lussumo
Posted on: Apr 22 2004, 09:35 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I set up iptables on my server a day or so ago. I wrote (I think) a pretty decent script to set up my rules. I have it running, and I've even tried various tools to break into it without any success - the script is working as it should.

Except...

I've set up the script to log *everything*, but I can't find *anything* being logged in my /var/log files

I wasn't sure which file it would be logged in, so I searched them all and didn't find a single thing.

I am running Debian, and I just used apt-get to install iptables. Was there some other kind of setup I had to do in order to make it log properly?
  Forum: Technical Support · Post Preview: #12175 · Replies: 9 · Views: 5,238

lussumo
Posted on: Apr 20 2004, 04:00 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


System: Debian Woody

I'm trying to set up an iptables startup script. Part of the script calls "modprobe ip_tables".

I was manually tinkering around (ie. I hadn't run the script yet), and I wanted to see what would happen if I just entered that command. I did, and I got this error:

CODE
modprobe: Can't open dependencies file /lib/modules/2.4.23-secure-2um/modules.dep (No such file or directory)


I checked out the directory, and sure enough the entire /lib/modules/ directory is completely empty. I searched the system for modules.dep and it didn't find it anywhere.

Any idea what I can do to fix this?
  Forum: Technical Support · Post Preview: #12075 · Replies: 1 · Views: 1,940

lussumo
Posted on: Mar 27 2004, 03:18 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


As a test, I added a few different sources to my sources.lst file. Still no dice.
  Forum: Technical Support · Post Preview: #10766 · Replies: 4 · Views: 2,812

lussumo
Posted on: Mar 27 2004, 10:23 AM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Yessir.
  Forum: Technical Support · Post Preview: #10752 · Replies: 4 · Views: 2,812

lussumo
Posted on: Mar 26 2004, 10:07 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I was just reading the help document (http://www.linuxhelp.ca/guides/qmail/) on how to install qmail on debian.

I got to step 5:

QUOTE
5. Installing Qmail
apt-get install ucspi-tcp-src
apt-get install qmail-src†
apt-get install procmail
build-ucspi-tcp


I tried to run the first line, and it said that it couldn't find the package. Is this because the tutorial is referring to Woody? If so, is there any way for me to get the package for sarge?
  Forum: Technical Support · Post Preview: #10733 · Replies: 4 · Views: 2,812

lussumo
Posted on: Mar 23 2004, 05:02 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Update: I did some more digging and found this:

http://www.geocrawler.com/archives/3/35/20...3/3/50/10413120

QUOTE
Looks like the L2 cache ECC checking spotted something going wrong,
and fixed it up. This can happen in cases where there is inadequate
cooling, power, or overclocking (or in rare circumstances, flaky CPUs)


I shut the machine down and took out cpu2 (Those cpu fans are HARD to get off!). Cleaned off the cooling goo and saw that it *is* pretty browned - more than you would expect.

At this point I think I'll just replace the two cpu's with newer ones.

Just thought I'd let anyone who reads this know that I've resolved the issue (sort of), or will soon.
  Forum: Technical Support · Post Preview: #10573 · Replies: 1 · Views: 2,166

lussumo
Posted on: Mar 23 2004, 03:39 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I recently installed debian on my server (thanks to hughesjr).

Today I came into my office and found that the server had an error on the screen. I opened up /var/log/syslog and found this error:

debian kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 1.
debian kernel: Bank 2: 940040000000017a

I googled that error code and found a bunch of different responses from people who said that it could be bad ram or a bad CPU.

The machine is a Dual proc athlon MP 1800.

The back story on it is that a few weeks ago it was happily running W2k server and then suddenly it started shutting down and rebooting. At that time we formatted it and reinstalled up to SP 4. However, it kept on rebooting. At the time we did a little research and found a lot of people reporting that happening after installing SP4. I decided that I was going to ditch windows anyway, so I'd just install linux and hope for the best.

When the machine was delivered to me (It had been co-located in Detroit), I turned it on and found that one of the CPU fans was bugging out. I ordered two new cpu fans and installed them both before installing linux.

So, it seems likely to me that the cpu with the screwed up fan is now toast. But how can I be sure that is what the problem is? I don't want to waste the money on a new cpu and find out that it was the ram - and I don't want to spend the money on new ram and find out it was the cpu.

Any idea how I can further debug this and find out who the culprit is?
  Forum: Technical Support · Post Preview: #10571 · Replies: 1 · Views: 2,166

lussumo
Posted on: Mar 21 2004, 07:41 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Here I am, many hours later, finally finished with the sarge install and the lamp setup.

A million thanks go out to hughesjr for the stunning amount of help you provided :)
  Forum: Technical Support · Post Preview: #10443 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 21 2004, 04:42 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I got the correct file, entered this:

CODE
cd /usr/local/src/lamps/mysql-4.0.18/
./configure --prefix=/usr/local/mysql/4.0.18
--localstatedir=/home/mysql/data --with-innodb


It started writing a ton of stuff to the screen a-la "checking blah" over and over again.

Eventually it failed here:

CODE
checking for tgetent in -lncurses... no
checking for tgetent in -lcurses... no
checking for tgetent in -ltermcap... no
checking for termcap functions library... configure: error: No curses/termcap library found


I did some digging for that error online, and most of the answers ppl gave were to install the ncurses library. So, I fired up dselect and searched for ncurses. It found it, but it is already installed.

// EDIT

I found a link that helped me, I just had to add a with statement to get it to work (pointing to the correct ncurses file)

--with-named-curses-libs=/lib/libncurses.so.5.3
  Forum: Technical Support · Post Preview: #10434 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 21 2004, 02:49 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Well, I'm half way done the fresh install, now (I'm a speed demon with it after doing it so much :)

My concern was that what I had done before that screwed up had cluttered up the machine. I wasn't sure what config files had been altered, or if I already had a mysql daemon running, and how I would go about removing that stuff. Plus, I had tried a bunch of different things to get it going and ended up messing everything up. It was easier for me to just re-install.

The way I see it, you learn through mistakes. If everything just worked all the time, would you ever learn anything?
  Forum: Technical Support · Post Preview: #10427 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 21 2004, 02:23 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Okay, screw it.
I'm starting all over again with the fresh install of the OS, and downloading the exact mysql source on my windows machine, burning it to a cd, and I'll copy it over to the linux box from there.
  Forum: Technical Support · Post Preview: #10424 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 21 2004, 01:28 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I've got some problems...

First of all, the links on to mysql didn't work when using lynx (I guess it didn't forward like it should), so I ended up going to one of the mirrors directly and downloading a source with a different file name.

I went here: http://mirror.cpsc.ucalgary.ca/mirror/mysq.../mysql-4.0.html

I got this: http://mirror.cpsc.ucalgary.ca/mirror/mysq...nux-i686.tar.gz

Then, following the walkthrough, I created and decompressed those files/folders here: /usr/local/src/lamps

Next up in the tutorial it said to do this:
CODE
cd /usr/local/src/lamps/mysql-3.23.57/
./configure --prefix=/usr/local/mysql/3.23.57
--localstatedir=/home/mysql/data --with-innodb


Instead of that, I did this:
CODE
cd /usr/local/src/lamps/mysql-standard-4.0.18-pc-linux-i686/
./configure --prefix=/usr/local/mysql/4.0.18
--localstatedir=/home/mysql/data --with-innodb


When I hit enter after that, it spit out a huge page of stuff. At the very top it said, "Note! this is a binary package and you do not need to compile." or something like that (it scrolled too far for me to see it for long).

From what I can still see on the screen, it said:

CODE
Preparing db table
Preparing host table
Preparing user table
Preparing func table
Preparing tables_priv table
Preparing columns_priv table
Installing all prepared tables
040321  8:19:53  ./bin/mysqld: Shutdown Complete

To start mysqld at boot time you have to copy support-files/mysql.server to the right place in your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
to do so, start the server ,then issue the following commands:
./bin/mysqladmin -u root password 'new-password'
./bin/mysqladmin -u root -h debian password 'new-password'
See the manual for more instructions.

You can start the MySQL daemon with:
cd .; ./bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench; perl run-all-tests

Please report any problems with the ./bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://mysql.com
Support MySQL by buying support/licenses at https://order.mysql.com

Starting the mysqld server. You can test that it is up and running with the command:
./bin/mysqladmin version
debian:/usr/local/src/lamps/mysql-standard-4.0.18-pc-linux-i686# chown: 'mysql' : invalid user
Starting mysqld daemon with databases from /usr/local/src/lamps/mysql-standard-4.0.18-pc-linux-i686/data
040321 08:19:54 mysqld ended


A little confused, I figured I'd just try to check it like it said above, so I typed in "./bin/mysqladmin version"

It spat out:

CODE
./bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/tmp/mysql.sock' exists!


Now, the next command in the LAMP walkthrough was the make/make install, but I take it that's not what I have to do here (duh). but something got screwed up, and I don't know if it was because of the command I ran to install the thing, or if it was because I tried to install it in this directory: "/usr/local/mysql/4.0.18" or what.

Not really sure what to do next. Not sure if I've totally screwed it up to the point where I'll need to remove everything and try again... or what...
  Forum: Technical Support · Post Preview: #10423 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 21 2004, 12:08 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Okay, new base system and new smp kernel installed and working biggrin.gif

The vga=792 line is a life saver. The giant text on my screen was killing me. Now I can actually see everything when I type ls smile.gif

Now moving on to LAMP...
  Forum: Technical Support · Post Preview: #10416 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 21 2004, 11:19 AM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Thanks again - Here I go smile.gif
  Forum: Technical Support · Post Preview: #10412 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 21 2004, 10:52 AM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


I can't believe how awesome you're being. Thank you!

One stupid question: when using the new installer, at one point it asks which version I'd like to install (stable, testing, etc). Since this is the sarge installer, should I be choosing stable (which would give me the most stable version of sarge)? Or will Stable get me the older version and I should be choosing testing?
  Forum: Technical Support · Post Preview: #10409 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 21 2004, 02:47 AM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


QUOTE
If you use sarge, you can install the kernel-image-2.6.3smp and it should recognize almost everything (including dual processors).


How can I specify a kernel?

I downloaded the sarge installer (http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-businesscard.iso) and installed using that. I looked through all of the options before installing, and I even tried installing as an expert, but never saw an option for the type of kernel to install. Do I have to use sarge-i386-netinst.iso ?
  Forum: Technical Support · Post Preview: #10394 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 20 2004, 08:57 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


Oh, another thing I forgot to mention/ask: My machine is a dual proc athlon mp 1800. Does the debian installer detect the dual procs automagically? Is there a way for me to check to see that it's using both? Will I need to recompile the kernel? (There's a mouthful for ya)
  Forum: Technical Support · Post Preview: #10378 · Replies: 37 · Views: 33,256

lussumo
Posted on: Mar 20 2004, 08:35 PM


Grub-er
**

Group: Members
Posts: 33
Joined: 15-March 04
From: Toronto, Ontario
Member No.: 2,590


awesome - thanks once again for all of the help. I'd be very interested to see that LAMP install/walkthrough. I'd even start over from scratch again and do it (I'm getting used to the installs at this point smile.gif.

I'm thinking at this point that I don't really need the gui. If I really want to go linux all the way, I might as well stick with the command prompt and midnight commander. Learn me up real good.

Another thing I'm not sure about: when all is said and done, how should I go about transporting my web apps over to the server? ftp? ssh? any recommendations?

edit /// btw: I installed the stable version (woody) because I am always afraid of software in testing phase. Is sarge in a stable enough state do you think?
  Forum: Technical Support · Post Preview: #10375 · Replies: 37 · Views: 33,256

2 Pages V   1 2 >

New Posts  New Replies
No New Posts  No New Replies
Hot topic  Hot Topic (New)
No new  Hot Topic (No New)
Poll  Poll (New)
No new votes  Poll (No New)
Closed  Locked Topic
Moved  Moved Topic
 

RSS Lo-Fi Version Time is now: 19th November 2017 - 07:29 PM