Re: [expert] Linux Mandrake 6.0 Question

[Jo]

There is an IPCHAINS howto. It explains very well how to set up
IPCHAINS. I also found a linux LAN & Firewall FAQ, that has helped
enormously to learn setup a firewall. You can find it at the following
address:

http://rlz.ne.mediaone.net/linux/

Make sure you have a look at the Firewall Design Tool!

Jo

Steve Philp wrote:
> 
> Axalon Bloodstone wrote:
> >
> > On Sat, 21 Aug 1999, Steve Fox wrote:
> >
> > > >
> > > > 5.  I haven't found any package that will masquerade other LAN machines onto
> > > > the internet.  Supposedly it can be done through ipchains scripts, but
> > > > I haven't made any work yet.  I did use PaNTs which is supposed to work for
> > > > RedHat 6 but I can't get anything through it on port 80 (web access).
> > >
> > > echo 1> /proc/sys/net/ipv4/conf/eth0/forwarding
> >   ipchains -P forward DENY
> > > ipchains -I forward -j MASQ -s 192.168.0.0/16 -i eth0 -d 0/0
> > > ipchains -I input -j DENY -s 192.168.0.0/16 -i ! eth0 -d 0/0 -l
> > >
> 
> I haven't played with IP chains yet, but I get the notion that I may be
> using it to put a bigger choke mechanism on a web server box.  Could you
> verify that my reading of the ipchains rules are correct?
> 
> By default, deny all forwarding.  Allow forwarding of packets sourced on
> 192.168. and received on eth0.  Deny forwarding of 192.168. packets that
> did not get received on eth0.
> 
> Is that correct?
> 
> I've got the following setup:  an ISDN connection that's terminated at a
> Cisco router with 2 ethernet connections running their PIX firewall
> software.  On one ether port (192.168.4.x), is our "Internet" network.
> It currently houses one machine which acts as the web/email server for
> outside connections.  Inside connections use that machine as their soul
> gateway to the outside world (junkbuster and squid along with pop3 and
> smtp services).  The other ether port (192.168.3.x) connects to our
> internal network.
> 
> I'd like to put a bigger limit on the kinds of things that the webserver
> will allow to be sent into the internal network.  We need to allow the
> squid and junkbuster conversations in, and I also need to be able to
> talk to the machine via telnet from the internal connection.
> 
> I'm not worried (much) about people being able to attack the internal
> network from the Internet, since they're all private IP net addresses
> that get nowhere when used on the Internet.  However, if someone is able
> to break into the web box, they can see the internal network and talk to
> it from there.  I'd prefer that not to be possible.
> 
> Any ideas?
> 
> --
> Steve Philp
> Network Administrator
> Advance Packaging Corp.
> [EMAIL PROTECTED]

Re: [expert] Linux Mandrake 6.0 Question (Ip Masq Tutorial. v0.0.1)

[Axalon Bloodstone]

On Sun, 22 Aug 1999, Steve Philp wrote:

> Thanks for the tips.  I've printed them out to ponder over a cup of
> coffee.  I'll be putting a few more lockdowns on the machine on Monday.
> 
> Primarily, I'm not concerned with the internal network.  The router is
> setup to deny all Internet packets from inside that don't come from the
> proxy machine.  I've got junkbuster setup to only allow access to about
> 5 "approved" sites (default deny is a wonderful thing!).  Squid is setup
> to allow a select few to connect to it directly (mostly IS and executive
> level -- those are assigned static IPs while the rest of the place is
> DHCP), any other attempts at direct connections to Squid are sent
> packing.
> 
> I'm mostly worried about closing up avenues to go from the .4.x machine
> to the .3.x network.  If (god forbid) that web/email machine gets
> cracked, I want there to be very little possibility of getting into the
> internal network.  I suppose I could setup rules that only allow packets
> originating from the 4.x machine and coming from ports 3128 and 8000
> (squid, junkbuster) and to allow packets originating from inside on a
> couple IPs.

something like
ipchains -A input -s 192.168.3.0/24 -d 0/0 -j DENY -l -b
ipchains -A output -s 192.168.3.0/24 -d 0/0 -j DENY -l -b

that should pretty much throw a wrench into things, and you'll need to
make a hole for the proxies.
 
> Thanks again for the explanation of the IP chains stuff.
> 
> 

--
MandrakeSoft  http://www.mandrakesoft.com/
--Axalon

Re: [expert] Linux Mandrake 6.0 Question (Ip Masq Tutorial. v0.0.1)

[Steve Philp]

