LQ Job Marketplace [Archive]NOTE: The new LQ Job Marketplace can be found here.
The LQ Job Marketplace allows you to post available jobs for Linux, Open Source and programming related positions. There is a fee associated with each thread. Please read the guidelines before posting.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

This is an open letter to all interested Linux developers. I had posted previously about this in other Linux forums - difference is, now I have a backer and a small but fair budget to actually do it!
---------------------------------------------
Hi All,

I'm an amateur inventor, and was struck by a cool idea for using Puppy Linux to recover data from Windows computers that won't boot, due to Windows failure, but still have working hardware. I'm in no way wedded to Puppy, but do feel that it offers several advantages - small size, good hardware recognition, etc.

I >have< a financial backer for this concept, preliminary outlines of the program, a needed companion website, and the start of a business plan. What I need is a skilled Linux programmer with integrity. That means a programmer who has the ability to deliver working product, in a timely manner, for fair pay, and not violate the terms of a basic NDA (non disclosure agreement).

If I can find a suitable Linux programmer, my backer is willing to pay a fair market rate for development of the project. I'd like this money to go into the Linux community, partly as payback for the use I've had of Linux, and also to further the development of Linux itself. It would be a real hoot to be able to say that Linux rescues Windows computers by the thousands on a world wide basis, every day. Of course, this is already happening, but my project would really 'kick it up a notch'.

I don't want to go into too much detail without having developers, sign a NDA, (non-disclosure agreement), but in a nutshell, it's a way for non-Linux users to put a Puppy Linux based CD into a Win computer that won't boot, and use it to recover data both over the Internet, and locally. I'm using Puppy as an example, because it's broadly
hardware compatible, runs with a small amount of memory, and is easy to modify and re-master. But I'm not wedded to Puppy - any distro that will do the job is fine by me...

The program I envision would act as a 'shell' sitting on top of an unmodified Puppy distro, with the first option being to run the data recovery program, which I've given the provisional name of 'Emergency Transfer System' - or ETS, for short, and the second option being to boot directly into Puppy.

The ETS code would be closed-code, but work with, and through, the unmodified Puppy distro to maintain the legality and spirit of Barry Kauler's copyright. The concept is to create a service for data recovery that could work globally to recover data, and ALSO to distribute Puppy (or whatever distro is used) globally, at the same time.

Your immediate question, as an open-source developer is why is the ETS program closed code? The answer is simple. There is no other way I can think of to make money with the project. And the project >has< to make money, in order to survive... Not gazillions of dollars, but a fair rate for a valuable service.

Since the unmodified Puppy/other distro is also distributed along with the ETS supervisor program, and end users can launch Linux directly at any time, I feel this is close enough to the spirit of open source coding to be ethical.

If you don't understand this viewpoint, I'm sorry, but my limited intellect cannot figure out any way to actually get paid for the work of data recovery without keeping the ETS code closed. If you, on the other hand can devise a method, I'm all ears...

I don't know how many Windows computers crash and need data recovery every day, on a global basis, but my guess is thousands - every one of whom is a potential customer for ETS services. We could create a business that would help support Linux software, and do a lot of good, helping non-technical people recover their data.

I do know from preliminary research that there are somewhere around 1,000,000,000 Windows computers currently installed. A tiny fraction of that number as clients, would create a substantial market for the ETS.

I'm not a programmer, just a computer tech with a knack for inventing. So I'd need the help of programmers and sysadmins from within the Linux community to create this project. But from working with Puppy for several years,

I feel certain that the ETS project is not only do-able, but actually pretty simple - if you have the expertise - which I don't.

If you're interested, please contact me, and I'll send you the NDA (non-disclosure agreement) form. If you like the concept, welcome aboard! If not, please just don't talk about it!

I don't really understand where you think you can go with this concept. There are already multiple live CDs that are designed for system repair and data recovery which use software that is already well established and robust; but perhaps most importantly, open source and actively developed.

To come out of left field with a plan to develop a closed source replacement for all this software, with no clear indication of why this project would be better than what is already on the market, is just a pipe dream. On top of it, you don't have any developers, and it doesn't sound like you even have the technical expertise or knowledge to understand the concept itself.

