Re: meaning of this? gethostby*.getanswer: ... got type 39
On 8/18/05, Anonymous [EMAIL PROTECTED] wrote: I sometimes find such messages in my syslog: mutella gethostby*.getanswer: asked for gwc1c.olden.ch.3557.nyud.net IN A, got type 39 I got a similar entry when ı visited the same domain following a link in slashdot. Nov 17 00:49:22 etch firefox-bin: gethostby*.getanswer: asked for www.stachliu.com.nyud.net IN A, got type 39
new hard drive
Hi all, yesterday I had only one hard drive. hda1 / #debian installation A hda5 /home Today this hard drive is hdb with the same structure. On hda there is grub installed pointing to debian installation A as well as other entries. When I try to load debian installation A, currently I am having kernel panic after an error: VFS can't find ext3 filesystem on dev hda1 Question: Which files should I edit to let linux know that it is on hdb now? I already edited fstab and mtab thank you
Re: new hard drive
On 9/24/05, Alvin Oga [EMAIL PROTECTED] wrote: On Sat, 24 Sep 2005, [ISO-8859-1] Kudret Güler wrote: Today this hard drive is hdb with the same structure. On hda there is grub installed pointing to debian installation A as well as other entries. When I try to load debian installation A, currently I am having kernel panic after an error: VFS can't find ext3 filesystem on dev hda1 Question: Which files should I edit to let linux know that it is on hdb now? I already edited fstab and mtab you do NOT edit /etc/mtab .. leave it alone good if you fixed /etc/fstab --- if you're using lilo, edit /etc/lilo.conf to root=/dev/hdb1 and remove /boot/map and rerun lilo ( which will create a new /boot/map file ) and make 100% sure oyu know how to boot the system from floppy or cdrom or usb or ?? in case it complains about lilo if you're using grub, edit /boot/grub/menu.lst .. if you have a /etc/grub.conf or /boot/grub/grub.conf, change it too remove /boot/grub/device.map and do grub-install /dev/hda or leave both of these 2 steps out and see if it still boots as it should still work since hd0 is still the original /dev/hda c ya alvin Thanks for the quick response. And I am sorry for the confusion. Let me make it clearer. On current hda there is a debian installation B, and it already saw the debian installation A which was on old hda1(new hdb1). Current grub is the grub on debian installation B on current hda. So I guess I do not need to touch any grub conf file in the debian installation A. right? Currently I have undone the change in mtab. fstab is fixed. still having the error.
Re: new hard drive (solved)
On 9/24/05, Simo Kauppi [EMAIL PROTECTED] wrote: On Sat, Sep 24, 2005 at 11:01:49AM -0400, Kudret Güler wrote: Hi all, yesterday I had only one hard drive. hda1 / #debian installation A hda5 /home Today this hard drive is hdb with the same structure. On hda there is grub installed pointing to debian installation A as well as other entries. When I try to load debian installation A, currently I am having kernel panic after an error: VFS can't find ext3 filesystem on dev hda1 Question: Which files should I edit to let linux know that it is on hdb now? I already edited fstab and mtab thank you Hi, AFAIK, you don't need to edit /etc/mtab as it is created/updated by the system. You need to edit the /boot/grub/menu.lst in your /dev/hda, which you obviously have already done, so make sure the entry for the hdb is correctly set. My hdb-entry looks like this: title Debian GNU/Linux i386 root(hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 initrd /boot/initrd.img boot Here was the problem. The new grub installation has misprepared those entries. title Debian GNU/Linux i386 (on dev hdb1) root(hd1,0) kernel /boot/vmlinuz root=/dev/hda1 initrd /boot/initrd.img boot I have corrected the third line as kernel /boot/vmlinuz root=/dev/hdb1 thank you all very much.. If you copy/paste this, edit the '/boot/vmlinuz' to point to the correct name in your hdb-kernel as well as the '/boot/initrd.img', if you use initrd. If you don't have initrd-image, then delete the initrd-line. HTH Simo -- :r ~/.signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDNW8k4RQe7Exc22QRAuLVAJ4xktuM39hzRCRRxz+NwtfR09v7bQCeOhtg /rdYXIKXIfdB/9rryESFsjA= =Dmfq -END PGP SIGNATURE-
Re: bu nedir bileniniz var mı?
On 7/5/05, özgür uncuoğlu [EMAIL PROTECTED] wrote: eski işyerinden hatırlıyorum.bir makina vardı.bu komutu verdiğim zaman makinanın tarihi düzeliyordu.bi reset attığımda bozuluyodu.bu EEST,EET nedir bilmiyorum.ama ondan şüphelenmiştim. EET doğu avrupa saati, EEST doğu avrupa yaz saati. Türkiye bu saat dilimlerindedir. Sorununuzun bununla ilgisi yoktur. Bahsettiğiniz sistemin anakartındaki pil bitmiş olabilir.
Re: cannot burn 612MB iso
On 6/28/05, Adam Majer [EMAIL PROTECTED] wrote: Kudret Güler wrote: No problem on writing, no problem on mounting the new cd-rom. However when I try to read one of the mentioned files, errors appear in /var/log/messages But now that I rebooted the system this morning, after burning a fresh copy with the same iso file I created yesterday, I can read all of the files successfully. Still I would like to hear any comments about the problem. If you can mount the ISO file (using loop device, as in `mount -t loop ISO file mount point`) and read all of the files, but cannot read them from the burnt CD, then the problem could be the CD writer. I have a CD writer that will not write at the advertised 12x speed propertly. I have to write at 8x. After a reboot, same iso file has been burned succesfully by all means. Therefore I doubt that the problem is the hardware.
Re: cannot burn 612MB iso
On 6/25/05, Carl Fink [EMAIL PROTECTED] wrote: On Fri, Jun 24, 2005 at 11:27:06PM -0400, Kudret G?ler wrote: However, when I try to check md5sums of all files on the new cd-rom, some of the files fail. also /var/log/messages collects some errors ... What happens when you try to mount the CD? No problem on writing, no problem on mounting the new cd-rom. However when I try to read one of the mentioned files, errors appear in /var/log/messages But now that I rebooted the system this morning, after burning a fresh copy with the same iso file I created yesterday, I can read all of the files successfully. Still I would like to hear any comments about the problem.
cannot burn 612MB iso
Hi, Trying to write 612 MB data on CD-ROM. I am using nautilus-cd-burner to create an iso image and then using dvdrecord(tried cdrecord, as well) to burn it on CD-ROM. iso file is created successfully and the image is written on the disk successfully. However, when I try to check md5sums of all files on the new cd-rom, some of the files fail. also /var/log/messages collects some errors when md5sum tries to read the mentioned files. Jun 24 22:03:01 localhost kernel: attempt to access beyond end of device Jun 24 22:03:01 localhost kernel: hdc: rw=0, want=944764, limit=800444 I recreated the iso and tried to burn those images several times, always the same files fail md5sum check. What can be the problem? thank you
Re: MPlayer Debian Paketini Istemiyorum Kardeşim. .! ;-)
On 4/14/05, Alper KANAT [EMAIL PROTECTED] wrote: Merhaba, APT ile MPlayer'n son srmn yklediimde Trke fontlarla ilgili (trke font paketini doru yere amama ramen) ve ekrandaki grntnn full ekrana getiimde bymemesi gibi sorunlar yayordum. Kaynak kodundan derlediimde sorun ortadan kalkyordu. MPlayer'n kaynak kodunu kendim checkinstall ile Debian paketi yaratarak kurdum. Ama imdi apt-get dist-upgrade komutu verdiimde MPlayer'n yeni paketi km gibi kurmak istiyor.. Debian-tr.org'daki Apt-Pinning dkmann okudum ama baarl olamadm. Yklediim MPlayer'n sistemde sabit kalmasn, APT ile gncelleme yaplmamasn, paketin ayn kalmasn falan nasl salayabilirim ? Teekkrler.. Synaptic te mplayer paketinizi seip package mensnden lock version' iaretlerseniz istediiniz olacaktr. Synaptic Package Manager Manual V0.1.2'den 3.10 To Lock a Package to the Current Version (Debian only) To lock a package to the current version follow these steps: 1- Select the package that you want to lock in the package list. 2- Choose Package Lock Version. The Synaptic Package Manager will reload the package information. You should now see, that the menu item Package Lock Version is checked. Furthermore all actions in the menu Package are disabled now. To unlock the package uncheck Package Lock Version.
hald stat shows Ds
hello, after a short while after booting, hald shows Ds status in ps.
Trying to start gnome-volume-properties I get the error:
libhal.c 767 : org.freedesktop.DBus.Error.NoReply raised
Message did not receive a reply
I also observe:
kernel: hdd: request sense failure: status=0x51 { DriveReady
SeekComplete Error }
kernel: hdd: request sense failure: error=0x04Aborted Command
hdd is dvd-rom and didn't have this error or any other single problem
before using udev.
What can be the problem?
regards
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: hald stat shows Ds
On Wed, 15 Dec 2004 10:16:26 -0800 (PST), Alvin Oga [EMAIL PROTECTED] wrote: yu should NOT mix foreign languages on the same ide cable - disks are talking ata-100/133 - the dvd is talking ata-33/66 ?? here is my setting: hda(ata-133) on ide0 master hdc(ata-33) on ide1 master hdd(ata-66) on ide1 slave I am not clear about having ata-33 and ata-66 on same cable posing a problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
On Thu, 09 Dec 2004 08:48:04 -0500, Adam Aube [EMAIL PROTECTED] wrote: root.cdrom. What version of udev do you have? Have you modified any files under /etc/udev? I hadn't modified any files then. udev version is 0.046-6 Maintainer informed me that it was a bug resolved in the next version. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284866 His work around worked for me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
verification after cd burn
Hi, I use nautilus-cd-burner to backup some important stuff(binary as well) on CD-Roms. How can I verify that the files on the cd and the files on the hard drive are exactly the same. I use diff on directories with -r switch. Is it totally safe? What about md5sum? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
udev question
udev creates /dev/hdc(burner) with permissions 640 and with owner root.hal. Therefore hal group members cannot burn. And any change is reversed on reboot. How can I tell udev to create it with permissions 660? Or should I just put it in a script to chmod /dev/hdc on every boot? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
