Re: install-prompt for missing features (Was: Re: Pull in upstream before 9.1 code freeze?)
On Thursday 05 Jul 2012 13:09:05 per...@pluto.rain.com wrote: Doug Barton do...@freebsd.org wrote: ... something like this would be *really* valuable to ease the transition for people coming from a Linux background. I'm sure some folks here would count this as a reason *not* to provide it :- I think the idea is quite silly all in all - There are 23k Ports a lot of which will have executeables - so everytime I make a typo - a database with - say 30,000-40,000 elements and give me a list back of things I could install from say the russian ports - I don't speak russian. I suggest looking at extending locate(1) or apropos(1) instead. Installed as a default in the shell I would count as a major reason to abandon FreeBSD. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: install-prompt for missing features (Was: Re: Pull in upstream before 9.1 code freeze?)
On Thu, Jul 05, 2012 at 10:32:16AM +0100, Thomas Sparrevohn wrote: On Thursday 05 Jul 2012 13:09:05 per...@pluto.rain.com wrote: Doug Barton do...@freebsd.org wrote: ... something like this would be *really* valuable to ease the transition for people coming from a Linux background. I'm sure some folks here would count this as a reason *not* to provide it :- I think the idea is quite silly all in all - There are 23k Ports a lot of which will have executeables - so everytime I make a typo - a database with - say 30,000-40,000 elements and give me a list back of things I could install from say the russian ports - I don't speak russian. I suggest looking at extending locate(1) or apropos(1) instead. Installed as a default in the shell I would count as a major reason to abandon FreeBSD. I would consider abandoning a OS that you originally installed for its functionality pretty silly but hey ... its a free world. And so is diabling things or choosing a optin. -- - (2^(N-1)) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
install-prompt for missing features (Was: Re: Pull in upstream before 9.1 code freeze?)
On 07/04/2012 15:57, Yuri wrote: On 07/04/2012 15:08, Doug Barton wrote: First, I agree that being able to turn it off should be possible. But I can't help being curious ... why would you *not* want a feature that tells you what to install if you type a command that doesn't exist on the system? Given the potentially controversial nature of this feature, it's maybe best to almost completely isolate it from the base system and make it into a port. Normally I would agree, but something like this would be *really* valuable to ease the transition for people coming from a Linux background. -- This .signature sanitized for your protection ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: install-prompt for missing features (Was: Re: Pull in upstream before 9.1 code freeze?)
On Wed, 04 Jul 2012 16:01:40 -0700 Doug Barton do...@freebsd.org wrote: On 07/04/2012 15:57, Yuri wrote: On 07/04/2012 15:08, Doug Barton wrote: First, I agree that being able to turn it off should be possible. But I can't help being curious ... why would you *not* want a feature that tells you what to install if you type a command that doesn't exist on the system? Given the potentially controversial nature of this feature, it's maybe best to almost completely isolate it from the base system and make it into a port. My first thought was to suggest it be a port as well, but I'm not sure that can be done sanely. Normally I would agree, but something like this would be *really* valuable to ease the transition for people coming from a Linux background. So would installing all the GNU tools instead of our own. To me, that's clearly a bad idea (yes, it's an ideological issue, but the issue is UI design, *not* licenses). For this kind of thing, I think a linux tools metaport (and group/option in the installer) would be a better approach. Linux users could then install one port, and possibly source a script in /usr/local/etc in their .bashrc, and get a system/shell that acts as much like some popular linux distro as the maintainers heart desired. Nuts, it may even be easy to config it for different distros. mike -- Mike Meyer m...@mired.org http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: install-prompt for missing features (Was: Re: Pull in upstream before 9.1 code freeze?)
On 07/04/2012 16:41, Jason Hellenthal wrote: On Wed, Jul 04, 2012 at 03:59:29PM -0700, Doug Barton wrote: On 07/04/2012 15:55, Jason Hellenthal wrote: Seeing as sudo plays a big part of this No ... not only is sudo not a necessary component, it shouldn't be involved at all. The feature works on debian/ubuntu for regular userspace commands. What are they using to authenticate for the install ? do you know ? Perhaps I misunderstood what you meant. Certainly you'd need proper permissions for installing something. What I meant was that the concept of prompting for uninstalled stuff does not, and should not require sudo to be involved in any way. Doug -- This .signature sanitized for your protection ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: install-prompt for missing features (Was: Re: Pull in upstream before 9.1 code freeze?)
On 2012-Jul-04 19:10:08 -0400, Mike Meyer m...@mired.org wrote: My first thought was to suggest it be a port as well, but I'm not sure that can be done sanely. The easiest way is probably to implement some form of generic command not found hook into sh(1) and tcsh(1) - in interactive mode, if a specific function exists, execute it rather than reporting an error message . The actual functionality to map a command name to a port and suggest it to the user could nten be implemented separately as a port and the user would enable it by adding the appropriate function definition to their .profile/.login/.[t]cshrc files. Note that I'm not currently interested in this functionality and am not volunteering to implement it. -- Peter Jeremy pgpLiwmiVDNPP.pgp Description: PGP signature
Re: install-prompt for missing features (Was: Re: Pull in upstream before 9.1 code freeze?)
On Wed, Jul 04, 2012 at 04:44:48PM -0700, Doug Barton wrote: On 07/04/2012 16:41, Jason Hellenthal wrote: On Wed, Jul 04, 2012 at 03:59:29PM -0700, Doug Barton wrote: On 07/04/2012 15:55, Jason Hellenthal wrote: Seeing as sudo plays a big part of this No ... not only is sudo not a necessary component, it shouldn't be involved at all. The feature works on debian/ubuntu for regular userspace commands. What are they using to authenticate for the install ? do you know ? Perhaps I misunderstood what you meant. Certainly you'd need proper permissions for installing something. What I meant was that the concept of prompting for uninstalled stuff does not, and should not require sudo to be involved in any way. Agreed. I didn't make that quite clear. Most of which I noticed from my very limited use of Fedora in the past since the only thing that was being installed was already built packages is the use of sudo to elevate privelages thats just why I refered to it in that manner. -- - (2^(N-1)) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: install-prompt for missing features (Was: Re: Pull in upstream before 9.1 code freeze?)
On Thu, Jul 05, 2012 at 11:11:10AM +1000, Peter Jeremy wrote: On 2012-Jul-04 19:10:08 -0400, Mike Meyer m...@mired.org wrote: My first thought was to suggest it be a port as well, but I'm not sure that can be done sanely. The easiest way is probably to implement some form of generic command not found hook into sh(1) and tcsh(1) - in interactive mode, if a specific function exists, execute it rather than reporting an error message . The actual functionality to map a command name to a port and suggest it to the user could nten be implemented separately as a port and the user would enable it by adding the appropriate function definition to their .profile/.login/.[t]cshrc files. Note that I'm not currently interested in this functionality and am not volunteering to implement it. Still appreciated input. I think it might be easier to make use securely of LD_PRELOAD and write a library with very specific functions and maybe even functions that will call in pkgng functions and such. LD_PRELOAD - Within interactive shell only load the functions... Check interactivity. Check return codes of commands issued. Make sure its a secure path and that any file referenced should not be owned by the user or writable by anyone else ... etc... etc... Check a database against plist mappings to packages for only those things that would be in the users PATH. Check to make sure that the user is in a preconfigured group of users authorized to be pestered by prompts.. - probably more - -- - (2^(N-1)) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: install-prompt for missing features (Was: Re: Pull in upstream before 9.1 code freeze?)
Doug Barton do...@freebsd.org wrote: ... something like this would be *really* valuable to ease the transition for people coming from a Linux background. I'm sure some folks here would count this as a reason *not* to provide it :- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
