Help Wanted

[HotShoe]

I have finished the major work on my DT file manager for linux. I would like to get some input on its functionality on various linux distros. This is a full function file manager for the linux console or a terminal, it is NOT a GUI program.

In the zip file is a man page, a pdf with the docs for use, change log, and the DT binary. I would appreciate any input, suggestions, and especially bug reports before I package it for .deb and .rpm distribution.

It is available at this link: www.mlsoft.org/dt.zip my email is in the docs for a more secure exchange if that is desired.

Thanks,
--- Jem

[Thaddy]

I can not review binaries. For that I need code.

[HotShoe]

Sorry man, that's not going to happen before the project is released to the world.

--- Jem

[Thaddy]

Then you are on your own. We can only help you when you show some source where you got stuck.

[HotShoe]

Thanks, but I am not stuck. The whole idea is to see if the BINARY runs on multiple platforrms, but allowing you to compile it on your own machine doesn't do me any good in that way does it? For get it, I thought that programmers might understand that concept.

Feel free to delete this thread.

[Thaddy]

I do not always need to compile sources, I want to read them.
That is usually enough to determine quality.
I used to work on Tandem and Burroughs mainframes, which lack F9 in their compilers: we wrote without testing on hardware and waited for a timeslot to run it.

[dbannon]

In addition to Thaddy's comments, many people are reluctant to run a 'black box' binary on our working machines. Especially if that someone is relatively new to this forum. Its just not a safe thing to do.

By having the source, we can, in theory, check it does not do something unexpected.

Thats how open source works. You have to decide if your project is open source or not !

Davo

[jamie]

Oh what's the matter I click on everything download everything run everything there is on the internet without a problem with a smile

[silvercoder70]

I know you probably mean well by sharing your project, and it’s always great to see people building things and contributing. But... in this day and age, most people are understandably reluctant to download a program from a website and run it, especially if it's not open source or doesn't come from a known and trusted source.

There are just too many risks out there, from malware to data theft, and users are right to be cautious. If you're serious about getting people to try your software, consider sharing the source code, signing your binaries, or even hosting it on a reputable platform like GitHub, GitLab, or SourceForge. That transparency builds trust and makes it much more likely that people will give your work a fair look.

No offense intended at all — just sharing some perspective from a user and developer standpoint. We’ve all become a little more careful, and for good reason.

[HotShoe]

I understand concerns about system security and trusting binaries. On linux it is easy to sandbox stuff, but I know most do not do that sort of thing. As far as releasing the source before the project is released to the public, that is just never going to happen. I've been doing contract programming for 47 years and have learned many lessons over that time. One of those lessons is that I control the source code, and only I can make changes to that source code until I determine that it is ready to be released. After that, all bets are off, but at least I can assure that the quality is there.

I have done many open source projects both in the DOS days  and for the linux community. I am aware of how it works. I appreciate all of the suggestions and I am aware that I do things differently than others, but the source stays on my machine until the project gets released. I'll stick to testing through my normal channels. I thought it would be nice to expand the testing pool, but I did not know that system killing binaries had become so prevalent in the linux world. 

Thanks for your time,
--- Jem

[af0815]

I thought it would be nice to expand the testing pool, but I did not know that system killing binaries had become so prevalent in the linux world. 

It is not depending on the platform. You can use ANY System in a network, to infect this. The world is harder and harder and any company or burgler want your data.

Not every sandbox is safe too, there are possibilities to break out of virtual machines too. And most people have not a isolated, hardened machine for testing purposes.

Its not on you, its on the actual times.