Slashdot Mirror

As everyone has noted, Ardour is great for recording. Another really useful tool is Guitarix which is a fantastic guitar amp and effects modelling piece of open source software. Plug your electric guitar directly into your computer via a USB interface (I use my Rocksmith connector) and you can amp/effect model in Guitarix and record as you play in Ardour. Add the Hydrogen and you've also got your drums playing and sync'ed as you record. As well recording, these make a great set of tools for guitar practice.

There is another option for Linux which is open source - PyDAW. Check out the project here:

http://sourceforge.net/projects/libmodsynth/

Although I have no experience with PyDAW, it has been in development for some time and should be very stable.

Peace,
Andy.

It just drives people to chrome

Good luck, Chrome has the same behavior. Even with a signed applet and updated Java, Chrome users had to click twice to run.

For the /.ers astounding by the persistence of Java applets, I was working with JMol. I bypassed the issue by switching to the HTML5-and-JavaScript version and using the applet as a fall-back.

Clicking twice to run is acceptable. Have the plugin disabled and requiring extra steps to re-enable it is not.

It just drives people to chrome

Good luck, Chrome has the same behavior. Even with a signed applet and updated Java, Chrome users had to click twice to run.

For the /.ers astounding by the persistence of Java applets, I was working with JMol. I bypassed the issue by switching to the HTML5-and-JavaScript version and using the applet as a fall-back.

Hear hear! A bit of background to the politics of this:

NFTables is brought to you by a group of codes created when Alexey Kuznetsov decided to replaced the low level linux network stack for Linux 2.2 to make it more like what Cisco provided in IOS. The result added whole pile of new functionality to Linux (eg routing rules), and a shiny new highly module traffic control engine. Alexey produced a beautifully written postscript documentation for the new user land routing tools (the "ip" command), and 100 line howto for the far more complex traffic control engine tools (the "tc" command).

Technically it was a was tour de force. But to end users it could at best be called a modest success. Alexey re-wrote the net-utils tools ("ifconfig", "route" and friends) to use the new system, and did such a good job very few bothered to learn the new "ip" command even though the documentation was good and it introduced a modest amount of new features. But real innovation was the traffic control engine, and to this day bugger all people know how to use it.

At this point it could have gone two ways. Someone could have brought tc's documentation up to the same standard Alexey provided for ip, or they could ignore the fact that almost no one used the code already written and add more of the same. They did the latter.

It was also at this time the network code wars started in the kernel. Not many people know that a modest amount of NAT, filtering and so on can be done by Alexey's new ip command. But rather than build on that Rusty Russell just ported the old ipfwadm infrastructure, called it ipchains (and later replaced it with iptables). There was some overlap between Rusty's work and tc, and this has grown over time. For example the tc U32 filter could do most of the packet tests ipchain's introduced over time on day 1. Technically the modular framework provided by tc was more powerful than ipchains, and inherently faster. Tc was however near impossible for mere mortals to use even if they had good documentation. There were some outside efforts to fix this - tcng was an excellent out-of-tree attempt to fix the complexity problems of tc. But in what seems like a recurring theme, it was out of tree and ignored. In contrast, Rusty provided ipchains with the some best documentation on the planet. In the real world the result of these two efforts are plain to see - while man + dog uses iptables, there maybe 100 people on the planet who can use tc.

