Date: Sat, 4 Aug 2007 09:03:05 -0400
From: Douglas Allan Tutty <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: Transitioning to 64bit, is it worth it, and how
Message-ID: <20070804130305.GC6564@titan>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sat, Aug 04, 2007 at 12:19:09PM +0100, Alan Chandler wrote:
> On Saturday 04 Aug 2007, Ron Johnson wrote:
> > On 08/04/07 03:25, Alan Chandler wrote:
>
> > > b) Is there a simple transition path?
> >
> > Reinstall from scratch, and pray that your /home is on a seperate
> > partition.
>
> Well the only home that matters - ie mine is - this is essentially just
> a personal machine. I am using raid1 with LVM on top, so I can easily
> create additional "partitions" and move things about as I wish.
>
> My only slight reservation is I am not sure if the installer supports
> raid, so it might be more complex than just installing. I also want to
> take the opportunity to enlarge my /boot partition (also raid 1) as 32M
> is just not enough these days - frequently seem to fill it up as I
> upgrade kernels.
>
I don't think that you can keep your 32-bit raid/LVM setup, but I don't
know. Your safest option is to backup your /home (you do this anyway,
right), and do a clean reinstall.
Doug.
Date: Sat, 04 Aug 2007 14:51:22 -0000
From: DanKegel <daniel.r.kegel@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: MS Word under wine/crossover office
Message-ID: <1186239082.646408.228490@x40g2000prg.googlegroups.com>
Content-Type: text/plain; charset="us-ascii"
On Aug 2, 5:10 pm, Tyler Smith <tyler.sm...@mail.mcgill.ca> wrote:
> Which brings me to my question: do any of you have any experience
> using wine or crossover office with MSWord?
Yes. That's what crossover is for. Purchasing a copy of
crossover will support the development of wine.
> in this case OpenOffice is definitely not good enough. It's great,
> of course, but not when it comes to exchanging .doc files with
> critical formatting intact.
Please try to file bug reports at
http://qa.openoffice.org/
with example documents (ideally reduced to simple cases).
You might search for existing bug reports there first to avoid
duplication.
- Dan
Date: Sat, 4 Aug 2007 11:23:56 -0400
From: "Francois Duranleau" <xiao.bai.xiong@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: ext3fs errors with kernel 2.6.18 but not with 2.4.27
Message-ID: <8eb883950708040823p332d4858ia475e90ca6266c02@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/4/07, Francois Duranleau <xiao.bai.xiong@gmail.com> wrote:
> On 8/3/07, Brad Sawatzky <brad+debian@swatter.net> wrote:
> > Hi Francois,
> >
> > I agree with Doug: CRC errors shouldn't be ignored. At _best_ they are a
> > sign that something in your system is marginal. At worst you end up
> > reading and/or writing bogus data. The fact that the errors persisted
> > after you changed hard drives suggest either a bad cable (most likely), bad
> > secondary device on that cable, or bad motherboard (unlikely).
>
> I tried to change the IDE cables (I had a few spares from my father's computer).
> I happened to notice that I had a 40 pins cable. I replaced it with a 80 pins
> cable. I have two, I tried both: nothing changed. I still have CRC errors. BTW,
> there is only one drive on that cable.
>
> However, I noticed that the motherboard's chipset's fan is dead. I knew it was
> having a hard time spinning lately, but now, it's gone. Would it be the
> motherboard's chipset that causes those errors because it's too hot?
Browsing around to look for potential problems with the VIA chipset driver, I
came upon this:
http://www.tiny.cc/xORCV
(see the last post in the thread)
Apparently, I am not the only one getting this kind of CRC errors on the
primary IDE interface (and I do happen to have this exact motherboard:
ABIT KT7). I will look if there are still some BIOS updates that may change
something.
--
Francois
Date: Sat, 4 Aug 2007 09:35:50 -0400
From: Wayne Topa <linuxone@intergate.com>
To: debian-user@lists.debian.org
Subject: Re: Issues with ethernet in testing/lenny
Message-ID: <20070804133550.GA26557@buddy.mtntop.home>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
percy tiglao(prtiglao@gmail.com) is reported to have said:
> Hello, I've recently purchased a Dell Inspiron 530 and wanted to get
> Debian onto it. I've installed Lenny mostly without any issues, but it
> did not autodetect my ethernet card. It is a 82562V-2 integrated card,
> at least according to the Windows Vista devise manager.
>
> Anyway, I do have a very basic system up and running. No internet
> support or anything, so I can really only do stuff from the Windows
> side of my system right now. I'm not sure how I can get logs of what I
> do to my email from Debian so I'm sorry about the lack of the logs.
> I'll do my best to describe the error messages however.
>
> As I stated earlier, the installer did not detect the network card. I
> tried loading the "e1000" module inside the installation program which
> according to intel should be the module I need:
> http://downloadmirror.intel.com/9180/ENG/README.txt
>
> The installer wouldn't acccept it, it would just loop back to the
> "select module" screen. I tried to "modprobe e1000" manually during
> the installation, but that didn't work either. No error messages come
> up.
>
> After that, the rest of the system installed without any hassle, but
> obviously I cannot connect to the internet right now without any
> network card, so I don't have anything installed aside from whatever
> is on the base netinstall on Lenny.
>
> I've tried to "modprobe e1000" after the installation, and there seems
> to be no errors that happen. I use dmesg and aside from the loading
> message from e1000, no other messages pop up. I've also added "iface
> eth0 inet dhcp" into my /etc/network/interfaces file, and tried to do
> "ifup eth0", but that fails with the message: 'Device "eth0" does not
> exist'
>
> Thank you for reading this message. I'd really like to get Debian up
> and running as soon as possible so please help. As an aside, all error
> messages and other logs are from memory + google. So they may not be
> 100% correct but they're the best I got right now.
Take a look at the /etc/udev/rules.d/z25_persistent-net.rules file.
I had a problem with a laptop, because of a lot of testing I was
doing, that thought the ethernet card was eth6. So ifup eth0 didn't
work but ifup eth6 did. I repaired that file and now so that eth0
was the only ethernet interface and all is well.
HTH=Hope This Helps, YMMV=Your Mileage May Vary, HAND=Have A Nice Day
Wayne
--
Any programming language is at its best before it is implemented and
used.
_______________________________________________________
Date: Sat, 04 Aug 2007 11:40:14 -0400
From: "H.S." <hs.samix@gmail.com>
To: debian-user@lists.debian.org
Subject: working with two nics (lan and wlan)
Message-ID: <f926le$mjq$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hello,
I have a headless machine on my home network with a LAN card and a
wireless card. If my lan cable is connected to its lan card, it gets an
IP automatically from my firewall machine. But if I activate the
wireless card, the networking seems to hang or freeze. My lan card is on
192.168.0.x network and the wireless card is on 192.168.5.x network.
Is there any way I can have both the cards active and networking
working? Perhaps by specifying somewhere which network has the higher
priority? This is so because there are many situations where I sometimes
want both cards up, mainly while trying out various wireless drivers
with my wireless card. Another situation when I want to transfer huge
amounts data via the wired network (higher speed) to other machines on
the local network.
Alternatively, I suppose ifplugd can handle multiple cards at the same
time. In my situations, can it be configured to use wlan card if it is
up, else to use the lan card?
Thanks,
->HS
Date: Sat, 4 Aug 2007 09:06:17 -0700
From: Andrew Sackville-West <andrew@farwestbilliards.com>
To: debian-user@lists.debian.org
Subject: Re: working with two nics (lan and wlan)
Message-ID: <20070804160326.GA23207@localhost.localdomain>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="xXmbgvnjoT4axfJE"
Content-Disposition: inline
--xXmbgvnjoT4axfJE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Aug 04, 2007 at 11:40:14AM -0400, H.S. wrote:
>
> Hello,
>
> I have a headless machine on my home network with a LAN card and a wirele=
ss=20
> card. If my lan cable is connected to its lan card, it gets an IP=20
> automatically from my firewall machine. But if I activate the wireless=20
> card, the networking seems to hang or freeze. My lan card is on 192.168.0=
=2Ex=20
> network and the wireless card is on 192.168.5.x network.
>
> Is there any way I can have both the cards active and networking working?=
=20
> Perhaps by specifying somewhere which network has the higher priority? Th=
is=20
> is so because there are many situations where I sometimes want both cards=
=20
> up, mainly while trying out various wireless drivers with my wireless car=
d.=20
> Another situation when I want to transfer huge amounts data via the wired=
=20
> network (higher speed) to other machines on the local network.
>
> Alternatively, I suppose ifplugd can handle multiple cards at the same=20
> time. In my situations, can it be configured to use wlan card if it is up=
,=20
> else to use the lan card?
we need more information. what hardware? what do the appropriate
config files look like? is there any relevant log output? etc etc
A
--xXmbgvnjoT4axfJE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGtKP4aIeIEqwil4YRAsOLAJ9K78ZLUhZyiJl2rP1Y0sSTPSkWCwCghruN
Fap+zUzwx8buOkhX3vbGKm4=
=oUAB
-----END PGP SIGNATURE-----
--xXmbgvnjoT4axfJE--
Date: Sat, 04 Aug 2007 17:49:45 +0200
From: Marko Randjelovic <marel@sbb.co.yu>
To: debian-user@lists.debian.org
Cc: debian-user@lists.debian.org
Subject: Re: ext3fs errors with kernel 2.6.18 but not with 2.4.27
Message-ID: <46B4A019.1020106@sbb.co.yu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Francois Duranleau wrote:
>> I tried to change the IDE cables (I had a few spares from my father's computer).
>> I happened to notice that I had a 40 pins cable. I replaced it with a 80 pins
>> cable. I have two, I tried both: nothing changed. I still have CRC errors. BTW,
>> there is only one drive on that cable.
>>
>> However, I noticed that the motherboard's chipset's fan is dead. I knew it was
>> having a hard time spinning lately, but now, it's gone. Would it be the
>> motherboard's chipset that causes those errors because it's too hot?
>
> Browsing around to look for potential problems with the VIA chipset driver, I
> came upon this:
>
> http://www.tiny.cc/xORCV
> (see the last post in the thread)
>
> Apparently, I am not the only one getting this kind of CRC errors on the
> primary IDE interface (and I do happen to have this exact motherboard:
> ABIT KT7). I will look if there are still some BIOS updates that may change
> something.
>
I think you are right. The fan malfunction is probably not the cause,
since it is mounted on north bridge, and IDE controler is in south
bridge, that doesn't need a fan.
So, replace a motherboard.
Date: Sat, 04 Aug 2007 13:32:13 -0400
From: Jose Luis Rivas Contreras <ghostbar38@gmail.com>
To: debian-user@lists.debian.org
Cc: debian-user@lists.debian.org
Subject: Re: Transitioning to 64bit, is it worth it, and how
Message-ID: <46B4B81D.1030901@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enig81AB422654128E1BF1364FA5"
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig81AB422654128E1BF1364FA5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Marko Randjelovic wrote:
> option. If you need Acroread, first install ia32-libs-gtk from Ubuntu.
Just for the record, I installed today ia32-libs-gtk from officials
unstable repos in Debian...
Regards,
Jose Luis.
--=20
ghostbar on Linux/Debian 'sid' x86_64-SMP - #382503
Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org
http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es
San Crist=C3=B3bal, Venezuela. http://chaslug.org.ve
Fingerprint =3D 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118
--------------enig81AB422654128E1BF1364FA5
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)
iD8DBQFGtLghOKCtW8rKsRgRAhONAKCWQqobCYi6s8F1U5hrTFF5Hz4IVACg0Nit
cFfVHGaH4O+yeCwAoURtI1M=
=NMHd
-----END PGP SIGNATURE-----
--------------enig81AB422654128E1BF1364FA5--
Date: Sat, 4 Aug 2007 13:53:05 -0400
From: "Andrew J. Barr" <andrew.james.barr@gmail.com>
To: "Alan Chandler" <alan@chandlerfamily.org.uk>
Cc: debian-user@lists.debian.org
Subject: Re: Transitioning to 64bit, is it worth it, and how
Message-ID: <903e17bb0708041053p3aa87671v69c5f71cce44abe1@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/4/07, Alan Chandler <alan@chandlerfamily.org.uk> wrote:
> I have a Core2 Duo on which I am running a 686 kernel (from Debian
> unstable). It has 1GB of memory
>
> I am wondering two things
>
> a) What are the pros and cons in switching to 64 bit mode?
> - Is it faster?
Yes. Unlike true 64-bit architectures like PowerPC, there is a penalty
for executing 32 bit code on amd64/em64t processors. This is why the
amd64 port of Debian has an all 64-bit user land, whereas other 64-bit
ports of Linux and other operating systems generally have mostly a
32-bit user land and compile only applications that would benefit for
64-bit.
--
Andrew Barr
We matter more than pounds and pence,
your economic theory makes no sense...
Date: Sat, 04 Aug 2007 17:46:07 GMT
From: "George N. White III" <aa056@chebucto.ns.ca>
To: debian-user@lists.debian.org
Subject: Re: Opinions XFS
Message-ID: <alpine.LFD.0.99.0708041406001.19465@cerberus.cwmannwn>
Content-Type: TEXT/PLAIN; format=flowed; charset=us-ascii
On Sat, 4 Aug 2007, michael@estone.ca wrote:
> Quoting Sergio Belkin <sebelk@gmail.com>:
>
>> Hi I was reading http://oss.sgi.com/projects/xfs/index.html and was
>> amazed because XFS powerful features. But I'd like opinions if xfs
>> should be a good alternative to ext3 in typical cases, or if it should
>> be relegated to critical missions servers.
>
> XFS is a rock solid filesystem. So is EXT3. XFS generally will be faster
> than EXT3, but only for medium to large files. EXT3 is faster with
> really small files around 1K or so. Depending on your needs, you may
> want to benchmark the 2 filesystems to compare. Bonnie++ is a nice tool
> to use, as it lets you change the test file sizes around.
>
> XFS and grub do not work nicely together, therefore you'll need /boot
> mounted with EXT3, everything else can be XFS, even / .
>
> XFS can destroy files, but its more of myth when people say it will just
> magically destroy files. XFS is designed this way as its a meta-data
> only journalling filesystem. Bottom line, is that only recently written
> files, within 60 seconds of write, will get hosed if your system
> suddenly loses power. Therefore, if you use XFS, use a UPS, of which
> will auto halt your box in case of power loss. Use good hardware, and of
> course, have good backups. Also, use smartmontools to monitor your
> drives. Its not 100% perfect against failing drives, but its better than
> nothing.
I suspect many of the bad experiences with XFS were using IDE drives on
32-bit x86 hardware. XFS was originally developed on RISC hardware, and
did not fit well with register-starved hardware. Red Hat in particular
has worked hard to run with 4k stacks, and XFS users have had to build
kernels with larger stack size. The xfsrepair tool needed ample
resources, so if you had a problem with XFS on a typical system (PIII with
256M) you had to move the disk to a better box to sort things out.
> I would not recommend XFS for a workstation environment where its your system
> drive. Why? Only because you might have to hard reboot it every once in
> awhile. Perhaps for storing media type files on a seperate [sic]
> filesystem though.
I use SGI IRIX workstations for remote sensing. The filesystems are all
XFS. Over the years I've had lots of disks fail, and also several SCSI
controllers. Often the first sign of hardware problems is errors from
fsr. Since the system disks were the oldest, most of the workstations
have crashed when the the root filesystem went poof, but the other (data)
filesystems were recovered with minimal problems.
I did have the experience of working on a program only to have big chunks
of an XFS filesystem on a RAID (5 9G SCSI disks) go poof when the
controller for the external SCSI failed. I moved the RAID to another box
and what was left of the XFS filesystem was fine.
> I'm quite impressed with the stability and performance of XFS and having been
> using it for over a year on production servers that run mail, file and web
> serving. (x86_64 etch)
Let us know how you feel once you have experienced a few hardware
failures.
--
George N. White III <aa056@chebucto.ns.ca>
Date: Sat, 4 Aug 2007 14:06:46 -0400
From: Wayne Topa <linuxone@intergate.com>
To: debian-user@lists.debian.org
Subject: Re: ext3fs errors with kernel 2.6.18 but not with 2.4.27
Message-ID: <20070804180646.GA3843@buddy.mtntop.home>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Francois Duranleau(xiao.bai.xiong@gmail.com) is reported to have said:
> On 8/4/07, Francois Duranleau <xiao.bai.xiong@gmail.com> wrote:
> > On 8/3/07, Brad Sawatzky <brad+debian@swatter.net> wrote:
> > > Hi Francois,
> > >
> > > I agree with Doug: CRC errors shouldn't be ignored. At _best_ they are a
> > > sign that something in your system is marginal. At worst you end up
> > > reading and/or writing bogus data. The fact that the errors persisted
> > > after you changed hard drives suggest either a bad cable (most likely), bad
> > > secondary device on that cable, or bad motherboard (unlikely).
> >
> > I tried to change the IDE cables (I had a few spares from my father's computer).
> > I happened to notice that I had a 40 pins cable. I replaced it with a 80 pins
> > cable. I have two, I tried both: nothing changed. I still have CRC errors. BTW,
> > there is only one drive on that cable.
> >
> > However, I noticed that the motherboard's chipset's fan is dead. I knew it was
> > having a hard time spinning lately, but now, it's gone. Would it be the
> > motherboard's chipset that causes those errors because it's too hot?
>
> Browsing around to look for potential problems with the VIA chipset driver, I
> came upon this:
>
> http://www.tiny.cc/xORCV
> (see the last post in the thread)
>
> Apparently, I am not the only one getting this kind of CRC errors on the
> primary IDE interface (and I do happen to have this exact motherboard:
> ABIT KT7). I will look if there are still some BIOS updates that may change
> something.
I also have the ABIT KT7 and it has gone from kernels 2.4.27 ->
2.6.18-4 with no CRC errors showing up at all. It's only been running
for 5-6 years. CPU Fan has been changed twice but other then that,
its fine.
Wayne
--
Turnaucka's Law:
The attention span of a computer is only as long as its electrical cord.
_______________________________________________________
Date: Sat, 04 Aug 2007 13:46:18 -0500
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: Transitioning to 64bit, is it worth it, and how
Message-ID: <46B4C97A.60209@cox.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/04/07 12:53, Andrew J. Barr wrote:
> On 8/4/07, Alan Chandler <alan@chandlerfamily.org.uk> wrote:
>> I have a Core2 Duo on which I am running a 686 kernel (from Debian
>> unstable). It has 1GB of memory
>>
>> I am wondering two things
>>
>> a) What are the pros and cons in switching to 64 bit mode?
>> - Is it faster?
>
> Yes. Unlike true 64-bit architectures like PowerPC, there is a penalty
> for executing 32 bit code on amd64/em64t processors.
Penalty? Absolutely fscking not!!!! The A64 processes 32 bit code
at a similar speed to "regular" Athlon CPUs.
> This is why the
> amd64 port of Debian has an all 64-bit user land, whereas other 64-bit
> ports of Linux and other operating systems generally have mostly a
> 32-bit user land and compile only applications that would benefit for
> 64-bit.
>
- --
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)
iD8DBQFGtMl5S9HxQb37XmcRAjzoAJ4x8X59ymK8SjExPbBZzPwgDQMYygCgx4Za
Nk/L+s4d7bUzlP5kwq2DrdQ=
=omH0
-----END PGP SIGNATURE-----
Date: Sat, 4 Aug 2007 15:31:32 -0400
From: "Andrew J. Barr" <andrew.james.barr@gmail.com>
To: "Ron Johnson" <ron.l.johnson@cox.net>
Cc: debian-user@lists.debian.org
Subject: Re: Transitioning to 64bit, is it worth it, and how
Message-ID: <903e17bb0708041231v599a2f9cq886c733810970c7c@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/4/07, Ron Johnson <ron.l.johnson@cox.net> wrote:
> On 08/04/07 12:53, Andrew J. Barr wrote:
> >> a) What are the pros and cons in switching to 64 bit mode?
> >> - Is it faster?
> >
> > Yes. Unlike true 64-bit architectures like PowerPC, there is a penalty
> > for executing 32 bit code on amd64/em64t processors.
>
> Penalty? Absolutely fscking not!!!! The A64 processes 32 bit code
> at a similar speed to "regular" Athlon CPUs.
Do you have any sources for this? I remember quite distinctly seeing
on a mailing list, I think it was debian-powerpc in fact, that the
only reason that AMD64 operating systems have an all-64-bit user land
is because there is a penalty for executing 32-bit code, one which is
not present on other true 64-bit architectures. 64-bit code /does/ use
more memory, so it is advantageous to have a mixed userland if you can
afford it--e.g. only compiling applications that will benefit from
64-bit into 64-bit executables. This is what the OSes for other 64-bit
architectures do.
Perhaps the penalty is only under a 64-bit kernel...
--
Andrew Barr
We matter more than pounds and pence,
your economic theory makes no sense...
Date: Sat, 4 Aug 2007 21:28:18 +0200
From: Florian Kulzer <florian.kulzer+debian@icfo.es>
To: debian-user@lists.debian.org
Subject: Re: Blurry fonts in OpenOffice and qt4 appliations
Message-ID: <20070804192818.GA4570@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Aug 03, 2007 at 22:54:10 -0700, Alan Ianson wrote:
> On Fri August 3 2007 21:50, Andrei Popescu wrote:
> > On Fri, Aug 03, 2007 at 07:15:39PM -0700, Alan Ianson wrote:
> > > On Fri August 3 2007 12:48, Vasil Benov wrote:
> > > > Hi all,
> > > >
> > > > The fonts in OpenOffice and qt4(skype 1.4 beta) applications are
> > > > blurry. Has anyone encountered the same problem?
> > > > There is a thread on the Ubuntu mailing list, but it does not offer any
> > > > solution.
> > >
> > > I noticed that too a while ago, one of the fonts I was using (sorry, I
> > > forget which one) seemed to have a rainbow color effect to it for reasons
> > > unknown. I changed the system font to something else and it has looked
> > > fine since.
> >
> > LCD or CRT monitor? Have a look at the sub-pixel rendering option
> > (dpkg-reconfigure fontconfig-config).
>
> LCD, it was on my laptop. Thanks, I'll run that and have a look.
The rainbow color effect can also be caused by RGB subpixel hinting,
which is an Xft option. Check the output of
xrdb -query | grep Xft
for the Xft.rgba setting. You can change the Xft settings by doing
things like:
echo "Xft.rgba: none" | xrdb -merge
You have to restart the affected application(s) to see the effect of the
changed settings.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Date: Sat, 4 Aug 2007 22:01:33 +0200
From: Stephan Hachinger <stephan.hachinger@gmx.de>
To: debian-user@lists.debian.org
Cc: me@phillatwood.name
Subject: Re: ntfs mount errors
Message-Id: <20070804220133.55bd1613.stephan.hachinger@gmx.de>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Fri, 3 Aug 2007 20:51:50 -0700
Andrew Sackville-West <andrew@farwestbilliards.com> wrote:
> On Fri, Aug 03, 2007 at 11:17:21PM -0400, Phill Atwood wrote:
> >
> >
> >
> > Success. Although I can't say that I really understand. Setting
> > umask=0222 in the /etc/fstab file did the trick. I don't understand why
> > mounting a ro partition to a directory with just write permissions would
> > work. 0544 or 0555 seemed the more logical thing to try...
(...)
> So I'm not sure how that translates to the first digit since i'm sure
> you don't want a perm to come out 7555 using umask of 0222 but maybe
> someone can enlighten
Well, wikipedia says ;), the bitwise-inverted umask is bitwise ANDed with the *default "full permission"*, i.e. 666 for files and 777 for dirs. This should mean, 0666 and 0777, if I am understanding it right (see interpretation for missing digits in chmod(1)). Thus:
000 110 110 110 AND
not(000 010 010 010) =
000 110 110 110 AND
111 101 101 101 = 0444
For dirs, the result is 0555.
> > c) Even after this success, dmesg shows:
> >
> > NTFS volume version 3.1.
> > NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> > flags 0x4000 encountered.
(...)
> i see that a lot and never have any problems. FWIW. but avoid writing
> in ntfs if you can.
That's really strange ... but I'm pretty sure that's not debian-specific (as I found this on forums for all kinds of distros).
> > > Another thing: If you also need write access onto ntfs, and want read access onto compressed files, then the ntfs-3g driver might be interesting for you. For newbies however, it might not be that easy to install... you need to make a package for stable yourself. On the other hand, if you'd need it, I can just do an update/recompile here on my system and send the resulting package to you via email.
>
> is it in backports?
Yep, that's a good hint: ntfs-3g ver 1.516 (slightly outdated) is available if you add the line:
deb http://www.backports.org/debian etch-backports main contrib non-free
into your /etc/apt/sources.list, do apt-get update, and then install.
Cheers,
Stephan
End of debian-user-digest Digest V2007 Issue #2097
**************************************************
Received on Sat Aug 4 16:47:56 2007