Hi,
can you provide some details about your hardware? I had the same problem
with an HP-Server, the RAID-Controller was just "to new" for debian
(woody). I solved this problem by using the newest Kernel from
kernel.org, but in this case either use a kernel with all vital modules
build in or find a way to fix the initrd (debian uses cramfs, this fs is
not supported by the vanilla sources).
Redhat/SuSE seem to backport a lot of drivers, that's why those distros
are working. I never tried debian testing/unstable...
Using a custom kernel can be very annoying: Every security whole means a
lot of work.
If you don't need special features provided by the newest releases, use
the debian package for squid. Works fine for me. You can as well build
your own with all features you need enabled.
Either way, delay pool usage is controlled via squid.conf. Default is
all delay pools of.
Regards, Hendrik Voigtländer
Hement Gopal wrote:
> hi all
>
> two questions in one mail..hope no one minds...
>
>
> first off, i'm building a new squid server and want to run it on Debian.
> Its an Intel 2.2 Gh with 2Gb RAM and 3 x 32 Gb Seagate SCSI drives.
>
> my first problem is that when i am installing debian, the hard drives
> are not found by Debian so i cannot continue with Debian install. Any
> debian users out there that can assist? or should i just install redhat
> 9 (coz that OS seems to see hard drives)
>
> secondly, i want to (at some point in teh future) use delay pools. can i
> compile squid with delay pools feature now but not activate it just yet.
> if yes, will it affect my squid perfromance in any way?
>
> many thanks
>
> rgds,
> hement gopal
>
Received on Wed May 19 2004 - 01:17:16 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Jun 01 2004 - 12:00:01 MDT