Another example of the same thing is IMQ. IMQ lets you unleash the full power of the traffic control engine on incoming traffic. (Natively the traffic control engine only deals with packets being sent, not incoming packets - a limitation introduced for purely philosophical reasons). IMQ was very well documented, and heavily used. The people who brought you tc had a list of technical objections to IMQ. I don't know whether they were real or just a case of Not Invented Here, but I'd give them the benefit of the doubt - they are pretty bright guys. So they replaced it with their own in-kernel-tree concoction. (For those of you who don't follow the kernel "in-tree" means it comes with the Linux Kernel. An out-of-tree module like IMQ means at the very least you have to compile the module source, and possibly the entire kernel.) For a while this discouraged the developers of IMQ so much they stopped working on it. If you follow that link, you will see it's back now. Why? Because the thing that replaced it had absolutely no documentation. They never do. So no one could use the replacement. Again, in the end, the thing code that was documented won the day.

By now you might be guess where this is heading. We have two groups in the kernel competing to provide the

LyX for reports and paper writing, with some raw LaTeX sprinkled in. I have a short python script that can merge multiple documents so I don't have extremely long bulks of content. And there is the python environment for LaTeX, which is awesome with sympy and matplotlib.
LibreOffice for quick documents perhaps with images for a quick WYSIWYG. There is no reason to do everything in text, for some (many?) things the feedback loop is just way too long.
reStructuredText for code documentation, anything that should be readable from command line, but also can be used to make pretty html websites. Sphinx helps. rst exports into plenty of formats via docutils (just expand for rst2* commands).
Converters to epub for stuff I want to read on my ebook reader (from Calibre).
For the text formats my usual editor is gedit. Simple and plain.

It doesn't matter much if you prefer Markdown or rst, that's like arguing which wiki has the best syntax. There are plenty of utilities that can cross-convert and export (pandoc is one of them).

LyX for reports and paper writing, with some raw LaTeX sprinkled in. I have a short python script that can merge multiple documents so I don't have extremely long bulks of content. And there is the python environment for LaTeX, which is awesome with sympy and matplotlib.
LibreOffice for quick documents perhaps with images for a quick WYSIWYG. There is no reason to do everything in text, for some (many?) things the feedback loop is just way too long.
reStructuredText for code documentation, anything that should be readable from command line, but also can be used to make pretty html websites. Sphinx helps. rst exports into plenty of formats via docutils (just expand for rst2* commands).
Converters to epub for stuff I want to read on my ebook reader (from Calibre).
For the text formats my usual editor is gedit. Simple and plain.

It doesn't matter much if you prefer Markdown or rst, that's like arguing which wiki has the best syntax. There are plenty of utilities that can cross-convert and export (pandoc is one of them).

If you're wondering what flow-based programming feels like, I work on an open-source framework called FlowVR.
It is advertised towards high-performance computing but suits small applications just fine.

Use /dev/random and Monolith... dd from random into a file the same size as your cleartext, use Monolith to xor the files into a third file, secured file. The random file is essentially your key, so it must be kept separate from your secured file to be safe.

http://monolith.sourceforge.net/

Diskcryptor
http://sourceforge.net/projects/diskcryptor/

I have used FreeOTFE before, and kind of forgotten about it. As it happens, I am looking for something just like this now for use with some USB keys I need to use to share data at different places.

Now that I look at it I see this on Wikipedia:
"The FreeOTFE website is unreachable as of June 2013 and the domain name is now registered by a new owner."

So I asked, is it even being maintained? I know its open source but, its good to know if a project is actively maintained too. Apparently the place to go is Sourceforge as freeotfe.org is something else now: http://sourceforge.net/projects/freeotfe.mirror/

AND the latest release is several months after the original website disappeared, So it looks like somebody is working on it anyway. May be just what I needed.

Computer systems are often complex

Have you seen Oberon and the work of the people around it? I was *not* saying that there are no existing complex SW systems around. I was just questioning the "If it isn't huge SW with huge documentation, it isn't serious" mindset that some people apparently seem to be suffering from. "If it's big, it must be good!"...? (See page 85.) There are always ways of making things simpler and smaller. And more efficient. And cheaper to maintain in the long run. But apparently, it cuts into your profits if your customers don't need you for continuous support.

Also, you're mentioning IBM. No matter how much technical brilliance the brought into the field (ACS/DIS, manufacturing technologies, VM/CMS etc.), somehow many of their systems have ended up as some the weirdest designs I've seen. (Witness Dijkstra tearing the IBM 1620 apart.)

The manuals for my first AS400 (E35) took up more space than the machine.

Yeah, when they shipped the computer, you had a problem. Then the documentation finally arrived, and you had two problems. :-)

Check out http://readable.sourceforge.net./ This adds additional abbreviations to s-expressions, just like 'x currently means (quote x), so that people can produce much more readable code and data. It's implemented in Scheme and Common Lisp, and is released as open source software using the MIT license.

Looks a lot like m-expressions to me.

Gee, I can't imagine why people would use Word over this.

Christ. This article, like so many here at Slashdot, summarizes to: Usability matters. Usability matters A LOT. Open source developers still don't fucking get it.

Here's a thought: if you want people to stop using Word, why not make something better than Word? Shocking.

Rather than paying gigabucks for a hardware router/firewall, take an ancient machine, add a second ethernet card to it and install OpenBSD onto it.OpenBSD will do you as well as anything hardware based, in terms of protecting your network -- even if it is bit more work to get properly configured. You can also then install stuff like Snort and wireshark to REALLY watch what your system is doing.

It won't take much in terms of hardware -- even a sub 1Gz machine will be more than sufficient for a 20 megabit feed.

For lurkers the link you wanted was: http://sourceforge.net/projects/readable/

The idea you are proposing is the idea behind Dylan: http://en.wikipedia.org/wiki/Dylan_(programming_language). It certainly is a reasonable idea for the base language. But when you construct a DSL you want your DSL code to be easy to construct and destruct data in the lower language. That is you don't want to have write complex parsers. Because once you start writing complex, you want to isolate them i.e. make them methods, make the protocols for putting data into and out of the DSL data structures isolated as well.... and soon you are looking at object oriented code. You've changed the whole paradigm.

What is truly unique about LISP is how easy it is to create a LISP and those s-expressions which are pre-parsed is a large part of that.

Make scales just fine. Badly using make, through mistakes like using recursive make, causes scalability problems.

The paper "Recursive make considered harmful" by Peter Miller identifies common mistakes in using make, and how to fix them. The biggest mistake is using recursive make; this is a common mistake that is NOT required by make. Once you stop making this mistake, make is suddenly much faster.

Two other issues with standard make were not part of POSIX, but they are now:

Issue 1: Historically, standard make only implements deferred assignment (where values are calculated when referenced, not when set). This meant that as size grows, there was an exponentially increasing calculation effort (eek). Miller recommends using immediate assignment op, but although GNU make has one (as :=) that wasn't in the POSIX standard. He also suggests using an appending assignment (+=_, which wasn't in POSIX either. Since then, POSIX has added the immediate-assignment operator ::= and the appendix-assignment += (see http://austingroupbugs.net/view.php?id=330). GNU make 4.0 implements "::=", so you can now start using it. This gets rid of a major scalability problem.

Issue 2: The "obvious" ways to implement automatic dependency generation in make require the ability to "include" multiple from one line, and the ability to silently ignore errors when including, and those weren't in POSIX either. These have since been added to POSIX (in http://austingroupbugs.net/view.php?id=333 and http://austingroupbugs.net/view.php?id=518).

Just getting something into the POSIX spec doesn't cause anything magical to happen. But if a capability is in a standard, it's way more likely to be implemented, and people are far more willing to depend on it.

Previous poster: "Being simpler for a computer means it is simpler to write evaluators for LISP expressions. Because of the simplicity of LISP an evaluator + applicator gives you a compiler or runtime environment. That is a huge huge advantage."

Yes, but that doesn't require using the old s-expression notation from the 1950s.

Check out http://readable.sourceforge.net./ This adds additional abbreviations to s-expressions, just like 'x currently means (quote x), so that people can produce much more readable code and data. It's implemented in Scheme and Common Lisp, and is released as open source software using the MIT license.

Forget the infotainment/bugging crap - we have that already and it's called a smartphone. What we need is Open Source and Open Standard systems for controlling the car and - new kid on the block - battery management.

Real hardware and software already exist in projects like Tumanako which even have the foresight to integrate with distributed power generation systems. But no, big auto manufacturers still focusing on bling that will date faster than a Miley Cyrus video.

Concept programming is the simple idea that the concept is not the code, and that being aware of the differences matters.
See http://xlr.sourceforge.net/Concept%20Programming%20Presentation.pdf for more details.

Why pay? Connect to their access point and tunnel all of your traffic over DNS or ICMP. The firewalls that they use rarely block ICMP and almost never block UDP port 53. All you need is to have a client installed on your machine and run a server out on the interwebs somewhere that is running the right server software and acts as a proxy. The tech to do this has been around for quite a while, and most linux distros have the clients and servers in their repositories. The main system used for DNS is called iodine and there are two different, very good ICMP tunnels that I know of. One is here and another here. If you search through your favorite linux or BSD distro's repository search for "ip over icmp" or "ip over dns" and you'll find what you need.

The solution to low-frequency brute force attempts is Denyhosts. It just blocks any host with repeated failed login attempts. I've been using it for longer than I can remember, probably longer than this "Hail Mary" botnet has been in existence. I'm not sure why this author seems to have never heard of it.

Will projects like OpenOCD

How many times do you have to wash your hands and open and close the door before you can use an Open On-Chip Debugger?

You should try MPC-BE: http://sourceforge.net/projects/mpcbe/
It's a fork of MPC-HC and it has thumbnail previews while seeking (like Youtube).

Also: 'codec packs'?
ffdshow-tryouts: http://sourceforge.net/projects/ffdshow-tryout/
and/or LAV: https://code.google.com/p/lavfilters/
There hasn't been the need for anything else for years.

Finally: when it comes to 'quality', proper framerate matching is way more noticeable than spatial resolution of the video. Using CTRL+J in MPC-HC or MPC-BE (using the Custom EVR or madVR) helps getting addictively good results.

You should try MPC-BE: http://sourceforge.net/projects/mpcbe/
It's a fork of MPC-HC and it has thumbnail previews while seeking (like Youtube).

Also: 'codec packs'?
ffdshow-tryouts: http://sourceforge.net/projects/ffdshow-tryout/
and/or LAV: https://code.google.com/p/lavfilters/
There hasn't been the need for anything else for years.

Finally: when it comes to 'quality', proper framerate matching is way more noticeable than spatial resolution of the video. Using CTRL+J in MPC-HC or MPC-BE (using the Custom EVR or madVR) helps getting addictively good results.

You may find a list of a lot of other alternatives on sourceforge http://sourceforge.net/directory/?q=erp Sourceforge provide an infomation on "Enterprise" ready solutions. Number of download is also a good indicator of popylarity of solution. You may find the Dolibarr ERP - CRM ( http://www.dolibarr.org/ ), or OpenBravo are also a very good choice if you are looking for an easy to use software.

You may have better luck with a script designed specifically to convert mysql to pg. We use one as part of our ora to PG migration project (ora2pg). It's not perfect but it works pretty well. A quick search showed a couple of options for mysql, maybe something like http://sourceforge.net/projects/mysql2pg/ would give you better luck. pg_dump isn't much better at bringing in dumps than psql is. These dedicated conversion scripts usually take advantage of perl DBI connectivity to both DBs simultaneously, versus trying to export ddl and sql, and it seems to be a more successful approach.

http://sourceforge.net/projects/cdesktopenv/

This is why you should be using KDE, not Gnome. In KDE, you have an applet (it's part of the standard build) called "Klipper"; it's a LIFO buffer of everything you Ctrl-C or highlight.

You mean like GNOME Clipboard Manager, from about a decade ago in Gnome 2? Or GPaste, actively-maintained for current Gnome Shell?

There's no reason your pseudonym needs to look like an IRC handle. Just start using a new name.... something like "Mark Twain". It's perfectly legal to take an assumed name, and use for any legal purpose.

Obviously, you cannot use a false name with intent to pass as another person/to further a criminal act -- as that would be wire fraud...

But for legal uses, you can take an assumed name as a legal alias. I would use a tool such as notwhoami to help generate this name.

It's called Gambas.

Probably not, but you could build one pretty easily...

I wonder if phlawed subscribed to https://lists.sourceforge.net/lists/listinfo/icewm-user whether he might then be able to send out a request for members willing to kick in towards paying a maintainer. With enough users they might also have fewer hops than six-degrees towards finding one.

Docker is based in LXC (linux containers), so not available in freebsd. But can be done a port or a similar project based on FreeBSD Jails. It also uses aufs and cgrups, but i think freebsd have similar tools too.

Have you tried contacting their developer mailing list and ask them what they need?

That means you need to deal with automake and friends which are insanely obscure and hard to learn.

You pretty much have to use autoconf anyway if you want any kind of portability. Yes, it is a pain, but doing without it by expecting the user to edit the makefile just to specifiy a different installation prefix (like his home dir) is much worse. Don't shift the work on the user! If you really can't figure out autoconf, at least try one of the many simpler substitutes available.

It's not so difficult if it's pure Python and you're not compiling anything. The main problem was getting Qt to compile so I could compile my extensions. For your project, I'd make a virtual machine with something like WinXP (this makes it easier to make new releases if nothing changes), install Python and the associated PySide. Install any other modules you need. I used PyInstaller to make the runnable exe file. See e.g. here for my pyinstaller file. I then used NSIS to make an installer using this configuration file.

The obvious "Use Version control/Git" is actually and improvement of your methods.
Here is an actual to the point answer to your question about software. A requirement of real time-sync was mention.

There is Synkron (has a scheduler) , OneSync (has real time sync), and Unison (uses rsync).

All are open source and free. Have fun.

Better yet:
Biebian

If you want to try out quantum computing simulation, consider checking out QCF in the Matlab-like Octave.

Thought I would use Bruce's Password safe http://passwordsafe.sourceforge.net/ and dowwnload http://sourceforge.net/projects/passwordsafe/files/ but no HTTPS, should I be worred?

Thought I would use Bruce's Password safe http://passwordsafe.sourceforge.net/ and dowwnload http://sourceforge.net/projects/passwordsafe/files/ but no HTTPS, should I be worred?

The high cost was in the hardware (telescope, CCD camera) not in the software. There have been open-source or free photometry codes available for years. Admittedly not all of them trivially easy to use, but then finding and observing the expolanet itself requires some ability and understanding. A popular and quite decent photometry program which is easy to use is C-Munipack. (Which is not to say another one isn't a good thing, the more the better.)

Fortunately, there are free alternatives such as Eternal September, so long as you are willing to stick with the text-only groups (which are the best part of Usenet anyway). Completely free access; just register, download and configure your Usenet client and subscribe to your favorite groups. Not all the groups are dead, and more traffic from intelligent posters is always welcome ;-)

Rebecca Black Linux

http://sourceforge.net/projects/rebeccablackos/

Hannah Montana Linux...

http://hannahmontana.sourceforge.net/

My Little Pony Gnome theme...

http://gnome-look.org/content/show.php/?content=144562

Unfortunately, Mattel is serious about its trademarks, so Barbie Linux doesn't exist (yet)(at least publicly)

Be afraid. Very afraid.

--
BMO

Rebecca Black Linux

http://sourceforge.net/projects/rebeccablackos/

Hannah Montana Linux...

http://hannahmontana.sourceforge.net/

My Little Pony Gnome theme...

http://gnome-look.org/content/show.php/?content=144562

Unfortunately, Mattel is serious about its trademarks, so Barbie Linux doesn't exist (yet)(at least publicly)

Be afraid. Very afraid.

--
BMO

ASSP, Anti-Spam SMTP Proxy.

Ran it for a few years with a domain of a several hundred users. What I liked best is that it blocks spam during the SMTP conversation with the spammy sender.

I use razor collaborative spam filter calling it directly from procmail, but my local rules usually catch any spam before razor-check is called.

When my ISP discontinued the use of procmail filters, I moved it to my home computer and configured two filters in Evolution: the first one to auto-remove mail marked by my ISP as suspected spam, and the next to pipe the mail through bmf and remove it if it tested positive for spam. When I say "auto-remove", I mean it's moved to a spam folder where I can double-check it in case false positives get through.

http://sourceforge.net/projects/bmf/

http://bogofilter.sourceforge.net/

I haven't timed it to see how well its been doing in the 6 years I've had it though.