It seems like you thought this up one day, assumed it must not currently exist because you were not personally aware of it, and decided it was an easy way to get rich by paying somebody else to develop your "groundbreaking" idea. Then to finish it off in the most stereotypical way possible, you demand that it must be completely closed source because there is "no way to make money from open source software" (while naturally basing 98% of your product on OSS so you don't have to do all the leg work).

I don't really understand where you think you can go with this concept. There are already multiple live CDs that are designed for system repair and data recovery which use software that is already well established and robust; but perhaps most importantly, open source and actively developed.

I'm well aware of what is available in live CDs, repair utilities, etc.
My gizmo doesn't attempt to repair anything. What it >does< do is make it >easy< for non-techy, non-computer savants to recover data quickly and cheaply.

Quote:

Originally Posted by MS3FGX

To come out of left field with a plan to develop a closed source replacement for all this software, with no clear indication of why this project would be better than what is already on the market, is just a pipe dream. On top of it, you don't have any developers, and it doesn't sound like you even have the technical expertise or knowledge to understand the concept itself.

(sigh) I'm not replacing anything. The ETS rides on top of an unmodified, source code available distro. As I said in the post - find me a way to make it open source and I'm "all ears." Don't rant at me - show me an >effective< business model I can implement, and I'm there in a heartbeat!

I have two PowerPoint screen shows that I did myself to 'mock up' the ETS program, and it's accompanying website. They show how the program works, and how the website works to complement it. So I think I >do< understand the concept - enough to show it to you, IF you sign my NDA. Until then, since you haven't seen it, as Bobby Dylan said, "Don't criticize what you can't understand." After you see it, understand the concept, and think about it - then you can criticize it all you want - but you may choose not to...

Quote:

Originally Posted by MS3FGX

It seems like you thought this up one day, assumed it must not currently exist because you were not personally aware of it, and decided it was an easy way to get rich by paying somebody else to develop your "groundbreaking" idea. Then to finish it off in the most stereotypical way possible, you demand that it must be completely closed source because there is "no way to make money from open source software" (while naturally basing 98% of your product on OSS so you don't have to do all the leg work).

Uh, I "thought it up" one day, because I needed it. I am the >first< to admit that I am not a programmer - that's why I want to hire one. But I am a pro computer tech, ex-audio engineer, tech, producer, and studio designer/builder. And I just had a tech book published globally by Focal Press. So I >do< have just a little experience with logical thinking, and problem solving. Isn't that what programming is all about? Not assuming things you don't know...

Further, >you< are the one who said. "no way to make money from open source software" - I never said that. Just because this particular project may require a small part of the total code to be closed code, does not mean that all code needs to be closed (or open). The tendency to think in only opposites, closed/open, good/bad, right/wrong, is characteristic of what Gurdjieffe (sp?) called "waking sleep". Perhaps other relationships can exist that meld both closed and open code - and thus are more synergistic and serendipitous. Show me how to do it only with open source code and maintain a marketshare - I really wish you would/could...

We shouldn't be here to question their product but instead only reply if you are actually interested or not for the job possibility.

Questioning a program like this is kind of like.. Why would anyone pay for Windows when there's Linux? Or why would anyone pay for MS Office when you can get OpenOffice for free!

They got a product they feel is possibly profitable and need a programmer to help develop it, can't we just leave it at that?

Thank you TK! I do appreciate people who understand what I'm asking for - which is skilled help for fair pay - no charity, no spec work. And I also appreciate your trying to keep the thread on topic...

It seems surprising to me that more Linux programmers wouldn't be enthused over a project that not only >pays< for their work, but will also promote whatever distro we use as the "engine" for the ETS globally. Not to mention that (if realized) the ETS would actually >help people<.

A way to (potentially) help people, promote Linux, and make money - all at the same time. Imagine that...

I'll sweeten the pie still more and say that the backer and I are both willing to give the programmer some equity in the project - this is not just a "work for hire". But so many no-budget losers tout equity, that I prefer to start by saying that we will pay a fair market rate for professional work. If the programmer is interested in equity, so much the better for all concerned.

jhecht, It would be nice if you provided a bit more details, if possible, or if you pointed something similar to what you want so people could get a picture of desired product complexity. And it would be nice to know how long you expect project to finish. Description of what you want is a bit "vague" - EST as described here can be simple GUI front-end (1 month of not very difficult work alone) over existing opensource recovery utilities, or it could mean writing really huge amount of code from scratch (which might turn into 6..12 month development hell and might require a team of several programmers).

Please do not see my reply as offer of services - I'm already "hired" in two projects, and can't take anything else now. It is just recommendation of what you could do to bring more attention from "right" people to your offer.

jhecht, It would be nice if you provided a bit more details, if possible, or if you pointed something similar to what you want so people could get a picture of desired product complexity. And it would be nice to know how long you expect project to finish. Description of what you want is a bit "vague" - EST as described here can be simple GUI front-end (1 month of not very difficult work alone) over existing opensource recovery utilities, or it could mean writing really huge amount of code from scratch (which might turn into 6..12 month development hell and might require a team of several programmers).

Please do not see my reply as offer of services - I'm already "hired" in two projects, and can't take anything else now. It is just recommendation of what you could do to bring more attention from "right" people to your offer.

1 - I'll provide >all< the details >after< someone signs my NDA, and gives me a Xerox of their driver's license or state ID. Right now, everything I'm going to say in public is in the first entry of this thread. If you read it carefully, some of your questions may be answered.

2 - I can't point you toward "anything like it" - because nothing else like it exists! If you think of the TRK with a GUI and certain semi-automated features, that's a good start...

3 - As the ETS works 'on top of' an existing distro, I've been told by other (over-committed) programmers that it is a relatively simple project, and could almost be done with shell scripting.

4 - We are flexible as to the timetable for the project. It is more important that it be done >right< than that it be done >fast<.

jhecht,
What is covered by your NDA? -- Just the programming concept, or also the the business model?

The NDA currently covers only the programming, but as soon as a final biz plan is drafted, I'd ask for a second one.

Quote:

Originally Posted by archtoad6

I am curious how you plan to make money from this. It's hard to suggest how to open the ETS source w/o knowing the business thinking that led to the conclusion that the ETS has to be closed.

We hope to make money by offering the ETS CD for free, and charging money for the data retrieval service it provides. Since the ETS sits 'on top of' an unmodified Linux distro, I and my backer feel it must be closed code to prevent people ripping it off - or at least making it harder to do so. Any program or device can be reverse-engineered, given enough time and effort. As my backer says, "Patent the bottleneck, not the bottle." The bottle is a few billion Windows users, some of whom will always need data recovery. The bottleneck is the expertise needed to do data recovery with Linux or something like the TRK. The ETS is the floodgate to make data recovery easy for the masses - who will (hopefully) be happy to pay a fair price for the service it provides. The main difference between the ETS and all other currently available tools is >ease of use<.

Quote:

Originally Posted by archtoad6

BTW, does anyone think TRK is easy to use, let alone possible for the average non-Linux user faced w/ an emergency?

NO! The TRK is NOT easy/possible to use for the average Windows user. That's part of what led me to devise the ETS. However, this fact does not seem to be obvious to some Linux users...

If he's offering to pay a fair rate for the work, then I don't see why anyone cares if the product is viable in the market. It is, or it isn't - you get paid anyway.

I might be interested in talking about this, but I find I have no handle at all on the scope of the job, which deters me. It could be quite a formidable task, depending.

Presently I do have enough work for myself, but I have been giving serious consideration to expanding anyway and hiring employees. It has been awhile since I directed a development team, but I have done it successfully in the past for other people and might be interested in doing it for myself.

And if anyone is curious, here is the exact wording of my NDA, and its accompanying instructions. I'm not exactly asking for your firstborn child...
-------------------------

CONFIDENTIALITY AGREEMENT

I,_______________________________________("Recipient") acknowledge and
agree that all information relating to__”The Emergency Transfer System” - a unique computer program and computer networking arrangement, designed to permit recovery of data from non-booting computers____________________________________________
(collectively referred to as "Information") which has been or will be disclosed by John Hechtman ("Discloser") has been and will be received by Recipient in confidence; that Recipient will not disclose the Information to others; that Recipient will not use the Information for himself or others without written permission from Discloser and he will return to Discloser upon request any written or other documentary description of the Information provided to him by Discloser.

Not withstanding the foregoing, Recipient will not be prevented from using or disclosing any Information received from Discloser which;

1. Was known to Recipient prior to disclosure by Discloser.
2. Was a matter of public knowledge or subsequently becomes public knowledge through no violation of this Agreement.
3. Becomes known to the Recipient on a non-confidential basis from a source other than Discloser.

Agreed to:

By:_________________________________________________________________

Date:_______________________________________________________________

By:_________________________________________________________________
John Hechtman

Date:_______________________________________________________________

*NOTES ON USING THE FORM ABOVE*

1. This is a generic form. Put your full legal name on the first blank line (before the word "Recipient").

2. Sign your full name on the FIRST line that says By:
PRINT your name under your signature and fill in the date.

3. Include some other I.D. I have to be able to trace you or this form isn't worth much. A Xerox of a current drivers license, and some other photo I.D. will do. Or any other way that I can easily verify you.

5. Mail the form back to me. My address is:

John Hechtman
410 West 46 St #3C
New York NY 10036
USA

Thanks for the interest!

John Hechtman
Cell 917-628-0192
Home 212-586-4633
Service 212-459-4323