Axalon Bloodstone wrote:
> 
> On Sat, 21 Aug 1999, Steve Philp wrote:
> 
> > Axalon Bloodstone wrote:
> > >
> > > On Sat, 21 Aug 1999, Steve Fox wrote:
> > >
> > > > >
> > > > > 5.  I haven't found any package that will masquerade other LAN machines onto
> > > > > the internet.  Supposedly it can be done through ipchains scripts, but
> > > > > I haven't made any work yet.  I did use PaNTs which is supposed to work for
> > > > > RedHat 6 but I can't get anything through it on port 80 (web access).
> > > >
> > > > echo 1> /proc/sys/net/ipv4/conf/eth0/forwarding
> > >   ipchains -P forward DENY
> > > > ipchains -I forward -j MASQ -s 192.168.0.0/16 -i eth0 -d 0/0
> > > > ipchains -I input -j DENY -s 192.168.0.0/16 -i ! eth0 -d 0/0 -l
> > > >
> >
> > I haven't played with IP chains yet, but I get the notion that I may be
> > using it to put a bigger choke mechanism on a web server box.  Could you
> > verify that my reading of the ipchains rules are correct?
> >
> > By default, deny all forwarding.  Allow forwarding of packets sourced on
> > 192.168. and received on eth0.  Deny forwarding of 192.168. packets that
> > did not get received on eth0.
> >
> > Is that correct?
> 
> First a demonstration of exactly what the above commands will accomplish
> 
> We have an existing private lan, operateing with non internet routable ip
> addresses. Say we have two interfaces, *0 and *1, * can be any type of
> network connection, eth ppp lo and all the others it doesn't matter.
> 
> Both will be ethernet, your basic highspeed connections.
> We'll use eth0 for the private network (192.168.1.0/24 for this example)
> eth1 for internet.
> 
> ##end /etc/rc.d/rc.firewall
> ##Begin Masq
> #Tell eth0 we want to be able to forward from it
> echo 1 > /proc/sys/net/ipv4/conf/eth0/forwarding
> #Setup a default reject on forwarding
> ipchains -P forward REJECT
> #Now the catch all logger
> ipchains -A forward -s 0/0 -d 0/0 -j DENY -l
> #Setup forwarding from the lan to anything not on it
> ipchains -I forward -s 192.168.1.0/24 -d \! 192.168.1.0/24 -i eth1 -j MASQ
> ##end Masq
> 
> So
> only forward from eth0.
> By default, REJECT all forwarding requests.
> Append, a DENY on everything, and log it
> (to many overly talented ipv4 people out there, congradulations i'm
> paranoid)
> Insert, a MASQ rule for our private lan. "outgoing" only
> (again the paranoid thing, some very talented source route'ers)
> 
> Now some rules when createing scripts like this.
> DOCUMENT every line or make some form of blocks, with comments, you WILL
> forget eventualy.
> Unless your really getting creative with custom chains,
> Appends (-A) should be used for DENY/REJECT commands
> Inserts (-I) should be used for ACCEPT/MASQ commands
> This help you to keep (me) from gettign denied when you swore you added
> the ip to the firewall, or prevent "well how the bleep did he even get to
> telnet, i had it firewalled" type situations. It basicly just makes it
> look nice also.
> 
> And now we tackle
> 
> > I've got the following setup:  an ISDN connection that's terminated at a
> > Cisco router with 2 ethernet connections running their PIX firewall
> > software.  On one ether port (192.168.4.x), is our "Internet" network.
> > It currently houses one machine which acts as the web/email server for
> > outside connections.  Inside connections use that machine as their soul
> > gateway to the outside world (junkbuster and squid along with pop3 and
> > smtp services).  The other ether port (192.168.3.x) connects to our
> > internal network.
> >
> > I'd like to put a bigger limit on the kinds of things that the webserver
> > will allow to be sent into the internal network.  We need to allow the
> > squid and junkbuster conversations in, and I also need to be able to
> > talk to the machine via telnet from the internal connection.
> >
> > I'm not worried (much) about people being able to attack the internal
> > network from the Internet, since they're all private IP net addresses
> > that get nowhere when used on the Internet.  However, if someone is able
> > to break into the web box, they can see the internal network and talk to
> > it from there.  I'd prefer that not to be possible.
> >
> > Any ideas?
> 
>  following the same basic princples, everybodys with me right? ,
> because here comes the fun part.
> 
> setup:
> ISDN to Cisco router,
> 2port Cisco router, supplying
> 192.168.4.0/24 (cisco1 for lack of a better name)
> And an unused cisco0
> 192.168.4.254, Will be our gateway, with an internet IP (provided by
> Cisco's PIX firewall)
> This machine provides 192.168.3.0/24 with proxying via squid and
> junkbuster
> with 192.168.3.254, as it's internal IP
> 
> How can we strengthen this with ipchains you ask? well lets see
> 
> ##
> # First verify forwarding is disabled
> echo 0 > /proc/sys/net/ipv4/conf/all/forwarding
> # Default REJECT
> ipchains -P forward REJECT
> # DENY and log anyones attempts to fo

Re: [expert] Linux Mandrake 6.0 Question (Ip Masq Tutorial. v0.0.2)

[Axalon Bloodstone]

Ooops!

On Sat, 21 Aug 1999, Axalon Bloodstone wrote:

> On Sat, 21 Aug 1999, Steve Philp wrote:
> 
> > Axalon Bloodstone wrote:
> > > 
> > > On Sat, 21 Aug 1999, Steve Fox wrote:
> > > 
> > > > >
> > > > > 5.  I haven't found any package that will masquerade other LAN machines onto
> > > > > the internet.  Supposedly it can be done through ipchains scripts, but
> > > > > I haven't made any work yet.  I did use PaNTs which is supposed to work for
> > > > > RedHat 6 but I can't get anything through it on port 80 (web access).
> > > >
> > > > echo 1> /proc/sys/net/ipv4/conf/eth0/forwarding
> > >   ipchains -P forward DENY
> > > > ipchains -I forward -j MASQ -s 192.168.0.0/16 -i eth0 -d 0/0
> > > > ipchains -I input -j DENY -s 192.168.0.0/16 -i ! eth0 -d 0/0 -l
> > > >
> > 
> > I haven't played with IP chains yet, but I get the notion that I may be
> > using it to put a bigger choke mechanism on a web server box.  Could you
> > verify that my reading of the ipchains rules are correct?
> > 
> > By default, deny all forwarding.  Allow forwarding of packets sourced on
> > 192.168. and received on eth0.  Deny forwarding of 192.168. packets that
> > did not get received on eth0.
> > 
> > Is that correct?
> 
> First a demonstration of exactly what the above commands will accomplish
> 
> We have an existing private lan, operateing with non internet routable ip
> addresses. Say we have two interfaces, *0 and *1, * can be any type of
> network connection, eth ppp lo and all the others it doesn't matter.
> 
> Both will be ethernet, your basic highspeed connections.
> We'll use eth0 for the private network (192.168.1.0/24 for this example)
> eth1 for internet.
> 
> ##end /etc/rc.d/rc.firewall
> ##Begin Masq
> #Tell eth0 we want to be able to forward from it
> echo 1 > /proc/sys/net/ipv4/conf/eth0/forwarding
  
  # Tell eth1 we want to beable to forward to it
  echo 1 > /proc/sys/net/ipv4/conf/eth0/forwarding

> #Setup a default reject on forwarding
> ipchains -P forward REJECT
> #Now the catch all logger
> ipchains -A forward -s 0/0 -d 0/0 -j DENY -l
> #Setup forwarding from the lan to anything not on it
> ipchains -I forward -s 192.168.1.0/24 -d \! 192.168.1.0/24 -i eth1 -j MASQ
> ##end Masq
> 
> So
> only forward from eth0.
> By default, REJECT all forwarding requests. 
> Append, a DENY on everything, and log it 
>   (to many overly talented ipv4 people out there, congradulations i'm
>   paranoid)
> Insert, a MASQ rule for our private lan. "outgoing" only 
>   (again the paranoid thing, some very talented source route'ers)
> 
> Now some rules when createing scripts like this.
> DOCUMENT every line or make some form of blocks, with comments, you WILL
>   forget eventualy.
> Unless your really getting creative with custom chains,
>   Appends (-A) should be used for DENY/REJECT commands
>   Inserts (-I) should be used for ACCEPT/MASQ commands
> This help you to keep (me) from gettign denied when you swore you added
> the ip to the firewall, or prevent "well how the bleep did he even get to
> telnet, i had it firewalled" type situations. It basicly just makes it
> look nice also.
> 
> 
> And now we tackle 
> 
> > I've got the following setup:  an ISDN connection that's terminated at a
> > Cisco router with 2 ethernet connections running their PIX firewall
> > software.  On one ether port (192.168.4.x), is our "Internet" network. 
> > It currently houses one machine which acts as the web/email server for
> > outside connections.  Inside connections use that machine as their soul
> > gateway to the outside world (junkbuster and squid along with pop3 and
> > smtp services).  The other ether port (192.168.3.x) connects to our
> > internal network.
> > 
> > I'd like to put a bigger limit on the kinds of things that the webserver
> > will allow to be sent into the internal network.  We need to allow the
> > squid and junkbuster conversations in, and I also need to be able to
> > talk to the machine via telnet from the internal connection.
> > 
> > I'm not worried (much) about people being able to attack the internal
> > network from the Internet, since they're all private IP net addresses
> > that get nowhere when used on the Internet.  However, if someone is able
> > to break into the web box, they can see the internal network and talk to
> > it from there.  I'd prefer that not to be possible.
> > 
> > Any ideas?
>  
>  following the same basic princples, everybodys with me right? ,
> because here comes the fun part.
> 
> setup:
> ISDN to Cisco router,
> 2port Cisco router, supplying
> 192.168.4.0/24 (cisco1 for lack of a better name)
> And an unused cisco0
> 192.168.4.254, Will be our gateway, with an internet IP (provided by
>   Cisco's PIX firewall)
> This machine provides 192.168.3.0/24 with proxying via squid and
>   junkbuster
> with 192.168.3.254, as it's internal IP
> 
> 
> How can we strengthen this with ipchains you ask? well lets see
> 
> 
> ##
> # First verify forwarding is disabled

Re: [expert] Linux Mandrake 6.0 Question (Ip Masq Tutorial. v0.0.1)

[Axalon Bloodstone]

On Sat, 21 Aug 1999, Steve Philp wrote:

> Axalon Bloodstone wrote:
> > 
> > On Sat, 21 Aug 1999, Steve Fox wrote:
> > 
> > > >
> > > > 5.  I haven't found any package that will masquerade other LAN machines onto
> > > > the internet.  Supposedly it can be done through ipchains scripts, but
> > > > I haven't made any work yet.  I did use PaNTs which is supposed to work for
> > > > RedHat 6 but I can't get anything through it on port 80 (web access).
> > >
> > > echo 1> /proc/sys/net/ipv4/conf/eth0/forwarding
> >   ipchains -P forward DENY
> > > ipchains -I forward -j MASQ -s 192.168.0.0/16 -i eth0 -d 0/0
> > > ipchains -I input -j DENY -s 192.168.0.0/16 -i ! eth0 -d 0/0 -l
> > >
> 
> I haven't played with IP chains yet, but I get the notion that I may be
> using it to put a bigger choke mechanism on a web server box.  Could you
> verify that my reading of the ipchains rules are correct?
> 
> By default, deny all forwarding.  Allow forwarding of packets sourced on
> 192.168. and received on eth0.  Deny forwarding of 192.168. packets that
> did not get received on eth0.
> 
> Is that correct?

First a demonstration of exactly what the above commands will accomplish

We have an existing private lan, operateing with non internet routable ip
addresses. Say we have two interfaces, *0 and *1, * can be any type of
network connection, eth ppp lo and all the others it doesn't matter.

Both will be ethernet, your basic highspeed connections.
We'll use eth0 for the private network (192.168.1.0/24 for this example)
eth1 for internet.

##end /etc/rc.d/rc.firewall
##Begin Masq
#Tell eth0 we want to be able to forward from it
echo 1 > /proc/sys/net/ipv4/conf/eth0/forwarding
#Setup a default reject on forwarding
ipchains -P forward REJECT
#Now the catch all logger
ipchains -A forward -s 0/0 -d 0/0 -j DENY -l
#Setup forwarding from the lan to anything not on it
ipchains -I forward -s 192.168.1.0/24 -d \! 192.168.1.0/24 -i eth1 -j MASQ
##end Masq

So
only forward from eth0.
By default, REJECT all forwarding requests. 
Append, a DENY on everything, and log it 
(to many overly talented ipv4 people out there, congradulations i'm
paranoid)
Insert, a MASQ rule for our private lan. "outgoing" only 
(again the paranoid thing, some very talented source route'ers)

Now some rules when createing scripts like this.
DOCUMENT every line or make some form of blocks, with comments, you WILL
forget eventualy.
Unless your really getting creative with custom chains,
Appends (-A) should be used for DENY/REJECT commands
Inserts (-I) should be used for ACCEPT/MASQ commands
This help you to keep (me) from gettign denied when you swore you added
the ip to the firewall, or prevent "well how the bleep did he even get to
telnet, i had it firewalled" type situations. It basicly just makes it
look nice also.


And now we tackle 

> I've got the following setup:  an ISDN connection that's terminated at a
> Cisco router with 2 ethernet connections running their PIX firewall
> software.  On one ether port (192.168.4.x), is our "Internet" network. 
> It currently houses one machine which acts as the web/email server for
> outside connections.  Inside connections use that machine as their soul
> gateway to the outside world (junkbuster and squid along with pop3 and
> smtp services).  The other ether port (192.168.3.x) connects to our
> internal network.
> 
> I'd like to put a bigger limit on the kinds of things that the webserver
> will allow to be sent into the internal network.  We need to allow the
> squid and junkbuster conversations in, and I also need to be able to
> talk to the machine via telnet from the internal connection.
> 
> I'm not worried (much) about people being able to attack the internal
> network from the Internet, since they're all private IP net addresses
> that get nowhere when used on the Internet.  However, if someone is able
> to break into the web box, they can see the internal network and talk to
> it from there.  I'd prefer that not to be possible.
> 
> Any ideas?
 
 following the same basic princples, everybodys with me right? ,
because here comes the fun part.

setup:
ISDN to Cisco router,
2port Cisco router, supplying
192.168.4.0/24 (cisco1 for lack of a better name)
And an unused cisco0
192.168.4.254, Will be our gateway, with an internet IP (provided by
Cisco's PIX firewall)
This machine provides 192.168.3.0/24 with proxying via squid and
junkbuster
with 192.168.3.254, as it's internal IP


How can we strengthen this with ipchains you ask? well lets see


##
# First verify forwarding is disabled
echo 0 > /proc/sys/net/ipv4/conf/all/forwarding
# Default REJECT
ipchains -P forward REJECT
# DENY and log anyones attempts to forward thru us
ipchains -A forward -s 0/0 -d 0/0 -l -j DENY

# Ok thats pretty basic, now we get paranoid

# DENY, and log any connections to us from inside as anything but our
# gateway IP
ipchains -I input -s 192.168.3.0/24 -d ! 192.168.3.254

Re: [expert] Linux Mandrake 6.0 Question

[Steve Philp]

Axalon Bloodstone wrote:
> 
> On Sat, 21 Aug 1999, Steve Fox wrote:
> 
> > >
> > > 5.  I haven't found any package that will masquerade other LAN machines onto
> > > the internet.  Supposedly it can be done through ipchains scripts, but
> > > I haven't made any work yet.  I did use PaNTs which is supposed to work for
> > > RedHat 6 but I can't get anything through it on port 80 (web access).
> >
> > echo 1> /proc/sys/net/ipv4/conf/eth0/forwarding
>   ipchains -P forward DENY
> > ipchains -I forward -j MASQ -s 192.168.0.0/16 -i eth0 -d 0/0
> > ipchains -I input -j DENY -s 192.168.0.0/16 -i ! eth0 -d 0/0 -l
> >

I haven't played with IP chains yet, but I get the notion that I may be
using it to put a bigger choke mechanism on a web server box.  Could you
verify that my reading of the ipchains rules are correct?

By default, deny all forwarding.  Allow forwarding of packets sourced on
192.168. and received on eth0.  Deny forwarding of 192.168. packets that
did not get received on eth0.

Is that correct?

I've got the following setup:  an ISDN connection that's terminated at a
Cisco router with 2 ethernet connections running their PIX firewall
software.  On one ether port (192.168.4.x), is our "Internet" network. 
It currently houses one machine which acts as the web/email server for
outside connections.  Inside connections use that machine as their soul
gateway to the outside world (junkbuster and squid along with pop3 and
smtp services).  The other ether port (192.168.3.x) connects to our
internal network.

I'd like to put a bigger limit on the kinds of things that the webserver
will allow to be sent into the internal network.  We need to allow the
squid and junkbuster conversations in, and I also need to be able to
talk to the machine via telnet from the internal connection.

I'm not worried (much) about people being able to attack the internal
network from the Internet, since they're all private IP net addresses
that get nowhere when used on the Internet.  However, if someone is able
to break into the web box, they can see the internal network and talk to
it from there.  I'd prefer that not to be possible.

Any ideas?

-- 
Steve Philp
Network Administrator
Advance Packaging Corp.
[EMAIL PROTECTED]

Re: [expert] Linux Mandrake 6.0 Question

[Axalon Bloodstone]

On Sat, 21 Aug 1999, Steve Fox wrote:

> > 
> > 5.  I haven't found any package that will masquerade other LAN machines onto
> > the internet.  Supposedly it can be done through ipchains scripts, but
> > I haven't made any work yet.  I did use PaNTs which is supposed to work for
> > RedHat 6 but I can't get anything through it on port 80 (web access).
> 
> echo 1> /proc/sys/net/ipv4/conf/eth0/forwarding
  ipchains -P forward DENY
> ipchains -I forward -j MASQ -s 192.168.0.0/16 -i eth0 -d 0/0
> ipchains -I input -j DENY -s 192.168.0.0/16 -i ! eth0 -d 0/0 -l
> 

--
MandrakeSoft  http://www.mandrakesoft.com/
--Axalon

Re: [expert] Linux Mandrake 6.0 Question

[Steve Fox]

> 
> 5.  I haven't found any package that will masquerade other LAN machines onto
> the internet.  Supposedly it can be done through ipchains scripts, but
> I haven't made any work yet.  I did use PaNTs which is supposed to work for
> RedHat 6 but I can't get anything through it on port 80 (web access).

echo 1> /proc/sys/net/ipv4/conf/eth0/forwarding
ipchains -I forward -j MASQ -s 192.168.0.0/16 -i eth0 -d 0/0
ipchains -I input -j DENY -s 192.168.0.0/16 -i ! eth0 -d 0/0 -l

Re: [expert] Linux Mandrake 6.0 Question

[Civileme]

Well, you are limited to PCI video cards--check at http://www.XFree86.org
to see what 3.3.3.1 supports, and get the best of those you can afford. 
I have had good luck with a generic S3 Virge DX, but some of those
12Mb Voodoo Banshees looked cheap on computersurplusoutlet.
Floppy?  Ack, watch me go down in flames for this, but LS120s are
great floppies.  I have had zero problems with them and my previous
experience was that I had difficulty writing on one computer and trying
to read on another after about 6 months use.  Somehow, they seem to
become eccentric.  On the other hand, LS120s cost more than the average
motherboard.
AFAIK, /boot on the IDE and all other partitions on a SCSI should(tm)
work.
Network?  Hmmm, I have had good luck with  Realtek
RTL8029 for about $9 each, a PCI ne2K very poor clone.  I have also
used 3Com509xyz 3Com905 and 3Com Vortex as well as Intel 10/100s and some
awful things based on a Winbond Chip (which is a black hole for SCSI probes,
so don't use it on your system) with acceptable results.  The only
ones I have had trouble with are SMC cards.  Anyway the metalab.unc.edu
site should have a Linux Ethernet HOWTO which lists cards and their abilities.
The initscripts are listed at the site http://www.linux-mandrake.com
in the "updates" section.  I didn't dissect them but I would
assume /etc/rc.d directories and some others would be involved.
 
I have never set up a SMP machine, but I do recall that
there is also an updated LILO booter for SMP machines among those
updates.  It might be necessary to run single-processor til you make
that update.
Best of luck.  If you make some discoveries, remember to share. 
Never can tell when someone else will benefit from the knowledge you gain.
Civileme
 
John Aldrich wrote:
Well, let me recap what I *do* have (hardware wise):
I have a PCI/ISA-ONLY motherboard with DUAL-PPro 200's.
I have 192 megs of RAM, almost 11 GIGS of drive space (heck, I might
dual-boot Red Hat 6 and Mandrake just for the fun of it )
I have an Advansys Ultra SCSI PCI card. On-board is an SB-16/clone
built-in.
Still to get: Floppy, Network and Video. AGP is out -- no AGP slot
on a
PPro. :-)
If I read all the threads correctly, I should IMMEDIATELY get the updated
kernels and SOX, etc. Which files are the "initscripts"? I am used
to doing
a "custom" install with everything except the foreign-language "how-to"
files, and I'll certainly have the drivespace for it. With SCSI, do
I still
need to have the /boot in the first 1023 cylinders? If so, I may have
/boot
on an IDE and boot from IDE and have the rest of the system on my 9.1
GB
SCSI.
Let me also recap that I'm NOT exactly a newbie, but I'm no expert either...
:-) I've been running Linux for the past 6 months at work (dual-booting
between Linux and Win98, mostly staying in Linux ) I think I'm
taking on
a bit of a challenge here setting up an SMP machine. :-)
    John

-- 
Civileme Say:

"One who buys on leading edge soon know feeling of slide down razor blade of
life."
 

Re: [expert] Linux Mandrake 6.0 Question

[John Aldrich]

Well, let me recap what I *do* have (hardware wise):
I have a PCI/ISA-ONLY motherboard with DUAL-PPro 200's.
I have 192 megs of RAM, almost 11 GIGS of drive space (heck, I might
dual-boot Red Hat 6 and Mandrake just for the fun of it )
I have an Advansys Ultra SCSI PCI card. On-board is an SB-16/clone built-in.
Still to get: Floppy, Network and Video. AGP is out -- no AGP slot on a
PPro. :-)

If I read all the threads correctly, I should IMMEDIATELY get the updated
kernels and SOX, etc. Which files are the "initscripts"? I am used to doing
a "custom" install with everything except the foreign-language "how-to"
files, and I'll certainly have the drivespace for it. With SCSI, do I still
need to have the /boot in the first 1023 cylinders? If so, I may have /boot
on an IDE and boot from IDE and have the rest of the system on my 9.1 GB
SCSI.

Let me also recap that I'm NOT exactly a newbie, but I'm no expert either...
:-) I've been running Linux for the past 6 months at work (dual-booting
between Linux and Win98, mostly staying in Linux ) I think I'm taking on
a bit of a challenge here setting up an SMP machine. :-)
John

