As you may or may not know I work in IT. As such I need access to CLI network diagnostic tools. Today while troublshooting a network I was very surprised to see that nmap, traceroute, dig, etc were not included in BL. I'm not complaining, just surprised. So might I asked that they be included in the next release? They don't add very much in terms of file size and are very handy to have.
Same with RDP. Not VNC, but honest to goodness RDP.
Thanks for the consideration.
while some cli tools might take very little space, have you also looked at the dependencies?
also, following that logic, there would be many, many, many more things that would have to be included, and the .iso would soon go boom.
debian (the father of many distros) devs are arguing about these sorts of things, and i think we'll leave it to them.
like imbecil said: it's just an apt-get away!
I agree, please don't stop making suggestions. That is one of the most important things of a forum. Of speech and ideas in a free enlightened society.
Linux in the backwoods of the Rocky Mountains...
Beer is cool with me, it's my drink of choice.
I have this mindset that minus techies setting up Ubuntu for their parents, that the average Linux user is more advanced in terms of their computer knowledge and skill set than your typical Windows or Apple user. Therefore, I have come to expect basic network troubleshooting packages to be installed in almost every version of linux. Heck, they're built into Windows and OS X also.
I was quite shocked to see the ommision of some very basic tools, hence my suggestion.
Last edited by Temetka (2015-08-13 08:20:43)
Last edited by ohnonot (2015-08-13 06:58:44)
Last edited by Temetka (2015-08-13 08:23:33)
+1 for dig & traceroute in the basic install.
EDIT: and wireless-tools
Last edited by Head_on_a_Stick (2015-08-14 09:52:16)
wireless-tools and traceroute are present on my latest builds (not released yet, soon though). nmap is large, so probably not. Is including dig important?
Yes. Dig is important.
But that being said, it is also trivial to do an apt-get for it.
Actually, I am enjoying the discussion as being a general purpose distro, we will see all different points of view. Recently, I bought a new SSD as space was getting tight on the one I had. I then discovered my lightweight version of wtfbox did not have gparted installed. I was needing to migrate some partitions around. So mental note to self, even though gparted is somewhat bloat, considering I could have just done what I needed to do via parted, it is nice to have for cases like this. Which leads me to my next thought:
A light-weight or cd-size install should likely need more troubleshooting and system-level like tools than my general purpose install, as I will be going to it when I need to rescue something or when I don't need my primary drive mounted.
As @hhh can likely tell you, it is hard to imagine everything that needs to go into an install when building up a system from Live Build. If I am building it up from a command-line Jessie base, then the whole thing sort of grows organically. However, I can tell you from experience, it is easy to miss packages and I am terrible at keeping notes, so sometimes I have to run into something more than once before it makes it onto a Live Build.
Anyway, keep up the discussion. I have not been real active lately. RL stuff and all that but I do read these forums and make notes to myself when I see this stuff come up. Whether a package makes it into Bunsen or not, I get to learn from the different points of view.
Last edited by tknomanzr (2015-08-15 02:37:47)