Mmm.. usually this means that you have a daemon/service running on startup that configures your resolv.conf. An example of such a daemon would be DHCP related programs.

I think there is a way to make the resolv.conf immutable. Try the following :-

If you want to change it again, use :-


But I do suggest you look through your list of startup programs/applications to find the problem.

I heard that debian is gonna die @@!

@scorps
DHCP won't cause this directly, but dhclient might.


If those don't work, check your startup services. install rcconf and run it (as root). You can see a list of daemons/services you can disable.

---

Added on February 27, 2011, 2:52 pmDunno about Network Manager (it's crap, imo, so I don't use it unless I need to connect to those USB-3G dongles)
So, is your problem solved or not? You're always like this. People take time to write possible solutions for you, but you don't reply with feedback and go off-tangent with a new question instead.

Mmm.. usually this means that you have a daemon/service running on startup that configures your resolv.conf. An example of such a daemon would be DHCP related programs.

I think there is a way to make the resolv.conf immutable. Try the following :-

If you want to change it again, use :-


But I do suggest you look through your list of startup programs/applications to find the problem.

Ah, so the dns problem is solved, then.
Your new problem is Network Manager related.
Well, you could try inserting the 'ifup eth1' in a start file, autostart.sh or create a script for it. What is your eth1, anyway? wired or wireless? I assume it's wireless since you wouldn't really need Network Manager for wired connections.

Regarding the network manager problem.... if you're not using a USB 3G type, get rid of it and install wicd.

90% of users find their connection problems go away once they replace network manager.

He'll probably be doing another fresh install before his dns changes.
It doesn't help that I sometimes find it sort of difficult to comprehend what his problem is from the way he phrases them.

Also, scorps, he means that you'll probably be doing a new install. Why? I dunno.

@scorps
Both are similar, but from what I know, powernowd only controls the CPU frequency, without any reference to power or battery loads. hence it doesn't require ACPI or APM to function, which is beneficial to those people who still run older kernels. It supposedly works best with AMD PowerNow capable processors. Cpufeqd/cpufreq-utils are more complete, in that they interface with ACPI and also maybe other sensor daemons (like lm-sensors).

If its NTFS , try install NTFS Configuration Tool

# /etc/fstab: filesystem table.
#
# filesystem  mountpoint  type  options  dump  pass
/dev/sda5  /  ext3  defaults,errors=remount-ro,noatime  0  1

proc  /proc  proc  defaults  0  0
/dev/fd0  /floppy  vfat  defaults,user,noauto,showexec,umask=022  0  0
usbfs  /proc/bus/usb  usbfs  devmode=0666  0  0
sysfs  /sys  sysfs  defaults  0  0
tmpfs  /dev/shm  tmpfs defaults  0  0
/dev/cdrom /cdrom  iso9660  defaults,ro,users,noexec,noauto  0  0
/dev/dvd /dvd  iso9660  defaults,ro,users,noexec,noauto  0  0
# Added by OSHIRIX
/dev/sda1      /media/sda1    ntfs-3g    defaults        0      0
# Added by OSHIRIX
/dev/sda3      /media/sda3    ntfs-3g    defaults        0      0
# Added by OSHIRIX
/dev/sda6      /media/sda6    ext4    auto,users,exec,noatime 0      0
# Added by OSHIRIX
/dev/sdb1      /media/sdb1    vfat    auto,users,rw,exec,noatime,umask=0,shortname=mixed,quiet 0      0

root@megadeth:/home/scorps# cp 58.flv /media/sdb1
cp: cannot create regular file `/media/sdb1/58.flv': Read-only file system

can you dmesg after you plug in and mount your usb drive?
It might because the usb drive is write protected (not by OS)

FAT: Directory bread(block 15756) failed
FAT: Directory bread(block 15757) failed
FAT: Directory bread(block 15758) failed
FAT: Directory bread(block 15759) failed
FAT: Filesystem error (dev sdc1)
    fat_get_cluster: invalid cluster chain (i_pos 0)
FAT: Filesystem error (dev sdc1)
    fat_get_cluster: invalid cluster chain (i_pos 0)
EFS: 1.0a - http://aeschi.ch.eu.org/efs/
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
FAT: Filesystem error (dev sdc1)
    fat_get_cluster: invalid cluster chain (i_pos 0)
FAT: Filesystem has been set read-only
FAT: Filesystem error (dev sdc1)
    fat_get_cluster: invalid cluster chain (i_pos 0)
FAT: Filesystem error (dev sdc1)
    fat_get_cluster: invalid cluster chain (i_pos 0)
FAT: Filesystem error (dev sdc1)
    fat_get_cluster: invalid cluster chain (i_pos 0)

Can you perform check disk on Windows pc? It seems your FAT file system is severely broken.

I sense something badly broken here.
Before jumping to unnecessary conclusions, just try reinstalling all the relevant libraries for FAT-related file transfer/mounting first.

I install Debian 6.0 Squeeze on one of my older computer on a Pentium 4, 2.0GHz, 512MB RAM, built in graphic card and 20GB hard disk. Everything went well but some how the IceWeasel and Epiphany browser doesn't recognize Chinese character. It just show some small square box. Although I don't really know how to read Chinese but its a bit annoying. Can someone help me please? Thanks!

title  OSHIRIX GNU/Linux, kernel 2.6.38-3.dmz.1-liquorix-686
root  (hd0,5)
kernel  /boot/vmlinuz-2.6.38-3.dmz.1-liquorix-686 root=/dev/sda5 ro ramdisk_size=100000 lang=us apm=power-off nomce vga=791 nouveau.modeset=0
initrd  /boot/initrd.img-2.6.38-3.dmz.1-liquorix-686

If you want to install an nvidia driver, you need to disable the nouveau driver first in order to avoid conflict between the 2 drivers.