Re: [expert] Linux Mandrake 6.0 Question

[Axalon]

On Sun, 8 Aug 1999, Civileme wrote:

> Axalon wrote:
> 
> > On Sun, 8 Aug 1999, Civileme wrote:
> >
> > >
> > >
> > > 1.  Buy a good PCI/Video card, not expensive.  A generic S3 Virge/DX with 4Mb
> > > RAM should be adequate, even if you plan to play Quake.
> >
> > Don't skimp here get something with a good linux 3d driver
> 
> Always good advice, but from his language, it sounded as if he was looking for a
> minimalistic solution.

Just my opinion, never skimp on video when you have to look at the crap
all day .

> > > 2.  Sound, if you equip your computer with it, is most easily installed, in my
> > > experience, for Creative/Soundslaster Products.  The NEWEST should be avoided
> > > unless you like to spend a few hours on the web finding beta drivers and
> > > instructions.  (No SBLive, get a good AWE 64 for the ISA Bus and it should work
> > > out all right.)  Save sndconfig for one of your later steps.  And if you get
> > > some weird error messages running it from a console or desktop, try booting
> > > into single-user mode and running sndconfig.
> >
> > I've never had problems with any soundblaster cards
> >
> 
> I have seen problems with SB PCI 128 and SBLive, though not often

