
converting an ground worm to svg
with inkscape is very easy to extract paths
Programmer 4 life
That means i have to add the other applications under "root"
Now www.example.com/application1/index.aspx is already mounted in apache configuration
but www.example.com/application2/index.aspx is not so that was the error
Here is the error trace
[ArgumentException: Path must be rooted.]
System.Web.Util.UrlPath.GetDirectory(String path) +161 System.Web.UI.TemplateControlParser.CompileAndGetParserCacheItem(String virtualPath, String inputFile, HttpContext context) +46 System.Web.UI.TemplateControlParser.GetCompiledInstance(String virtualPath, String inputFile, HttpContext context) +36 System.Web.UI.PageParser.GetCompiledPageInstanceInternal(String virtualPath, String inputFile, HttpContext context) +43 System.Web.UI.PageHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String path) +44 System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, String path, String pathTranslated, Boolean useAppConfig) +691 System.Web.MapHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +95
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +173
try mp3toogg , it's a nice bash script to convert in vorbis format (better one)
>What does this kernel message mean?
>
>Apr 5 23:16:20 lfs kernel: APIC error on CPU0: 60(60)
>Apr 5 23:16:31 lfs kernel: APIC error on CPU0: 60(60)
>
>kernel is 2.6.5 with reiser4 patch.
Send Illegal Vector and Receive Illegal Vector at the same time.
This is more interesting than the usual 40(40) errors
(just Receive Illegal Vector), since 60 implies that the
CPU itself is the source of the bogus vector, whereas 40
usually implies a crap mainboard.
My guess is that either your hardware (whatever it is,
you didn't leave any clues) has problems with a noisy
APIC bus, broken chipset, or something like that, or
you enabled ACPI and the ACPI tables are crap.
Solution on this post
download phpmailer from this address
wget http://unc.dl.sourceforge.net/sourceforge/phpmailer/phpmailer-1.73.tar.gz
tar -zxvf phpmailer-1.73.tar.gz
copy and paste code from the previous Part I
and name it nmsformmail.php
Now you have to write the front-end (html page)
First create an file bad_referer.php with only these lines
<?php
echo "Bad referer";
?>
cp -r phpmailer/language .
cp phpmailer/class.* .
mod_gb is a Apache module which aims to provide an ASP/VBScript compatibility layer for your web-pages. In other words it allows you to run with none or little modifications your ASP pages on your Linux server running Apache.
nice module
I got this error when compiling gbak
make[3]: Entering directory `/home/mariuz/firebird20/firebird2/gen'
g++ -Wl,-rpath,/home/mariuz/bin/firebird/lib -Wl,-rpath,/home/mariuz/bin/firebird/intl ../temp/boot/burp/backup.o ../temp/boot/burp/restore.o ../temp/boot/burp/burp.o ../temp/boot/burp/canonical.o ../temp/boot/burp/misc.o ../temp/boot/burp/mvol.o -o ../gen/firebird/bin/gbak_static -L../gen/firebird/lib -lfbstatic -lfbcommon -lstdc++ -lm -lc -ldl -leditline
../temp/boot/burp/burp.o(.text+0x2724): In function `common_main':
../src/burp/burp.cpp:1130: undefined reference to `RESTORE_restore(char const*, char const*)' 1728,1 27%
../temp/boot/burp/burp.o(.text+0x273c):../src/burp/burp.cpp:1134: undefined reference to `BACKUP_backup(char const*, char const*)'
collect2: ld returned 1 exit status
If you want to play/develop with it on one of ibm's servers
On my to do list :i will try firebird on it: 2.0 or vulcan)
"The OpenPower Project is a group of like-minded people who come from many fields and disciplines. All share a goal: Advancing the Linux® cause. "
"The OpenPower Project intends to give Linux developers an opportunity to try out the latest POWER5 processor-based OpenPower™ servers,"
http://www.openpowerproject.org/us/about.php
If you cannot attend the demonstation in Strasbourg in person please phone or fax your member of the European Parliament (MEP). Or better yet discuss the situation with others you work with and send a company FAX to show them how this new legislation will hurt your business if the Buzek-Rocard-Duff amendments are not adopted by parlement on Wednesday. If you don't inform your parliament, mega-corporations are doing the job for you: "The European Parliament is filled with lobbyists of Microsoft, Eicta, CompTIA and so on. There are 30 to 40 lobbyists permanently roaming the halls."
Join us now...
..::mysql::..
..::linux::..
..::microsoft::..
..::open source::..
I have this message from the log
upibm3 Mon Jul 4 10:54:12 2005
Database: /home/mariuz/firebird20/firebird2/gen/empty.fdb
internal gds software consistency check (Internal error code (179), file: sqz.cpp line: 232)
and when i looked for that line
msg 179 decompression overran buffer
Abstract
========
The Pentium CPU shares caches between HyperThreads. This permits a local
process to gain a side-channel against cryptographic processes running
on the other HyperThread. Testing for cached data can be accomplished by
timing reads. Under some circumstances, this permits the spying process
to extract bits of the key. This has been demonstrated against OpenSSL.
Technical Details
=================
The full explanation of the issue can be found here:
http://www.daemonology.net/papers/htt.pdf
This issue affects only a subset of i386 systems.
Your system is not affected if you are running a CPU without HyperThreading.
Your system is not affected if you are running a non-SMP kernel.
Your system is not affected if you have disabled HyperThreading in your
BIOS, and confirmed that the virtual CPUs are not detected by the kernel
during boot.
Your system is affected, but probably not at risk, if you do not permit
shell access by untrusted users.
Additional resources:
http://www.daemonology.net/hyperthreading-considered-harmful/
ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:09.htt.asc
Solutions and Workarounds
=========================
This issue is fundamental to the design and implementation of
HyperThreading in Intel processors. Avoiding the problem is possible,
and two workarounds are available now. Others which may appear later are
also discussed.
Option 1. Disable HyperThreading in the BIOS.
Disabling HyperThreading is a complete workaround for the issue.
Option 2. Run a non-SMP kernel.
On single physical CPU systems, running a non-SMP kernel
effectively disables HyperThreading. On a multi-CPU system, this
option is not the best solution, since it will disable
additional physical CPUs as well.