On 6/5/2014 6:05 PM, Erich Dollansky wrote:
Hi,
On Thu, 05 Jun 2014 15:09:53 -0500
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system
instead of outright breaking ports? The idiots are apparent
yle overhaul my friend.
-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Who-was-the-mental-genius-tp5918254p5918986.html
Sent from the freebsd-ports mailing list archive at Nabble.
On Sat, Jun 7, 2014 at 5:24 PM, Mark Linimon wrote:
> On Sun, Jun 08, 2014 at 12:42:27AM +0200, John Marino wrote:
> > The next time you are right will be the first time. [...] You are being
> > ridiculed because you're a boor and consistently wrong, which is not a
> > good combination.
>
> None
On Sun, Jun 08, 2014 at 12:42:27AM +0200, John Marino wrote:
> The next time you are right will be the first time. [...] You are being
> ridiculed because you're a boor and consistently wrong, which is not a
> good combination.
None of the above represents what I think FreeBSD ought to be about.
On 6/7/2014 18:52, Paul Schmehl wrote:
> I've searched. There's no notice in UPDATING. There was no
> announcement on the ports list. I found NOTHING to warn me of this
> problem except other people complaining of the same problem. 8.4 went
> EOL in September 2012. This problem was introduced w
On Fri 2014-06-06 17:17:40 UTC+0200, Baptiste Daroussin (b...@freebsd.org)
wrote:
> Yes it would have been a good idea to give a warning to the user about
> the fact that the ports tree won't be support long on after EOL of
> 8.3, given the ports tree will break again quite soon after EOL of 8.4
--On June 7, 2014 at 1:32:08 PM +0200 Michelle Sullivan
wrote:
Paul Schmehl wrote:
I appreciate the advice. I've elected to setup an alternate form of
backup (using rsync over ssh to backup each server to its sibling) so
I can upgrade to 8.4 without worrying about a loss. Once that's
compl
Paul Schmehl wrote:
>
> I appreciate the advice. I've elected to setup an alternate form of
> backup (using rsync over ssh to backup each server to its sibling) so
> I can upgrade to 8.4 without worrying about a loss. Once that's
> complete, I'll get the new backup system in place (using Storgrid
Jerry wrote:
> Really ...
> Hi, I am a FreeBSD user, and I would like to report a problem that doesn't
> exist. I have a theoretical solution for this unknown problem, but I cannot
> test it because I cannot create the environment.
>
> Seriously, there are plenty of real problems. Attempting to ant
Baptiste Daroussin wrote:
> The mental genius is me apparently (thanks for the kind words, btw) I'm
> responsible for both the pkg_install EOL message and for breaking ports tree
> with older make (btw you can recover with installing manually bmake).
>
That is quite a task... you can't easily
On 6/6/14, 7:52 PM, Mark Linimon wrote:
On Fri, Jun 06, 2014 at 04:10:03PM -0400, Jim Ohlstein wrote:
Not to get too far off topic but as a life long east coaster (except
for a short sojourn in the flatlands of Kansas), and being old
enough to know better, that is not "normal" east coast chidin
On Fri, Jun 06, 2014 at 04:10:03PM -0400, Jim Ohlstein wrote:
> Not to get too far off topic but as a life long east coaster (except
> for a short sojourn in the flatlands of Kansas), and being old
> enough to know better, that is not "normal" east coast chiding.
> Maybe that's normal northeast tal
eally* meant "no longer
supported" in this case, and you got bit, and got angry. Sadly, you have
no one to blame but yourself, since this was in fact well documented.
If I was not a polite southerner, perhaps I'd ask who was the mental
genius that expected to run an unsupported O
> On Jun 6, 2014, at 10:02 AM, Warren Block wrote:
>
>> On Fri, 6 Jun 2014, Paul Schmehl wrote:
>>
>> No offense was meant. I deliberately chose the subject to stimulate
>> discussion, which it has obviously done.
>
> Stimulating discussion without insulting people generally gives better
>
On Fri, 6 Jun 2014 11:02:48 -0600 (MDT), Warren Block stated:
> Stimulating discussion without insulting people generally gives better
> results.
That is debatable. After spending much of my life in a managerial role of one
kind or another, I have determined that you either have to kick them in
On Fri, 6 Jun 2014, Paul Schmehl wrote:
No offense was meant. I deliberately chose the subject to stimulate
discussion, which it has obviously done.
Stimulating discussion without insulting people generally gives better
results.
Look, we are all doing the best we can with what we've got.
--On June 6, 2014 at 5:17:40 PM +0200 Baptiste Daroussin
wrote:
On Fri, Jun 06, 2014 at 09:34:26AM -0500, Paul Schmehl wrote:
--On June 6, 2014 at 10:51:04 AM +0200 Michael Gmelin
wrote:
>
>
>> On 06 Jun 2014, at 10:22, John Marino
>> wrote:
>>
>>> On 6/6/2014 10:18, Alfred Perlstein wrot
On Fri, Jun 06, 2014 at 09:34:26AM -0500, Paul Schmehl wrote:
> --On June 6, 2014 at 10:51:04 AM +0200 Michael Gmelin
> wrote:
>
> >
> >
> >> On 06 Jun 2014, at 10:22, John Marino wrote:
> >>
> >>> On 6/6/2014 10:18, Alfred Perlstein wrote:
> >>> Sure, but really a couple of lines to warn peopl
--On June 6, 2014 at 10:51:04 AM +0200 Michael Gmelin
wrote:
On 06 Jun 2014, at 10:22, John Marino wrote:
On 6/6/2014 10:18, Alfred Perlstein wrote:
Sure, but really a couple of lines to warn people and wave them towards
next steps is probably advisable next time.
Maybe we can alter th
On 6/6/2014 16:19, Paul Schmehl wrote:
> --On June 6, 2014 at 8:35:06 AM +0200 John Marino
> I have no idea why you've decided to assume the role of preacher and
> tell me what to do, but I can assure you that you are completely
> ignorant of the circumstances behind my complaints. They have
> abs
--On June 6, 2014 at 5:27:58 PM +1000 Dewayne Geraghty
wrote:
On 6/06/2014 11:05 AM, Erich Dollansky wrote:
Hi,
On Thu, 05 Jun 2014 15:09:53 -0500
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning
--On June 6, 2014 at 8:35:06 AM +0200 John Marino
wrote:
On 6/6/2014 05:37, Paul Schmehl wrote:
Something like that would have been more than adequate. As I pointed
out, the warning you get about pkgng and the 9/1/2014 deadline is
perfect. It's been there for a couple of months, and it pops
On 2014-06-05 15:51, Dewayne Geraghty wrote:
On 6/06/2014 6:09 AM, Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running the
asyl
On Fri, 6 Jun 2014, John Marino wrote:
On 6/6/2014 10:18, Alfred Perlstein wrote:
Sure, but really a couple of lines to warn people and wave them towards
next steps is probably advisable next time.
Maybe we can alter the "uname -a" string to show the EOL so that every
time the machine boots
On 06/06/14 04:32, Paul Schmehl wrote:
> --On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi
> wrote:
>
>> On 06/05/14 23:43, Paul Schmehl wrote:
>>> --On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
>>> wrote:
>>>
Paul Schmehl wrote:
> That decided it was a good idea
> On 06 Jun 2014, at 10:22, John Marino wrote:
>
>> On 6/6/2014 10:18, Alfred Perlstein wrote:
>> Sure, but really a couple of lines to warn people and wave them towards
>> next steps is probably advisable next time.
>
> Maybe we can alter the "uname -a" string to show the EOL so that every
>
On 6/6/2014 10:18, Alfred Perlstein wrote:
> Sure, but really a couple of lines to warn people and wave them towards
> next steps is probably advisable next time.
>
Maybe we can alter the "uname -a" string to show the EOL so that every
time the machine boots you see it on top of the MOTD.
:)
Of
On 6/5/14, 11:35 PM, John Marino wrote:
On 6/6/2014 05:37, Paul Schmehl wrote:
Something like that would have been more than adequate. As I pointed
out, the warning you get about pkgng and the 9/1/2014 deadline is
perfect. It's been there for a couple of months, and it pops up ever
time you d
On 6/06/2014 11:05 AM, Erich Dollansky wrote:
> Hi,
>
> On Thu, 05 Jun 2014 15:09:53 -0500
> Paul Schmehl wrote:
>
>> That decided it was a good idea to completely break ports to force
>> people to upgrade? You couldn't come up with a warning system
>> instead of outright breaking ports? The idi
On 6/6/2014 05:37, Paul Schmehl wrote:
> Something like that would have been more than adequate. As I pointed
> out, the warning you get about pkgng and the 9/1/2014 deadline is
> perfect. It's been there for a couple of months, and it pops up ever
> time you do a port. If you miss that and don't
--On June 5, 2014 at 8:08:35 PM -0700 Alfred Perlstein
wrote:
On 6/5/14, 7:32 PM, Paul Schmehl wrote:
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi
wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
wrote:
Paul Schmehl wr
On 6/5/14, 7:32 PM, Paul Schmehl wrote:
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi
wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't c
Hi,
On Thu, 05 Jun 2014 15:09:53 -0500
Paul Schmehl wrote:
> That decided it was a good idea to completely break ports to force
> people to upgrade? You couldn't come up with a warning system
> instead of outright breaking ports? The idiots are apparently
> running the asylum. {{sigh}}
>
th
For me, I had to upgrade an 8.2 FreeBSD to 10.0 current.
and got the same issue...
What I did was:
1) copy the "make" program from the 10.0 series to replace
the /usr/bin/make
2) copy via tar /usr/src /usr/obj from the 10.0 to the 8.2
cd /usr/src
export KERNCONF to the config in /usr/src/sys/amd6
W dniu 2014-06-05 23:43, Paul Schmehl pisze:
> --On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
> wrote:
>
>> Paul Schmehl wrote:
>>
>>> That decided it was a good idea to completely break ports to force
>>> people to upgrade? You couldn't come up with a warning system instead
>>
On 06/05/14 23:43, Paul Schmehl wrote:
> --On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
> wrote:
>
>> Paul Schmehl wrote:
>>
>>> That decided it was a good idea to completely break ports to force
>>> people to upgrade? You couldn't come up with a warning system instead
>>> of ou
On 6/5/2014 23:43, Paul Schmehl wrote:
> --On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
> wrote:
>
>> Paul Schmehl wrote:
>>
>>> That decided it was a good idea to completely break ports to force
>>> people to upgrade? You couldn't come up with a warning system instead
>>> of ou
--On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running
Paul Schmehl wrote:
> That decided it was a good idea to completely break ports to force people to
> upgrade? You couldn't come up with a warning system instead of outright
> breaking ports? The idiots are apparently running the asylum. {{sigh}}
It might help to know exactly what you're talkin
On 6/06/2014 6:09 AM, Paul Schmehl wrote:
> That decided it was a good idea to completely break ports to force
> people to upgrade? You couldn't come up with a warning system instead
> of outright breaking ports? The idiots are apparently running the
> asylum. {{sigh}}
>
Are you referring to t
That decided it was a good idea to completely break ports to force people
to upgrade? You couldn't come up with a warning system instead of outright
breaking ports? The idiots are apparently running the asylum. {{sigh}}
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious,
42 matches
Mail list logo