Haven't played with a sblive yet

> > > 2.1  With hardware in place, Run Install.  I recommend you select "Custom" or
> > > else run Upgrade off the CD right after install and make sure the network
> > > management workstation stuff gets loaded.
> >
> > Why do they want snmpd?
> >
> 
> He mentions at the end of his message that he plans to learn System Administration 
>from
> this machine

I wouldn't want to start learning with snmp, it gets on my nerves and i've
been at this awhile ;)

> > > 3.  Get X running and kfm(by clicking on the "Home" icon on the panel at the
> > > bottom of the screen).  Point kfm to http://www.linux-mandrake.com and look on
> > > the left side of the screen for the "Updates".  Go there, then find a mirror,
> > > still using kfm.  Once you are where the updates are listed, open another
> > > window of kfm with your home directory.  Select all the update files you want
> > > and drag them to your home directory.  Yes, you'll get "Copying files" instead
> > > of "Downloading" messages, but I believe you'll think this is prety cool.
> > > Those files are .rpm.gz so you will have to click on console which will bring a
> > > command line window up at your home directory.  (Don't do that until the copy
> > > is finished.)  DISCONNECT from the Internet (by closing the kfm window or by
> > > stopping Kppp).
> > >
> > > Then enter
> > >
> > > [noise @ /home/noise]$ su
> > > password: *give the root password here*
> > > [root@ /home/noise]# gunzip *.gz
> >
> > Did somebody hack kde and forget to tell me? The files on the mirrors
> > should be .rpm not .gz
> 
> check http://www.math.utah.edu/pub/linux/Mandrake/updates/6.0/RPMS/
> You will find *.rpm.gz files

