On Tue, 2004-09-14 at 14:17 -0700, Karl Hegbloom wrote:
> Perhaps for a very important
> production server you should have both a staging system and the real
> thing, so that you can test updates on the staging box before putting
> them onto the deployment server. Maybe that could be done with a
On Tue, 2004-09-14 at 22:06 +0200, Pavol Luptak wrote:
> I need to choose a stable software/hardware server solution based on Debian
> distribution.
What sort of server will it be? What particular software set do you
need to run on it?
I've a related question. Are the source packages for Debia
Pavol Luptak wrote:
Hello,
I need to choose a stable software/hardware server solution based on Debian
distribution. I'm planning to buy a 64-bit system (MB GigaByte K8VT800,
AMD Athlon 64, socket 754, chipset VIA K8T800+8237 with SATA disks).
According to the compatibility list
http://alioth.deb
Greetings --
A big thank you to everyone who has worked hard to get this port
running! It's a thrill to be back on Debian.
I just switched my SuSE 9.0 system over, using the cross-install
instructions at http://www.burgettsys.com/stories/59455/ and the
debian-amd64-howto.
Documentation suggest
Hello,
I need to choose a stable software/hardware server solution based on Debian
distribution. I'm planning to buy a 64-bit system (MB GigaByte K8VT800,
AMD Athlon 64, socket 754, chipset VIA K8T800+8237 with SATA disks).
According to the compatibility list
http://alioth.debian.org/docman/view.
This is only important because i _really_ want to compile my own customized
kernel,
and I haven't done this since 2.0.21, I think it was...
And I'm trying to get into kernel customizing in general.
I probably should put this question in some other mailing-list, but since the
amd64 port is a rea
In The Night wrote:
Hmmm
I've tried that.
I've tried mkinitrd -r /dev/sdb1 too...
The problem seems to be me having root on a SATA-drive
mkinitrd fails to find the sata driver necessary to mount
your root disk. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263169
Workaround is to add
Hmmm
I've tried that.
I've tried mkinitrd -r /dev/sdb1 too...
The problem seems to be me having root on a SATA-drive
My menu.lst-entry is for 2.6.7 (working):
title Debian GNU/Linux, kernel 2.6.7
root(hd0,2)
kernel /vmlinuz-2.6.7 root=/dev/hdg1 ro
initrd
Kurt Roeckx wrote:
Both binary-amd64/Packages and
debian-installer/binary-amd64/Packages are empty. I have no idea
why.
There are new Packages files generated about 20 minutes
ago, but they are still empty.
Harri
On Wed, Sep 15, 2004 at 01:11:28PM +0200, Ludovic watteaux wrote:
> modprobe snd-via82xx
Try
snd-via82xx dxs_support=1
--
Raul
Hello !
I've some trouble to use correctly my via82xx sound chip !
I use the module snd-via82xx but i 'm force to make a script launch in /etc/init.d/snd-via82xx --> /etc/rc2.d/S90snd-via82xx
Otherwise juste with a line with snd-via82xx in /etc/modules : Sound is with crackle noise !
I had a go with the monolithic mini and unfortunately I get the same
thing, no drivers found for my built in NIC, only my firewire ports
found. Would you have to manually configure this somehow?
Frederik Schueler wrote:
Hi,
the nic-extra-modules udeb has the via-velocity module. Try installing
ANd the Panic was:
pivot_root: No such file or directory
/usr/sbin..
It has something to do with my SATA-root drive changing from /dev/hdg to
/dev/sda,
but I cannot get i to workSomebody mentioned trying to hack initrd, but I
don't know how.
In The Night ([EMAIL PROTECTED]) wrote
13 matches
Mail list logo