Pantek Library
Hosting Provided By
CybrHost
High Speed Hosting
Mailing Lists: lists.debian.org > debian-user-digest > 07 > 080410.html (Request Expert lists.debian.org Support)

debian-user-digest Digest V2007 #2246

From: <debian-user-digest-request(at)lists.debian.org>
Date: Fri Aug 24 2007 - 21:10:50 EDT


Content-Type: text/plain

debian-user-digest Digest Volume 2007 : Issue 2246

Today's Topics: 

  Re: Good fdisk Practices              [ Stefan Monnier  ]
  Re: Possible LKM Trojan installed     [ Jude DaShiell  ]
  Re: Getting W: mdadm: /etc/mdadm/mda  [ J  ]
  Any way to stop dist-upgrade from up  [ - Tong -  ]
  Re: Any way to stop dist-upgrade fro  [ Mathias Brodala  ]
  Re: Any way to stop dist-upgrade fro  [ Jude DaShiell  ]
  Believing what you read (was Re: Goo  [ Ron Johnson  ]
  Re: Any way to stop dist-upgrade fro  [ - Tong -  ]
  Re: Possible LKM Trojan installed     [ Mike Bird  ]
  Re: boot error                        [ Frank McCormick  ]

Date: Fri, 24 Aug 2007 17:24:19 -0400
From: Stefan Monnier <monnier@iro.umontreal.ca> To: debian-user@lists.debian.org
Subject: Re: Good fdisk Practices
Message-ID: <jwv4piopqxb.fsf-monnier+linux.debian.user@gnu.org> Content-Type: text/plain; charset=us-ascii

> I read recently on this list that LVM is not portable across CPU

Don't believe everything you read.

        Stefan

Do you need help?X

Date: Fri, 24 Aug 2007 14:56:38 -0700
From: David Brodbeck <brodbd@u.washington.edu> To: List Debian User <debian-user@lists.debian.org> Subject: LVM volume portability (was: Re: Good fdisk Practices) 

Message-Id: <44F994E9-768B-4453-AF27-6798D509243E@u.washington.edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit

On Aug 24, 2007, at 1:18 PM, David Brodbeck wrote:

>
> On Aug 24, 2007, at 12:13 PM, Ron Johnson wrote:
>> I read recently on this list that LVM is not portable across CPU
>> architectures, so that you can't just upgrade your mobo to AMD64 and
>> retain your /home.
>
> Well, now you've got me curious. If so, this is potentially a
> serious issue, because most rescue disks are 32-bit. If it's true,
> then an LVM created on a 64-bit system wouldn't be readable with a
> 32-bit rescue disk. It also might have implications for things
> like USB hard disks. (These are getting big enough where it might
> start to make sense to LVM them -- I have one USB array that's 1.5
> TB.)
>
> I happen to have a spare AMD64 system and a couple of spare IA32
> systems, all with hot-swap drive bays that take the same sleds, so
> I may try this and see what happens.

OK, so here are the results.

I installed RHEL Server 5 AMD64 on a dual Opteron system. (Yeah, I know. But I had the CDs handy, and I didn't have any 64-bit Debian CDs.) I stuck a spare 160 gigabyte hard disk in one of the hot-swap bays and created a single LVM partition covering the entire drive. I then initialized it and created a 100 gigabyte logical volume, which I formatted with ext3fs. Then, for good measure, I created a 100 megabyte file of random bits and calculated its md5 checksum.

First test: Same hardware, 32-bit kernel: I rebooted the same system, this time using a RIP Linux 2.5 rescue CD. Ran vgscan, vgchange -ay to activate the volume group, then mounted it. No errors. The md5 checksums matched.

Second test: 32-bit hardware:
I moved the drive to a dual Xeon system and booted RIP Linux 2.5. Again, no problems. The volume mounted cleanly and the checksums matched.

Do you need more help?X

So, I'm concluding for now that there aren't any portability issues when moving an LVM volume group between IA32 and AMD64 architectures. If someone has tried it and had it *not* work, I'd like to know about it, because this is an issue that could potentially affect me at some point in the future.

Date: Sat, 25 Aug 2007 00:09:17 +0200
From: Florian Kulzer <florian.kulzer+debian@icfo.es> To: debian-user@lists.debian.org
Subject: Re: cannot logoff/shutdown properly 

Message-ID: <20070824220917.GA3509@localhost>
Content-Type: text/plain; charset=us-ascii

Can we help you?X

Content-Disposition: inline

On Fri, Aug 24, 2007 at 10:46:13 -0400, Manu Hack wrote:
> On 8/24/07, Florian Kulzer wrote:
> > On Thu, Aug 23, 2007 at 22:38:27 -0400, Manu Hack wrote:
> > > On 8/23/07, Florian Kulzer wrote:
> > > > On Wed, Aug 22, 2007 at 01:25:47 -0400, Manu Hack wrote:
> > > > > On 8/21/07, Florian Kulzer wrote:
> > > > > > On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
> > > > > > > I finally have the chance to look at /var/log/Xorg.0.log in recovery
> > > > > > > mode but it didn't have anything with "(EE)" or "(WW)".
> > > > > > >
> > > > > > > And in recovery mode, I can shutdown properly with shutdown -h now.
> > > > > >
> > > > > > That suggests to me that the shutdown problem might be related to the
> > > > > > video driver that you use for Xorg.

[...]

> > > > lspci | egrep -i 'vga|graphic|display|video'
> > >
> > > 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
> > > 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
> >
> > I have the exact same hardware on my laptop and I don't have any
> > problems with shutting down or restarting X.
> >
> > > > awk '/Section "(Device|Monitor)"/,/EndSection/' /etc/X11/xorg.conf
> > >
> > > Section "Device"
> > > Identifier "Intel Corporation 82852/855GM Integrated
> > > Graphics Device"
> > > Driver "i810"
> > > BusID "PCI:0:2:0"
> >
> > I use "intel" instead of "i810". This should not matter if you have the
> > newest version of the driver since the "i810" is only a legacy symlink
> > nowadays which points to the "intel" module. What is your output for:
> >
> > dpkg -l xserver-xorg-video-{intel,i810} | awk '/^[^D|+]/{print $1,$2,$3}'
>
> ii xserver-xorg-video-i810 2:2.1.0-2
> ii xserver-xorg-video-intel 2:2.1.0-2

I have slightly newer versions right now since I track Sid, but I don't recall any problems in the recent past.

> > > > > > Also, are there any interesting entries in /var/log/syslog around the
> > > > > > time of the crashes/freezes?
> > > > > I don't think so.
> > > >
> > > > I think the next thing to try is if X blocks the shutdown or if
> > > > something else in runlevel 2 is responsible. Shut down X and/or stop the
> > > > graphical login manager with
> > > >
> > > > invoke-rc.d gdm stop
> > >
> > > Maybe a more detailed way to do so is helpful to me for if I run the
> > > above command the screen goes black and I lose control of everything.
> >
> > This still looks like a crash of the graphics driver during mode
> > switching to me. (Did you also try this with the "vesa" driver?) If you
> > are at the graphical login screen, can you switch to a terminal with
> > CTRL + ALT + F1 (or F2, ..., F6)?
>
> I tried vesa, but the screen is not very stable and I can logoff once
> and then when I login again, I couldn't log off like I was using i810.

Can't find what you're looking for?X

I would still like to know whether your system hangs if you try to switch to a terminal without shutting down gdm.

> > Unless you can find a related message in either the syslog or the xorg
> > log I don't know how to track this down. The only other thing I can
> > think of right now is having a look at your loaded modules; what is
> > your output for
> >
> > lsmod | egrep 'i(810|830|915)|drm|agp|i2c'
> >
> i915 21280 3
> drm 73908 4 i915
> intel_agp 23004 1
> agpgart 32168 3 drm,intel_agp

That looks OK to me. (I have compiled drm, intel_agp and agpgart into my kernel, but that should not make a difference.) You do not seem to have any i2c-related modules loaded. I am not sure if this is relevant, but you do have these somewhat ominous DVOI2C errors in your xorg log. Does your system have an SMBus? Post the output of

lspci | egrep -i 'i2c|smb' 

-- 
Regards,            | 
http://users.icfo.es/Florian.Kulzer
          Florian   |

Date: Fri, 24 Aug 2007 15:22:06 -0700 From: J <j1234f@excite.com> To: debian-user@lists.debian.org Subject: Re: Getting W: mdadm: /etc/mdadm/mdadm.conf defines no arrays in install of linux-image 2.6.28-5 Message-ID: <1187994126.896130.294830@l22g2000prc.googlegroups.com> Content-Type: text/plain; charset="us-ascii" It is still booting to the old image even thought lilo seems to have run. /etc/lilo.conf has these bits of the lines in it: image=/vmlinz ... initrd=/initrd.img But initrd.img and /vmlinz point to my old 2.6.8-3-386 image. maybe lilo is not working? J wrote:
> Getting W: mdadm: /etc/mdadm/mdadm.conf defines no arrays in install
> of linux-image 2.6.28-5
> -----------
> Getting warning message:
> W: mdadm: /etc/mdadm/mdadm.conf defines no arrays
> W: mdadm:no array defined in conifuration file.
> W: mdadm:falling back to emergency procedure in initramfs.
> Added Linux *
> during in install of linux-image 2.6.28-5
>
> Will my system reboot if I power off?
>
> thanks
> j

Date: Fri, 24 Aug 2007 18:16:45 -0500 (CDT) From: Jude DaShiell <jdashiel@shellworld.net> To: John <JohnRChamplin@columbus.rr.com> Cc: debian-user@lists.debian.org, feedback@lists.sourceforge.net Subject: Re: Possible LKM Trojan installed Message-ID: <Pine.BSF.4.64.0708241811320.24271@freire2.furyyjbeyq.arg> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Those trojans trash very many files whenever anyone tries surgery on them. That was found out in a security lab by security professionals. If you can get to a friends computer and download the dban iso file from http://dban.sf.net and burn that on a single session CD and boot it up on the infected machine and at the boot prompt type autonuke dban will return your hard drive to the state it was in before it got its first operating system. Once finished, shut the machine down and leave it off for a minute. That should clear the memory. If security professionals had a hard time, I'm sure I wouldn't have a chance. dban will take a day to clear a 300gb disk. Figure 8 hours for a 100gb disk.

Date: Fri, 24 Aug 2007 23:39:38 +0000 (UTC) From: - Tong - <mlist4suntong@yahoo.com> To: debian-user@lists.debian.org Subject: Re: lenny repo unstable now? Message-ID: <fanq7q$i3l$1@sea.gmane.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, 23 Aug 2007 18:09:09 -0700, David Fox wrote:
> As of right now (6PM Pacific time, 8/23/07) I am about to do a dist-upg=
rade
> on my current Lenny installation.
Thanks a lot for the info. It really helps me to locate the problem -- it turns out that the mirror that I was using, mirror.peer1.net, has been quite unstable recently. Switching to another mirror solve all those=20 unstable issues. thanks --=20 Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/

Date: Fri, 24 Aug 2007 16:02:15 -0700 From: J <j1234f@excite.com> To: debian-user@lists.debian.org Subject: Re: Getting W: mdadm: /etc/mdadm/mdadm.conf defines no arrays in install of linux-image 2.6.28-5 Message-ID: <1187996535.297406.241480@z24g2000prh.googlegroups.com> Content-Type: text/plain; charset="us-ascii" Read manuals about mdadm and saw it has to do with raid, which I don't have, so I deleted the mdadm package. really an aptitude question. I have installed new kernels with aptitude, but ls -ltra / ... ...........initrd.img -> boot/initrd.img-2.6.8-3-386

Don't know where to look next?X

Date: Fri, 24 Aug 2007 23:44:28 +0000 (UTC) From: - Tong - <mlist4suntong@yahoo.com> To: debian-user@lists.debian.org Subject: Any way to stop dist-upgrade from upgrading tetex to texlive Message-ID: <fanqgr$i3l$2@sea.gmane.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,=20 Is there any way to stop dist-upgrade from upgrading tetex to texlive?=20 I just upgraded from Etch to Lenny, and have loads of things to fix, keeping tetex from upgrading to texlive will sure ease the transition for the moment.=20 thanks --=20 Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/

Date: Sat, 25 Aug 2007 02:03:42 +0200 From: Mathias Brodala <info@noctus.net> To: debian-user@lists.debian.org Subject: Re: Any way to stop dist-upgrade from upgrading tetex to texlive Message-ID: <46CF71DE.70000@noctus.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2FE0CC5A5CF036B37DE05D67" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2FE0CC5A5CF036B37DE05D67 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi. - Tong -, 25.08.2007 01:44:
> Is there any way to stop dist-upgrade from upgrading tetex to texlive? =
See the manpage of aptitude and look for "hold". Regards, Mathias --=20 debian/rules --------------enig2FE0CC5A5CF036B37DE05D67 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGz3HeYfUFJ3ewsJgRAi7EAJ9L1xCte8p+KDCUch1PkP2LcVf6rQCgkgM6 c32SqhmK3/2xn8roEUyqtlo= =RFeS -----END PGP SIGNATURE----- --------------enig2FE0CC5A5CF036B37DE05D67--

Date: Fri, 24 Aug 2007 18:48:25 -0500 (CDT) From: Jude DaShiell <jdashiel@shellworld.net> To: - Tong - <mlist4suntong@yahoo.com> Cc: debian-user@lists.debian.org Subject: Re: Any way to stop dist-upgrade from upgrading tetex to texlive Message-ID: <Pine.BSF.4.64.0708241847341.24271@freire2.furyyjbeyq.arg> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed In your apt.conf file try a line like exclude texl* and see if that helps. On Fri, 24 Aug 2007, - Tong - wrote:
> Hi,
>
> Is there any way to stop dist-upgrade from upgrading tetex to texlive?
>
> I just upgraded from Etch to Lenny, and have loads of things to fix,
> keeping tetex from upgrading to texlive will sure ease the transition for
> the moment.
>
> thanks
>
> --
> Tong (remove underscore(s) to reply)
> http://xpt.sourceforge.net/techdocs/
> http://xpt.sourceforge.net/tools/
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>

Date: Fri, 24 Aug 2007 23:51:16 +0000 (UTC) From: - Tong - <mlist4suntong@yahoo.com> To: debian-user@lists.debian.org Subject: Re: dpms setting does not work for vesa Message-ID: <fanqtk$i3l$3@sea.gmane.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, 24 Aug 2007 00:33:46 +0200, Nigel Henry wrote:
> xset -dpms
>=20
> This appears to work ok, and my monitor stays on all the time.
Thanks for the respond, Nigel. But unfortunately what I want is how to ge= t dpms working, not to disable it.=20 --=20 Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/

Date: Fri, 24 Aug 2007 18:55:09 -0500 From: Ron Johnson <ron.l.johnson@cox.net> To: debian-user@lists.debian.org Subject: Believing what you read (was Re: Good fdisk Practices) Message-ID: <46CF6FDD.2080406@cox.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/24/07 16:24, Stefan Monnier wrote:
>> I read recently on this list that LVM is not portable across CPU
>
> Don't believe everything you read.
That's why I qualified my statement. I think it was Doug Tutty who reported here that he had LVM problems when upgrading to AMD64. - -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGz2/dS9HxQb37XmcRAhQbAJ9/sOTntAMjsBqSxIJbkhZHP61OzgCfekmJ sZDvdybRrfozQR+QSFen+og= =jA7X -----END PGP SIGNATURE-----

Date: Fri, 24 Aug 2007 23:57:05 +0000 (UTC) From: - Tong - <mlist4suntong@yahoo.com> To: debian-user@lists.debian.org Subject: Re: Any way to stop dist-upgrade from upgrading tetex to texlive Message-ID: <fanr8h$i3l$4@sea.gmane.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, 24 Aug 2007 18:48:25 -0500, Jude DaShiell wrote:
>> Is there any way to stop dist-upgrade from upgrading tetex to texlive?
>>
>> I just upgraded from Etch to Lenny, and have loads of things to fix,
>> keeping tetex from upgrading to texlive will sure ease the transition =
for
>> the moment.
>=20
> In your apt.conf file try a line like exclude texl* and see if that
> helps.
wow, that's fast respond!=20 unfortunately, it doesn't work for me: echo 'exclude texl*' >> /etc/apt/apt.conf $ aptitude dist-upgrade The following NEW packages will be installed: [...] python2.5-minimal texlive texlive-base texlive-base-bin=20 texlive-bibtex-extra texlive-common texlive-doc-base texlive-font-utils= =20 [...] 1127 packages upgraded, 146 newly installed, 28 to remove and 0 not upgra= ded. [...] --=20 Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/

Date: Fri, 24 Aug 2007 17:01:21 -0700 From: Mike Bird <mgb-debian@yosemite.net> To: debian-user@lists.debian.org Subject: Re: Possible LKM Trojan installed Message-Id: <200708241701.22279.mgb-debian@yosemite.net> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Friday 24 August 2007 16:16, Jude DaShiell wrote:
> Those trojans trash very many files whenever anyone tries surgery on them.
> That was found out in a security lab by security professionals. If you
> can get to a friends computer and download the dban iso file from
> http://dban.sf.net and burn that on a single session CD and boot it up on
> the infected machine and at the boot prompt type autonuke dban will return
> your hard drive to the state it was in before it got its first operating
> system. Once finished, shut the machine down and leave it off for a
> minute. That should clear the memory. If security professionals had a
> hard time, I'm sure I wouldn't have a chance. dban will take a day to
> clear a 300gb disk. Figure 8 hours for a 100gb disk.
Why do you believe a security erasure is needed rather than simply starting with a fresh block zero? If infected, the OP can use a Debian Installation CD and make new partition tables. --Mike Bird

Date: Fri, 24 Aug 2007 20:46:22 -0400 From: Frank McCormick <fmccormick@videotron.ca> To: debian-user@lists.debian.org Subject: Re: boot error Message-id: <20070824204622.ce11f576.fmccormick@videotron.ca> Content-type: multipart/signed; protocol="application/pgp-signature"; micalg=PGP-SHA1; boundary="Signature=_Fri__24_Aug_2007_20_46_22_-0400_rnNCpD4/1Op9LJeY" --Signature=_Fri__24_Aug_2007_20_46_22_-0400_rnNCpD4/1Op9LJeY Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 24 Aug 2007 15:07:49 +0200 Florian Kulzer <florian.kulzer+debian@icfo.es> wrote:
> n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> > For the past few weeks I've been seeing an error message fly by
> > (doesn't seem to affect anything) and I curious what's going on.
> >=20
> > the message is:
> >=20
> > dbus unknown username "haldemon" in message bus configuration file.
>=20
> It should be "haldaemon". (I assume this is just a typo since you
> probably could not copy/paste the message directly.) The relevant
> configuration file is /etc/dbus-1/system.d/hal.conf:
>=20
> $ grep -A2 haldaemon /etc/dbus-1/system.d/hal.conf
> <!-- Only root or user haldaemon can own the HAL service -->
> <policy user=3D"haldaemon">
> <allow own=3D"org.freedesktop.Hal"/>
> </policy>
I have no hal.conf in that directory ??
>=20
> Hald, the daemon that manages the Hardware Abstraction Layer, used to
> run as the system user "hal". About a year ago (version 0.5.7.1-1)
> this was changed to user "haldaemon" (maybe to free "hal" as a name
> for normal users). It seems that this transition was not carried out
> correctly on your system. The post-installation script of the hal
> package is supposed to create the haldaemon user and group if they do
> not exist. You can check if the user exists:
>=20
> $ grep hal /etc/passwd
and no hal or haldaemon user??? Cheers Frank --=20 Change the world one loan at a time - visit Kiva.org to find out how =20 =20 =20 =20 =20 --Signature=_Fri__24_Aug_2007_20_46_22_-0400_rnNCpD4/1Op9LJeY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGz3vhzWG7ldLG6fIRAvCbAJ9eHE0ctP0aDf/gBHMdV2dsDvRMtgCfTBXr IH+Umv58LYMg8XJUXeBatRQ= =//2j -----END PGP SIGNATURE----- --Signature=_Fri__24_Aug_2007_20_46_22_-0400_rnNCpD4/1Op9LJeY--

Confused? Frustrated?X

Date: Sat, 25 Aug 2007 00:30:57 +0000 From: "Douglas A. Tutty" <dtutty@porchlight.ca> To: debian-user@lists.debian.org Subject: Re: Believing what you read (was Re: Good fdisk Practices) Message-ID: <20070825003057.GA8812@titan.hooton> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 24, 2007 at 06:55:09PM -0500, Ron Johnson wrote:
> On 08/24/07 16:24, Stefan Monnier wrote:
> >> I read recently on this list that LVM is not portable across CPU
> >
> > Don't believe everything you read.
>
> That's why I qualified my statement.
>
> I think it was Doug Tutty who reported here that he had LVM problems
> when upgrading to AMD64.
>
Not that I recall; but then again I have a bad memory. Don't make work, but if you find the link for such a message from me I'd like to review it. My Athlon64 uses SATA and all my other boxes use PATA so I've never moved a drive from one to the other. I use routinely the raid1/boot, raid1/LVM combos for the system directories with plain LVM on normal partitions for /home. When I get into video editing, I plan to put /var/tmp (or whatever) on a striped LV. I'm also a big fan of LVM for my old boxes. Old boxes have old drives. So far, the old drives have given some pre-failure warnings (non-SMART) in syslog before the filesystem gets corrupted. Its nice to be able to add a drive to the system and migrate the data, without needing to keep two drives in the box for raid1. Also, no two of my PATA drives are the same size. The only problem with installing that I've had consistently is that GRUB doesn't end up on the disk. I think I've tracked it down to the partitioner forgetting that I've set up the /boot partition whenever I set up something else. My recent re-install of my Athlon64 box (wanted to change from JFS back to ext3) took me 4 hours just to get the partitioner to work right; I had to keep starting the install over. Luckily, I have CD-bin1.iso since I'm on dialup. Thanks, Doug.

Date: Sat, 25 Aug 2007 00:34:13 +0000 From: "Douglas A. Tutty" <dtutty@porchlight.ca> To: debian-user@lists.debian.org Subject: Re: Possible LKM Trojan installed Message-ID: <20070825003413.GB8812@titan.hooton> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 24, 2007 at 05:01:21PM -0700, Mike Bird wrote:
> Why do you believe a security erasure is needed rather than simply
> starting with a fresh block zero? If infected, the OP can use a
> Debian Installation CD and make new partition tables.
>
Good question. I've yet to hear a definitive, absolute, take-it-to-the-bank answer. For my friend, Justin Case, I boot GRML and run wipe on the whole disk. I let it run overnight. Probably overkill, but it gives the whole drive a workout. Doug.

Date: Fri, 24 Aug 2007 20:55:19 -0400 From: Frank McCormick <fmccormick@videotron.ca> To: debian-user@lists.debian.org Subject: Re: hda: DMA timeout error, is it a problem ? Message-id: <20070824205519.36bab5fd.fmccormick@videotron.ca> Content-type: multipart/signed; protocol="application/pgp-signature"; micalg=PGP-SHA1; boundary="Signature=_Fri__24_Aug_2007_20_55_19_-0400_pJDZ=.ib7YEepIQK" --Signature=_Fri__24_Aug_2007_20_55_19_-0400_pJDZ=.ib7YEepIQK Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, 25 Aug 2007 00:45:27 +0000 "Douglas A. Tutty" <dtutty@porchlight.ca> wrote:
> On Fri, Aug 24, 2007 at 08:12:28PM +0200, Shams Fantar wrote:
> > Douglas A. Tutty wrote:
> >=20
> > >Try shutdown, disable DMA in the bios, and reboot into single-user
> > >mode (avoids mounting the drive rw). See if the messages show up
> > >in dmesg. Then reboot into normal mode and check syslog for that
> > >boot (ignore previous boots). =20
> >=20
> > There are the same messages.
> >=20
> > >The thing about S.M.A.R.T. If it says the drive is failing, then
> > >it is. If it says the drive is OK then it may be, or not.
> > >
> > >Try booting either the install disk in rescue mode or a live CD so
> > >that the drive is totally unmounted. Run a full filesystem check
> > >with read/write badblocks check. I'm not thinking you'll find bad
> > >blocks, but it forces the drive firmware to verify each block of
> > >the disk platter. Check the syslog of the live or install CD to
> > >see if you have the same errors. =20
> >=20
> > Yes, there are still the same messages.
> >=20
> > >Then reboot the normal system and check syslog again. Then start
> > >another S.M.A.R.T. long test and wait its recommended time and
> > >review the result.
> >=20
> > The new long test available at
> > http://jumble.snurf.info/desktop/hard-disk
> >=20
> > So is it dead?
> >=20
>=20
> According to SMART, the drive is fine. If the filesystem badblocks
> check was OK then that seems to be OK too.
>=20
> So I don't know why you're having DMA errors. Hopefully someone who
> knows more about SMART and the ide driver can shed some light.
> Perhaps its a driver issue.
I've been following this thread for quite a while - I have been getting DMA timeout errors on boot for about a year - i am also running SMART and every test I have done shows no problem. Booted with the install disk and run fschk so many time I have lost track. Never a problem, but DMA timeouts continue. I have come to the conclusion it's some obscure bug, perhaps in the IDE module. It *never* affects anything else as the drive is fast and so far reliable. If/when it dies I'll change my opinion. --=20 Change the world one loan at a time - visit Kiva.org to find out how =20 =20 =20 =20 =20 --Signature=_Fri__24_Aug_2007_20_55_19_-0400_pJDZ=.ib7YEepIQK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGz333zWG7ldLG6fIRAvgxAJ4zi3FiDrGwSx8OeucIHpOuSnz6DwCeLx2I sO2m7LNwWmnFkmM/aUzFQAY= =P9LG -----END PGP SIGNATURE----- --Signature=_Fri__24_Aug_2007_20_55_19_-0400_pJDZ=.ib7YEepIQK--

Date: Sat, 25 Aug 2007 10:37:28 +1000 From: Cameron Hutchison <lists@xdna.net> To: debian-user@lists.debian.org Subject: Re: Good fdisk Practices Message-Id: <1188002248.0@orthanc> David Brodbeck <brodbd@u.washington.edu> wrote:
>I'd always heard that swap files are slower than swap partitions. Is
>that a myth?
Not a myth, just old information. It used to be the case that swap files were slower than swap partitions, but this stopped being true sometime around kernel 2.4
>Also, is there any good reason to have a separate /boot on a modern
>system? I always thought /boot was just a kludge to get around old
>BIOSes that couldn't load anything that wasn't on the first part of
>the disk. I tend to just combine /boot and / on my newer systems --
>am I taking some kind of risk by doing so?
I do the same and have had no problems. This may restrict the type of filesystem you can use on your root partition though. I dont think GRUB can load a kernel from an XFS filesystem, so by separating root and /boot, you can put ext2/3 on /boot and something else on root. End of debian-user-digest Digest V2007 Issue #2246 ************************************************** Received on Fri Aug 24 21:05:27 2007

This archive was generated by hypermail 2.1.8 : Sun Oct 07 2007 - 07:54:10 EDT

Contact Us  Legal Notices  Order Services Online 
Pantek Home  Privacy Policy  IT news  Site Map  Pantek Library