Well sure enough, maybe someone should tell them that those are compressed
already and if they really want to cut the diskspace they shouldn't just
gzip them again but use bzip2 instead. I think it was done so winders
boxes know to use binary transfers, but it's definatly the first time i've
seen that.

> >
> >
> > > Logout
> > > login as root
> > > return to your user's home directory and open the home folder there
> > >
> > > Single-click the first .rpm file.  KPackage will open a window and you can
> > > click "Install" after ticking "replace files".  On printtool, also unclick
> > > "Check Dependencies"
> 
> >
> > seeing as your at the console already just type 'rpm -F *.rpm' , if you do
> > use kpackage it should have an Upgrade checkbox use this not Install, and
> > it generaly isn't required to use --nodeps or uncheck "Check Dependancies"
> >
> 
> The printtool update is broken and keeps reporting an unresolved dependency ">=", 
>thus the
> advice on uncheck.  Some other packages report conflicts unless you use replace 
>files.
> Moreover, the instructions are a mix of -ivh, --force, and -Uvh options.  As for 
>using
> Kpackage instead of the simple console instruction  Well, I am working on 
>migrating 20
> windows and MAC users to Linux-Mandrake, so I try to avoid command lines whenever 
>possible,
> out of habit.  Yes, the rpm is a lot simpler, but there are those who will say 
>"Command
> line?  That's too complicated."

Quite the contrary, you should enlighten them that the commandline is
nothing to be afraid of, atleast that would be my goal

> >
> > > After all of this, you should have a fairly stable system and stable Netscape
> > > to work with.
> > >
> > > 4.  The setup for remote SAMBA printers does not work.  I haven't had time to
> > > verify if it is the "filter" script in /var/spool/lpd/lp (or whatever printer
> > > name you use in place of lp) or the script filter that is copied to
> > > /usr/bin/smbprint.  I have a fix, an *ugly* one, where I add these lines to
> > > .config in the /var/spool/lpd/printername directory

Re: [expert] Linux Mandrake 6.0 Question

[Bernhard Rosenkraenzer]

On Sun, 8 Aug 1999, Civileme wrote:

> > Did somebody hack kde and forget to tell me? The files on the mirrors
> > should be .rpm not .gz
> 
> check http://www.math.utah.edu/pub/linux/Mandrake/updates/6.0/RPMS/
> You will find *.rpm.gz files

Use a different mirror then - gzip'ing RPMs is a stupid idea because they
already contain compressed data.

LLaP
bero

-- 
Tired of waiting for Windows 2000?
STOP WAITING! http://www.ms-windows-2000.com/

Re: [expert] Linux Mandrake 6.0 Question

[Civileme]

Axalon wrote:

> On Sun, 8 Aug 1999, Civileme wrote:
>
> >
> >
> > 1.  Buy a good PCI/Video card, not expensive.  A generic S3 Virge/DX with 4Mb
> > RAM should be adequate, even if you plan to play Quake.
>
> Don't skimp here get something with a good linux 3d driver

Always good advice, but from his language, it sounded as if he was looking for a
minimalistic solution.


>
>
> > 2.  Sound, if you equip your computer with it, is most easily installed, in my
> > experience, for Creative/Soundslaster Products.  The NEWEST should be avoided
> > unless you like to spend a few hours on the web finding beta drivers and
> > instructions.  (No SBLive, get a good AWE 64 for the ISA Bus and it should work
> > out all right.)  Save sndconfig for one of your later steps.  And if you get
> > some weird error messages running it from a console or desktop, try booting
> > into single-user mode and running sndconfig.
>
> I've never had problems with any soundblaster cards
>

I have seen problems with SB PCI 128 and SBLive, though not often

>
> > 2.1  With hardware in place, Run Install.  I recommend you select "Custom" or
> > else run Upgrade off the CD right after install and make sure the network
> > management workstation stuff gets loaded.
>
> Why do they want snmpd?
>

He mentions at the end of his message that he plans to learn System Administration from
this machine

>
> > 3.  Get X running and kfm(by clicking on the "Home" icon on the panel at the
> > bottom of the screen).  Point kfm to http://www.linux-mandrake.com and look on
> > the left side of the screen for the "Updates".  Go there, then find a mirror,
> > still using kfm.  Once you are where the updates are listed, open another
> > window of kfm with your home directory.  Select all the update files you want
> > and drag them to your home directory.  Yes, you'll get "Copying files" instead
> > of "Downloading" messages, but I believe you'll think this is prety cool.
> > Those files are .rpm.gz so you will have to click on console which will bring a
> > command line window up at your home directory.  (Don't do that until the copy
> > is finished.)  DISCONNECT from the Internet (by closing the kfm window or by
> > stopping Kppp).
> >
> > Then enter
> >
> > [noise @ /home/noise]$ su
> > password: *give the root password here*
> > [root@ /home/noise]# gunzip *.gz
>
> Did somebody hack kde and forget to tell me? The files on the mirrors
> should be .rpm not .gz

check http://www.math.utah.edu/pub/linux/Mandrake/updates/6.0/RPMS/
You will find *.rpm.gz files


>
>
> > Logout
> > login as root
> > return to your user's home directory and open the home folder there
> >
> > Single-click the first .rpm file.  KPackage will open a window and you can
> > click "Install" after ticking "replace files".  On printtool, also unclick
> > "Check Dependencies"

>
> seeing as your at the console already just type 'rpm -F *.rpm' , if you do
> use kpackage it should have an Upgrade checkbox use this not Install, and
> it generaly isn't required to use --nodeps or uncheck "Check Dependancies"
>

