Re: Wcal packaging question
On Wed, Jan 23, 2002 at 10:42:59AM -0800, John H. Robinson, IV wrote: > On Wed, Jan 23, 2002 at 07:04:25PM +0100, Wouter Eerdekens wrote: > > > > Another thing is the apache config: it must be edited before one can > > use wcal: I added the following: > > there are other webservers besides apache. > like boa. I know, but the READE/INSTALL (I don't know which at the moment, I'm on a different machine) only talks about apache, I only use apache, and at the moment, the only people I know using the deb all use apache. I'm creating this package to "master the art of packaging", and I have no idea how to automate the updating of the apache configuration "cleanly", let alone how to do this for every webserver... (But the deb alreade depends on httpd, not on apache :) ... ) > > is there a generic handler to add the cgi information to the webserver > backends? i am not aware of any. > > i doubt that wcal is so closely welded to the apache webserver that it > cannot work with any of the other webservers available. > > i have no solutions for you, but i do want to bring up the awareness > issue: there is more than one httpd. > > -john > > i count a dozen in sid: > % grep-available --count -F Provides httpd > 12 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Blessed are they who Go Around in Circles, for they Shall be Known as Wheels. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Wcal packaging question
Hi, Debian policy states that the directory for CGI content should be /usr/lib/cgi-bin - Create a directory (say, /usr/lib/cgi-bin/wcal) and install in it. You should not need to modify Apache configuration - This directory is already scrpiptaliased in a default Debian installation. Always, if possible, avoid messing with other programs. If you have to... Well, then do it ;-) but I would recommend you not to. Greetings, > Hi, > > First of all: I am not an official debian developer. > > I'm packaging Wcal (a web-based calender/planner). It is by no means an > official deb, but I want to do it as good as possible. I have some > questions though: > > The Wcal installer asks me for the "HTML directory for wcal". This is > the directory that holds the CGI scripts and images (according to > INSTALL). > > I currently use /var/www/wcal for this, but I doubt it is the right > place for it. (I wouldn't like packages installing stuff in > /var/www anyhow...). Can anybody give some advice on this? > > Another thing is the apache config: it must be edited before one can > use wcal: I added the following: > > >AddHandler cgi-script .cgi >DirectoryIndex index.cgi >Options +ExecCGI > > > How should I do this in the postinstall? Will it be overwritten when > there's an apache update? I currently put this in README.Debian, and > ask the user to it him/herself. > > Thanks in advance, hope this is the right place to ask this kind of > questions... > > Wouter > > -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-1118 +--- |PARTICIPA EN EL CONSOL - Congreso Nacional de Software Libre, |http://www.consol.org.mx, Ciudad de México, 11-14 feb 2002 +-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Portable system logging
I am in the process of implementing an option for dictd to permit the user to select which logging facility will be used by syslog. I have used the openlog() and syslog() functions, and the facilities listed in /usr/include/sys/syslog.h. I have just realized that sysklogd is Architecture: i386. Is there a similar logging package for other architectures with an interface that is compatible with i-386 syslog? Bob -- _ |_) _ |_ Robert D. Hilliard <[EMAIL PROTECTED]> |_) (_) |_) 1294 S.W. Seagull Way <[EMAIL PROTECTED]> Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Portable system logging
On Thu, 24 Jan 2002 10:15, Bob Hilliard wrote: > I am in the process of implementing an option for dictd to permit > the user to select which logging facility will be used by syslog. I > have used the openlog() and syslog() functions, and the facilities > listed in /usr/include/sys/syslog.h. > > I have just realized that sysklogd is Architecture: i386. Is > there a similar logging package for other architectures with an > interface that is compatible with i-386 syslog? The interface is the same on other CPUs and other versions of Unix. openlog() and syslog() were originally for BSD Unix (I think) but are now in all versions of Unix. Anyway I just checked the debian/control file for sysklogd: Package: sysklogd Architecture: any So it's not i386... -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SOME ITEMS THAT YOU MAY BE INTERESTED IN OR BE ABLE TO ADVISE ME ON
These are the items that iam interested in selling.. Could you help me with some details on the goods, history, origin etc. are these worth anything and if so who would i contact with regards to selling them? and the best way to sell them ie auction etc APOLOGISE IF YOU HAVE ALREADY RECEIVED THIS E-MAIL JPEGS ARE AVAILABLE AT YOUR REQUEST MANY THANX kriss rolo tel: 0044 182760393 office (uk) 0044 1216864211 home (uk) 0044 7814294018 mobile (uk) return e-mail address [EMAIL PROTECTED] UK ONLY VEHICLE REGISTRATION NUMBER N64 CON NINTENDO 64 CONSOLE item 1 hand carved round table with metal chain link in the middle item 2 magnum laurent perrier vintage 1988 champagne item 3 miniture football on stand from euro96 signed by pele and bobby charlton item 4 is a bit more interesting. its a protana minifon attache, as u will see ive enclosed notes from a web site regarding this and you will see back in the 50's it cost $340.00 so i could imagine this to be worth a bit. it also has an original tape inside i do not know what is on this tape, but judging by who made it and the cost of the machine, the tape could have some important information on it. heres the note. The Minifon, developed in the early 1950s by Monske GMBH of Hanover(or by Protona GMBH- I'm not certain), was an ultra-miniaturized, battery operated magnetic recording device. It could not (initially at least) record the full range of sounds and was thus limited to voice recording, but it did offer easy portability in a very small package. The idea of offering a pocket dictating machine was novel, since dictation had previously been done in the office. However, it was thought that people like salesmen could take the machine "on the road" with them. Once on the market, the Minifon's promoters discovered that many people took advantage of the recorder's small size to make secret recordings to be used as evidence, as in court. The "legitimate" use of the Minifon, as a dictating machine, was somewhat problematical. Recordings made on regular dictating equipment were usually letters, and thus were normally sent almost immediately to a typist. The Minifon offered no obvious advantages over standard dictation equipment for office use, but its developers hoped to cultivate new uses for dictation equipment, such as stock taking in warehouses, or the use of the machine as a substitute for note-taking by reporters, insurance adjusters, salesmen, and others. In its original form, the Minifon was a wire recorder, using a type of wire medium developed by the Armour Research Foundation of Chicago and employed in many similar devices since the late 1940s. The machine at its introduction in 1952 had a recording time of one hour, which was remarkably long, and weighed only about 3 pounds at a time when a typical office dictating machine weighed upwards of 10 pounds. It accomplished this small size and light weight in part through the use of miniature tubes and clever mechanical design. The basic machine cost $289.50-- a price that sounds high today but was very much in line with competing office dictating machines. The parent company attempted to set up distribution, sales and service networks in the United States. It established a business office called the Minifon Export Corp in New York, and an existing company, Harvey Radio in New York City became the main distributor. Although smaller tape recorders appeared at about the same time, the main competition in the voice recording field was from an American company, Mohawk, which made a small, battery-operated cartridge tape recorder called the Migetape. Both products sold less than 10,000 units per year in the U.S. After a few years, the Minifon was modified to use transistors and magnetic tape, further lowering its weight and cost. By 1962 the basic machine weighed in at only 1.5 pounds. Competition by this time had helped bring the cost down to $249.50. The Minifon after about 1962 was distributed by the international conglomerate ITT through its subsidiary in the U.S., Federal Electric Corp. A little later, distribution was taken over by the ITT Distributor Products Division in Lodi, New Jersey. (I don't know whether these were the same company with different names) By the time ITT became associated with this product, it had taken on the name of Minifon "Attache," and a new line of models and options appeared. These included a hi-fi model, the 978H, which sold for $330.50.Usinga two-track, 1/4 inch tape cartridge operating at 1 7/8 inches per second, the machine claimed a frequency response of up to 12,000 Hz, plus or minus 3db. The coming of magnetic tape did not completely displace wire. The Model 240 series of recorders introduced in the early 1960s were probably the last wire recorders in regular production. The 240L, at a price of $269.50 used a special long-playing wire cartridge that held 4 hours of wire. Otherwise it looked like both the tape model and the 240S, which
Broadcasting Solution...
Hello everyone! I'm trying to find a cost-effective solution for a broadcast service i'm providing, so i need your help to figure this out. This is what i got in mind: Since we know that we can put more than one sound card device in one computer, and each RS (radio station) that we broadcast through a server has a domain name (example: http://dr.radio.com:), i though to set up a server with at least 4-5 sound cards and broadcast 4-5 RS using one ip address and each RS with a different domain name. For example: - http://dr.radio.com:8001 - http://dr.radio.com:8002 - http://dr.radio.com:8003 - http://dr.radio.com:8004 - http://dr.radio.com:8005 Here are my questions: - Is it possible to broadcast more than one radio stations from one server using one ip address? - Will it be a problem for you to receive each one of these RS signal there? In case it's not possible, what can i do to make it happend? Best regards, Jenner Cell Phone 809.222.5053 E-mail [EMAIL PROTECTED]Get your FREE download of MSN Explorer at http://explorer.msn.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Broadcasting Solution...
I have published multiple radio stations from a single box using 22khz stereo @ 24kbps per stream, this would be a encoder box, the audio card was an antex studio 2000 which is a multi channel card, it was not to hard to make linux drivers but this hardware is windows pnp I was able to have 3 cards in one box and output 3 stereo fm radios stations in stereo and send the streams on different ports to the streaming server farm, it works well, to well the radio stations became so popular over the internet that we where streaming 120 megs per second at a red cent per meg you are looking at a 120,000 bucks a month bandwidth charges. If you have a ton of cash you want to spend, drop me a line and I will set you up. regards Charles Sherwood http://admart.ca -Original Message-From: Jenner Almanzar [mailto:[EMAIL PROTECTED]]Sent: Wednesday, January 23, 2002 9:19 PMTo: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]Subject: Broadcasting Solution... Hello everyone! I'm trying to find a cost-effective solution for a broadcast service i'm providing, so i need your help to figure this out. This is what i got in mind: Since we know that we can put more than one sound card device in one computer, and each RS (radio station) that we broadcast through a server has a domain name (example: http://dr.radio.com:), i though to set up a server with at least 4-5 sound cards and broadcast 4-5 RS using one ip address and each RS with a different domain name. For example: - http://dr.radio.com:8001 - http://dr.radio.com:8002 - http://dr.radio.com:8003 - http://dr.radio.com:8004 - http://dr.radio.com:8005 Here are my questions: - Is it possible to broadcast more than one radio stations from one server using one ip address? - Will it be a problem for you to receive each one of these RS signal there? In case it's not possible, what can i do to make it happend? Best regards, Jenner Cell Phone 809.222.5053 E-mail [EMAIL PROTECTED] Get your FREE download of MSN Explorer at http://explorer.msn.com.-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Best practices for shared C++ libs?
Hello, The Debian policy for shared libraries works well for C libraries. In particular, one can generally tell if the library has retained or broken binary compatibility so one knows whether to change the SONAME (i.e. SONAME version) or not. For C++ libraries, in contrast, the ABI can change just by changing the compiler. Some folks think that templates cause a problem, too (see below). How difficult is it to maintain binary compatibility with C++ libraries? Should we bother trying, or just give up and embed the complete "major.minor.micro" version string into its SONAME? Is libtool safe to use to build C++ libraries with Debian's compilers? The libtool manual has this to say about C++ libraries: from libtool manual - 11.1 Writing libraries for C++ Creating libraries of C++ code should be a fairly straightforward process, because its object files differ from C ones in only three ways: 1.Because of name mangling, C++ libraries are only usable by the C++ compiler that created them. This decision was made by the designers of C++ in order to protect users from conflicting implementations of features such as constructors, exception handling, and RTTI. 2.On some systems, the C++ compiler must take special actions for the dynamic linker to run dynamic (i.e., run-time) initializers. This means that we should not call `ld' directly to link such libraries, and we should use the C++ compiler instead. 3.C++ compilers will link some Standard C++ library in by default, but libtool does not know which are these libraries, so it cannot even run the inter-library dependence analyzer to check how to link it in. Therefore, running `ld' to link a C++ program or library is deemed to fail. However, running the C++ compiler directly may lead to problems related with inter-library dependencies. The conclusion is that libtool is not ready for general use for C++ libraries. You should avoid any global or static variable initializations that would cause an "initializer element is not constant" error if you compiled them with a standard C compiler. There are other ways of working around this problem, but they are beyond the scope of this manual. Furthermore, you'd better find out, at configure time, what are the C++ Standard libraries that the C++ compiler will link in by default, and explicitly list them in the link command line. Hopefully, in the future, libtool will be able to do this job by itself. - Is #2 or #3 an issue with any of the compilers in Debian? Here's a message about the Boost libraries. Remember that John Maddock is concerned about binary compatibility on many different platforms, not just Debian. However, I'm curious whether this is an issue for Debian or not. - Forwarded message from John Maddock <[EMAIL PROTECTED]> - To: "INTERNET:[EMAIL PROTECTED]" <[EMAIL PROTECTED]> From: John Maddock <[EMAIL PROTECTED]> Mailing-List: list [EMAIL PROTECTED]; contact [EMAIL PROTECTED] Date: Sun, 20 Jan 2002 06:45:52 -0500 Subject: Re: [boost] building shared boost libraries Reply-To: [EMAIL PROTECTED] At the risk of throwing cold water all over the place, one reason that I've always avoided version numbering shared libraries with the regex code is that it's not at all clear to me that it's possible to maintain binary compatibility in C++. In C it's pretty obvious if you do anything to break binary compatibility, it's not clear to me what in C++ breaks compatibility and what doesn't, particularly when the library contains template instances *and* the compiler does link-time template instantiation. I would guess that one would have to ensure that the library always contained the same template instances - probably by doing explicit template instantiation - I for one don't want to go into that level of detail. It is also apparent to me that at least one commercial vendor of C++ libraries (Rogue Wave) never assume that updated versions of their standard lib are binary compatible with previous versions, I would be interested to know if anyone has ever maintained binary compatibility with in C++ libraries as complex as boost. So the question is, if binary compatibility is effectively impossible, what do we do? Increment the major version number with every boost release? Remember that even if I think that regex hasn't changed, something it depends upon (shared pointer for eg) may have :-( - End forwarded message - -Steve -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Wcal packaging question
On Wed, Jan 23, 2002 at 01:58:41PM -0600, Gunnar Wolf wrote: > Hi, > > Debian policy states that the directory for CGI content should be > /usr/lib/cgi-bin - Create a directory (say, /usr/lib/cgi-bin/wcal) and > install in it. Thanks, I'll see how I can do that (the installer installs the cgi's and the images in $html_dir, so I guess I'll have to split $html_dir in the installer in a cgi and an images section... > > You should not need to modify Apache configuration - This directory is > already scrpiptaliased in a default Debian installation. I know, I only had to change it because the cgi's were installed in /var/www/wcal... > > Always, if possible, avoid messing with other programs. If you have to... > Well, then do it ;-) but I would recommend you not to. > > Greetings, Thanks for the advice! Wouter > > > Hi, > > > > First of all: I am not an official debian developer. > > > > I'm packaging Wcal (a web-based calender/planner). It is by no means an > > official deb, but I want to do it as good as possible. I have some > > questions though: > > > > The Wcal installer asks me for the "HTML directory for wcal". This is > > the directory that holds the CGI scripts and images (according to > > INSTALL). > > > > I currently use /var/www/wcal for this, but I doubt it is the right > > place for it. (I wouldn't like packages installing stuff in > > /var/www anyhow...). Can anybody give some advice on this? > > > > Another thing is the apache config: it must be edited before one can > > use wcal: I added the following: > > > > > >AddHandler cgi-script .cgi > >DirectoryIndex index.cgi > >Options +ExecCGI > > > > > > How should I do this in the postinstall? Will it be overwritten when > > there's an apache update? I currently put this in README.Debian, and > > ask the user to it him/herself. > > > > Thanks in advance, hope this is the right place to ask this kind of > > questions... > > > > Wouter > > > > > > -- > Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-1118 > +--- > |PARTICIPA EN EL CONSOL - Congreso Nacional de Software Libre, > |http://www.consol.org.mx, Ciudad de México, 11-14 feb 2002 > +-- > -- Blessed are they who Go Around in Circles, for they Shall be Known as Wheels. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
one source -> two sections (main and contrib) = possible?
Hello,
I'm preparing a new snd package. Because snd still works better with
motif I made three versions of my package: snd (with gtk), snd-dmotif
and snd-smotif. I have to use OpenMotif so snd-{s,d}motif have to go
into contrib.
Am I doing the right thing when I build the free package from one source
(snd) and the other packages from another (snd-motif), or can I build
all binary packages from one source? I don't think so, but I want to be
sure...
regards, Stefan
--
http://www.shockfrosted.org
Re: one source -> two sections (main and contrib) = possible?
On Wed, Jan 23, 2002 at 01:54:05PM +0100, Stefan Schwandter wrote: > Am I doing the right thing when I build the free package from one source > (snd) and the other packages from another (snd-motif), or can I build > all binary packages from one source? I don't think so, but I want to be > sure... You are doing the right thing - if you built the contrib packages from the same source package as the packages in main then either the source package in main wouldn't build without things from outside main or there would be binaries in main without a corresponding source package. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgp3snOzd7txp.pgp Description: PGP signature
Re: Bug#89433: I want to adopt osh
Hi, junichi. Excuse me, I was too harsh and rude on you in my last mail. In <[EMAIL PROTECTED]>, on "Wed, 23 Jan 2002 04:05:11 +0900", with "Re: Bug#89433: I want to adopt osh", Junichi Uekawa <[EMAIL PROTECTED]> wrote: > Ah, I've probably missed this point. > > I don't know what his intent was, but I can see a possibility now. > > In fact, I thought he was trying to say that > "debuild" will unset all variables on invocation, unless > specified otherwise in the command-line. You won. According to the last Oohara's mail, he actually misunderstood as you thought. > Maybe he was just talking about shell constructs. I'd thought he was, so I couldn't understand why you opened the lesson on shell grammer here, instead of just writing "Don't put such tirivial things in debian/rules". But I was wrong. Your lesson worked for him, I see now. Thanks for your work. -- Taketoshi Sano: <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>
Best Source of Internet Traffic - Email 75,000,000 recipients for FREE
TrafficWoW Daily Newsletter January 21, 2002 Disclaimer: --- This email is NEVER sent unsolicited. THIS IS NOT SPAM. You are receiving this because you have either answered classified ad, posted to our FFA pages, are on the same opt-in list or have sent me something in the past. If you'd like to be removed, see instructions at the bottom of this message. FREE PRIZEEmail 75,000,000 Recipients, for ever and ever, SPAM Free This is a VERY powerful method of advertising as all of the recipients have requested to receive YOUR emails so they are HOT PROSPECTS, please do not abuse this service and ruin it for other members. You MUST follow the exact instructions on this page so that you are able to mail to the opt in email safe lists. This system is designed so that YOU send YOUR emails to the lists so that you KNOW that your ad has been sent Others are charging $20 and more... Get this report FREE !!!*** Including list names and subscribe lists *** === IN THIS ISSUE === 1. Traffic for your website 2. Bulk E-mail 3. FFA Submission 4. Our traffic secrets revealed to show you how we do it 5. Popquiz == The New Way To Make Your Website Buzz for Less Than 1-Cent Per Targeted User. == TrafficWOW will deliver 1000's of users to your site within 3 days!!! Or Your Money Back "Guaranteed". How do we do it? With our vast marketing network set within search engine pages, newsletters and content positioning, YOUR website will get the traffic it deserves. NO SPAM! Just good quality traffic. Read some more at http://www.trafficwow.net\faq_wow.htm What areas can we target? Adult, Arts, Business, Computers, Casino, Entertainment, Financial, Games, Webmasters, Marketing, Shopping, Sports, Automotive, Career, Education, Family, Food, Health, Real Estate, Software, Travel. More categories will be introduced. Why are we different? Trafficwow will give you a full refund if we do not deliver every single user you have paid for. All you need to do, is to ensure your site is ready for the world of e-commerce. Don't buy traffic if your website is poor. (Be Honest with yourself!) For further info on the above traffic package or any of the others incredible packages we offer, take a good look: http://www.trafficwow.net PS - All new customers in January will receive a FREE website health check at http://www.trafficwow.net How good are our prices? We have traffic packages starting at $99 per 10,000 unique users or just about the very best price for "real" traffic for your website. Over and above it, many other traffic solutions are available and will be tailormade at your request. Please note TrafficWoW offers a 100% money back guarantee. If we do not deliver all of the traffic you purchased, a full rebate will be given. Visit our website today and let us know how good our prices really are. Try us, we will pleasantly surprise you. ==BULK E-MAIL WORKS !!!== TrafficWOW can send your message to 1 Million people for only $999. Interested? We are! Contact me directly at [EMAIL PROTECTED] ==LIGHT UP YOUR SITE WITH THIS POWERFUL SYSTEM. FREE == Everyone on the web will tell you how he or she makes money but how many really do? You can register your heart out. But with out people linking to your site you are in for a long wait. Click below and find out how it's really done! FREE! http://pages.ffanet.com/links/trafficwow.htm ==Our traffic secrets revealed to show you how we do it == TrafficWoW want to send you the best traffic available. Our product ensures that your web site gets the best opportunity to succeed. There are several different ways that you can make your website better. Click here to find out how? We recommend this strongly as a bad web site will never succeed! http://www.trafficwow.net/faq_wow.ht
Wcal packaging question
Hi, First of all: I am not an official debian developer. I'm packaging Wcal (a web-based calender/planner). It is by no means an official deb, but I want to do it as good as possible. I have some questions though: The Wcal installer asks me for the "HTML directory for wcal". This is the directory that holds the CGI scripts and images (according to INSTALL). I currently use /var/www/wcal for this, but I doubt it is the right place for it. (I wouldn't like packages installing stuff in /var/www anyhow...). Can anybody give some advice on this? Another thing is the apache config: it must be edited before one can use wcal: I added the following: AddHandler cgi-script .cgi DirectoryIndex index.cgi Options +ExecCGI How should I do this in the postinstall? Will it be overwritten when there's an apache update? I currently put this in README.Debian, and ask the user to it him/herself. Thanks in advance, hope this is the right place to ask this kind of questions... Wouter -- Blessed are they who Go Around in Circles, for they Shall be Known as Wheels.
Re: Wcal packaging question
On Wed, Jan 23, 2002 at 07:04:25PM +0100, Wouter Eerdekens wrote: > > Another thing is the apache config: it must be edited before one can > use wcal: I added the following: there are other webservers besides apache. like boa. is there a generic handler to add the cgi information to the webserver backends? i am not aware of any. i doubt that wcal is so closely welded to the apache webserver that it cannot work with any of the other webservers available. i have no solutions for you, but i do want to bring up the awareness issue: there is more than one httpd. -john i count a dozen in sid: % grep-available --count -F Provides httpd 12
Re: Wcal packaging question
On Wed, Jan 23, 2002 at 10:42:59AM -0800, John H. Robinson, IV wrote: > On Wed, Jan 23, 2002 at 07:04:25PM +0100, Wouter Eerdekens wrote: > > > > Another thing is the apache config: it must be edited before one can > > use wcal: I added the following: > > there are other webservers besides apache. > like boa. I know, but the READE/INSTALL (I don't know which at the moment, I'm on a different machine) only talks about apache, I only use apache, and at the moment, the only people I know using the deb all use apache. I'm creating this package to "master the art of packaging", and I have no idea how to automate the updating of the apache configuration "cleanly", let alone how to do this for every webserver... (But the deb alreade depends on httpd, not on apache :) ... ) > > is there a generic handler to add the cgi information to the webserver > backends? i am not aware of any. > > i doubt that wcal is so closely welded to the apache webserver that it > cannot work with any of the other webservers available. > > i have no solutions for you, but i do want to bring up the awareness > issue: there is more than one httpd. > > -john > > i count a dozen in sid: > % grep-available --count -F Provides httpd > 12 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Blessed are they who Go Around in Circles, for they Shall be Known as Wheels.
Re: Wcal packaging question
Hi, Debian policy states that the directory for CGI content should be /usr/lib/cgi-bin - Create a directory (say, /usr/lib/cgi-bin/wcal) and install in it. You should not need to modify Apache configuration - This directory is already scrpiptaliased in a default Debian installation. Always, if possible, avoid messing with other programs. If you have to... Well, then do it ;-) but I would recommend you not to. Greetings, > Hi, > > First of all: I am not an official debian developer. > > I'm packaging Wcal (a web-based calender/planner). It is by no means an > official deb, but I want to do it as good as possible. I have some > questions though: > > The Wcal installer asks me for the "HTML directory for wcal". This is > the directory that holds the CGI scripts and images (according to > INSTALL). > > I currently use /var/www/wcal for this, but I doubt it is the right > place for it. (I wouldn't like packages installing stuff in > /var/www anyhow...). Can anybody give some advice on this? > > Another thing is the apache config: it must be edited before one can > use wcal: I added the following: > > >AddHandler cgi-script .cgi >DirectoryIndex index.cgi >Options +ExecCGI > > > How should I do this in the postinstall? Will it be overwritten when > there's an apache update? I currently put this in README.Debian, and > ask the user to it him/herself. > > Thanks in advance, hope this is the right place to ask this kind of > questions... > > Wouter > > -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-1118 +--- |PARTICIPA EN EL CONSOL - Congreso Nacional de Software Libre, |http://www.consol.org.mx, Ciudad de México, 11-14 feb 2002 +--
Portable system logging
I am in the process of implementing an option for dictd to permit the user to select which logging facility will be used by syslog. I have used the openlog() and syslog() functions, and the facilities listed in /usr/include/sys/syslog.h. I have just realized that sysklogd is Architecture: i386. Is there a similar logging package for other architectures with an interface that is compatible with i-386 syslog? Bob -- _ |_) _ |_ Robert D. Hilliard <[EMAIL PROTECTED]> |_) (_) |_) 1294 S.W. Seagull Way <[EMAIL PROTECTED]> Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9
Re: Portable system logging
On Thu, 24 Jan 2002 10:15, Bob Hilliard wrote: > I am in the process of implementing an option for dictd to permit > the user to select which logging facility will be used by syslog. I > have used the openlog() and syslog() functions, and the facilities > listed in /usr/include/sys/syslog.h. > > I have just realized that sysklogd is Architecture: i386. Is > there a similar logging package for other architectures with an > interface that is compatible with i-386 syslog? The interface is the same on other CPUs and other versions of Unix. openlog() and syslog() were originally for BSD Unix (I think) but are now in all versions of Unix. Anyway I just checked the debian/control file for sysklogd: Package: sysklogd Architecture: any So it's not i386... -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
SOME ITEMS THAT YOU MAY BE INTERESTED IN OR BE ABLE TO ADVISE ME ON
These are the items that iam interested in selling.. Could you help me with some details on the goods, history, origin etc. are these worth anything and if so who would i contact with regards to selling them? and the best way to sell them ie auction etc APOLOGISE IF YOU HAVE ALREADY RECEIVED THIS E-MAIL JPEGS ARE AVAILABLE AT YOUR REQUEST MANY THANX kriss rolo tel: 0044 182760393 office (uk) 0044 1216864211 home (uk) 0044 7814294018 mobile (uk) return e-mail address [EMAIL PROTECTED] UK ONLY VEHICLE REGISTRATION NUMBER N64 CON NINTENDO 64 CONSOLE item 1 hand carved round table with metal chain link in the middle item 2 magnum laurent perrier vintage 1988 champagne item 3 miniture football on stand from euro96 signed by pele and bobby charlton item 4 is a bit more interesting. its a protana minifon attache, as u will see ive enclosed notes from a web site regarding this and you will see back in the 50's it cost $340.00 so i could imagine this to be worth a bit. it also has an original tape inside i do not know what is on this tape, but judging by who made it and the cost of the machine, the tape could have some important information on it. heres the note. The Minifon, developed in the early 1950s by Monske GMBH of Hanover(or by Protona GMBH- I'm not certain), was an ultra-miniaturized, battery operated magnetic recording device. It could not (initially at least) record the full range of sounds and was thus limited to voice recording, but it did offer easy portability in a very small package. The idea of offering a pocket dictating machine was novel, since dictation had previously been done in the office. However, it was thought that people like salesmen could take the machine "on the road" with them. Once on the market, the Minifon's promoters discovered that many people took advantage of the recorder's small size to make secret recordings to be used as evidence, as in court. The "legitimate" use of the Minifon, as a dictating machine, was somewhat problematical. Recordings made on regular dictating equipment were usually letters, and thus were normally sent almost immediately to a typist. The Minifon offered no obvious advantages over standard dictation equipment for office use, but its developers hoped to cultivate new uses for dictation equipment, such as stock taking in warehouses, or the use of the machine as a substitute for note-taking by reporters, insurance adjusters, salesmen, and others. In its original form, the Minifon was a wire recorder, using a type of wire medium developed by the Armour Research Foundation of Chicago and employed in many similar devices since the late 1940s. The machine at its introduction in 1952 had a recording time of one hour, which was remarkably long, and weighed only about 3 pounds at a time when a typical office dictating machine weighed upwards of 10 pounds. It accomplished this small size and light weight in part through the use of miniature tubes and clever mechanical design. The basic machine cost $289.50-- a price that sounds high today but was very much in line with competing office dictating machines. The parent company attempted to set up distribution, sales and service networks in the United States. It established a business office called the Minifon Export Corp in New York, and an existing company, Harvey Radio in New York City became the main distributor. Although smaller tape recorders appeared at about the same time, the main competition in the voice recording field was from an American company, Mohawk, which made a small, battery-operated cartridge tape recorder called the Migetape. Both products sold less than 10,000 units per year in the U.S. After a few years, the Minifon was modified to use transistors and magnetic tape, further lowering its weight and cost. By 1962 the basic machine weighed in at only 1.5 pounds. Competition by this time had helped bring the cost down to $249.50. The Minifon after about 1962 was distributed by the international conglomerate ITT through its subsidiary in the U.S., Federal Electric Corp. A little later, distribution was taken over by the ITT Distributor Products Division in Lodi, New Jersey. (I don't know whether these were the same company with different names) By the time ITT became associated with this product, it had taken on the name of Minifon "Attache," and a new line of models and options appeared. These included a hi-fi model, the 978H, which sold for $330.50.Usinga two-track, 1/4 inch tape cartridge operating at 1 7/8 inches per second, the machine claimed a frequency response of up to 12,000 Hz, plus or minus 3db. The coming of magnetic tape did not completely displace wire. The Model 240 series of recorders introduced in the early 1960s were probably the last wire recorders in regular production. The 240L, at a price of $269.50 used a special long-playing wire cartridge that held 4 hours of wire. Otherwise it looked like both the tape model and the 240S, which
Broadcasting Solution...
Hello everyone! I'm trying to find a cost-effective solution for a broadcast service i'm providing, so i need your help to figure this out. This is what i got in mind: Since we know that we can put more than one sound card device in one computer, and each RS (radio station) that we broadcast through a server has a domain name (example: http://dr.radio.com:), i though to set up a server with at least 4-5 sound cards and broadcast 4-5 RS using one ip address and each RS with a different domain name. For example: - http://dr.radio.com:8001 - http://dr.radio.com:8002 - http://dr.radio.com:8003 - http://dr.radio.com:8004 - http://dr.radio.com:8005 Here are my questions: - Is it possible to broadcast more than one radio stations from one server using one ip address? - Will it be a problem for you to receive each one of these RS signal there? In case it's not possible, what can i do to make it happend? Best regards, Jenner Cell Phone 809.222.5053 E-mail [EMAIL PROTECTED]Get your FREE download of MSN Explorer at http://explorer.msn.com.
RE: Broadcasting Solution...
I have published multiple radio stations from a single box using 22khz stereo @ 24kbps per stream, this would be a encoder box, the audio card was an antex studio 2000 which is a multi channel card, it was not to hard to make linux drivers but this hardware is windows pnp I was able to have 3 cards in one box and output 3 stereo fm radios stations in stereo and send the streams on different ports to the streaming server farm, it works well, to well the radio stations became so popular over the internet that we where streaming 120 megs per second at a red cent per meg you are looking at a 120,000 bucks a month bandwidth charges. If you have a ton of cash you want to spend, drop me a line and I will set you up. regards Charles Sherwood http://admart.ca -Original Message-From: Jenner Almanzar [mailto:[EMAIL PROTECTED]Sent: Wednesday, January 23, 2002 9:19 PMTo: debian-user@lists.debian.org; debian-consultants@lists.debian.org; debian-devel@lists.debian.org; debian-mentors@lists.debian.org; debian-ssh@lists.debian.org; debian-www@lists.debian.org; debian-x@lists.debian.orgSubject: Broadcasting Solution... Hello everyone! I'm trying to find a cost-effective solution for a broadcast service i'm providing, so i need your help to figure this out. This is what i got in mind: Since we know that we can put more than one sound card device in one computer, and each RS (radio station) that we broadcast through a server has a domain name (example: http://dr.radio.com:), i though to set up a server with at least 4-5 sound cards and broadcast 4-5 RS using one ip address and each RS with a different domain name. For example: - http://dr.radio.com:8001 - http://dr.radio.com:8002 - http://dr.radio.com:8003 - http://dr.radio.com:8004 - http://dr.radio.com:8005 Here are my questions: - Is it possible to broadcast more than one radio stations from one server using one ip address? - Will it be a problem for you to receive each one of these RS signal there? In case it's not possible, what can i do to make it happend? Best regards, Jenner Cell Phone 809.222.5053 E-mail [EMAIL PROTECTED] Get your FREE download of MSN Explorer at http://explorer.msn.com.-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Best practices for shared C++ libs?
Hello, The Debian policy for shared libraries works well for C libraries. In particular, one can generally tell if the library has retained or broken binary compatibility so one knows whether to change the SONAME (i.e. SONAME version) or not. For C++ libraries, in contrast, the ABI can change just by changing the compiler. Some folks think that templates cause a problem, too (see below). How difficult is it to maintain binary compatibility with C++ libraries? Should we bother trying, or just give up and embed the complete "major.minor.micro" version string into its SONAME? Is libtool safe to use to build C++ libraries with Debian's compilers? The libtool manual has this to say about C++ libraries: from libtool manual - 11.1 Writing libraries for C++ Creating libraries of C++ code should be a fairly straightforward process, because its object files differ from C ones in only three ways: 1.Because of name mangling, C++ libraries are only usable by the C++ compiler that created them. This decision was made by the designers of C++ in order to protect users from conflicting implementations of features such as constructors, exception handling, and RTTI. 2.On some systems, the C++ compiler must take special actions for the dynamic linker to run dynamic (i.e., run-time) initializers. This means that we should not call `ld' directly to link such libraries, and we should use the C++ compiler instead. 3.C++ compilers will link some Standard C++ library in by default, but libtool does not know which are these libraries, so it cannot even run the inter-library dependence analyzer to check how to link it in. Therefore, running `ld' to link a C++ program or library is deemed to fail. However, running the C++ compiler directly may lead to problems related with inter-library dependencies. The conclusion is that libtool is not ready for general use for C++ libraries. You should avoid any global or static variable initializations that would cause an "initializer element is not constant" error if you compiled them with a standard C compiler. There are other ways of working around this problem, but they are beyond the scope of this manual. Furthermore, you'd better find out, at configure time, what are the C++ Standard libraries that the C++ compiler will link in by default, and explicitly list them in the link command line. Hopefully, in the future, libtool will be able to do this job by itself. - Is #2 or #3 an issue with any of the compilers in Debian? Here's a message about the Boost libraries. Remember that John Maddock is concerned about binary compatibility on many different platforms, not just Debian. However, I'm curious whether this is an issue for Debian or not. - Forwarded message from John Maddock <[EMAIL PROTECTED]> - To: "INTERNET:[EMAIL PROTECTED]" <[EMAIL PROTECTED]> From: John Maddock <[EMAIL PROTECTED]> Mailing-List: list [EMAIL PROTECTED]; contact [EMAIL PROTECTED] Date: Sun, 20 Jan 2002 06:45:52 -0500 Subject: Re: [boost] building shared boost libraries Reply-To: [EMAIL PROTECTED] At the risk of throwing cold water all over the place, one reason that I've always avoided version numbering shared libraries with the regex code is that it's not at all clear to me that it's possible to maintain binary compatibility in C++. In C it's pretty obvious if you do anything to break binary compatibility, it's not clear to me what in C++ breaks compatibility and what doesn't, particularly when the library contains template instances *and* the compiler does link-time template instantiation. I would guess that one would have to ensure that the library always contained the same template instances - probably by doing explicit template instantiation - I for one don't want to go into that level of detail. It is also apparent to me that at least one commercial vendor of C++ libraries (Rogue Wave) never assume that updated versions of their standard lib are binary compatible with previous versions, I would be interested to know if anyone has ever maintained binary compatibility with in C++ libraries as complex as boost. So the question is, if binary compatibility is effectively impossible, what do we do? Increment the major version number with every boost release? Remember that even if I think that regex hasn't changed, something it depends upon (shared pointer for eg) may have :-( - End forwarded message - -Steve -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants
