Re: Fw: pico and/or nano in the releases and snapshots
On 2010-02-03, Giridhari giridh...@live.com.au wrote: I was very comfortable with pico, and nano. I am running a new system with multiprocessor kernel, and currently have no support for the ZTE MF626 modem I connect via cellular network with. search the list archives for suggestions about the MF626. the diff for sys/dev/usb is probably ok, the problem the person trying it had was most likely to do with ppp configuration. I have tried installing the package of pico but it failed, so I installed it's dependencies, but pico still would not install because it had partially installed, would not pkg_delete (not even when forced), and I could not find a way to clean this up. failed? how? this is a really poor quality bug report. if you spent the time to write a good bug report instead of ranting, you would have it running by now. packages work pretty well for a lot of people. I fly with those. PLEASE INCLUDE PICO OR NANO OR BOTH IN A NEW SNAPSHOT pico is part of pine/alpine, Apache 2 licensed, not suitable for adding to base. nano is GPLv3 licensed, again not suitable for adding to base.
Re: Fw: pico and/or nano in the releases and snapshots
Giridhari wrote: blah blah pico or nano blah blah part of the distribution. and more blah blah blah. All that because you find 'pkg_add pico or pkg_add nano too difficult to type? -- -RSM http://www.erratic.ca
Re: Fw: pico and/or nano in the releases and snapshots
El 04/02/2010 0:52, Giridhari escribis: Hare Krsna. From: Giridhari Sent: Thursday, February 04, 2010 7:37 AM To: dera...@cvs.openbsd.org ; dera...@openbsd.org Subject: Fw: pico and/or nano in the releases and snapshots ATTENTION Last night I saved a rat from certain death at the hands of a cat whose ovaries had been cut out. This is the cutting edge of bhakti in the interests of OpenBSD. You have been notified. Note: The below message has been slightly adjusted to that which was sent to dera...@theos.org. From: Giridhari Sent: Thursday, February 04, 2010 7:28 AM To: dera...@theos.com Subject: pico and/or nano in the releases and snapshots Hare Krsna Mr. DeRaadt. I am trying to write a new security implementation for OpenBSD, but find vi to be clumsy and hampering. I was very comfortable with pico, and nano. I am running a new system with multiprocessor kernel, and currently have no support for the ZTE MF626 modem I connect via cellular network with. I have tried installing the package of pico but it failed, so I installed it's dependencies, but pico still would not install because it had partially installed, would not pkg_delete (not even when forced), and I could not find a way to clean this up. I would really appreciate if pico or nano, which are simple and elegant, perhaps not with the frills vi uses apparently seem to appreciate, but simple and natural nonetheless, we part of the distribution. I fly with those. PLEASE INCLUDE PICO OR NANO OR BOTH IN A NEW SNAPSHOT, and from now-on, and please overlook the apparent justifications for vi-only exclusivity, and help please. FOR BHAKTA GIRIDHARI. Krsna is your friend. PLEASE!!! I know its is a non-standard request, but honestly, vi is so clumsy, and I have LOTS of coding to do, including writing support for umodem for the MF626, and I would like to write it as a learning exercise in assembly. The new security mechanism is brute force resilient, and it is for particularly nasty weather. Pull a Torvaldsesque dictatorship because-I-said-so if you have to. Hare Bol. You're loosing your time, not only for asking something like put MY favourite s**t on YOUR system but also for using something like pico/nano as text editor. It's the most improductive thing I've seen in my life (comparing to vi/vim/vi-clones). What makes vi/Vim editors so clumsy and hampering it's the same that makes Photoshop better than MSpaint: design with productivity in mind. In the worst case you can make your own iso with pino/nano/whatever in it, but seriously, if I were you, I would learn how to use vi/Vim editors ASAP, it's in ALL unix-like systems, use vi, and you will never have to use another text editor in your life. By the way, this was written using Vim. -J
Re: Fw: pico and/or nano in the releases and snapshots
He's not asking you to do it, it is all up to the LordKrsna in this case. Mehma === On Wed, Feb 3, 2010 at 4:35 PM, Scott McEachern sc...@erratic.ca wrote: Giridhari wrote: blah blah pico or nano blah blah part of the distribution. and more blah blah blah. All that because you find 'pkg_add pico or pkg_add nano too difficult to type? -- -RSM http://www.erratic.ca
Re: Fw: pico and/or nano in the releases and snapshots
I've been avoiding this OP, but I guess I'll weigh in now. This smells like roe. Don't feed it. On Thu, Feb 04, 2010 at 01:54:07AM +0100, Jesus Sanchez wrote: El 04/02/2010 0:52, Giridhari escribis: Hare Krsna. From: Giridhari Sent: Thursday, February 04, 2010 7:37 AM To: dera...@cvs.openbsd.org ; dera...@openbsd.org Subject: Fw: pico and/or nano in the releases and snapshots ATTENTION Last night I saved a rat from certain death at the hands of a cat whose ovaries had been cut out. This is the cutting edge of bhakti in the interests of OpenBSD. You have been notified. Note: The below message has been slightly adjusted to that which was sent to dera...@theos.org. From: Giridhari Sent: Thursday, February 04, 2010 7:28 AM To: dera...@theos.com Subject: pico and/or nano in the releases and snapshots Hare Krsna Mr. DeRaadt. I am trying to write a new security implementation for OpenBSD, but find vi to be clumsy and hampering. I was very comfortable with pico, and nano. I am running a new system with multiprocessor kernel, and currently have no support for the ZTE MF626 modem I connect via cellular network with. I have tried installing the package of pico but it failed, so I installed it's dependencies, but pico still would not install because it had partially installed, would not pkg_delete (not even when forced), and I could not find a way to clean this up. I would really appreciate if pico or nano, which are simple and elegant, perhaps not with the frills vi uses apparently seem to appreciate, but simple and natural nonetheless, we part of the distribution. I fly with those. PLEASE INCLUDE PICO OR NANO OR BOTH IN A NEW SNAPSHOT, and from now-on, and please overlook the apparent justifications for vi-only exclusivity, and help please. FOR BHAKTA GIRIDHARI. Krsna is your friend. PLEASE!!! I know its is a non-standard request, but honestly, vi is so clumsy, and I have LOTS of coding to do, including writing support for umodem for the MF626, and I would like to write it as a learning exercise in assembly. The new security mechanism is brute force resilient, and it is for particularly nasty weather. Pull a Torvaldsesque dictatorship because-I-said-so if you have to. Hare Bol. You're loosing your time, not only for asking something like put MY favourite s**t on YOUR system but also for using something like pico/nano as text editor. It's the most improductive thing I've seen in my life (comparing to vi/vim/vi-clones). What makes vi/Vim editors so clumsy and hampering it's the same that makes Photoshop better than MSpaint: design with productivity in mind. In the worst case you can make your own iso with pino/nano/whatever in it, but seriously, if I were you, I would learn how to use vi/Vim editors ASAP, it's in ALL unix-like systems, use vi, and you will never have to use another text editor in your life. By the way, this was written using Vim. -J
Re: Fw: pico and/or nano in the releases and snapshots
Wow this easily is the best troll of the year so far. On Thu, Feb 04, 2010 at 10:52:32AM +1100, Giridhari wrote: Hare Krsna. From: Giridhari Sent: Thursday, February 04, 2010 7:37 AM To: dera...@cvs.openbsd.org ; dera...@openbsd.org Subject: Fw: pico and/or nano in the releases and snapshots ATTENTION Last night I saved a rat from certain death at the hands of a cat whose ovaries had been cut out. This is the cutting edge of bhakti in the interests of OpenBSD. You have been notified. Note: The below message has been slightly adjusted to that which was sent to dera...@theos.org. From: Giridhari Sent: Thursday, February 04, 2010 7:28 AM To: dera...@theos.com Subject: pico and/or nano in the releases and snapshots Hare Krsna Mr. DeRaadt. I am trying to write a new security implementation for OpenBSD, but find vi to be clumsy and hampering. I was very comfortable with pico, and nano. I am running a new system with multiprocessor kernel, and currently have no support for the ZTE MF626 modem I connect via cellular network with. I have tried installing the package of pico but it failed, so I installed it's dependencies, but pico still would not install because it had partially installed, would not pkg_delete (not even when forced), and I could not find a way to clean this up. I would really appreciate if pico or nano, which are simple and elegant, perhaps not with the frills vi uses apparently seem to appreciate, but simple and natural nonetheless, we part of the distribution. I fly with those. PLEASE INCLUDE PICO OR NANO OR BOTH IN A NEW SNAPSHOT, and from now-on, and please overlook the apparent justifications for vi-only exclusivity, and help please. FOR BHAKTA GIRIDHARI. Krsna is your friend. PLEASE!!! I know its is a non-standard request, but honestly, vi is so clumsy, and I have LOTS of coding to do, including writing support for umodem for the MF626, and I would like to write it as a learning exercise in assembly. The new security mechanism is brute force resilient, and it is for particularly nasty weather. Pull a Torvaldsesque dictatorship because-I-said-so if you have to. Hare Bol.
Re: Fw: pico and/or nano in the releases and snapshots
On Wed, Feb 03, 2010 at 07:06:49PM -0600, Marco Peereboom wrote: Wow this easily is the best troll of the year so far. really? to me it looks like someone was trying to be funny and totally failed. I give it a two thumbs down. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: Fw: pico and/or nano in the releases and snapshots
Giridhari wrote: Hare Krsna. From: Giridhari Sent: Thursday, February 04, 2010 7:37 AM To: dera...@cvs.openbsd.org ; dera...@openbsd.org Subject: Fw: pico and/or nano in the releases and snapshots ATTENTION Last night I saved a rat from certain death at the hands of a cat whose ovaries had been cut out. This is the cutting edge of bhakti in the interests of OpenBSD. You have been notified. Note: The below message has been slightly adjusted to that which was sent to dera...@theos.org. From: Giridhari Sent: Thursday, February 04, 2010 7:28 AM To: dera...@theos.com Subject: pico and/or nano in the releases and snapshots Hare Krsna Mr. DeRaadt. I am trying to write a new security implementation for OpenBSD, but find vi to be clumsy and hampering. I was very comfortable with pico, and nano. I am running a new system with multiprocessor kernel, and currently have no support for the ZTE MF626 modem I connect via cellular network with. I have tried installing the package of pico but it failed, so I installed it's dependencies, but pico still would not install because it had partially installed, would not pkg_delete (not even when forced), and I could not find a way to clean this up. I would really appreciate if pico or nano, which are simple and elegant, perhaps not with the frills vi uses apparently seem to appreciate, but simple and natural nonetheless, we part of the distribution. I agree, vi is terribly complicated and confusing to use. That is way I have always found ed to be a wonderful editor It is in the base and ALWAYS works even under the most terrifying and frightening conditions. Long Live ED! I fly with those. PLEASE INCLUDE PICO OR NANO OR BOTH IN A NEW SNAPSHOT, and from now-on, and please overlook the apparent justifications for vi-only exclusivity, and help please. FOR BHAKTA GIRIDHARI. Krsna is your friend. PLEASE!!! I know its is a non-standard request, but honestly, vi is so clumsy, and I have LOTS of coding to do, including writing support for umodem for the MF626, and I would like to write it as a learning exercise in assembly. The new security mechanism is brute force resilient, and it is for particularly nasty weather. Pull a Torvaldsesque dictatorship because-I-said-so if you have to. Hare Bol. -- A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein
Re: Fw: pico and/or nano in the releases and snapshots
On Thu, Feb 4, 2010 at 11:35 AM, Scott McEachern sc...@erratic.ca wrote: Giridhari wrote: blah blah pico or nano blah blah part of the distribution. and more blah blah blah. All that because you find 'pkg_add pico or pkg_add nano too difficult to type? -- -RSM http://www.erratic.ca Or not be an arse and learn vi. Giridhari, I once thought like you did. Then I discovered a wonderful resource - a mug that is sold by ThinkGeek. It has all of the commands you could hope to need, and how to use them. The graphic that's used on the cup is freely downloadable, so you can blow it up to A3 and stick it on the wall behind your computer for easy reference. Believe me, learning how to use vi will save you a lot of headaches in the long run. -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
Re: Fw: pico and/or nano in the releases and snapshots
Hello, While you're likely a troll, you may just be some sad religious zealot ranting on a mailing list. If you're not fond of vi(1), you may be interested in mg(1).. while it's not exactly the same as pico or nano, it's not that far off. Keep it off the lists next time, -Bryan.