The printtool update is broken and keeps reporting an unresolved dependency ">=", thus 
the
advice on uncheck.  Some other packages report conflicts unless you use replace files.
Moreover, the instructions are a mix of -ivh, --force, and -Uvh options.  As for using
Kpackage instead of the simple console instruction  Well, I am working on 
migrating 20
windows and MAC users to Linux-Mandrake, so I try to avoid command lines whenever 
possible,
out of habit.  Yes, the rpm is a lot simpler, but there are those who will say "Command
line?  That's too complicated."

>
> > After all of this, you should have a fairly stable system and stable Netscape
> > to work with.
> >
> > 4.  The setup for remote SAMBA printers does not work.  I haven't had time to
> > verify if it is the "filter" script in /var/spool/lpd/lp (or whatever printer
> > name you use in place of lp) or the script filter that is copied to
> > /usr/bin/smbprint.  I have a fix, an *ugly* one, where I add these lines to
> > .config in the /var/spool/lpd/printername directory
> >
> > server=remoteservername
> > service=remoteprinternameonserver
> >
> > In my case that was
> >
> > server=TESTRIG
> > service=HPBIG
> >
> > for \\TESTRIG\HPBIG as accessed by the windows machines in the LAN
> >
> > ALSO, the /var/spool/lpd/lp/filter file will need editing.  In the "if" toward
> > the end of the file where it checks for "SMB", change the text
>
> The type-o introduced by Redhat, was fixed along time ago if you find
> another please let us know.
>
>

You bet.  Still not able to get any error log output when it doesn't work, even though
I have a file as target.  And why it does not work on my system while it works well on
others is yet another mystery.  I am going to try an update from a different mirror, 
as the
unfamiliarity you had with the  *.rpm.gz files suggests I might not be getting what
linux-mandrake intended.


