On Thu, 07 Sep 2000, Michael Soulier wrote:
> On Thu, 7 Sep 2000, Jonathan Wheelhouse wrote:
>
> > Some people say to install from unstable the debs for ALSA and then
> > run alsaconf. A couple of questions - I could change my sources to
> > point at unstable but I don't want to upgrade to woody
Hi everyone,
The kde.tdyc.com Woody tree for kde2 has been emptied, I'm sure of it because I
used to apt kde2 from there. I happened to have been reinstalling my Woody box
from scratch yesterday (the 6th), starting from a couple of potato disks. All
went well, but when it came to installing kde2 b
ogether a server box which will hold 512 MB RAM and now
I'm kinda wondering what to do with the swap size. Of course it doesn't
matter to add a few hundred megs to it, but is it useful?
--
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
terfaces. Then restart the networking daemon;
/etc/init.d/networking stop|start
You can also experiment by using the ifconfig program on the command line.
Debian 2.2 differs a bit from 2.1, the ifconfig is a little different also.
Check the man page.
Good luck,
--
Danny Pansters
[EMAIL PROTECTED]
t; I see those all day long.
--
I have those too, I don't believe they mean anything bad is going on, but I
also would like to know what exactly this is.
I always thought it were kernel messages relating to memory swapping or
network checks or something.
Thanks,
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
Sorry there, I didn't read everything, you've already tried that.
--
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
btw. xf86config isnt as hard as it seems, give it a go.
good luck,
--
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
n
> 'in X' and 'X not running', then getting rid of *dm is appropriate (though
> you could also use `/etc/init.d/*dm stop`, do your console stuff, and
> `/etc/init.d/*dm start`).
Exactly, then you can kill your xdm and your X and look into the problem at
the first place
r to check the setups once again than to find the exact
problem from diagnostic output. I don't believe you have a hardware problem
and certainly not an IRQ problem!!
The networking HOWTO will likely be needed.
Good luck,
--
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
I run kde2 from the deb packages provided at kde.tdyc.com, I use apt to
update them, kde2 works well (bit slow though).
Did you try to dpkg --purge any international kde packages (the ones that are
about other charsets/languages)? I think something might be broken there (?)
--
Danny Pansters
This might have been said earlier in this thread (in which case I apologise),
but I think there is a HOWTO on Linux Telephony..
$ cd /usr/doc/HOWTO/en-txt
$ zless LINUX_TELEPHONY_OR_THE_LIKE.gz
I don't think it's trivial though.
Dan
--
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
et away with two disks and a lot of
apting... anyhow I think it makes sense to initially narrow down your
packages installs as much as possible.
Greetings to everyone,
Dan
--
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
t; > --
> > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] <
> > /dev/null
LOL
--
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
eway box. The local net is masqueraded
as the "outer" IP# of the box connected to the cable ISP. All works well, I
have the box load the masq modules for ftp and the like (even icq) on
start-up; all but ftp'ing to my workstation from my gateway box.
Same problem. Que? Anyone?
Dan
--
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
I'm not sure about SB Live, but shouldn't it also work as es1371 just like
SB128? or does it have a different chipset?
--
Danny Pansters
[EMAIL PROTECTED]
www.ricin.com
> the '/dev' directory? it's hard for me to believe. if you
> truly don't have any such item, i'm not sure how to create
> it; but it shoula been created when you formatted your
> linux/unix system...
[very big albeit interesting snip]
No he's saying he
it again (hint: it involves running sysctrl again :-).
What the hell,
--
Danny Pansters
[EMAIL PROTECTED]
17 matches
Mail list logo
