RE: [Samba] Filename problem (filenames containing slashes aka.\and /)
We _cannot_ go about renaming files, for a number of reasons.. the primary being some of the files are technically not ours to alter without a clients permission (names and all) and you don't understand just how many files there are. There are quite probably thousands of files, spread across _hundreds_ of cds and dvds which comes to a total of roughly 400GB. As to a Mac server, i'm not sure how much they cost but i'm guessing a lot for what i'm wanting. I'm planning on building a RAID-5 fileserver running Linux (still undecided on distro) most likely running Netatalk and Samba. The server itself i'm planning for roughly 1TB of storage, possibly more. (at the moment in my plans it calls for 6x 250GB hdd's which gives me 1.2TB) The cost of the above if I use Linux (and build it myself) comes to roughly £1000, which i'm guessing is a damn sight cheaper than a Mac equivalent server solution. (hell that's cheaper than a normal Mac tower) Mark -Original Message- From: Craig White [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 18:45 To: Mark C. Casey Subject: RE: [Samba] Filename problem (filenames containing slashes aka.\and /) On Tue, 2004-09-21 at 09:03, Mark C. Casey wrote: I've since got it partially working with Netatalk. I can access it on OS 9 machines but not OS 10 for some reason. For example, I created a directory called test / sedrs \ sfg and according to ls the actual filename under linux is test :2f sedrs \ sfg. So, it displays great on the Mac. So i'm sortof halfway there since the OS 10 machines cannot access the netatalk share. :D Still, I would prefer if there was a way to do this using Samba 3 instead. I have netatalk working with both OS9 OSX clients and you should be able to as well - new version RC2 released yesterday - but this is beside the subject of samba There fact that Macintosh permits usage of characters not normally permitted in other operating systems is a liability for Macintosh and the indifference to others naming rules (not only characters such as ?/\ but also ending a name with a space or a period) is to the Macintosh users detriment. I have subjected several of my clients to the 'new rules' and run wholesale name cleanup on their existing files as it's more important to play nicely with others than it is to unthinkingly persist in Macintosh ignorance. The benefit is that with names that have been cleaned up and legal means that I can use various Unix/Linux/Windows utilities to backup/find/grep/index/tar etc. - not just Macintosh centric software on Macintosh computers. Craig -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Filename problem (filenames containing slashes aka.\and /)
Mark C. Casey wrote: We _cannot_ go about renaming files, for a number of reasons.. the primary being some of the files are technically not ours to alter without a clients permission (names and all) and you don't understand just how many files there are. There are quite probably thousands of files, spread across _hundreds_ of cds and dvds which comes to a total of roughly 400GB. I understand what you are saying, but it doesn't change the situation - that no-one has a 'solution' for you. Perhaps there is some 'middle ground' you can explore (see below). As to a Mac server, i'm not sure how much they cost but i'm guessing a lot for what i'm wanting. I'm planning on building a RAID-5 fileserver running Linux (still undecided on distro) most likely running Netatalk and Samba. The server itself i'm planning for roughly 1TB of storage, possibly more. (at the moment in my plans it calls for 6x 250GB hdd's which gives me 1.2TB) The cost of the above if I use Linux (and build it myself) comes to roughly £1000, which i'm guessing is a damn sight cheaper than a Mac equivalent server solution. (hell that's cheaper than a normal Mac tower) You are right that a Mac server will cost more than your home-brew Linux box. FWIW, I recently had to decide how to equip our Design department with their own fileserver. I decided to put in a G5 XServe so that OS X could take care of any file name mangling required (Samba is an integral service with OS X Server). When I get time the plan is to integrate it with the LDAP database from the main fileserver. I also felt it was 'safer' given that Netatalk still has issues (not least that it stores files differently to OS X via Samba) and they still have OS 9 machines which don't natively talk to Samba servers. To be perfectly honest, the price wasn't all that much more than buying a rack mount Dell server - especially taking all the 'incidental' costs (how much will it cost you to fix your filenames ?) into account. BTW, you haven't said how many users, you might find that you can 'liberate' a G4 that's due for an upgrade from someones desk, stick on OS X Server 10 user, and have an adequate server (400G isn't much BTW - our XServe has 500G of space available on raid 5 (3x250G disks) and I expect to have to switch to an external XRaid in a year or two when we run out of capacity.) So where can you go from here ? Well the obvious (but not very helpful) response is not to start from here ! Going forward you must educate your designers to avoid all characters that have any issues with cross platform compatibility - it is the only long term solution. For existing work, do you really, absolutely, HAVE to put it all on the server ? For stuff that's spread across _hundreds_ of cds and dvds just leave it there until you have to do some work on it, and fix the problems as you come to them. As to stuff that you'd need a clients permission to alter, well go and ask them ! Many of your clients are probably having the same issues and wishing they could change the names but they can't because the designers did it that way and are afraid to ask you to change them. Combine that with only fixing stuff when you have to change anything (ie when a client comes back for some changes, get permission to sort the filenames) and I think you'll find that the scale of the problem is reduced significantly. Simon -- Simon Hobson MA MIEE, Technology Specialist Colony Gift Corporation Limited Lindal in Furness, Ulverston, Cumbria, LA12 0LD Tel 01229 461100, Fax 01229 461101 Registered in England No. 1499611 Regd. Office : 100 New Bridge Street, London, EC4V 6JA. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Filename problem (filenames containing slashes aka.\and /)
Hi, i total agree with you, using a mac server, or and educate the users will be the only solution which will work now and in the future. If it such important to store this ugly named stuff on a fileserver costs will rise for sure, but costs shouldnt be the main problem if you plan to setup a long term staying fileserver. Regards Simon Hobson schrieb: Mark C. Casey wrote: We _cannot_ go about renaming files, for a number of reasons.. the primary being some of the files are technically not ours to alter without a clients permission (names and all) and you don't understand just how many files there are. There are quite probably thousands of files, spread across _hundreds_ of cds and dvds which comes to a total of roughly 400GB. I understand what you are saying, but it doesn't change the situation - that no-one has a 'solution' for you. Perhaps there is some 'middle ground' you can explore (see below). As to a Mac server, i'm not sure how much they cost but i'm guessing a lot for what i'm wanting. I'm planning on building a RAID-5 fileserver running Linux (still undecided on distro) most likely running Netatalk and Samba. The server itself i'm planning for roughly 1TB of storage, possibly more. (at the moment in my plans it calls for 6x 250GB hdd's which gives me 1.2TB) The cost of the above if I use Linux (and build it myself) comes to roughly £1000, which i'm guessing is a damn sight cheaper than a Mac equivalent server solution. (hell that's cheaper than a normal Mac tower) You are right that a Mac server will cost more than your home-brew Linux box. FWIW, I recently had to decide how to equip our Design department with their own fileserver. I decided to put in a G5 XServe so that OS X could take care of any file name mangling required (Samba is an integral service with OS X Server). When I get time the plan is to integrate it with the LDAP database from the main fileserver. I also felt it was 'safer' given that Netatalk still has issues (not least that it stores files differently to OS X via Samba) and they still have OS 9 machines which don't natively talk to Samba servers. To be perfectly honest, the price wasn't all that much more than buying a rack mount Dell server - especially taking all the 'incidental' costs (how much will it cost you to fix your filenames ?) into account. BTW, you haven't said how many users, you might find that you can 'liberate' a G4 that's due for an upgrade from someones desk, stick on OS X Server 10 user, and have an adequate server (400G isn't much BTW - our XServe has 500G of space available on raid 5 (3x250G disks) and I expect to have to switch to an external XRaid in a year or two when we run out of capacity.) So where can you go from here ? Well the obvious (but not very helpful) response is not to start from here ! Going forward you must educate your designers to avoid all characters that have any issues with cross platform compatibility - it is the only long term solution. For existing work, do you really, absolutely, HAVE to put it all on the server ? For stuff that's spread across _hundreds_ of cds and dvds just leave it there until you have to do some work on it, and fix the problems as you come to them. As to stuff that you'd need a clients permission to alter, well go and ask them ! Many of your clients are probably having the same issues and wishing they could change the names but they can't because the designers did it that way and are afraid to ask you to change them. Combine that with only fixing stuff when you have to change anything (ie when a client comes back for some changes, get permission to sort the filenames) and I think you'll find that the scale of the problem is reduced significantly. Simon -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Filename problem (filenames containing slashes aka.\and /)
I've now got Netatalk working flawlessly with OS 10. (hurray!) What I now plan to do is for a monthly backup of the raid server to tar gzip (to ensure filenames and permissions are kept) the entire archive then write it to tapes or dvds. I can simply use samba so I can access the tar.gz file to write to multiple tapes or dvds. Thanks for all the help Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of rruegner Sent: 22 September 2004 10:10 To: Simon Hobson Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka.\and /) Hi, i total agree with you, using a mac server, or and educate the users will be the only solution which will work now and in the future. If it such important to store this ugly named stuff on a fileserver costs will rise for sure, but costs shouldnt be the main problem if you plan to setup a long term staying fileserver. Regards Simon Hobson schrieb: Mark C. Casey wrote: We _cannot_ go about renaming files, for a number of reasons.. the primary being some of the files are technically not ours to alter without a clients permission (names and all) and you don't understand just how many files there are. There are quite probably thousands of files, spread across _hundreds_ of cds and dvds which comes to a total of roughly 400GB. I understand what you are saying, but it doesn't change the situation - that no-one has a 'solution' for you. Perhaps there is some 'middle ground' you can explore (see below). As to a Mac server, i'm not sure how much they cost but i'm guessing a lot for what i'm wanting. I'm planning on building a RAID-5 fileserver running Linux (still undecided on distro) most likely running Netatalk and Samba. The server itself i'm planning for roughly 1TB of storage, possibly more. (at the moment in my plans it calls for 6x 250GB hdd's which gives me 1.2TB) The cost of the above if I use Linux (and build it myself) comes to roughly £1000, which i'm guessing is a damn sight cheaper than a Mac equivalent server solution. (hell that's cheaper than a normal Mac tower) You are right that a Mac server will cost more than your home-brew Linux box. FWIW, I recently had to decide how to equip our Design department with their own fileserver. I decided to put in a G5 XServe so that OS X could take care of any file name mangling required (Samba is an integral service with OS X Server). When I get time the plan is to integrate it with the LDAP database from the main fileserver. I also felt it was 'safer' given that Netatalk still has issues (not least that it stores files differently to OS X via Samba) and they still have OS 9 machines which don't natively talk to Samba servers. To be perfectly honest, the price wasn't all that much more than buying a rack mount Dell server - especially taking all the 'incidental' costs (how much will it cost you to fix your filenames ?) into account. BTW, you haven't said how many users, you might find that you can 'liberate' a G4 that's due for an upgrade from someones desk, stick on OS X Server 10 user, and have an adequate server (400G isn't much BTW - our XServe has 500G of space available on raid 5 (3x250G disks) and I expect to have to switch to an external XRaid in a year or two when we run out of capacity.) So where can you go from here ? Well the obvious (but not very helpful) response is not to start from here ! Going forward you must educate your designers to avoid all characters that have any issues with cross platform compatibility - it is the only long term solution. For existing work, do you really, absolutely, HAVE to put it all on the server ? For stuff that's spread across _hundreds_ of cds and dvds just leave it there until you have to do some work on it, and fix the problems as you come to them. As to stuff that you'd need a clients permission to alter, well go and ask them ! Many of your clients are probably having the same issues and wishing they could change the names but they can't because the designers did it that way and are afraid to ask you to change them. Combine that with only fixing stuff when you have to change anything (ie when a client comes back for some changes, get permission to sort the filenames) and I think you'll find that the scale of the problem is reduced significantly. Simon -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Filename problem (filenames containing slashes aka. \ and /)
I'm currently in the process of creating a fileserver so some mac guys at the company I work at can save files as a backup medium. (long story short i'm creating a fileserver running samba 3 with 1TB of storage) However, a lot of the files that they want backed up contain characters that samba refuses to accept (when I try transferring a file to the samba share with say the filename as test \ test / test the mac reports that it cannot transfer the file. I've been told there is a way to use UTF8 with Samba 3 so it can accept these, how can I do this? Mark -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Filename problem (filenames containing slashes aka. \ and /)
Hi Mark, as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Regards Mark C. Casey schrieb: I'm currently in the process of creating a fileserver so some mac guys at the company I work at can save files as a backup medium. (long story short i'm creating a fileserver running samba 3 with 1TB of storage) However, a lot of the files that they want backed up contain characters that samba refuses to accept (when I try transferring a file to the samba share with say the filename as test \ test / test the mac reports that it cannot transfer the file. I've been told there is a way to use UTF8 with Samba 3 so it can accept these, how can I do this? Mark -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Filename problem (filenames containing slashes aka. \ and /)
Unfortunately this is something that is extremely important. There are LOTS of filenames which contain slashes. Some of these are also customer artwork, meaning we cannot go about renaming them either. Mark -Original Message- From: rruegner [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 14:50 To: Mark C. Casey Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \ and /) Hi Mark, as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Regards Mark C. Casey schrieb: I'm currently in the process of creating a fileserver so some mac guys at the company I work at can save files as a backup medium. (long story short i'm creating a fileserver running samba 3 with 1TB of storage) However, a lot of the files that they want backed up contain characters that samba refuses to accept (when I try transferring a file to the samba share with say the filename as test \ test / test the mac reports that it cannot transfer the file. I've been told there is a way to use UTF8 with Samba 3 so it can accept these, how can I do this? Mark -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Filename problem (filenames containing slashes aka. \ and /)
rruegner wrote: as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Except that the Mac uses neither (internally it uses ':' as a path element separator) and both are valid for use in filenames (as are ?, *, -, and a whole pile more). So in the context of the original query, there is no element bug in user brain - the users have simply been using what the OS allows. Interestingly, with OS X if I create a folder called Test/Folder, in a terminal shell ls shows it as Test:Folder. Simon PS - and no this isn't an attempt to start a my OS is better than yours war ! -- Simon Hobson MA MIEE, Technology Specialist Colony Gift Corporation Limited Lindal in Furness, Ulverston, Cumbria, LA12 0LD Tel 01229 461100, Fax 01229 461101 Registered in England No. 1499611 Regd. Office : 100 New Bridge Street, London, EC4V 6JA. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Filename problem (filenames containing slashes aka. \and /)
I'm still looking but is it possible to use mangled maps? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Simon Hobson Sent: 21 September 2004 15:10 To: [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \and /) rruegner wrote: as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Except that the Mac uses neither (internally it uses ':' as a path element separator) and both are valid for use in filenames (as are ?, *, -, and a whole pile more). So in the context of the original query, there is no element bug in user brain - the users have simply been using what the OS allows. Interestingly, with OS X if I create a folder called Test/Folder, in a terminal shell ls shows it as Test:Folder. Simon PS - and no this isn't an attempt to start a my OS is better than yours war ! -- Simon Hobson MA MIEE, Technology Specialist Colony Gift Corporation Limited Lindal in Furness, Ulverston, Cumbria, LA12 0LD Tel 01229 461100, Fax 01229 461101 Registered in England No. 1499611 Regd. Office : 100 New Bridge Street, London, EC4V 6JA. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Filename problem (filenames containing slashes aka. \ and /)
Hi Mark, i had this problems too, when i worked with some grafics , i wrote a bash script which renamed there special filenames every day. Maybe a guru has an solution for you , but in case of /\ i dont know any Regards Mark C. Casey schrieb: Unfortunately this is something that is extremely important. There are LOTS of filenames which contain slashes. Some of these are also customer artwork, meaning we cannot go about renaming them either. Mark -Original Message- From: rruegner [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 14:50 To: Mark C. Casey Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \ and /) Hi Mark, as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Regards Mark C. Casey schrieb: I'm currently in the process of creating a fileserver so some mac guys at the company I work at can save files as a backup medium. (long story short i'm creating a fileserver running samba 3 with 1TB of storage) However, a lot of the files that they want backed up contain characters that samba refuses to accept (when I try transferring a file to the samba share with say the filename as test \ test / test the mac reports that it cannot transfer the file. I've been told there is a way to use UTF8 with Samba 3 so it can accept these, how can I do this? Mark -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Filename problem (filenames containing slashes aka. \ and /)
Sorry Simon, for sure the users does what their os allows them to do, but that musnt be named as inteligent in anyway. Building filenames which are not compatibel between varias oses is simply brainbugged, in my proffesional setups, i never gave support to users which worked so.My oppinion is , thats simply their problem. If i would know a solution, i would work it out ,but i dont know a solution which will help out with creating filesnames in any case, so the simple advice not to do so, seems to me the best way, until some wonder may come . Regards Simon Hobson schrieb: rruegner wrote: as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Except that the Mac uses neither (internally it uses ':' as a path element separator) and both are valid for use in filenames (as are ?, *, -, and a whole pile more). So in the context of the original query, there is no element bug in user brain - the users have simply been using what the OS allows. Interestingly, with OS X if I create a folder called Test/Folder, in a terminal shell ls shows it as Test:Folder. Simon PS - and no this isn't an attempt to start a my OS is better than yours war ! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Filename problem (filenames containing slashes aka. \and /)
I've since got it partially working with Netatalk. I can access it on OS 9 machines but not OS 10 for some reason. For example, I created a directory called test / sedrs \ sfg and according to ls the actual filename under linux is test :2f sedrs \ sfg. So, it displays great on the Mac. So i'm sortof halfway there since the OS 10 machines cannot access the netatalk share. :D Still, I would prefer if there was a way to do this using Samba 3 instead. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of rruegner Sent: 21 September 2004 16:53 To: Simon Hobson Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \and /) Sorry Simon, for sure the users does what their os allows them to do, but that musnt be named as inteligent in anyway. Building filenames which are not compatibel between varias oses is simply brainbugged, in my proffesional setups, i never gave support to users which worked so.My oppinion is , thats simply their problem. If i would know a solution, i would work it out ,but i dont know a solution which will help out with creating filesnames in any case, so the simple advice not to do so, seems to me the best way, until some wonder may come . Regards Simon Hobson schrieb: rruegner wrote: as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Except that the Mac uses neither (internally it uses ':' as a path element separator) and both are valid for use in filenames (as are ?, *, -, and a whole pile more). So in the context of the original query, there is no element bug in user brain - the users have simply been using what the OS allows. Interestingly, with OS X if I create a folder called Test/Folder, in a terminal shell ls shows it as Test:Folder. Simon PS - and no this isn't an attempt to start a my OS is better than yours war ! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Filename problem (filenames containing slashes aka. \ and /)
Hi Mark, as thought about your problem did you try nfs or ssh for this file types, as your users use mac os 10 this maybe a possible solution, but i am nearly sure that windows will fail to open it , if your try to catch them afterwards from a win client. but perhaps its a workaround Regards rruegner schrieb: Hi Mark, i had this problems too, when i worked with some grafics , i wrote a bash script which renamed there special filenames every day. Maybe a guru has an solution for you , but in case of /\ i dont know any Regards Mark C. Casey schrieb: Unfortunately this is something that is extremely important. There are LOTS of filenames which contain slashes. Some of these are also customer artwork, meaning we cannot go about renaming them either. Mark -Original Message- From: rruegner [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 14:50 To: Mark C. Casey Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \ and /) Hi Mark, as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Regards Mark C. Casey schrieb: I'm currently in the process of creating a fileserver so some mac guys at the company I work at can save files as a backup medium. (long story short i'm creating a fileserver running samba 3 with 1TB of storage) However, a lot of the files that they want backed up contain characters that samba refuses to accept (when I try transferring a file to the samba share with say the filename as test \ test / test the mac reports that it cannot transfer the file. I've been told there is a way to use UTF8 with Samba 3 so it can accept these, how can I do this? Mark -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Filename problem (filenames containing slashes aka. \ and /)
They use a mixture of OS 9.x (primary Mac OS they use) and 10.x. So NFS is probably out of the question. Mark -Original Message- From: rruegner [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 17:04 To: rruegner Cc: Mark C. Casey; [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \ and /) Hi Mark, as thought about your problem did you try nfs or ssh for this file types, as your users use mac os 10 this maybe a possible solution, but i am nearly sure that windows will fail to open it , if your try to catch them afterwards from a win client. but perhaps its a workaround Regards rruegner schrieb: Hi Mark, i had this problems too, when i worked with some grafics , i wrote a bash script which renamed there special filenames every day. Maybe a guru has an solution for you , but in case of /\ i dont know any Regards Mark C. Casey schrieb: Unfortunately this is something that is extremely important. There are LOTS of filenames which contain slashes. Some of these are also customer artwork, meaning we cannot go about renaming them either. Mark -Original Message- From: rruegner [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 14:50 To: Mark C. Casey Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \ and /) Hi Mark, as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Regards Mark C. Casey schrieb: I'm currently in the process of creating a fileserver so some mac guys at the company I work at can save files as a backup medium. (long story short i'm creating a fileserver running samba 3 with 1TB of storage) However, a lot of the files that they want backed up contain characters that samba refuses to accept (when I try transferring a file to the samba share with say the filename as test \ test / test the mac reports that it cannot transfer the file. I've been told there is a way to use UTF8 with Samba 3 so it can accept these, how can I do this? Mark -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Filename problem (filenames containing slashes aka. \and /)
If I can add more to that... It needs to be accessible from both OS 9.x, 10.x and possibly (maybe) from Windows. So, for me Samba seems like the best option since all three can access Samba. Netatalk seems to have the most elegant solution of file naming but that isn't accessible from Windows unless I have both Netatalk and Samba running on the same machine sharing the same directory. (which I currently do) I guess you need to see my other post to understand. The whole test / sedrs \ sfg and test :2f sedrs \ sfg thing. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark C. Casey Sent: 21 September 2004 17:10 To: rruegner Cc: [EMAIL PROTECTED] Subject: RE: [Samba] Filename problem (filenames containing slashes aka. \and /) They use a mixture of OS 9.x (primary Mac OS they use) and 10.x. So NFS is probably out of the question. Mark -Original Message- From: rruegner [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 17:04 To: rruegner Cc: Mark C. Casey; [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \ and /) Hi Mark, as thought about your problem did you try nfs or ssh for this file types, as your users use mac os 10 this maybe a possible solution, but i am nearly sure that windows will fail to open it , if your try to catch them afterwards from a win client. but perhaps its a workaround Regards rruegner schrieb: Hi Mark, i had this problems too, when i worked with some grafics , i wrote a bash script which renamed there special filenames every day. Maybe a guru has an solution for you , but in case of /\ i dont know any Regards Mark C. Casey schrieb: Unfortunately this is something that is extremely important. There are LOTS of filenames which contain slashes. Some of these are also customer artwork, meaning we cannot go about renaming them either. Mark -Original Message- From: rruegner [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 14:50 To: Mark C. Casey Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \ and /) Hi Mark, as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Regards Mark C. Casey schrieb: I'm currently in the process of creating a fileserver so some mac guys at the company I work at can save files as a backup medium. (long story short i'm creating a fileserver running samba 3 with 1TB of storage) However, a lot of the files that they want backed up contain characters that samba refuses to accept (when I try transferring a file to the samba share with say the filename as test \ test / test the mac reports that it cannot transfer the file. I've been told there is a way to use UTF8 with Samba 3 so it can accept these, how can I do this? Mark -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Filename problem (filenames containing slashes aka. \and /)
Hi Mark , what about a using a mac server, this should solve your problems and you should be able to compile samba 3 on mac os 10 too Regards Mark C. Casey schrieb: If I can add more to that... It needs to be accessible from both OS 9.x, 10.x and possibly (maybe) from Windows. So, for me Samba seems like the best option since all three can access Samba. Netatalk seems to have the most elegant solution of file naming but that isn't accessible from Windows unless I have both Netatalk and Samba running on the same machine sharing the same directory. (which I currently do) I guess you need to see my other post to understand. The whole test / sedrs \ sfg and test :2f sedrs \ sfg thing. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark C. Casey Sent: 21 September 2004 17:10 To: rruegner Cc: [EMAIL PROTECTED] Subject: RE: [Samba] Filename problem (filenames containing slashes aka. \and /) They use a mixture of OS 9.x (primary Mac OS they use) and 10.x. So NFS is probably out of the question. Mark -Original Message- From: rruegner [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 17:04 To: rruegner Cc: Mark C. Casey; [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \ and /) Hi Mark, as thought about your problem did you try nfs or ssh for this file types, as your users use mac os 10 this maybe a possible solution, but i am nearly sure that windows will fail to open it , if your try to catch them afterwards from a win client. but perhaps its a workaround Regards rruegner schrieb: Hi Mark, i had this problems too, when i worked with some grafics , i wrote a bash script which renamed there special filenames every day. Maybe a guru has an solution for you , but in case of /\ i dont know any Regards Mark C. Casey schrieb: Unfortunately this is something that is extremely important. There are LOTS of filenames which contain slashes. Some of these are also customer artwork, meaning we cannot go about renaming them either. Mark -Original Message- From: rruegner [mailto:[EMAIL PROTECTED] Sent: 21 September 2004 14:50 To: Mark C. Casey Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Filename problem (filenames containing slashes aka. \ and /) Hi Mark, as far i know, \ / are interpreted as path signs, i am not clear why any software should interpret this in another way. using special signs as filenames are a bug in user brain not in the software of fileservers, whatever you use Regards Mark C. Casey schrieb: I'm currently in the process of creating a fileserver so some mac guys at the company I work at can save files as a backup medium. (long story short i'm creating a fileserver running samba 3 with 1TB of storage) However, a lot of the files that they want backed up contain characters that samba refuses to accept (when I try transferring a file to the samba share with say the filename as test \ test / test the mac reports that it cannot transfer the file. I've been told there is a way to use UTF8 with Samba 3 so it can accept these, how can I do this? Mark -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] filename problem
On Fri, 2002-11-15 at 22:58, Mirek Hankus wrote: I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with character, example: user on server (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Yes, we have some problems in this area - because of our use of DOS codepages in Samba 3.0, this kind of thing happens. I'm told that if you don't specify any codepage settings at all, then it shouldn't munge the path, but I'm not sure. I would try again with Samba 3.0 (currently in alpha), with the default settings. In that case we *should* be correctly translating unicode-on-the-wire to utf8 on the disk, and avoid some of these problems. (Existing files may still be 'broken', but new files will be created in utf8). Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net signature.asc Description: This is a digitally signed message part
[Samba] filename problem
I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with character, example: user on server (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Regards Mirek smime.p7s Description: S/MIME Cryptographic Signature
RE: [Samba] filename problem
correct me if i am wrong but is no allowed character within a filename under windows hope that helps bernd I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with character, example: user on server (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Regards Mirek -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] filename problem
Problem is that Windows creates such file automatically. Steps to create such file. 1. mount your home directory under h: 2. open "my computer" and drag h: drive to your desktop. 3. now you have file with " character, which can be copied to samba, but not from samba to windows. Mirek Bernd Wölfel wrote: correct me if i am wrong but " is no allowed character within a filename under windows hope that helps bernd I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with " character, example: user on "server" (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Regards Mirek smime.p7s Description: S/MIME Cryptographic Signature
RE: [Samba] filename problem
strange... just tried it with servers win2k,samba 2.2.3a, samba 2.2.6 and clients 2kpro sp3, xp sp1 (all german edition) under my computer I see the natwork drive as blabla on server xyz(z) but as soon as i drag the share to the desktop the charcters are automagically removed my smb.conf says character set = ISO8859-15 (but I think this has nothing to do with the problem) which client operating system are you using? bernd Problem is that Windows creates such file automatically. Steps to create such file. 1. mount your home directory under h: 2. open my computer and drag h: drive to your desktop. 3. now you have file with character, which can be copied to samba, but not from samba to windows. Mirek Bernd Wölfel wrote: correct me if i am wrong but is no allowed character within a filename under windows hope that helps bernd I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with character, example: user on server (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Regards Mirek -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] filename problem
strange... just tried it with servers win2k,samba 2.2.3a, samba 2.2.6 and clients 2kpro sp3, xp sp1 (all german edition) under my computer I see the natwork drive as blabla on server xyz(z) but as soon as i drag the share to the desktop the charcters are automagically removed my smb.conf says character set = ISO8859-15 (but I think this has nothing to do with the problem) which client operating system are you using? bernd Problem is that Windows creates such file automatically. Steps to create such file. 1. mount your home directory under h: 2. open my computer and drag h: drive to your desktop. 3. now you have file with character, which can be copied to samba, but not from samba to windows. Mirek Bernd Wölfel wrote: correct me if i am wrong but is no allowed character within a filename under windows hope that helps bernd I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with character, example: user on server (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Regards Mirek -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] filename problem
On Win2k sp3 Polish and XP Polish " are preserved when dragging drive to desktop, so I've got big problem. Have you tried to create a file with " on server (directly in shell), and see how client see it ??? Mirek Bernd Wlfel wrote: strange... just tried it with servers win2k,samba 2.2.3a, samba 2.2.6 and clients 2kpro sp3, xp sp1 (all german edition) under my computer I see the natwork drive as "blabla" on server xyz(z) but as soon as i drag the share to the desktop the " charcters are automagically removed my smb.conf says character set = ISO8859-15 (but I think this has nothing to do with the problem) which client operating system are you using? bernd Problem is that Windows creates such file automatically. Steps to create such file. 1. mount your home directory under h: 2. open "my computer" and drag h: drive to your desktop. 3. now you have file with " character, which can be copied to samba, but not from samba to windows. Mirek Bernd Wlfel wrote: correct me if i am wrong but " is no allowed character within a filename under windows hope that helps bernd I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with " character, example: user on "server" (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Regards Mirek
RE: [Samba] filename problem
alright.. just tried it with 2.2.3a and 2.2.6 i created a file test.txt with vi \test\.txt, the file shows up correctly within the shell as test.txt when i look under windows (2k sp3 and xp sp1 both german) the file shows up as TEST~AO.TXT same on samba 2.2.3a and 2.2.6 (see the filename is converted to uppercase?!) could still be your characterset or your codepage could you comment both lines out just for testing? On Win2k sp3 Polish and XP Polish are preserved when dragging drive to desktop, so I've got big problem. Have you tried to create a file with on server (directly in shell), and see how client see it ??? Mirek Bernd Wölfel wrote: strange... just tried it with servers win2k,samba 2.2.3a, samba 2.2.6 and clients 2kpro sp3, xp sp1 (all german edition) under my computer I see the natwork drive as blabla on server xyz(z) but as soon as i drag the share to the desktop the charcters are automagically removed my smb.conf says character set = ISO8859-15 (but I think this has nothing to do with the problem) which client operating system are you using? bernd Problem is that Windows creates such file automatically. Steps to create such file. 1. mount your home directory under h: 2. open my computer and drag h: drive to your desktop. 3. now you have file with character, which can be copied to samba, but not from samba to windows. Mirek Bernd Wölfel wrote: correct me if i am wrong but is no allowed character within a filename under windows hope that helps bernd I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with character, example: user on server (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Regards Mirek -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] filename problem
I can't turn character encoding off right now (too many users are using this server), but in my opinion if you created file named: "test".txt you should see it in the same way in windows. Windows in Polish editions allow to create files with " characters. You can store, and use them from Win2k server, but not from Samba server. Notice that it is posible to copy file with " from windows to samba (file is created correctly in unix filesystem), but that is all you can do. File created in that way can't even be deleted. In my opinion it is bug in Samba. Should I report it ?? Mirek Bernd Wlfel wrote: alright.. just tried it with 2.2.3a and 2.2.6 i created a file "test".txt with vi \"test\".txt, the file shows up correctly within the shell as "test".txt when i look under windows (2k sp3 and xp sp1 both german) the file shows up as TEST~AO.TXT same on samba 2.2.3a and 2.2.6 (see the filename is converted to uppercase?!) could still be your characterset or your codepage could you comment both lines out just for testing? On Win2k sp3 Polish and XP Polish " are preserved when dragging drive to desktop, so I've got big problem. Have you tried to create a file with " on server (directly in shell), and see how client see it ??? Mirek Bernd Wlfel wrote: strange... just tried it with servers win2k,samba 2.2.3a, samba 2.2.6 and clients 2kpro sp3, xp sp1 (all german edition) under my computer I see the natwork drive as "blabla" on server xyz(z) but as soon as i drag the share to the desktop the " charcters are automagically removed my smb.conf says character set = ISO8859-15 (but I think this has nothing to do with the problem) which client operating system are you using? bernd Problem is that Windows creates such file automatically. Steps to create such file. 1. mount your home directory under h: 2. open "my computer" and drag h: drive to your desktop. 3. now you have file with " character, which can be copied to samba, but not from samba to windows. Mirek Bernd Wlfel wrote: correct me if i am wrong but " is no allowed character within a filename under windows hope that helps bernd I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with " character, example: user on "server" (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Regards Mirek
RE: [Samba] filename problem
yes, could be a bug, maybe someone else could check it too? I am far to inexperienced to judge whether or not samba has a bug... just changed my regional settings and input settings to polish but i am still not allowed to create a file seems like you need the polish edition of windows to do this... your codepage file for 852 is in the right directory (default: /usr/local/samba/lib/codepages) sorry but there's nothing more that comes to my mind.. for the moment regards bernd I can't turn character encoding off right now (too many users are using this server), but in my opinion if you created file named: test.txt you should see it in the same way in windows. Windows in Polish editions allow to create files with characters. You can store, and use them from Win2k server, but not from Samba server. Notice that it is posible to copy file with from windows to samba (file is created correctly in unix filesystem), but that is all you can do. File created in that way can't even be deleted. In my opinion it is bug in Samba. Should I report it ?? Mirek Bernd Wölfel wrote: alright.. just tried it with 2.2.3a and 2.2.6 i created a file test.txt with vi \test\.txt, the file shows up correctly within the shell as test.txt when i look under windows (2k sp3 and xp sp1 both german) the file shows up as TEST~AO.TXT same on samba 2.2.3a and 2.2.6 (see the filename is converted to uppercase?!) could still be your characterset or your codepage could you comment both lines out just for testing? On Win2k sp3 Polish and XP Polish are preserved when dragging drive to desktop, so I've got big problem. Have you tried to create a file with on server (directly in shell), and see how client see it ??? Mirek Bernd Wölfel wrote: strange... just tried it with servers win2k,samba 2.2.3a, samba 2.2.6 and clients 2kpro sp3, xp sp1 (all german edition) under my computer I see the natwork drive as blabla on server xyz(z) but as soon as i drag the share to the desktop the charcters are automagically removed my smb.conf says character set = ISO8859-15 (but I think this has nothing to do with the problem) which client operating system are you using? bernd Problem is that Windows creates such file automatically. Steps to create such file. 1. mount your home directory under h: 2. open my computer and drag h: drive to your desktop. 3. now you have file with character, which can be copied to samba, but not from samba to windows. Mirek Bernd Wölfel wrote: correct me if i am wrong but is no allowed character within a filename under windows hope that helps bernd I got problem with filenames. Some info on my configuration Samba 2.2.6 client code page=852 character set=ISO8859-2 When serving files with character, example: user on server (H).lnk (standard link to home drive). Windows 2000 sees something like user~x% It is even worse when such file is located in user profile, which makes it impossible to save user profile to samba server. Coping is possible only from windows to samba (filename is preserved) but coping back fails besause windows see different filename. Regards Mirek -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