> > ${FPID

Re: [expert] Linux Mandrake 6.0 Question

[Ben Derr]

On Sun, 8 Aug 1999, Jason Bodnar wrote:

> Basic ipchains is very easy. Read the IP-CHAINS HOWTO. There's a quick three
> line section for setting it up. Then load any extra masq modules you may need
> (irc, ftp, realaudio, etc). The ipchains package comes with ip-chains save to
> save your rules. There is also an ipchains-restore script that you can use to
> bring masquerading back up on boot.
> 
> If you want a graphical tool to do ipchains go to freshmeat and search for gfcc
> or ipchains. gfcc is nice but you need to know ipchains in order to use it.
> (Somebody should make a gui ipchains tools for dummies.)

kfirewall isn't bad for a gui fireall tool. It works for both ipfwadm and
ipcahins, and has masquerading support.

Re: [expert] Linux Mandrake 6.0 Question

[Axalon]

On Sun, 8 Aug 1999, Civileme wrote:

> 
> 
> 1.  Buy a good PCI/Video card, not expensive.  A generic S3 Virge/DX with 4Mb
> RAM should be adequate, even if you plan to play Quake.

Don't skimp here get something with a good linux 3d driver
 
> 2.  Sound, if you equip your computer with it, is most easily installed, in my
> experience, for Creative/Soundslaster Products.  The NEWEST should be avoided
> unless you like to spend a few hours on the web finding beta drivers and
> instructions.  (No SBLive, get a good AWE 64 for the ISA Bus and it should work
> out all right.)  Save sndconfig for one of your later steps.  And if you get
> some weird error messages running it from a console or desktop, try booting
> into single-user mode and running sndconfig.

I've never had problems with any soundblaster cards

> 2.1  With hardware in place, Run Install.  I recommend you select "Custom" or
> else run Upgrade off the CD right after install and make sure the network
> management workstation stuff gets loaded.

Why do they want snmpd?

> 3.  Get X running and kfm(by clicking on the "Home" icon on the panel at the
> bottom of the screen).  Point kfm to http://www.linux-mandrake.com and look on
> the left side of the screen for the "Updates".  Go there, then find a mirror,
> still using kfm.  Once you are where the updates are listed, open another
> window of kfm with your home directory.  Select all the update files you want
> and drag them to your home directory.  Yes, you'll get "Copying files" instead
> of "Downloading" messages, but I believe you'll think this is prety cool.
> Those files are .rpm.gz so you will have to click on console which will bring a
> command line window up at your home directory.  (Don't do that until the copy
> is finished.)  DISCONNECT from the Internet (by closing the kfm window or by
> stopping Kppp).
> 
> Then enter
> 
> [noise @ /home/noise]$ su
> password: *give the root password here*
> [root@ /home/noise]# gunzip *.gz

Did somebody hack kde and forget to tell me? The files on the mirrors
should be .rpm not .gz

> Logout
> login as root
> return to your user's home directory and open the home folder there
> 
> Single-click the first .rpm file.  KPackage will open a window and you can
> click "Install" after ticking "replace files".  On printtool, also unclick
> "Check Dependencies"

seeing as your at the console already just type 'rpm -F *.rpm' , if you do
use kpackage it should have an Upgrade checkbox use this not Install, and
it generaly isn't required to use --nodeps or uncheck "Check Dependancies" 

> After all of this, you should have a fairly stable system and stable Netscape
> to work with.
> 
> 4.  The setup for remote SAMBA printers does not work.  I haven't had time to
> verify if it is the "filter" script in /var/spool/lpd/lp (or whatever printer
> name you use in place of lp) or the script filter that is copied to
> /usr/bin/smbprint.  I have a fix, an *ugly* one, where I add these lines to
> .config in the /var/spool/lpd/printername directory
> 
> server=remoteservername
> service=remoteprinternameonserver
> 
> In my case that was
> 
> server=TESTRIG
> service=HPBIG
> 
> for \\TESTRIG\HPBIG as accessed by the windows machines in the LAN
> 
> ALSO, the /var/spool/lpd/lp/filter file will need editing.  In the "if" toward
> the end of the file where it checks for "SMB", change the text

The type-o introduced by Redhat, was fixed along time ago if you find
another please let us know.

> ${FPIDIR}
> 
> to
> 
> /usr/bin
> 
> so the new filter added to the filter path will be /usr/bin/smbprint
> 
> 5.  I haven't found any package that will masquerade other LAN machines onto
> the internet.  Supposedly it can be done through ipchains scripts, but
> I haven't made any work yet.  I did use PaNTs which is supposed to work for
> RedHat 6 but I can't get anything through it on port 80 (web access).

echo 1> /proc/sys/net/ipv4/conf/eth0/forwarding
ipchains -I forward -j MASQ -s 192.168.0.0/16 -i eth0 -d 0/0
ipchains -I input -j DENY -s 192.168.0.0/16 -i ! eth0 -d 0/0 -l

> SO far, those are the annoyances, gotchas, etc.  Naturally, the little caveats
> such as "don't go surfing/chatting as root" I have omitted.
> 
> Civileme

in order of discovery:
 you'll need the updated sox package to use sndconfig
 you'll need the updated kernel and initscripts, so if it does crash you
don't have to reinstall which is pretty much the case after a few fsck's
 netscape as usual not quite in the best of shape downgrade/upgrade to the
version in updates

Thats about all the true killers i can think of off hand

> John Aldrich wrote:
> 
> > Hey, all just picked up my copy of Mandrake 6.0 from the computer store
> > (figured I might as well, since no one is going to burn me a copy of the ISO
> > image )
> > My machine will be a Dual-PPro 200 with 192 Megs of ram and about 10.7 Gigs
> > of drivespace. I haven't picked up a video card yet, but that's the next
> > purchase, alo

Re: [expert] Linux Mandrake 6.0 Question

[Jason Bodnar]

On 08-Aug-99 Civileme wrote:
> 2.  Sound, if you equip your computer with it, is most easily installed, in
> my
> experience, for Creative/Soundslaster Products.  The NEWEST should be avoided
> unless you like to spend a few hours on the web finding beta drivers and
> instructions.  (No SBLive, get a good AWE 64 for the ISA Bus and it should
> work
> out all right.)  Save sndconfig for one of your later steps.  And if you get
> some weird error messages running it from a console or desktop, try booting
> into single-user mode and running sndconfig.

the Creative Ensoniq works flawlessly.

> 4.  The setup for remote SAMBA printers does not work.  I haven't had time to
> verify if it is the "filter" script in /var/spool/lpd/lp (or whatever printer
> name you use in place of lp) or the script filter that is copied to
> /usr/bin/smbprint.  I have a fix, an *ugly* one, where I add these lines to
> .config in the /var/spool/lpd/printername directory

I used the printtool to setup a remote samba printer without a problem. Entered
the hostname, ip, printer name and selected a drive. Printed a test page. No
problem.

> 5.  I haven't found any package that will masquerade other LAN machines onto
> the internet.  Supposedly it can be done through ipchains scripts, but
> I haven't made any work yet.  I did use PaNTs which is supposed to work for
> RedHat 6 but I can't get anything through it on port 80 (web access).

Basic ipchains is very easy. Read the IP-CHAINS HOWTO. There's a quick three
line section for setting it up. Then load any extra masq modules you may need
(irc, ftp, realaudio, etc). The ipchains package comes with ip-chains save to
save your rules. There is also an ipchains-restore script that you can use to
bring masquerading back up on boot.

If you want a graphical tool to do ipchains go to freshmeat and search for gfcc
or ipchains. gfcc is nice but you need to know ipchains in order to use it.
(Somebody should make a gui ipchains tools for dummies.)

Re: [expert] Linux Mandrake 6.0 Question

[Civileme]

 
1.  Buy a good PCI/Video card, not expensive.  A generic S3
Virge/DX with 4Mb RAM should be adequate, even if you plan to play Quake.
2.  Sound, if you equip your computer with it, is most easily installed,
in my experience, for Creative/Soundslaster Products.  The NEWEST
should be avoided unless you like to spend a few hours on the web finding
beta drivers and instructions.  (No SBLive, get a good AWE 64 for
the ISA Bus and it should work out all right.)  Save sndconfig for
one of your later steps.  And if you get some weird error messages
running it from a console or desktop, try booting into single-user mode
and running sndconfig.
2.1  With hardware in place, Run Install.  I recommend
you select "Custom" or else run Upgrade off the CD right after install
and make sure the network management workstation stuff gets loaded.
3.  Get X running and kfm(by clicking on the "Home" icon on the
panel at the bottom of the screen).  Point kfm to http://www.linux-mandrake.com
and look on the left side of the screen for the "Updates".  Go there,
then find a mirror, still using kfm.  Once you are where the updates
are listed, open another window of kfm with your home directory. 
Select all the update files you want and drag them to your home directory. 
Yes, you'll get "Copying files" instead of "Downloading" messages, but
I believe you'll think this is prety cool.  Those files are .rpm.gz
so you will have to click on console which will bring a command line window
up at your home directory.  (Don't do that until the copy is finished.) 
DISCONNECT from the Internet (by closing the kfm window or by stopping
Kppp).
Then enter
[noise @ /home/noise]$ su
password: *give the root password here*
[root@ /home/noise]# gunzip *.gz
Logout
login as root
return to your user's home directory and open the home folder there
Single-click the first .rpm file.  KPackage will open a window
and you can click "Install" after ticking "replace files".  On printtool,
also unclick "Check Dependencies"
After all of this, you should have a fairly stable system and stable
Netscape to work with.
4.  The setup for remote SAMBA printers does not work.  I haven't
had time to verify if it is the "filter" script in /var/spool/lpd/lp (or
whatever printer name you use in place of lp) or the script filter that
is copied to /usr/bin/smbprint.  I have a fix, an *ugly* one,
where I add these lines to
.config in the /var/spool/lpd/printername directory
server=remoteservername
service=remoteprinternameonserver
In my case that was
server=TESTRIG
service=HPBIG
for \\TESTRIG\HPBIG as accessed by the windows machines in the LAN
ALSO, the /var/spool/lpd/lp/filter file will need editing.  In
the "if" toward the end of the file where it checks for "SMB", change the
text
${FPIDIR}
to
/usr/bin
so the new filter added to the filter path will be /usr/bin/smbprint
5.  I haven't found any package that will masquerade other
LAN machines onto the internet.  Supposedly it can be done through
ipchains scripts, but I haven't made any work yet.  I did
use PaNTs which is supposed to work for RedHat 6 but I can't get anything
through it on port 80 (web access).
SO far, those are the annoyances, gotchas, etc.  Naturally, the
little caveats such as "don't go surfing/chatting as root" I have
omitted.
Civileme
John Aldrich wrote:
Hey, all just picked up my copy of Mandrake 6.0
from the computer store
(figured I might as well, since no one is going to burn me a copy of
the ISO
image )
My machine will be a Dual-PPro 200 with 192 Megs of ram and about 10.7
Gigs
of drivespace. I haven't picked up a video card yet, but that's the
next
purchase, along with a "generic" PCI ethernet card.
Question is, what should I look out for with regards to installation
headaches on this system? I understand Mandrake has a 6.1 version out
now
(not available in the local stores, apparently.)
This is really going to be a "training" machine for me to teach myself
Linux
Admin skills. Anything I should watch out for with this?
Thanks...
    John

-- 
Civileme Say:

"He who buy on leading edge know what it feel like to slide down razor blade of life."
 

Re: [expert] Linux Mandrake 6.0 Question

[Jay Summet for [EMAIL PROTECTED]]

My point was that the install program did not automatically pick the SMP
kernel for me, which the original poster claimed that it should do. Either
he was wrong, or that feature does not always work.

Jay W. Summet

On Sat, 7 Aug 1999, Arandir wrote:

> On Sat, 07 Aug 1999, [EMAIL PROTECTED] wrote:
> > I used Mandrake 6.0 and I have a Dual Pentium II system, and the install
> > program didn't do this for me!  I had to re-compile the kernel and enable
> > SMP support before it would see my second CPU.
> 
> Mandrake includes a precompiled SMP kernel. Poke around on the CD ROM. There
> were several kernels for various things there all ready to go. No need to
> recompile, unless you want to.
> 
>  --
> Arandir...
> ___
> 
> 

Re: [expert] Linux Mandrake 6.0 Question

[Brett Jones]

There is a set of stock mandrake kernels on the cd built for SMP machines you
could've used. I don't know why the install fail to pick up on your SMP setup.

On Sat, 07 Aug 1999, you wrote:
> I used Mandrake 6.0 and I have a Dual Pentium II system, and the install
> program didn't do this for me!  I had to re-compile the kernel and enable
> SMP support before it would see my second CPU.
> 
> Jay Summet
--
Brett Jones
[EMAIL PROTECTED]

Re: [expert] Linux Mandrake 6.0 Question

[John Aldrich]

Hmm...wonder if it's a dual-ppro thing or whether there is something else
different about your box than the other two gentlemen who have responded
I'm hoping I don't have to recompile at worst, though, I think it will
be a matter of specifying the SMP kernel (I think that Linux typically ships
with an SMP kernel as well as a single-processor kernel.)
John

- Original Message -
From: Jay Summet for [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 07, 1999 1:15 PM
Subject: Re: [expert] Linux Mandrake 6.0 Question


> I used Mandrake 6.0 and I have a Dual Pentium II system, and the install
> program didn't do this for me!  I had to re-compile the kernel and enable
> SMP support before it would see my second CPU.
>
> Jay Summet
>
> On Sat, 7 Aug 1999, Brett Jones wrote:
>
> > The install will pick up you dual cpu's and install a kernel that will
support
> > them out of the box (nice touch I think). Pick up a good mid range card.
A 4 meg
> > AGP Diamond card would be a good choice if the budget is tight. Or if
you got
> > the dough a G200 16 meg card would be super sweet. I've had good luck
with the
> > pci realtek 10/100 cards. Mandrake 6.1 from what I understand is the
cooker
> > version, a development version. Make sure you download the updates and
install
> > them straight away.
> >
> > Is the drive dedicated to Linux? Make sure the /boot directory is under
the
> > 1023 cylinder on the drive. When you partition it make a 15 meg
partition first
> > off and mount is as /boot
> >
> > When you run the install choose custom, then select the packages you
want to
> > install by hand. It's a great way to learn about the system and the
packages on
> > it.
> >
> > Have fun.
> >
> > --
> > Brett Jones
> > [EMAIL PROTECTED]
> >
>

Re: [expert] Linux Mandrake 6.0 Question

[John Aldrich]

Machine doesn't have AGP...PPro never has, AFAIK. :-)
Video will PROBABLY be a PCI TNT card, and boot drive will likely be my new
9.1 GB SCSI. :-) Then again, maybe I'll boot to one of the 850 meg IDE
drives... :-)
I typically do run a "custom" install...at least with my work machine,
that's what I did :-) I appreciate the suggestions!
John
- Original Message -
From: Brett Jones <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 07, 1999 12:05 AM
Subject: Re: [expert] Linux Mandrake 6.0 Question


> The install will pick up you dual cpu's and install a kernel that will
support
> them out of the box (nice touch I think). Pick up a good mid range card. A
4 meg
> AGP Diamond card would be a good choice if the budget is tight. Or if you
got
> the dough a G200 16 meg card would be super sweet. I've had good luck with
the
> pci realtek 10/100 cards. Mandrake 6.1 from what I understand is the
cooker
> version, a development version. Make sure you download the updates and
install
> them straight away.
>
> Is the drive dedicated to Linux? Make sure the /boot directory is under
the
> 1023 cylinder on the drive. When you partition it make a 15 meg partition
first
> off and mount is as /boot
>
> When you run the install choose custom, then select the packages you want
to
> install by hand. It's a great way to learn about the system and the
packages on
> it.
>
> Have fun.
>
> --
> Brett Jones
> [EMAIL PROTECTED]
>

Re: [expert] Linux Mandrake 6.0 Question

[Arandir]

On Sat, 07 Aug 1999, [EMAIL PROTECTED] wrote:
> I used Mandrake 6.0 and I have a Dual Pentium II system, and the install
> program didn't do this for me!  I had to re-compile the kernel and enable
> SMP support before it would see my second CPU.

Mandrake includes a precompiled SMP kernel. Poke around on the CD ROM. There
were several kernels for various things there all ready to go. No need to
recompile, unless you want to.

 --
Arandir...
___

Re: [expert] Linux Mandrake 6.0 Question

[Jay Summet for [EMAIL PROTECTED]]

I used Mandrake 6.0 and I have a Dual Pentium II system, and the install
program didn't do this for me!  I had to re-compile the kernel and enable
SMP support before it would see my second CPU.

Jay Summet

On Sat, 7 Aug 1999, Brett Jones wrote:

> The install will pick up you dual cpu's and install a kernel that will support
> them out of the box (nice touch I think). Pick up a good mid range card. A 4 meg
> AGP Diamond card would be a good choice if the budget is tight. Or if you got
> the dough a G200 16 meg card would be super sweet. I've had good luck with the
> pci realtek 10/100 cards. Mandrake 6.1 from what I understand is the cooker
> version, a development version. Make sure you download the updates and install
> them straight away. 
> 
> Is the drive dedicated to Linux? Make sure the /boot directory is under the
> 1023 cylinder on the drive. When you partition it make a 15 meg partition first
> off and mount is as /boot
> 
> When you run the install choose custom, then select the packages you want to
> install by hand. It's a great way to learn about the system and the packages on
> it.
> 
> Have fun.
> 
> --
> Brett Jones
> [EMAIL PROTECTED]
> 

Re: [expert] Linux Mandrake 6.0 Question

[Jacques Le Marois]

John Aldrich wrote:
> 
> Hey, all just picked up my copy of Mandrake 6.0 from the computer store
> (figured I might as well, since no one is going to burn me a copy of the ISO
> image )
> My machine will be a Dual-PPro 200 with 192 Megs of ram and about 10.7 Gigs
> of drivespace. I haven't picked up a video card yet, but that's the next
> purchase, along with a "generic" PCI ethernet card.
> Question is, what should I look out for with regards to installation
> headaches on this system? I understand Mandrake has a 6.1 version out now
> (not available in the local stores, apparently.)

Mandrake 6.1 is not out. You can play with cooker:
http://www.linux-mandrake.com/cooker which is usable now.

Jacques.

Re: [expert] Linux Mandrake 6.0 Question

[Brett Jones]

The install will pick up you dual cpu's and install a kernel that will support
them out of the box (nice touch I think). Pick up a good mid range card. A 4 meg
AGP Diamond card would be a good choice if the budget is tight. Or if you got
the dough a G200 16 meg card would be super sweet. I've had good luck with the
pci realtek 10/100 cards. Mandrake 6.1 from what I understand is the cooker
version, a development version. Make sure you download the updates and install
them straight away. 

Is the drive dedicated to Linux? Make sure the /boot directory is under the
1023 cylinder on the drive. When you partition it make a 15 meg partition first
off and mount is as /boot

When you run the install choose custom, then select the packages you want to
install by hand. It's a great way to learn about the system and the packages on
it.

Have fun.

--
Brett Jones
[EMAIL PROTECTED]

[expert] Linux Mandrake 6.0 Question

[John Aldrich]

Hey, all just picked up my copy of Mandrake 6.0 from the computer store
(figured I might as well, since no one is going to burn me a copy of the ISO
image )
My machine will be a Dual-PPro 200 with 192 Megs of ram and about 10.7 Gigs
of drivespace. I haven't picked up a video card yet, but that's the next
purchase, along with a "generic" PCI ethernet card.
Question is, what should I look out for with regards to installation
headaches on this system? I understand Mandrake has a 6.1 version out now
(not available in the local stores, apparently.)
This is really going to be a "training" machine for me to teach myself Linux
Admin skills. Anything I should watch out for with this?
Thanks...
John