My goodness.... what is this ?
pradeep_chauhan said:
1. The static route are put in the file /etc/init.d/networking (it took two days to get it right and it does not work in the location you said) here is the addition
Contact some good network wizard... Ricky might me able to figure this out...
pradeep_chauhan said:
2.The problem of installing etereal still exists here is the output
I just did the same for my computer... and it worked...
Anyhow, if it asks to do
# apt-get -f install then just give that command... what it means is Fix Broken installations... and the state of your system suggests some thing in debian package tree is broken... just give
# apt-get -f install and it will fix those broken installations... it will download those packages again and ask you for confirmation...
pradeep_chauhan said:
Preparing to replace kontact-plugins 4:3.2.2-1 (using .../kontact-plugins_4%3a3.2.3-2_i386.deb) ...
Unpacking replacement kontact-plugins ...
dpkg: error processing /var/cache/apt/archives/kontact-plugins_4%3a3.2.3-2_i386.deb (--unpack):
trying to overwrite `/usr/lib/kde3/kcm_kontactknt.so', which is also in package kontact
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/kontact-plugins_4%3a3.2.3-2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Hmmmm, it seems that package
kontact-plugins is corrupt or something... go to
*packages.debian.org and click on
Search package directories.. enter kontact-plugins and download the debian package... and install that package manually using
dpkg ...
Any way, if apt-get is acting up then go to *packages.debian.org and download package files individually... if they dont install, then put all the package files into one directory and give...
# dpkg --install --force-all *.deb
i'm not joking, but when i get frustrated then i do a forced inatall and many a times it works...
pradeep_chauhan said:
4. Changing the boot level no success ( I did not spell it wrong. come on yar i think i can do this bit)
# The default runlevel.
id:3:initdefault:
Check out the following directories and make sure there are no suspicious looking scripts that are starting Xserver...
/etc/rc3.d
/etc/rcS.d
/etc/rc.boot
Contents in rcS.d and rc.boot directory will be executed no matter what your runlevel is... so make sure there is no reference to anything like
kdm, gdm, xdm ... these are the graphical login managers and should be present only in
/etc/rc5.d and nowhere else...
Otherwise there's no reason why X server has to start... inittab file is the only thing that controls runlevel...
pradeep_chauhan said:
lastly there is no file sudoers i tried to make one it did not work
pebble:/etc# ll s*
then make a new file and enter this inside it.
Code:
## User alias specification
# User privilege specification
root ALL=(ALL) ALL
I cant write in more... just read
$ man sudoers to learn how to edit sudoers file...
pradeep_chauhan said:
Do you think my system is jinxed?
might be...