<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">I can see the email.</DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"> </DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">David Cerezo.<BR><BR></DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">----- Original Message ----<BR>From: "filepro-list-request@lists.celestial.com" <filepro-list-request@lists.celestial.com><BR>To: filepro-list@lists.celestial.com<BR>Sent: Friday, July 27, 2007 11:09:09 AM<BR>Subject: Filepro-list Digest, Vol 42, Issue 51<BR><BR>
<DIV>Send Filepro-list mailing list submissions to<BR> filepro-list@lists.celestial.com<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR> <A href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target=_blank>http://mailman.celestial.com/mailman/listinfo/filepro-list</A><BR>or, via email, send a message with subject or body 'help' to<BR> filepro-list-request@lists.celestial.com<BR><BR>You can reach the person managing the list at<BR> filepro-list-owner@lists.celestial.com<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of Filepro-list digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. test (Howard Wolowitz)<BR> 2. Re: test (scooter6)<BR> 3. RE: test (Bruce Easton)<BR> 4. Export Syntax (Scott Walker)<BR> 5. Re: Filepro-list Digest, Vol 42, Issue 50
(Boaz Bezborodko)<BR> 6. Re: Export Syntax (Fairlight)<BR> 7. RE: Export Syntax (Bruce Easton)<BR> 8. Re: Export Syntax (Kenneth Brody)<BR> 9. Re: Filepro-list Digest, Vol 42, Issue 48 (Bill Campbell)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Fri, 27 Jul 2007 11:13:51 -0400<BR>From: "Howard Wolowitz" <howiewz@aljex.com><BR>Subject: test<BR>To: "filepro list" <filepro-list@lists.celestial.com><BR>Message-ID: <19ca01c7d060$bd395f00$6623a8c0@Howie><BR>Content-Type: text/plain; format=flowed; charset="iso-8859-1";<BR> reply-type=original<BR><BR>Please respond if you can see this email.<BR><BR>Thanks,<BR><BR>Howie<BR><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Fri, 27 Jul 2007 11:22:40 -0400<BR>From: scooter6 <scooter6@gmail.com><BR>Subject: Re: test<BR>To: "Howard Wolowitz"
<howiewz@aljex.com><BR>Cc: filepro list <filepro-list@lists.celestial.com><BR>Message-ID:<BR> <445ca8160707270822g32ca8eedwaa138e20d7a455e4@mail.gmail.com><BR>Content-Type: text/plain; charset="iso-8859-1"<BR><BR> yep saw it<BR><BR>On 7/27/07, Howard Wolowitz <howiewz@aljex.com> wrote:<BR>><BR>> Please respond if you can see this email.<BR>><BR>> Thanks,<BR>><BR>> Howie<BR>> _______________________________________________<BR>> Filepro-list mailing list<BR>> Filepro-list@lists.celestial.com<BR>> <A href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target=_blank>http://mailman.celestial.com/mailman/listinfo/filepro-list</A><BR>><BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <A href="http://mailman.celestial.com/pipermail/filepro-list/attachments/20070727/889e9291/attachment-0001.html"
target=_blank>http://mailman.celestial.com/pipermail/filepro-list/attachments/20070727/889e9291/attachment-0001.html</A> <BR><BR>------------------------------<BR><BR>Message: 3<BR>Date: Fri, 27 Jul 2007 11:44:06 -0400<BR>From: "Bruce Easton" <bruce@stn.com><BR>Subject: RE: test<BR>To: "filepro list" <filepro-list@lists.celestial.com><BR>Message-ID: <BBEALIBBDKJHFKICDGELGEIDDLAA.bruce@stn.com><BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>Here is a plain text response :)<BR><BR>Bruce<BR><BR>Bruce Easton<BR>STN, Inc.<BR><BR>> -----Original Message-----<BR>> From: filepro-list-bounces+bruce=stn.com@lists.celestial.com<BR>> [mailto:filepro-list-bounces+bruce=stn.com@lists.celestial.com]On Behalf<BR>> Of Howard Wolowitz<BR>> Sent: Friday, July 27, 2007 11:14 AM<BR>> To: filepro list<BR>> Subject: test<BR>> <BR>> <BR>> Please respond if you can see this email.<BR>> <BR>> Thanks,<BR>>
<BR>> Howie<BR>> _______________________________________________<BR>> Filepro-list mailing list<BR>> Filepro-list@lists.celestial.com<BR>> <A href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target=_blank>http://mailman.celestial.com/mailman/listinfo/filepro-list</A><BR>> <BR><BR><BR>------------------------------<BR><BR>Message: 4<BR>Date: Fri, 27 Jul 2007 11:07:55 -0400<BR>From: "Scott Walker" <ScottWalker@RAMSystemsCorp.com><BR>Subject: Export Syntax<BR>To: "Filepro_List" <filepro-list@lists.celestial.com><BR>Message-ID: <000e01c7d05f$eaaa7a60$6901a8c0@SWT40><BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>I am exporting an ascii file on a SCO Unix system. The file will<BR>actually be used on a windows system so I want the record separator to<BR>be a CR/LF. <BR><BR>I'm using:<BR><BR> export ascii banner=(mv) r=chr("10")&chr("13") f=, o="
c="<BR><BR>but that bombs on syntax check.<BR><BR>How do I tell fp to use CR/LF as record separator?<BR><BR>Thanks.<BR><BR>Scott Walker<BR>RAM Systems Corp.<BR>ScottWalker@RAMSystemsCorp.com<BR>Ph: (704) 896-6549<BR>Fx: (704) 896-7458<BR><BR><BR><BR><BR><BR><BR>------------------------------<BR><BR>Message: 5<BR>Date: Fri, 27 Jul 2007 11:53:28 -0400<BR>From: Boaz Bezborodko <boaz@mirrotek.com><BR>Subject: Re: Filepro-list Digest, Vol 42, Issue 50<BR>To: filepro-list@lists.celestial.com<BR>Message-ID: <46AA14F8.6010307@mirrotek.com><BR>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<BR><BR><BR>> Message: 4<BR>> Date: Fri, 27 Jul 2007 10:31:48 -0400<BR>> From: Fairlight <fairlite@fairlite.com><BR>> Subject: Re: Filepro-list Digest, Vol 42, Issue 48<BR>> To: filepro-list@lists.celestial.com<BR>> Message-ID: <20070727103148.B6583@iglou.com><BR>> Content-Type: text/plain; charset=us-ascii<BR>><BR>> Only Boaz
Bezborodko would say something like:<BR>> <BR>>> What I learned in the process is that the learning curve on Samba was <BR>>> steep enough that I probably would have been better off moving FP to <BR>>> <BR>><BR>> I don't recall samba as having a steep learning curve. man smb.conf<BR>> I've been through older versions (2.x) and newer (3.x) and had to migrate<BR>> between the two. It's never taken more than a couple hours to figure out<BR>> what was wrong.<BR>><BR>> The biggest issue was SuSE 10.1 having some issue whereby the registry got<BR>> corrupted, and I wasn't aware they'd added one until I started digging.<BR>> Remind me again why samba needs its own registry files? Anyway, I think<BR>> the user corrupted it in that case, although I can't prove it one way or<BR>> another. It could have shipped bad, it could have been<BR>>
misconfiguration--they screwed up enough else even using yast that it took<BR>> longer to undo their damage than to do it properly from scratch.<BR>><BR>> Which just goes to show you, having an admin tool isn't everything, you<BR>> actually have to know what data you're putting into it. And this was a<BR>> person that keeps touting scoadmin as easy. YaST makes far more achievable<BR>> easily, but it's that "far more" that's at issue. For instance, the<BR>> user complains sendmail and apache are hard to configure on linux. They<BR>> can't configure it properly on SCO either, but they blame the OS anyway,<BR>> nevermind that more tools are provided to do it at a basic level that they<BR>> still can't get right due to lack of understanding of the basic subsystem.<BR>> That annoys the hell out of me.<BR>><BR>> What people -want- are psychic admin tools that do what they want, not what<BR>>
they tell it to do. Anything less, and you get, "This OS is horrible<BR>> compared to [insert their favourite OS]." Sorry folks, it's not the OS,<BR>> it's a lack of fundamental low-level knowledge. Given that knowledge, you<BR>> can do it at the raw level on any system without admin tools of -any- sort.<BR>><BR>> And people complain that I come across as elitist when saying people in<BR>> general should know what they're doing or have time to learn. The truth<BR>> is, -they're- the ones damaging their systems via ignorance. It's a valid<BR>> point they just don't want to hear because they've been indoctrinated into<BR>> the, "All OSes should be PnP," school of thought. I'm sorry, but after the<BR>> hardware detection and driver loading is done, *nix should not be PnP in my<BR>> opinion. It's too powerful a tool to give to the ignorant. It's like<BR>>
giving a .50cal machine gun to a 5yr-old, or letting kids drive at age 10.<BR>><BR>> Okay, you may have touched a sore point, there. :) Nothing personal...more<BR>> wrapped up in what I've seen in the past. But citing the whole learning<BR>> curve thing just sets it off. The learning curve isn't that steep, and<BR>> with power comes complexity anyway (usually), so it's actually ahead of the<BR>> game. I see no grounds for complaints unless something is made -so- overly<BR>> complex that it's ludicrous. Best example of needlessly complex that comes<BR>> to mind is the sudoers file syntax. THAT is needlessly complex, although<BR>> pretty powerful.<BR>><BR>> mark-><BR>> <BR>No offense, Mark, but you were the one who was most hostile to my <BR>request for assistance in what I would have to know or learn to move <BR>forward. An example of what I was looking for
was a list or some links <BR>to some of the basic aspects of what I was looking to do.<BR><BR>For example, if someone was looking to set up a Samba server I would <BR>tell them to look up some basics (in no particular order and not <BR>comprehensive)<BR><BR>-- Understand Linux security via file permissions etc.<BR>-- Decide if you need better granularity. If you do then explore using <BR>ACLs and read up on Samba and its implementation of ACLs (I decided I <BR>didn't need to bother) and get a later version of Samba to support it.<BR>-- Forget SELinux (as per your instructions- thanks for that help in <BR>case I forgot to thank you before) unless you absolutely need the extra <BR>protection--and most don't.<BR>-- Install Webmin for some basic functions such as modifying the <BR>firewall setups. Don't bother with it for Samba unless you are only <BR>doing a very basic setup.<BR>-- If your setup is this complex then spend the money on decent backup
<BR>software. BackupEdge is easy to use and has so many different features <BR>and options its worth the money. Yes, you can do wonderful things with <BR>basic Linux functions, but you'll spend quite a bit of time figuring <BR>them out and setting them up. (I read up on them, but I didn't bother <BR>putting the time in.)<BR>-- Learn the command line interface. It's not the the GUI doesn't have <BR>tools that help, it's that they are so limited that they hide access to <BR>the functionality and features you probably need to modify for such a <BR>more complex environment.<BR>-- If you want to set up printing and automatic driver downloading <BR>through the Samba server then read this:<BR><A href="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#9_1"
target=_blank>http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#9_1</A><BR>Especially the tagged location for the "Point'nPrint". Just <BR>understanding the need to "tickle" the driver setup will help you from <BR>wasting a lot of time trying to figure out why some drivers won't <BR>print. (This isn't pointed out in all the documentation on the subject.)<BR>-- Oplock setup for Samba use with FilePro (on the share level of the <BR>configuration file)<BR> level2 oplocks = no<BR> oplocks = no<BR><BR>I went up not a few wrong branches because of a lack of direction. <BR>Sometimes it was because I got an idea of how I might be able to use a <BR>particular feature only to find out later that I shouldn't have bothered <BR>for whatever
reason.<BR><BR>Boaz<BR><BR><BR>------------------------------<BR><BR>Message: 6<BR>Date: Fri, 27 Jul 2007 11:57:16 -0400<BR>From: Fairlight <fairlite@fairlite.com><BR>Subject: Re: Export Syntax<BR>To: Filepro_List <filepro-list@lists.celestial.com><BR>Message-ID: <20070727115716.A9843@iglou.com><BR>Content-Type: text/plain; charset=us-ascii<BR><BR>This public service announcement was brought to you by Scott Walker:<BR>> I am exporting an ascii file on a SCO Unix system. The file will<BR>> actually be used on a windows system so I want the record separator to<BR>> be a CR/LF. <BR>> <BR>> I'm using:<BR>> <BR>> export ascii banner=(mv) r=chr("10")&chr("13") f=, o=" c="<BR>> <BR>> but that bombs on syntax check.<BR>> <BR>> How do I tell fp to use CR/LF as record separator?<BR><BR>I was told that you can only use single-byte separators in export and<BR>import, so the answer
would appear to be, "You can't."<BR><BR>TTBOMK, you need to use open/writeline/close instead. Since writeline will<BR>append its own \n, just make sure you toss in a \r at the end of your line<BR>contents.<BR><BR>mark-><BR>-- <BR>The latest synth mixdown...<BR><A href="http://media.fairlite.com/Isolation_Voiceless_Cry_Mix.mp3" target=_blank>http://media.fairlite.com/Isolation_Voiceless_Cry_Mix.mp3</A><BR><BR><BR>------------------------------<BR><BR>Message: 7<BR>Date: Fri, 27 Jul 2007 11:58:33 -0400<BR>From: "Bruce Easton" <bruce@stn.com><BR>Subject: RE: Export Syntax<BR>To: "filepro list" <filepro-list@lists.celestial.com><BR>Message-ID: <BBEALIBBDKJHFKICDGELGEIEDLAA.bruce@stn.com><BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>Scott Walker wrote Friday, July 27, 2007 11:08 AM:<BR>> <BR>> I am exporting an ascii file on a SCO Unix system. The file will<BR>> actually be used on a windows
system so I want the record separator to<BR>> be a CR/LF. <BR>> <BR>> I'm using:<BR>> <BR>> export ascii banner=(mv) r=chr("10")&chr("13") f=, o=" c="<BR>> <BR>> but that bombs on syntax check.<BR>> <BR>> How do I tell fp to use CR/LF as record separator?<BR>> <BR>> Thanks.<BR>> <BR>> Scott Walker<BR><BR>Scott, try r=10&13<BR><BR><BR>Bruce<BR><BR>Bruce Easton<BR>STN, Inc.<BR><BR><BR>------------------------------<BR><BR>Message: 8<BR>Date: Fri, 27 Jul 2007 12:02:39 -0400<BR>From: Kenneth Brody <kenbrody@bestweb.net><BR>Subject: Re: Export Syntax<BR>To: Scott Walker <ScottWalker@RAMSystemsCorp.com><BR>Cc: Filepro_List <filepro-list@lists.celestial.com><BR>Message-ID: <20070727120239.lvd0ks8ckok80wc8@webmail.spamcop.net><BR>Content-Type: text/plain; charset="ISO-8859-1"<BR><BR>Quoting Scott Walker (Fri, 27 Jul 2007 11:07:55 -0400):<BR><BR>> I am exporting an ascii
file on a SCO Unix system. The file will<BR>> actually be used on a windows system so I want the record separator to<BR>> be a CR/LF.<BR>><BR>> I'm using:<BR>><BR>> export ascii banner=(mv) r=chr("10")&chr("13") f=, o=" c="<BR>><BR>> but that bombs on syntax check.<BR>><BR>> How do I tell fp to use CR/LF as record separator?<BR><BR>You can't have a multi-character separator, as you have seen.<BR><BR>My recomendation would be to use "r=\n" to get the Unix end-of-line<BR>character, and then use a text-mode transfer when copying it over to<BR>Windows. This will convert LF to CRLF for you.<BR><BR>If this is not an option, then use the "xtod" utility (I believe<BR>that is what SCO calls it) to convert the file to CRLF.<BR><BR>Also, is the conversion even required? Many programs on Windows<BR>will work just with with LF instead of CRLF.<BR><BR>Finally, if no other option is available, then
your last resort<BR>might be to force the CR into the last field of the export, as in:<BR><BR> output[37] = field & chr("13")<BR><BR>--<BR>KenBrody at BestWeb dot net spamtrap: <g8ymh8uf001@sneakemail.com><BR><A href="http://www.hvcomputer.com/" target=_blank>http://www.hvcomputer.com</A><BR><A href="http://www.fileproplus.com/" target=_blank>http://www.fileProPlus.com</A><BR><BR><BR>------------------------------<BR><BR>Message: 9<BR>Date: Fri, 27 Jul 2007 09:07:42 -0700<BR>From: Bill Campbell <bill@celestial.com><BR>Subject: Re: Filepro-list Digest, Vol 42, Issue 48<BR>To: filepro-list@lists.celestial.com<BR>Message-ID: <20070727160742.GA19774@ayn.mi.celestial.com><BR>Content-Type: text/plain; charset=us-ascii<BR><BR>On Fri, Jul 27, 2007, Fairlight wrote:<BR>>Only Boaz Bezborodko would say something like:<BR>>> <BR>>> What I learned in the process is that the
learning curve on Samba was <BR>>> steep enough that I probably would have been better off moving FP to <BR>><BR>>I don't recall samba as having a steep learning curve. man smb.conf<BR>>I've been through older versions (2.x) and newer (3.x) and had to migrate<BR>>between the two. It's never taken more than a couple hours to figure out<BR>>what was wrong.<BR><BR>I've found that using the standard ``swat'' web configuration tool very<BR>helpful, particularly as it provides on-line help for every option. It's<BR>part of the standard Samba distribution, and runs on port 901.<BR><BR>John Terpstra's books ``The Official Samba-3 HOWTO and Reference Guide'',<BR>and ``Samba33 by Example'' are also excellent. These are available as PDF<BR>downloads from the samba.org site as well as in the dead-trees versions.<BR><BR>...<BR>Bill<BR>--<BR>INTERNET: bill@celestial.com Bill Campbell; Celestial
Software LLC<BR>URL: <A href="http://www.celestial.com/" target=_blank>http://www.celestial.com/</A> PO Box 820; 6641 E. Mercer Way<BR>FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676<BR><BR>When you have an efficient government, you have a dictatorship.<BR> -- Harry Truman<BR><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>Filepro-list mailing list<BR>Filepro-list@lists.celestial.com<BR><A href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target=_blank>http://mailman.celestial.com/mailman/listinfo/filepro-list</A><BR><BR><BR>End of Filepro-list Digest, Vol 42, Issue 51<BR>********************************************</DIV></DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"><BR></DIV></div></body></html>