Date: Tue, 31 Jul 2007 14:09:33 -0700
From: Glen Pfeiffer <glen@thepfeiffers.net>
To: debian-user@lists.debian.org
Subject: Re: Firefox \ Iceweasel Differences?
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
On 07/31/2007 01:50 PM, John Hasler wrote:
> Glen Pfeiffer writes:
>> Accept that it will not display the same on all browsers.
>
> Why do you think it should display the same on all browsers?
> Or even on all instances of the same browser?
Oh, I don't. But there are certain types of designs that only
look good in their original form. Hence number one from my list:
>> 1. Change the design so I do not have the problem.
But it is a very common problem among graphic designers and
corporate types.
--
Glen
Date: Tue, 31 Jul 2007 23:21:27 +0200
From: Florian Kulzer <florian.kulzer+debian@icfo.es>
To: debian-user@lists.debian.org
Subject: Re: Udev. Problems with ordering hardware using /dev/video
Message-ID: <20070731212127.GA4405@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue, Jul 31, 2007 at 19:47:51 +0200, Nigel Henry wrote:
> I've managed to resolve most of my problems on my own, but Udev has beaten me.
>
> Sarge is not a problem, as it's using the 2.4.27, or 2.6.8 kernel, and Udev is
> not in the equation. Etch has a 2.6.8, and a 2.6.17 kernel, and Lenny has a
> 2.6.11, and a 2.6.17 kernel. The problem is with the 2.6.17 kernel that uses
> Udev.
>
> My TV card was set as /dev/video0, and some time later the webcam was set
> as /dev/video1. this works fine with the pre 2.6.17 kernels (no Udev), and
> the TV card consistently is /dev/video0, and the webcam /dev/video1. Booting
> with the 2.6.17 kernel is a different scenario. Very hit and miss. Sometimes
> I boot up and starting Xawtv, I get the TV /dev/video0. Othertimes I bootup
> and start Xawtv, and get my webcam /dev/video1.
This flip-flopping is, AFAIK, more the fault of the newer kernel then
the fault of udev. If the kernel would always load the modules in the
same order then udev would probably assign the device nodes in a
consistent manner.
> I've worked with ordering my soundcards, and the lines are quite simple, and
> have seen that something similar is possible with Udev, although the lines a
> re a bit more complex. Could someone give me a couple of lines so that my TV
> card is always /dev/video0, and the webcam is always /dev/video1?
>
> Any help gratefully appreciated for fixing this annoying problem.
Post the output of:
udevinfo -a -p $(udevinfo -q path -n /dev/video0)
udevinfo -a -p $(udevinfo -q path -n /dev/video1)
(Only the blocks that have things like "ATTRS{model}" or "ATTRS{vendor}"
are important.)
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Date: Tue, 31 Jul 2007 23:24:56 +0200
From: Florian Kulzer <florian.kulzer+debian@icfo.es>
To: debian-user@lists.debian.org
Subject: Re: A question of fonts
Message-ID: <20070731212456.GB4405@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue, Jul 31, 2007 at 21:35:50 +0100, andy wrote:
>> On Mon, Jul 30, 2007 at 21:45:07 +0100, andy wrote:
[...]
>>> And in response to xrdb -query:
>>>
>>> Xft.antialias: 1
>>> Xft.dpi: 120.000000
>>> Xft.hinting: 1
>>> Xft.hintstyle: hintfull
>>> Xft.rgba: none
>>>
[...]
> Output of the .fonts.conf file:
>
> <?xml version="1.0"?>
> <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
> <fontconfig>
> <match target="font" >
> <edit mode="assign" name="rgba" >
> <const>none</const>
> </edit>
> </match>
> <match target="font" >
> <edit mode="assign" name="hinting" >
> <bool>true</bool>
> </edit>
> </match>
> <match target="font" >
> <edit mode="assign" name="hintstyle" >
> <const>hintfull</const>
> </edit>
> </match>
> <match target="font" >
> <edit mode="assign" name="antialias" >
> <bool>true</bool>
> </edit>
> </match>
> </fontconfig>
>
> I have yet to try changing fontconfig/hinting_type to "Native" but will
> when a decent reason to shut X down presents in terms of work flow.
>
> Any thoughts on the conf file settings?
The fons.conf file is consistent with your Xft settings. Which desktop
environment or WM are you using?
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Date: Tue, 31 Jul 2007 23:28:01 +0100
From: andy <geek_show@dsl.pipex.com>
To: debian-user@lists.debian.org
Subject: Re: A question of fonts
Message-ID: <46AFB771.4010501@dsl.pipex.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Florian Kulzer wrote:
> On Tue, Jul 31, 2007 at 21:35:50 +0100, andy wrote:
>
>
>>> On Mon, Jul 30, 2007 at 21:45:07 +0100, andy wrote:
>>>
>
> [...]
>
>
>>>> And in response to xrdb -query:
>>>>
>>>> Xft.antialias: 1
>>>> Xft.dpi: 120.000000
>>>> Xft.hinting: 1
>>>> Xft.hintstyle: hintfull
>>>> Xft.rgba: none
>>>>
>>>>
>
> [...]
>
>
>> Output of the .fonts.conf file:
>>
>> <?xml version="1.0"?>
>> <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
>> <fontconfig>
>> <match target="font" >
>> <edit mode="assign" name="rgba" >
>> <const>none</const>
>> </edit>
>> </match>
>> <match target="font" >
>> <edit mode="assign" name="hinting" >
>> <bool>true</bool>
>> </edit>
>> </match>
>> <match target="font" >
>> <edit mode="assign" name="hintstyle" >
>> <const>hintfull</const>
>> </edit>
>> </match>
>> <match target="font" >
>> <edit mode="assign" name="antialias" >
>> <bool>true</bool>
>> </edit>
>> </match>
>> </fontconfig>
>>
>> I have yet to try changing fontconfig/hinting_type to "Native" but will
>> when a decent reason to shut X down presents in terms of work flow.
>>
>> Any thoughts on the conf file settings?
>>
>
> The fons.conf file is consistent with your Xft settings. Which desktop
> environment or WM are you using?
>
>
Sorry - forgot you asked me that. I predominantly use Gnome, but switch
to Xfce from time-to-time. I login using GDM.
A
--
"If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Date: Wed, 1 Aug 2007 00:45:54 +0200
From: Nigel Henry <cave.dnb@tiscali.fr>
To: debian-user@lists.debian.org
Subject: Re: Udev. Problems with ordering hardware using /dev/video
Message-Id: <200708010045.54197.cave.dnb@tiscali.fr>
Content-Disposition: inline
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
On Tuesday 31 July 2007 23:21, Florian Kulzer wrote:
> On Tue, Jul 31, 2007 at 19:47:51 +0200, Nigel Henry wrote:
> > I've managed to resolve most of my problems on my own, but Udev has
> > beaten me.
> >
> > Sarge is not a problem, as it's using the 2.4.27, or 2.6.8 kernel, and
> > Udev is not in the equation. Etch has a 2.6.8, and a 2.6.17 kernel, and
> > Lenny has a 2.6.11, and a 2.6.17 kernel. The problem is with the 2.6.17
> > kernel that uses Udev.
> >
> > My TV card was set as /dev/video0, and some time later the webcam was set
> > as /dev/video1. this works fine with the pre 2.6.17 kernels (no Udev),
> > and the TV card consistently is /dev/video0, and the webcam /dev/video1.
> > Booting with the 2.6.17 kernel is a different scenario. Very hit and
> > miss. Sometimes I boot up and starting Xawtv, I get the TV /dev/video0.
> > Othertimes I bootup and start Xawtv, and get my webcam /dev/video1.
>
> This flip-flopping is, AFAIK, more the fault of the newer kernel then
> the fault of udev. If the kernel would always load the modules in the
> same order then udev would probably assign the device nodes in a
> consistent manner.
>
> > I've worked with ordering my soundcards, and the lines are quite simple,
> > and have seen that something similar is possible with Udev, although the
> > lines a re a bit more complex. Could someone give me a couple of lines so
> > that my TV card is always /dev/video0, and the webcam is always
> > /dev/video1?
> >
> > Any help gratefully appreciated for fixing this annoying problem.
>
> Post the output of:
>
> udevinfo -a -p $(udevinfo -q path -n /dev/video0)
>
> udevinfo -a -p $(udevinfo -q path -n /dev/video1)
>
> (Only the blocks that have things like "ATTRS{model}" or "ATTRS{vendor}"
> are important.)
>
> --
> Regards, | http://users.icfo.es/Florian.Kulzer
> Florian |
Output below. Bear in mind that /dev/video0 should be the TV card, /dev/video1
the webcam, at least that is how they are loaded with pre Udev kernels.
ssh 192.168.0.8
Password:
Linux debian 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10 UTC 2006 i686
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Jul 31 20:37:05 2007
djmons@debian:~$ udevinfo -a -p $(udevinfo -q path -n /dev/video0)
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/class/video4linux/video0':
KERNEL=="video0"
SUBSYSTEM=="video4linux"
DRIVER==""
ATTR{exposure}=="0"
ATTR{hue}=="128"
ATTR{contrast}=="54"
ATTR{saturation}=="110"
ATTR{brightness}=="124"
ATTR{sensor}=="OV7620"
ATTR{bridge}=="OV511+"
ATTR{model}=="Generic Camera _no ID_"
ATTR{custom_id}=="0"
ATTR{name}=="OV511 USB Camera"
ATTR{dev}=="81:0"
looking at parent device '/devices/pci0000:00/0000:00:07.2/usb1/1-2':
KERNELS=="1-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{maxchild}=="0"
ATTRS{version}==" 1.00"
ATTRS{devnum}=="3"
ATTRS{speed}=="12"
ATTRS{bMaxPacketSize0}=="8"
ATTRS{bNumConfigurations}=="1"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceClass}=="00"
ATTRS{bcdDevice}=="0100"
ATTRS{idProduct}=="a511"
ATTRS{idVendor}=="05a9"
ATTRS{bMaxPower}=="500mA"
ATTRS{bmAttributes}=="80"
ATTRS{bConfigurationValue}=="1"
ATTRS{bNumInterfaces}==" 1"
looking at parent device '/devices/pci0000:00/0000:00:07.2/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{serial}=="0000:00:07.2"
ATTRS{product}=="UHCI Host Controller"
ATTRS{manufacturer}=="Linux 2.6.17-2-686 uhci_hcd"
ATTRS{maxchild}=="2"
ATTRS{version}==" 1.10"
ATTRS{devnum}=="1"
ATTRS{speed}=="12"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{bNumConfigurations}=="1"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceClass}=="09"
ATTRS{bcdDevice}=="0206"
ATTRS{idProduct}=="0000"
ATTRS{idVendor}=="0000"
ATTRS{bMaxPower}==" 0mA"
ATTRS{bmAttributes}=="e0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bNumInterfaces}==" 1"
looking at parent device '/devices/pci0000:00/0000:00:07.2':
KERNELS=="0000:00:07.2"
SUBSYSTEMS=="pci"
DRIVERS=="uhci_hcd"
ATTRS{modalias}=="pci:v00001106d00003038sv00000925sd00001234bc0Csc03i00"
ATTRS{local_cpus}=="ff"
ATTRS{irq}=="11"
ATTRS{class}=="0x0c0300"
ATTRS{subsystem_device}=="0x1234"
ATTRS{subsystem_vendor}=="0x0925"
ATTRS{device}=="0x3038"
ATTRS{vendor}=="0x1106"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
djmons@debian:~$ udevinfo -a -p $(udevinfo -q path -n /dev/video1)
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/class/video4linux/video1':
KERNEL=="video1"
SUBSYSTEM=="video4linux"
DRIVER==""
ATTR{card}=="10"
ATTR{name}=="BT878 video _Hauppauge _bt878__"
ATTR{dev}=="81:1"
looking at parent device '/devices/pci0000:00/0000:00:0a.0':
KERNELS=="0000:00:0a.0"
SUBSYSTEMS=="pci"
DRIVERS=="bttv"
ATTRS{modalias}=="pci:v0000109Ed0000036Esv00000070sd000013EBbc04sc00i00"
ATTRS{local_cpus}=="ff"
ATTRS{irq}=="10"
ATTRS{class}=="0x040000"
ATTRS{subsystem_device}=="0x13eb"
ATTRS{subsystem_vendor}=="0x0070"
ATTRS{device}=="0x036e"
ATTRS{vendor}=="0x109e"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
I saw that someone with network device problems, and Udev, was able to specify
the devices by name on 2 separate lines, so that Udev always recognised them
by name. I don't know if something similar is possible with my situation with
the TV card, and the webcam.
Thanks for your concern.
Nigel.
Date: Tue, 31 Jul 2007 22:59:30 +0000 (UTC)
From: - Tong - <mlist4suntong@yahoo.com>
To: debian-user@lists.debian.org
Subject: Re: Debian Linux in Chroot
Message-ID: <f8oesi$t8t$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Tue, 31 Jul 2007 08:04:10 -0400, Matthew K Poer wrote:
> My understanding of chroot is extremely limited, right now. I have sear=
ched=20
> around, but can anyone point me to anything specific that they know to =
be a=20
> good tutorial/explanation or how chroot works and what its capabilities=
are?
Check this out:
System Chroot And Debootstrap
http://xpt.sourceforge.net/techdocs/nix/chroot/
HTH
--=20
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
Date: Tue, 31 Jul 2007 19:25:24 -0400
From: "Andrew J. Barr" <andrew.james.barr@gmail.com>
To: "Matthew K Poer" <matthewpoer@gmail.com>
Cc: debian-user@lists.debian.org
Subject: Re: Debian Linux in Chroot
Message-ID: <903e17bb0707311625l303f51c9v2115f601b3cecf81@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 7/31/07, Matthew K Poer <matthewpoer@gmail.com> wrote:
> My understanding of chroot is extremely limited, right now. I have searched
> around, but can anyone point me to anything specific that they know to be a
> good tutorial/explanation or how chroot works and what its capabilities are?
chroot is a system call that causes all descended processes to treat a
directory in the filesystem as the root directory (/). When you do
this to an interactive Bash shell, you then have the ability to launch
programs and do development work, etc. from this chroot.
Debian has good tools for doing this sort of thing--debootstrap and
friends can install a new system (etch, lenny, sid, and more) in a
folder for you, and you can even install an entire 32-bit userland on
a 64-bit system, which is useful for running 32-bit Firefox with stuff
like the non-free Adobe Flash plugin (FYI-if you're going to point out
nspluginwrapper, please also tell me how to make sound with PulseAudio
work in that setup). Then there are tools like schroot (apt-get
install schroot) which can be configured to launch programs from
inside the chroot in one command line, complete with 32-bit uname()
emulation if so desired.
--
Andrew Barr
We matter more than pounds and pence,
your economic theory makes no sense...
Date: Wed, 1 Aug 2007 09:27:50 +1000
From: Keith Bates <keith@new-life.org.au>
To: debian-user@lists.debian.org
Subject: Re: Using Wine to do my Tax (Australia)
Message-ID: <20070801092750.35dac953@yariknow.home>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Tue, 31 Jul 2007 17:04:23 +1000
Keith Bates <keith@new-life.org.au> wrote:
> On Mon, 30 Jul 2007 10:29:20 -0500
> "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net> wrote:
>
> > On 07/30/2007 05:35 AM, Keith Bates wrote:
> > > Hi,
> > >
> > > I wonder if anyone using the Australian Taxation Office's infamous
> > > e-tax package has been able to get it going under wine.
>
> > >
> > > Error saving data: Access violation at address 0055521C in module
> > > 'etax2007.exe'. Read of address 00000008
> > >
> > > I've made sure that every folder and file in my .wine folder has
> > > 777 permissions, but I still get the error.
> > >
> > > I've done a search of both the wine site and the internet but
> > > haven't been able to find a solution.
> > >
> > > Does anyone know how to get the program to work? Or will I have to
> > > comply with the ATO's "Windows only" agenda?
> > >
> > > Thanks!
> > >
> >
> > It partially seems to work for me.
> >
> > I entered a file name and an example TFN on the first screen, and
> > it lets me get into the other screen where I see Michael D'Ascenzo
> > introducing the program. I've visited these pages "Our commitment
> > to you," "Welcome," "Getting around etax" and "Using the navigator
> > in etax."
> >
> > I'm running under this software:
> > Debian 3.1 i386
> > wine 0.0.200503
> > wine-utils 0.0.200503
> >
> > (I'm not Australian.)
> >
> >
> >
> OK Thanks for that Murnia.
>
> I guess that means my configuration might be incorrect in some way.
>
> It looks like I have to either invest some time to fix the problem or
> else find a windows machine. :-(
>
Just a quick update...
I was able to get e-tax running on my wife's computer, also running
debian testing. We must have slightly different versions of wine or
something.
--
God bless you,
Keith Bates
4 Mooloobar St
Narrabri NSW 2390
Phone: 02 67924890
Fax: 02 67925418
www.new-life.org.au
If you don't have a reason to live
JESUS IS THE ANSWER!
Ask him into your life today...
He really does make a difference.
Date: Wed, 1 Aug 2007 01:34:03 +0200
From: "Martin Marcher" <martin.marcher@gmail.com>
To: debian-user <debian-user@lists.debian.org>
Subject: PAM + LDAP and SSH
Message-ID: <db90db6e0707311634t7570bc99ke1730a91da425263@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
and now for everyone else too :)
---------- Forwarded message ----------
From: Martin Marcher <martin.marcher@gmail.com>
Date: Aug 1, 2007 1:33 AM
Subject: Re: PAM + LDAP and SSH
To: Ron Peterson <rpeterso@mtholyoke.edu>
hello,
On 7/31/07, Ron Peterson <rpeterso@mtholyoke.edu> wrote:
> 2007-07-31_12:51:35-0400 Allan Senna Porto <allan.porto@gmail.com>:
> > Hi,
> > Anyone know about problems with /etc/security/access.conf and
> > SSH in Etch?
> > I'm trying to block ldap users to access my servers, but
> > everything that I made don't block user to loggin.
> > If I use this to /etc/pam.d/login and /etc/pam.d/gdm, the
> > user can't loggin.
>
> It would help others to help you to see what you actually did.
this is how i do it:
# ldapsearch -x -LLL -b 'ou=people,dc=example,dc=com'\
'(&(objectClass=sambaSamAccount))' dn host
dn: uid=will.waldo,ou=accounts,ou=people,dc=example,dc=com
host: havanna.example.com
host: kairo.example.com
host: novosibirsk.example.com
# grep filter /etc/pam_ldap.conf
pam_filter |(host=backend.example.com)(host=\*)
hth
martin
--
Martin Marcher
martin.marcher@gmail.com
http://www.mycorners.com
https://www.xing.com/profile/Martin_Marcher
http://www.linkedin.com/in/martinmarcher
http://www.studivz.net/profile.php?ids=9f83ea8c5996b8ec
http://www.amazon.de/gp/registry/wishlist/3KDAGCL2NKOIM/ref=reg_hu-wl_goto-registry/302-4432803-5146435?ie=UTF8&sort=date-added
Date: Wed, 1 Aug 2007 01:40:35 +0200
From: "Martin Marcher" <martin.marcher@gmail.com>
To: debian-user <debian-user@lists.debian.org>
Subject: Re: Swap configuration for 16GB of RAM, 8 cores
Message-ID: <db90db6e0707311640i446410f4jd68f5c3573710641@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
hello,
On 7/31/07, Ron Johnson <ron.l.johnson@cox.net> wrote:
> On 07/31/07 15:18, agenkin@gmail.com wrote:
> > What are the current best practices with regards to swap partitions?
> > Is it
> > better to create one big, or several smaller swap partitions? Is the
> > rule
> > of thumb still RAM*2 for the total size?
i dropped the "rule of thumb" advices for swap long ago. usually i
watch load (uptime), htop and free as closely as possible (let it mail
to you about every 30 minutes the first few weeks) and decide how much
swap you need.
i know these are really basic tools (especially free only reporting
specific points in time) but they are available everywhere and usable
everywhere. once you got used to initially calculating the stats by
hand it's not that bad at all. monitoring software can be added later
on when everything runs stable.
> Create swap *files* instead. See "man mkswap" for the technique.
> Put them on /.
personally I stay with LVM. I found it a lot easier to manage
(probably just being a habit) as it is the _single_ source of storage
for me (as in I try to avoid using other storage techniques as loop
mounting, swap files in this case, yadda yadda as much as possible)
hth
martin
Date: Tue, 31 Jul 2007 20:08:19 -0400
From: Phill Atwood <me@phillatwood.name>
To: debian-user@lists.debian.org
Subject: Re: ntfs mount errors
Message-Id: <1185926899.3585.6.camel@goonyam.goonyam.local>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
> > >
> > > Further to my problem of not being able to automatically mount my
> > > windows xp partition and cd to it as a regular user.
> > >
> > > >from dmesg:
> > >
> > > NTFS driver 2.1.27 [Flags: R/W MODULE].
> > > NTFS volume version 3.1.
> > > NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> > > flags 0x4000 encountered.
> > > NTFS-fs warning (device sda1): load_system_files(): Volume has
> > > unsupported flags set. Will not be able to remount read-write. Run
> > > chkdsk and mount in Windows.
> >
> > ----
> >
> > Hi there,
> >
> > I have no information about what was discussed before, but to me this looks like: Boot into windoze. Click on Start->Execute (don't know how this is exactly called on English windoze) or open a command window (cmd.exe). There, type: chkdsk /f . Tell windoze you want it to check the disk at reboot. Reboot into windoze, and let chkdsk repair the disk. Then reboot into linux and see what happens.
> >
> > Cheers,
> >
> > Stephan
You were right. I did this. I ended up having to use fsutil to force
the partition to be dirty to get windoze to check it. It did. There
were no errors. However, when I rebooted to Linux I still have the same
problem. I can mount the partition, but I can only cd to it as root.
I tried googling the error msg above but not much. Maybe I need to
contact the developers who have written this ntfs support for linux.
How would I go about finding them?
Phill
Date: Tue, 31 Jul 2007 20:15:01 -0400
From: Phill Atwood <me@phillatwood.name>
To: Stephan Hachinger <s.hachinger@gmx.de>
Cc: debian-user@lists.debian.org
Subject: Re: ntfs mount errors
Message-Id: <1185927301.3585.14.camel@goonyam.goonyam.local>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
On Tue, 2007-31-07 at 21:14 +0200, Stephan Hachinger wrote:
> On Tue, 31 Jul 2007 14:26:41 -0400
> Phill Atwood <me@phillatwood.name> wrote:
>
> >
> > Further to my problem of not being able to automatically mount my
> > windows xp partition and cd to it as a regular user.
> >
> > >from dmesg:
> >
> > NTFS driver 2.1.27 [Flags: R/W MODULE].
> > NTFS volume version 3.1.
> > NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> > flags 0x4000 encountered.
> > NTFS-fs warning (device sda1): load_system_files(): Volume has
> > unsupported flags set. Will not be able to remount read-write. Run
> > chkdsk and mount in Windows.
>
> ----
>
> Hi there,
>
> I have no information about what was discussed before, but to me this looks like: Boot into windoze. Click on Start->Execute (don't know how this is exactly called on English windoze) or open a command window (cmd.exe). There, type: chkdsk /f . Tell windoze you want it to check the disk at reboot. Reboot into windoze, and let chkdsk repair the disk. Then reboot into linux and see what happens.
>
> Cheers,
>
> Stephan
Thanks for helping me see what I needed to do. However, it did not
work. I had to use fsutil to force c: drive to be "dirty" so windoze
would check it. Finally it did and there were no errors. Rebooting
into linux and I still have the problem. ie. The windoze partition is
mounted automatically fine, but I can only cd to it if I am root.
Again, my /etc/fstab is:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda1 /windoze ntfs user,auto,ro 0 0
/dev/sda2 / ext3 defaults,errors=remount-ro 0
1
/dev/sda8 /home ext3 defaults 0 2
/dev/sda7 /tmp ext3 defaults 0 2
/dev/sda5 /usr ext3 defaults 0 2
/dev/sda6 /var ext3 defaults 0 2
/dev/sda3 none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
I tried googling the ntfs error msg above but there isn't much.
Perhaps, I should try to contact the developers of this ntfs support for
linux. How would I go about that? Or are there other ideas? I
appreciate the help.
Thanks,
Phill
Date: Tue, 31 Jul 2007 19:16:17 -0500
From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: Debian User List <debian-user@lists.debian.org>
Subject: Re: Disabling Print Screen key
Message-ID: <46AFD0D1.8050701@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 07/31/2007 04:18 PM, Luis Finotti wrote:
> [...]
> On the other hand, I still don't see why the key wasn't disabled by
> the "xmodmap -e" command... Is that a bug??
>
> Thanks again,
>
> Luis
>
>
What about this:
xmodmap -e "keycode 111 = BackSpace"
or
xmodmap -e "keycode 111 ="
End of debian-user-digest Digest V2007 Issue #2075
**************************************************
Received on Tue Jul 31 21:33:44 2007