I came across a small script called pyBurn (attached) which is a frontend for cdrecord. But it only burns cd's and doesn't even recognize my dvd-burner. I'm still learning python (very early stages) so I can't do much with it... is it possible to make it burn dvd's too?
(I'm running Ubuntu Gutsy server btw)
Hello,
I have Solaris 10 U13 and I try to burn an ISO image.
First try:
# cdrw -i myfile.iso
Looking for CD devices...
Device not ready.
Second try:
# cdrecord dev=0,0,0 -v -multi -pad -data myfile.iso
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.... (3 Replies)
I have just about given up trying to find a reliable package.
Imagination - Pitvi - Openshot - DVD Styler are just some of those tried, but even if success has been achieved in exporting a viable result - Brasero will not burn it this includes VOB files. It seems that there is no alternative to... (1 Reply)
I wrote the following script after reading a tutorial, but...
#!/usr/bin/ksh
DATE=`date +"%y%m%d%H%M"`
echo $DATE
FILENAME=`echo "obase = 16\n $DATE"|bc`
echo $FILENAME ... (1 Reply)
Hi,
I am doing frontend for gdb.
Got such things in place:
- gdb from mingw package
- windows OS
- sample aplication to be debugged
- my application (frontend)
I can open sample application under gdb and debug it.
What I want is to connect somehow from my application to gdb and debug... (0 Replies)
I'm new to all this cdrecord and I'm struggling trying to create backups on a DVD-RW disk using a NEC DVD writer that supports PACKET & SAO modes.
I've created two cd images by:
mkisofs -r -J -l -L -o /file1.iso /mnt
mkisofs -r -J -l -L -o /file2.iso /mnt
Then burned the first image to the... (0 Replies)
Hi,
I'm dealing with iptables on Linux, and even if I personally like text configuration, I believe in the case of a firewall would be nice to have a graphical tool.
I've cheked several frontends like Vuurmuur and UIF, but I wanted to know your opinion on the subject.
Thanks.. (3 Replies)
SPEEDY_BACKEND(1p)SPEEDY_BACKEND(1p)NAME
speedy_backend - the backend process for a persistent Perl interpreter
SYNOPSIS
none ; this program is not meant to be called directly.
DESCRIPTION
speedy, short for SpeedyCGI, is a way to run perl scripts persistently, which can make them run much more quickly.
After the script is initially run, instead of exiting, the perl interpreter is kept running inside a backend process, speedy_backend. Dur-
ing subsequent runs, this interpreter is used to handle new executions instead of starting a new perl interpreter each time. A very fast
frontend program, speedy, written in C, is executed for each request. This fast frontend then contacts the persistent Perl process, which
is usually already running, to do the work and return the results.
Each perl script runs in its own Unix process, so one perl script can't interfere with another. Command line options can also be used to
deal with programs that have memory leaks or other problems that might keep them from otherwise running persistently.
The speedy front end connects to the back end process, speedy_backend, via a Unix socket in /tmp. A queue is kept in a shared file in /tmp
that holds an entry for each process. In that queue are the pids of the perl processes waiting for connections. The frontend pulls a
process out of this queue, connects to its socket, sends over the environment and argv, and then uses this socket for stdin/stdout to the
perl process.
FILES
/tmp/speedy* A unix socket used to connect to the frontend process.
AUTHOR
Sam Horrocks
http://daemoninc.com
sam@daemoninc.com
NOTES
This manual page was created by Niko Tyni <ntyni@iki.fi> for Debian GNU/Linux, because the original program does not have one. It is based
on the original and more complete CGI::SpeedyCGI(3pm) manual page.
SEE ALSO perl(1), CGI::SpeedyCGI(3pm), speedy(1)SPEEDY_BACKEND(1p)
