This is a copy of the message source: Received: from HSNMMI01B02.hsn.alice-dsl.net ([192.168.125.51]) by HSNMST02V06.hsn.alice-dsl.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 25 Jun 2011 08:10:46 +0200 Received: from mx.alice-dsl.de ([192.168.125.56]) by HSNMMI01B02.hsn.alice-dsl.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 25 Jun 2011 08:10:45 +0200 Received: from liszt.debian.org ([82.195.75.100]) by mx.alice-dsl.de with Microsoft SMTPSVC(6.0.3790.3959); Sat, 25 Jun 2011 08:10:45 +0200 Received: from localhost (localhost [127.0.0.1]) by liszt.debian.org (Postfix) with QMQP id 865A613A75DF; Sat, 25 Jun 2011 06:10:43 +0000 (UTC) From: debian-user-digest-requ...@lists.debian.org Subject: debian-user-digest Digest V2011 #1212 X-Loop: debian-user-dig...@lists.debian.org X-Mailing-List: <debian-user-dig...@lists.debian.org> archive/volume2011/1212 List-Id: <debian-user-digest.lists.debian.org> List-Post: <mailto:debian-user@lists.debian.org> List-Help: <mailto:debian-user-digest-requ...@lists.debian.org?subject=help> List-Subscribe: <mailto:debian-user-digest-requ...@lists.debian.org?subject=subscribe> List-Unsubscribe:
<mailto:debian-user-digest-requ...@lists.debian.org?subject=unsubscribe> Precedence: list MIME-Version: 1.0 Content-Type: multipart/digest; boundary="7c39597f207084ebfc442dc57bfa14ab" To: debian-user-dig...@lists.debian.org Reply-To: debian-user@lists.debian.org Message-Id: <20110625061043.865a613a7...@liszt.debian.org> Date: Sat, 25 Jun 2011 06:10:43 +0000 (UTC) Return-Path: bounce-debian-user-digest=ralf.mardorf=alice-dsl....@lists.debian.org X-OriginalArrivalTime: 25 Jun 2011 06:10:45.0855 (UTC) FILETIME=[9F0F16F0:01CC32FE] X-Evolution-Source: pop://ralf.mardorf%40alice-dsl....@in.alice-dsl.net/ --7c39597f207084ebfc442dc57bfa14ab Content-Type: text/plain Date: Sat, 25 Jun 2011 08:11:15 +0200 Subject: No Subject Message-ID: <1308982275.16430.9.camel@debian> Mime-Version: 1.0 From: debian-user-digest Digest Volume 2011 : Issue 1212 Today's Topics: Re: virtualbox cannot see USB anymor [ wolf python london <lyh19901223@gma ] Re: Threading [ Scott Ferguson <prettyfly.productio ] Re: No more GRUB legacy at install t [ consul tores <consultor...@gmail.co ] Re: Ripping CD [ T o n g <mlist4sunt...@yahoo.com> ] Re: No more GRUB legacy at install t [ Scott Ferguson <prettyfly.productio ] Re: Unread bug reports ? [ Scott Ferguson <prettyfly.productio ] Re: Accented chars in filenames issu [ Scott Ferguson <prettyfly.productio ] Re: Accented chars in filenames issu [ Scott Ferguson <prettyfly.productio ] Re: Accented chars in filenames issu [ Scott Ferguson <prettyfly.productio ] Re: virtualbox cannot see USB anymor [ Scott Ferguson <prettyfly.productio ] Re: Accented chars in filenames issu [ Scott Ferguson <prettyfly.productio ] Re: Ripping CD [ Ralf Mardorf <ralf.mardorf@alice-ds ] Re: Accented chars in filenames issu [ William Hopkins <we.hopkins@gmail.c ] Re: Re: posting (was: Threading) [ Andrew McGlashan <andrew.mcglashan@ ] Re: Accented chars in filenames issu [ William Hopkins <we.hopkins@gmail.c ] Re: posting [ Andrew McGlashan <andrew.mcglashan@ ] --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 10:42:47 +0800 From: wolf python london <lyh19901...@gmail.com> To: "H.S." <hs.sa...@gmail.com> Cc: debian-user@lists.debian.org Subject: Re: virtualbox cannot see USB anymore Message-ID: <BANLkTi=4v1sctvwfx4ksgehbxhtwe8i...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Mime-Version: 1.0 On 25 June 2011 09:19, H.S. <hs.sa...@gmail.com> wrote: > Hello. > > I am running an updating Testing box. For some reasons, I had to use > Windows 7 and installed Virtualbox. > > First, I tried the virtualbox-ose from Debian repos until I realized it > does not support USB. Next, I discovered I can install Virtualbox from > Oracle to get USB support (after installing the extensions as well). > That worked quite well. Till I updated my machine several days ago. > > Since that update, I keep getting a message about some USB Node creation > script not being found during boot. The message is something like: > $> /usr/share/virtualbox/VBoxCreateUSBNode.sh not found. > I have this problem too! > However, the file does exist. Looks like virtualbox is trying to run the > script even before the partitions are mounted. So looks like something > changed in udev or something related. In any case, my USB support is now > gone. > but my USB support is fine . I cannot figure it out why at the moment. > Can somebody guide me as to how to fix this or how to get USB support > with stock Debian package (preferable)? > > Thanks. > > -- > > Please reply to this list only. I read this list on its corresponding > newsgroup on gmane.org. Replies sent to my email address are just > filtered to a folder in my mailbox and get periodically deleted without > ever having been read. > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/iu3d27$phv$1...@dough.gmane.org > > -- ________________________ wolf python london(WPL) Do as you soul should do ! ________________________ --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 13:24:01 +1000 From: Scott Ferguson <prettyfly.producti...@gmail.com> To: debian-user@lists.debian.org CC: Ralf Mardorf <ralf.mard...@alice-dsl.net> Subject: Re: Threading Message-ID: <4e0554d1.6030...@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 On 25/06/11 02:38, Celejar wrote: > On Wed, 22 Jun 2011 22:04:24 +1000 > Scott Ferguson <prettyfly.producti...@gmail.com> wrote: > > ... > >> If someone feels the need to subscribe to the "digest" version - which >> is not one "bit" smaller than all the individual messages - it's no > > It's not? Aren't many of the many headers not repeated per each digest > element? > > Celejar Is that a question? If so I "assume" the answer is yes - though I fail to see any relevance to the subject unless the intention is to "flip turtles". Are you asking me to subscribe to both forms in order to provide meaningful metrics? If so to what end? Cheers -- I'm tired of this back-slapping "Isn't humanity neat?" bullsh#t. We're a virus with shoes, okay? That's all we are. ~ Bill Hicks --7c39597f207084ebfc442dc57bfa14ab Date: Fri, 24 Jun 2011 20:31:55 -0700 From: consul tores <consultor...@gmail.com> To: debian-user@lists.debian.org Subject: Re: No more GRUB legacy at install time since wheezy? Message-ID: <banlktimyvdsrpbm-a2o5zqy5ttq4osi...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 2011/6/24 Brian <a...@cityscape.co.uk>: > On Fri 24 Jun 2011 at 21:35:16 +0200, Sven Joachim wrote: > >> Having switched to grub2 recently, I do that as well. =A0But I suspect >> most people will be content with the simpler configuration options >> offered by editing /etc/default/grub and running update-grub. > > That's me! Although I do have a little change made to debian_theme. > > Why is it some people dislike GRUB2? My experience isn't great but it > boots Debian kernels reliably on my machines. Nothing complicated I > admit, and I'm not overfussed about configuring it to display fancy > menus. What basic changes to grub.cfg cannot be made from the files in > /etc? Multibooting: It does not recognize Windows partitions correctly. It becomes crazy with ufs. Some times it recognize the same partition twice. It might has been build to work alone, which is not really necessary. > > As an aside: Is having 'DO NOT EDIT THIS FILE' and making the file > read-only really an invitation to do the opposite? > > --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 03:50:42 +0000 (UTC) From: T o n g <mlist4sunt...@yahoo.com> To: debian-user@lists.debian.org Subject: Re: Ripping CD Message-ID: <iu3lui$ram$1...@dough.gmane.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Mime-Version: 1.0 On Sat, 25 Jun 2011 02:23:45 +0000, T o n g wrote: > I gave asunder a whirl but somehow it always freeze on me. It works fine now -- I shouldn't have messed with the proxy setting. -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/ --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 13:59:49 +1000 From: Scott Ferguson <prettyfly.producti...@gmail.com> To: debian-user@lists.debian.org Subject: Re: No more GRUB legacy at install time since wheezy? Message-ID: <4e055d35....@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 On 25/06/11 06:51, Brian wrote: > On Fri 24 Jun 2011 at 21:35:16 +0200, Sven Joachim wrote: > >> Having switched to grub2 recently, I do that as well. But I suspect >> most people will be content with the simpler configuration options >> offered by editing /etc/default/grub and running update-grub. > > That's me! Although I do have a little change made to debian_theme. > > Why is it some people dislike GRUB2? My experience isn't great but it > boots Debian kernels reliably on my machines. Nothing complicated I > admit, and I'm not overfussed about configuring it to display fancy > menus. What basic changes to grub.cfg cannot be made from the files in > /etc? > > As an aside: Is having 'DO NOT EDIT THIS FILE' and making the file > read-only really an invitation to do the opposite? > > Indeed! - not only is /etc/default/grub the appropriate place to make changes - it's simpler, and it shows respect for the developers taking the time to document it as being the place to make (most) changes. There's even a gui for changing from grub-legacy and grub2 (grub-choose-default)(Squeeze). For the splash screens in grub2 try - gfxboot. For gnome there is a package called startupmanager - which looks interesting (though I don't run gnome). For pure time-wasting distractions try grub-invaders, as a bonus it loads very fast! I agree that there have been some problems with grub2 during upgrades - but for me it's worth it. Grub(legacy) was better than lilo, and grub2 is better than grub-legacy. I look forward to trying pxe from grub2 and grub-coreboot on an old supported mb. Cheers -- I'm tired of this back-slapping "Isn't humanity neat?" bullsh#t. We're a virus with shoes, okay? That's all we are. ~ Bill Hicks --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 14:27:19 +1000 From: Scott Ferguson <prettyfly.producti...@gmail.com> To: debian-user@lists.debian.org Subject: Re: Unread bug reports ? Message-ID: <4e0563a7.7060...@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 On 25/06/11 03:36, Vecu BOSSEUR wrote: > Hi, > > It is ~a week~ or more now that I filed two bug reports. > > - Bug #630237 related to FUSE > ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630237 ) > - Bug #630903 related to FUSECOMPRESS > ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630903 ) > > I wondered if any single people caugth them ! People have responded to your posted bug... > > The one the most interesting to me is the FUSE bug. > > The other one really is not really a problem cauz' there's no solution > : FUSECOMPRESS has always been a bullsh&t ! Please comply with the posting rules - ^ it's not prudishness, it's a legal issue. If you can't control what you post and respect the rules why should any one take the time to help you? NO F*&&%^G swearing in this list. Ok? :-) See:- http://www.debian.org/MailingLists/#codeofconduct > > Have you been stricken by those bugs ? > > Don't hesitate to tell your experience. > > In hope this booster will prove useful. > > Regards, > Valentin > > 1. Daniel Baumann might not work on the project full-time. He does not appear to be paid for his work - so rudeness is not likely to motivate him. Certainly there seems to be a lot of unresolved issues with that particular project. Perhaps, if the issue is truly Debian, (not Ubuntu), and you were to post the particulars here, some one might suggest a solution. 2. The developer may have read and followed your bug report:- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630237 which leads to this:- https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/737457/comments/3 where you say "The problem seem to have disappeared." You also state that you are running Ubuntu "I always use the same ntfs-3g version 1:2010.8.8-0ubuntu1 ." So how is that a Debian problem. 3. Why post to Ubuntu when you say the problem is Debian? Don't make it more confused than it has to be. You contradict yourself and cross-post, which make it more difficult to help you. 4. Your second Debian bug report was responded to by the maintainer (Ritesh Raj Sarraf). The polite thing to do is follow his advice and remain patient. 4. Your failure to observe the established conventions hardly constitutes an emergency on anyone's part. Cheers -- I'm tired of this back-slapping "Isn't humanity neat?" bullsh#t. We're a virus with shoes, okay? That's all we are. ~ Bill Hicks --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 15:11:09 +1000 From: Scott Ferguson <prettyfly.producti...@gmail.com> To: debian-user@lists.debian.org Subject: Re: Accented chars in filenames issue Message-ID: <4e056ded.8030...@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 On 25/06/11 08:05, David Jardine wrote: > $ mkdir newdir; cd newdir > $ touch 'one space' 'and two spaces' > $ for jim in *; do echo $jim; done > and two spaces > one space > > So far, so good, but: > > $ for jim in `ls`; do echo $jim; done > and > two > spaces > one > space I don't understand why you'd use that method. If you do need to use that approach "$jim" might be better (for other uses). Try:- $ ls -Q "and two spaces" "one space" Or if the long route is required :- $ ls -1Q | while read jim; do echo "$jim" ; done "and two spaces" "one space" Cheers -- I'm tired of this back-slapping "Isn't humanity neat?" bullsh#t. We're a virus with shoes, okay? That's all we are. ~ Bill Hicks --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 15:13:29 +1000 From: Scott Ferguson <prettyfly.producti...@gmail.com> To: debian-user@lists.debian.org Subject: Re: Accented chars in filenames issue Message-ID: <4e056e79.2010...@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 On 25/06/11 08:05, David Jardine wrote: > On Sat, Jun 25, 2011 at 01:34:54AM +1000, Scott Ferguson wrote: >> >> [...] >> >> I don't think the "no white spaces" and "no accented characters" "rule" >> is valid in the 21st century. But if some one can put up an >> authoritative, and recent, reason I'll reconsider. >> > > You won't get anything authoritative from me, but I have noticed traps > for the unwary, for example: > > $ mkdir newdir; cd newdir > $ touch 'one space' 'and two spaces' > $ for jim in *; do echo $jim; done > and two spaces > one space > > So far, so good, but: > > $ for jim in `ls`; do echo $jim; done > and > two > spaces > one > space > > which is not what was intended. > > Cheers, > David > > man bash /IFS ??? Cheers -- I'm tired of this back-slapping "Isn't humanity neat?" bullsh#t. We're a virus with shoes, okay? That's all we are. ~ Bill Hicks --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 15:20:13 +1000 From: Scott Ferguson <prettyfly.producti...@gmail.com> To: debian-user@lists.debian.org Subject: Re: Accented chars in filenames issue Message-ID: <4e05700d.3030...@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Mime-Version: 1.0 On 25/06/11 10:16, lee wrote: > Scott Ferguson <prettyfly.producti...@gmail.com> writes: > >> I don't think the "no white spaces" and "no accented characters" >> "rule" is valid in the 21st century. But if some one can put up an >> authoritative, and recent, reason I'll reconsider. > > Since (unfortunately) there isn't anything preventing users from > creating files with names that contain special characters or spaces, you > could say that there isn't such a rule anymore. There is... > > Nonetheless I advise against it, very un-authoritatively of course, > because it can be troublesome to create files with special characters or > spaces in their names. > > To give a silly example, a file named "-rf *" or "rm -rf *" I defy you to create a file with those name ;-p NOTE: I've tried. No point in it just being an untested opinion. > could turn > out to be disastrous. Using other special characters, for example ä, ü, > ö, and ß, can give you trouble when locale settings change and may have > effects that I'm even not aware of. > > It's only common sense not to create file names that are likely to yield > unexpected results. > Agreed - but *as it's not possible* my agreement is worthless. It also belies the point of UTF. Cheers -- I'm tired of this back-slapping "Isn't humanity neat?" bullsh#t. We're a virus with shoes, okay? That's all we are. ~ Bill Hicks --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 15:26:19 +1000 From: Scott Ferguson <prettyfly.producti...@gmail.com> To: debian-user@lists.debian.org Subject: Re: virtualbox cannot see USB anymore Message-ID: <4e05717b.6040...@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 On 25/06/11 11:19, H.S. wrote: > Hello. > > I am running an updating Testing box. For some reasons, I had to use > Windows 7 and installed Virtualbox. > > First, I tried the virtualbox-ose from Debian repos until I realized it > does not support USB. Next, I discovered I can install Virtualbox from > Oracle to get USB support (after installing the extensions as well). > That worked quite well. Till I updated my machine several days ago. > > Since that update, I keep getting a message about some USB Node creation > script not being found during boot. The message is something like: > $> /usr/share/virtualbox/VBoxCreateUSBNode.sh not found. > > However, the file does exist. Looks like virtualbox is trying to run the > script even before the partitions are mounted. So looks like something > changed in udev or something related. In any case, my USB support is now > gone. > > Can somebody guide me as to how to fix this or how to get USB support > with stock Debian package (preferable)? > > Thanks. > Have you installed the latest Guest Additions? If so have you run:- # apt-get update; apt-get upgrade since?? Cheers -- I'm tired of this back-slapping "Isn't humanity neat?" bullsh#t. We're a virus with shoes, okay? That's all we are. ~ Bill Hicks --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 15:36:48 +1000 From: Scott Ferguson <prettyfly.producti...@gmail.com> To: debian-user@lists.debian.org Subject: Re: Accented chars in filenames issue Message-ID: <4e0573f0.40...@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Mime-Version: 1.0 On 25/06/11 11:27, Doug wrote: > On 06/24/2011 08:16 PM, lee wrote: >> Scott Ferguson<prettyfly.producti...@gmail.com> writes: >> <snipped> >> >> > Probably the best reason is if you *ever* share files, or send one to > someone else, he/she is as likely as not not to have the capability of > inputting the accented character. --doug In this case it would require educating Microsoft Windows users (and corrupting my nicely organised and extensive music collection). Which is where the problem came from. I have no problems with either ext3 or ext4 in "creating" filenames with whitespaces and accented characters. Note the screen shot:- http://lists.debian.org/debian-user/2011/06/pngTe0u43cmOF.png - that's a file being transferred from a MS users NTFS drive to mine - I can play the file fine (on their drive) but it won't copy across unless I create a non-UTF file system, or rename it. Dumbing down all song, album, and artist names to remove whitespaces and accented characters is not feasible. There's a difference between Camaleon and Camaleón, and it's a difference Amarok has no trouble with. The whole point of UTF is to be able to deal with extended character sets. Cheers -- I'm tired of this back-slapping "Isn't humanity neat?" bullsh#t. We're a virus with shoes, okay? That's all we are. ~ Bill Hicks --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 07:33:09 +0200 From: Ralf Mardorf <ralf.mard...@alice-dsl.net> To: debian-user@lists.debian.org Subject: Re: Ripping CD Message-ID: <1308979989.16430.8.camel@debian> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 > email message attachment > > -------- Forwarded Message -------- > > From: T o n g <mlist4sunt...@yahoo.com> > > To: debian-user@lists.debian.org > > Subject: Re: Ripping CD > > Date: Sat, 25 Jun 2011 02:23:45 +0000 (UTC) > >=20 > > On Thu, 23 Jun 2011 20:48:13 +0200, Andreas R=C3=B6nnquist wrote: > >=20 > > > asunder is pretty nice for the ripping part of your request (lightwei= ght > > > and GTK-based) > >=20 > > Thanks Andreas,=20 > >=20 > > I gave asunder a whirl but somehow it always freeze on me. I guess it= =20 > > might be because that I'm using an old version, v1.9.3-2 on ubuntu=20 > > maverick. On other Linux I used another CD ripper, but for Debian I unselected installed Asunder and it does rip the CD to .wav ok for my needs. Asunder here is version 2.1-1 from testing. I dunno if it check errors on CDs and I dunno if you can comfortably convert to what ever audio format you like. Since I'm not comfortable with 44.1 KHz @ what bit ever, I don't care much about the quality, when ripping a CD to .wav. Anyway, Asunder does work here. --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 01:53:54 -0400 From: William Hopkins <we.hopk...@gmail.com> To: debian-user@lists.debian.org Subject: Re: Accented chars in filenames issue Message-ID: <20110625055354.GS7152@slimer> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mln0rGgUGuXEqmuI" Content-Disposition: inline Mime-Version: 1.0 --mln0rGgUGuXEqmuI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 06/25/11 at 03:20pm, Scott Ferguson wrote: > On 25/06/11 10:16, lee wrote: > > Scott Ferguson <prettyfly.producti...@gmail.com> writes: > >=20 > >> I don't think the "no white spaces" and "no accented characters" > >> "rule" is valid in the 21st century. But if some one can put up an > >> authoritative, and recent, reason I'll reconsider. > >=20 > > Since (unfortunately) there isn't anything preventing users from > > creating files with names that contain special characters or spaces, you > > could say that there isn't such a rule anymore. >=20 > There is... >=20 > >=20 > > Nonetheless I advise against it, very un-authoritatively of course, > > because it can be troublesome to create files with special characters or > > spaces in their names. > >=20 > > To give a silly example, a file named "-rf *" or "rm -rf *"=20 >=20 > I defy you to create a file with those name ;-p > NOTE: I've tried. No point in it just being an untested opinion. Why wouldn't you be able to? None of those are forbidden characters for fil= enames. ,---------------------------- |liam@slimer:~/safe$ touch ./-rf\ * |liam@slimer:~/safe$ ls |-rf * `--------------------------- --=20 Liam --mln0rGgUGuXEqmuI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: attachment -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk4Fd/IACgkQ44gGVkxWOPS+ZgCgnWnFyS0HXt/5UG6ungcml8nD Ty4AoOi8cvONDRK5lRnW3KQHdYZEic4+ =U7M2 -----END PGP SIGNATURE----- --mln0rGgUGuXEqmuI-- --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 15:54:51 +1000 From: Andrew McGlashan <andrew.mcglas...@affinityvision.com.au> To: debian-user@lists.debian.org Subject: Re: Re: posting (was: Threading) Message-ID: <4e05782b.2020...@affinityvision.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Test reply from link in archive at: http://lists.debian.org/debian-user/2011/06/msg01787.html I want to see if the reply ends up in the thread properly, I think it should as the html link from the online archive is this: <a href="mailto:debian-user@lists.debian.org?In-Reply-To=<8db18074-5ae4-4e07-aac5-c41967b5e...@queernet.org>&Subject=Re:%20Re: posting (was: Threading)">debian-user@lists.debian.org</a> -- Kind Regards AndrewM Andrew McGlashan Broadband Solutions now including VoIP --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 01:56:48 -0400 From: William Hopkins <we.hopk...@gmail.com> To: debian-user@lists.debian.org Subject: Re: Accented chars in filenames issue Message-ID: <20110625055648.GT7152@slimer> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/FJxnyttrH06HRq2" Content-Disposition: inline Mime-Version: 1.0 --/FJxnyttrH06HRq2 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 06/25/11 at 03:36pm, Scott Ferguson wrote: > On 25/06/11 11:27, Doug wrote: > > On 06/24/2011 08:16 PM, lee wrote: > >> Scott Ferguson<prettyfly.producti...@gmail.com> writes: > >> >=20 > <snipped> >=20 > >> > >> > > Probably the best reason is if you *ever* share files, or send one to > > someone else, he/she is as likely as not not to have the capability of > > inputting the accented character. --doug >=20 > In this case it would require educating Microsoft Windows users (and > corrupting my nicely organised and extensive music collection). Which is > where the problem came from. I have no problems with either ext3 or ext4 > in "creating" filenames with whitespaces and accented characters. >=20 > Note the screen shot:- > http://lists.debian.org/debian-user/2011/06/pngTe0u43cmOF.png > - that's a file being transferred from a MS users NTFS drive to mine - > I can play the file fine (on their drive) but it won't copy across > unless I create a non-UTF file system, or rename it. >=20 > Dumbing down all song, album, and artist names to remove whitespaces and > accented characters is not feasible. There's a difference between > Camaleon and Camale=F3n, and it's a difference Amarok has no trouble with. >=20 > The whole point of UTF is to be able to deal with extended character sets. Maybe you should reply to one of the troubleshooting responses instead of t= he philosophical ones, then :P What happens when you try touch touch a file with a special character? Any error message? Have you tried mounting with the encoding options as recomme= nded elsewhere?=20 --=20 Liam --/FJxnyttrH06HRq2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: attachment -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk4FeKAACgkQ44gGVkxWOPSGKACgyms6NZyDWDpbz9anT75NYkuq QOUAoNSikc4Y9EsUridYZHh64Lb6Ws7w =hc69 -----END PGP SIGNATURE----- --/FJxnyttrH06HRq2-- --7c39597f207084ebfc442dc57bfa14ab Date: Sat, 25 Jun 2011 15:57:54 +1000 From: Andrew McGlashan <andrew.mcglas...@affinityvision.com.au> To: "Roger B.A. Klorese" <rog...@queernet.org> CC: lee <l...@yun.yagibdah.de>, debian-user@lists.debian.org Subject: Re: posting Message-ID: <4e0578e2.90...@affinityvision.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Roger B.A. Klorese wrote: > On Jun 22, 2011, at 7:01 AM, lee wrote: > >> Hm, I wonder why anyone is going to the lengths of replying to digest >> messages rather than just subscribing to the list ... > > > So they don't need to get hundreds of separate messages?! Most people don't treat a digest as separate from a list, just an alternate subscription format. > > It's incumbent on those who own the technology to evolve digests so it's easier to reply to individual posts, not on readers to jump through hoops to reply. The answer to this problem, replying to digests, is to go to the web source [1] and do a reply from there. I expect it will keep the threading working properly. Can somebody send me a full digest message, so I can see what is tacked onto the end of the message? Send as an attachment please so that I can see headers as well. The link below is one from the individual emails that I receive and the one I am replying to. [1] Archive: http://lists.debian.org/debian-user/2011/06/msg01787.html -- Kind Regards AndrewM Andrew McGlashan Broadband Solutions now including VoIP --7c39597f207084ebfc442dc57bfa14ab-- End of debian-user-digest Digest V2011 Issue #1212 ************************************************** -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1308985409.17986.1.camel@debian
