guys, it was so funny to see you biting each other.
come on, can you do it one more time, please ?
2012/1/23 Nico Kadel-Garcia nka...@gmail.com
On Sun, Jan 22, 2012 at 5:38 PM, L. V. Lammert l...@omnitec.net wrote:
On Sun, 22 Jan 2012, Philip Guenther wrote:
snip the BS
There is no
2012/1/23 Lars nore...@z505.com:
Also MySQL became a billion dollar company and it doesn't even sell any
product
http://www.mysql.com/products/
http://www.mysql.com/products/cluster/faq.html#20
On Sat, Jan 21, 2012 at 11:35 AM, Anonymous cri...@ecn.org wrote:
Lars, you ass-licking dog, what I am saying to you and prima donnas like you
is you can be a good human being and that is more important than all the
patches and code in the world. ...
And yet you, L.V. Lammert, use the code,
On Sun, Jan 22, 2012 at 3:35 AM, Anonymous cri...@ecn.org wrote:
I asked this before but I guess you didn't see it. So if you contribute
much more code to OpenBSD than someone else do you automatically get
license to insult people and post 100% noise as some kind of reward?
Since you're such
And yet you, L.V. Lammert,
I am not Lammert. I don't approve of the way Lammert handled the issue but
that is separate from the fairly regular piss parades and walls of text
taking place here when a simple answer would work. The consensus of the
vocal parties is that contribution = abuseLicense
On Sun, 22 Jan 2012, Anonymous wrote:
Whooever told him to man up was justified.
HUH?? WTF?? That's a CROCK!!
It's amuzing to watch the flames flying, however, there *ARE* some people
on the list that have an interest in solving problems.
It IS unfortunate, however, that the actual PROBLEM
On Sun, 22 Jan 2012, Philip Guenther wrote:
And yet you, L.V. Lammert, use the code, don't clearly explain what
was failing on your system, and behave in exactly the way you rant
about.
Now THAT's quite laughahble! The ONLY problem here is with all the IDIOTS
spouting CRAP with no interest
For those that happen to google this thread trying to find the
solution: upgrading *would* have fixed his system due to the various
steps done during upgrades,
BZZZT! WRONG! If the system rebooted clean [which this one did], the
problem would not have been found during a normal upgrade.
On Sun, 22 Jan 2012, Amit Kulkarni wrote:
a recent system does a fsck -fp of each partition, so it would have
fixed your problem.
Would 4.4? 4.5? I don't think so, .. if you recall, the system is 4.3 so a
normal upgrade (i.e. not a clean install) would not have fixed the
problem.
you are
On Sun, Jan 22, 2012 at 12:39 PM, L. V. Lammert l...@omnitec.net wrote:
On Sun, 22 Jan 2012, Amit Kulkarni wrote:
a recent system does a fsck -fp of each partition, so it would have
fixed your problem.
Would 4.4? 4.5? I don't think so,
You keep stating things that you believe to be true
On Sun, 22 Jan 2012, Philip Guenther wrote:
snip the BS
There is no way of knowing if it would have found the problem, so why
continue with this drivel? Contrary to the lengthy diatribes here trying
to distract from the original problem an solution:
1) The problem with locate was traced to a
Lammert, I am going to have to ask you to leave our lists.
You are no longer welcome here.
On Sun, Jan 22, 2012 at 5:38 PM, L. V. Lammert l...@omnitec.net wrote:
On Sun, 22 Jan 2012, Philip Guenther wrote:
snip the BS
There is no way of knowing if it would have found the problem, so why
continue with this drivel? Contrary to the lengthy diatribes here trying
to distract from the
Nico Kadel-Garcia wrote:
...
The yelling and namecalling is unfortunate. But from observation and
professional experience, if you want professional grade support for a
software livecycle of over 3 years, you should be willing to pay for
it.
It would be cool to see more BSD consulting
On 23 January 2012 04:04, Lars nore...@z505.com wrote:
It would be cool to see more BSD consulting companies and support
companies, and web hosting companies. If I was to look for an OpenBSD web
hosting company, I'd have difficulty finding one. There are far too many
LINUX web hosts out
I notice you spend much more time scolding people than actually saying
anything worthwhile. You should work on yourself and find out why that is.
Perhaps you could benefit from some anger management training?
I notice that Henning is contributing much more code to OpenBSD than
you ever have
Lars Hansson romaby...@gmail.com whined
I notice you spend much more time scolding people than actually saying
anything worthwhile. You should work on yourself and find out why that
is. Perhaps you could benefit from some anger management training?
I notice that Henning is contributing
With apologies to all, this will be my last reply on this thread.
On Wed, Jan 18, 2012 at 04:18:11PM -0600, L. V. Lammert wrote:
| At 03:59 PM 1/18/2012, you wrote:
| Wait - so there's an issue that you have identified, with help from
| members on this list ? And you're refusing to divulge the
On Wed, Jan 18, 2012 at 10:15 AM, L. V. Lammert l...@omnitec.net wrote:
It was truly a shame that so many people here prefer to start their
flamethrowers rather than offer any sort of constructive information! In
this case, THE PROBLEM HAS BEEN IDENTIFIED AND IT WOULD MOST LIKELY NOT
HAVE
BEEN
On Thu, 19 Jan 2012, Paul de Weerd wrote:
With apologies to all, this will be my last reply on this thread.
Really? That WOULD be nice. Hopefully you will abide by your promise.
Lee
L. V. Lammert wrote on Thu, Jan 19, 2012 at 09:20:44AM -0600:
On Thu, 19 Jan 2012, Paul de Weerd wrote:
With apologies to all, this will be my last reply on this thread.
Really? That WOULD be nice. Hopefully you will abide by your promise.
Sure, I'd appreciate if Paul wrote a bit more, in
It was truly a shame that so many people here prefer to start their
flamethrowers rather than offer any sort of constructive information!
In this case, THE PROBLEM HAS BEEN IDENTIFIED AND IT WOULD MOST
LIKELY NOT HAVE BEEN FIXED WITH A NORMAL UPGRADE! !! !!!
Before reading further,
On 2012 Jan 18 (Wed) at 10:15:34 -0600 (-0600), L. V. Lammert wrote:
:Running the find separately identified the file system problem, and
:it was easily fixed as a result.
So, what was the actual problem? Permissions?
--
There are two types of people in this world, good and bad. The good
On 2012 Jan 18 (Wed) at 10:15:34 -0600 (-0600), L. V. Lammert wrote:
:Running the find separately identified the file system problem, and
:it was easily fixed as a result.
So, what was the actual problem? Permissions?
Idiot near the keyboard.
On Wed, 18 Jan 2012, Theo de Raadt wrote:
On 2012 Jan 18 (Wed) at 10:15:34 -0600 (-0600), L. V. Lammert wrote:
:Running the find separately identified the file system problem, and
:it was easily fixed as a result.
So, what was the actual problem? Permissions?
Idiot near the keyboard.
On Wed, 18 Jan 2012, Peter Hessler wrote:
On 2012 Jan 18 (Wed) at 10:15:34 -0600 (-0600), L. V. Lammert wrote:
:Running the find separately identified the file system problem, and
:it was easily fixed as a result.
So, what was the actual problem? Permissions?
No, a file system problem. In
Wait - so there's an issue that you have identified, with help from
members on this list ? And you're refusing to divulge the exact
details that would probably help resolve the problem in future OpenBSD
releases ?
What the hell.
That's a great thank you to all those people that helped you, Lee,
At 03:59 PM 1/18/2012, you wrote:
Wait - so there's an issue that you have identified, with help from
members on this list ? And you're refusing to divulge the exact
details that would probably help resolve the problem in future OpenBSD
releases ?
Of course, an exposition was to be expected,
On Sat, Jan 14, 2012 at 10:07:15PM -0600, L. V. Lammert wrote:
| On Sat, 14 Jan 2012, Philip Guenther wrote:
|
| Any progress? I see plenty of replies to the people that you *don't*
| think are helping you but no reply to my question about what user you
| think locate.updatedb runs as,
Perhaps he did. Wouldn't it be useful to help the guy trying to help
you (you know, the wheat) by giving a really simple and
straightforward answer, even if it is repeating yourself ? Probably
would've been less typing than what you just did (e.g. Sorry, I think
it runs as user ).
On Thu, 12 Jan 2012 02:15:39 -0700
Duncan Patton a Campbell campb...@neotext.ca wrote:
On Wed, 11 Jan 2012 13:47:48 -0600
L. V. Lammert l...@omnitec.net wrote:
At 01:30 PM 1/11/2012, Jeremy O'Brien wrote:
4.3 was released May 1, 2008. That's almost 4 years old software. What
are you
On Fri, Jan 13, 2012 at 1:02 PM, L. V. Lammert l...@omnitec.net wrote:
Thanks again to those that actually read the original question, .. I am
continuing to try and resolve the issue.
Any progress? I see plenty of replies to the people that you *don't*
think are helping you but no reply to my
On Sat, 14 Jan 2012, Philip Guenther wrote:
Any progress? I see plenty of replies to the people that you *don't*
think are helping you but no reply to my question about what user you
think locate.updatedb runs as, something which does factor into being
able to solve this...
The answer was
On Thu, Jan 12, 2012 at 03:28:37PM +0100, Fritz Wuehler wrote:
Hey Henning,
off-topic diatribes? coming to this mailing list asking for help about
a 4 year old release when it is clearly documented that you are
ENTIRELY ON YOUR OWN with releases older than a year is at least off
topic,
On Fri, Jan 13, 2012 at 08:38:37AM -0500, Kenneth R Westerback wrote:
On Thu, Jan 12, 2012 at 03:28:37PM +0100, Fritz Wuehler wrote:
Hey Henning,
off-topic diatribes? coming to this mailing list asking for help about
a 4 year old release when it is clearly documented that you are
Spoke the self-proclaimed guru:
Upgrading is a rule of this list. It cannot get anymore simple than that.
So you're saying OpenBSD and Windows are really the same? No need to
actually diagnose problems just upgrade. Whatever it is is fixed in the
current version. Arsewipe LOL
On 01/13/12 14:47, Otto Moerbeek wrote:
On Fri, Jan 13, 2012 at 08:38:37AM -0500, Kenneth R Westerback wrote:
On Thu, Jan 12, 2012 at 03:28:37PM +0100, Fritz Wuehler wrote:
Hey Henning,
off-topic diatribes? coming to this mailing list asking for help about
a 4 year old release when it is
On 01/13/12 13:50, Fritz Wuehler wrote:
Spoke the self-proclaimed guru:
Upgrading is a rule of this list. It cannot get anymore simple than that.
So you're saying OpenBSD and Windows are really the same? No need to
actually diagnose problems just upgrade. Whatever it is is fixed in the
On Wed, 11 Jan 2012 20:28:57 +0100
Marian Hettwer wrote:
Try to look from a different angle here.
Say, you would have an old Debian Sarge release (years old) and you
would approach a debian mailing list with something is weird with
locate, pretty sure you would get a lot of advises to
On Thu, 12 Jan 2012, Kevin Chadwick wrote:
I'm surprised you've had so much help.
You shouldn't be, .. there *ARE* a few decent folks here on the list.
Personally and If I had time I'd want to find out the problem but I'd be
wiping and reinstalling from scratch anyway, especially with an
On Fri, Jan 13, 2012 at 03:02:35PM -0600, L. V. Lammert wrote:
| Personally and If I had time I'd want to find out the problem but I'd be
| wiping and reinstalling from scratch anyway, especially with an unknown
| cause.
|
| So, which is it? The attitude 'an upgrade will fix everything' is
On 2012-01-13, L. V. Lammert l...@omnitec.net wrote:
*Especially* in this case since locate is a standard utility with a shell
script that has not changed between 4.3 4.9, and I expect it hasn't for
5.0 either. If the system utilities have not changed, then the problem
must be elsewhere;
Oh,
On Jan 11, 2012, at 4:08 PM, L. V. Lammert wrote:
On Wed, 11 Jan 2012, Philip Guenther wrote:
Agreed, .. but if locate.update does NOT run as root, that would seem to
indicate some problem other than permissions.
If you're saying what I think you're saying, then I disagree and think
your
* L. V. Lammert l...@omnitec.net [2012-01-11 20:48]:
Another typical reply - the question was has anyone ever seen
anything like this, .. or, perhaps, what could be causing it. No
need for the off-topic diatribes - a simple no would more than
suffice.
ah, you think the other kids won't find
FWIW, on my system it seems to work (and yes, I should upgrade!)
$ uname -a
OpenBSD foo.bar 4.3 GENERIC.MP#587 i386
On Wed, Jan 11, 2012 at 03:09:50PM -0600, L. V. Lammert wrote:
On Wed, 11 Jan 2012, Philip Guenther wrote:
Lesson #1: examine the anomalous data for clues.
So, you're
On Wed, 11 Jan 2012 13:47:48 -0600
L. V. Lammert l...@omnitec.net wrote:
At 01:30 PM 1/11/2012, Jeremy O'Brien wrote:
4.3 was released May 1, 2008. That's almost 4 years old software. What
are you expecting here? Someone to check out the code from that
version and deeply inspect what may be
On 2012-01-11 16.26, L. V. Lammert wrote:
Have a 4.3 server with a really weird problem: locate ONLY indexes one
[user file] partition! IOW, no binaries are indexed, nor is /usr/, /var, ..
Is this a new phenomenon? That is, did it use to work earlier and
something is now broken? In that case,
Hey Henning,
off-topic diatribes? coming to this mailing list asking for help about
a 4 year old release when it is clearly documented that you are
ENTIRELY ON YOUR OWN with releases older than a year is at least off
topic, if not outright rude.
I notice you spend much more time scolding
At 05:59 AM 1/12/2012, you wrote:
Is this a new phenomenon? That is, did it use to work earlier and
something is now broken? In that case, what did you change? :-)
Yes, .. nothing.
(I'm not even gonna comment on the rest of this discussion. Ah, yet I
just did, didn't I? Oh well, in that
On , LV Lammert l...@omnitec.net wrote:
Recommendations to upgrade are total BS - the system is 4.3 for reasons
which I will not share with the list because they are not germaine to any
issue raised herein. Such comments (beyond Theo's first one, to which he
is more than entltled) are
Have a 4.3 server [rest deleted]
There is a ton of documentation that makes it clear you are on your
own more than two releases back.
At 10:41 AM 1/11/2012, Theo de Raadt wrote:
Have a 4.3 server [rest deleted]
There is a ton of documentation that makes it clear you are on your
own more than two releases back.
So, you're advocating incomplete information? Is that not a bigger problem?
Lee
Have a 4.3 server [rest deleted]
There is a ton of documentation that makes it clear you are on your
own more than two releases back.
So, you're advocating incomplete information? Is that not a bigger problem?
No, I am advocating that you TAKE CARE OF YOUR OWN PROBLEMS YOURSELF.
We do not
So, you're advocating incomplete information? Is that not a bigger problem?
No, we don't support old releases. 4.3 is very old. You should update
your OS to something supported, and likely your problem will go away.
On Wed, Jan 11, 2012 at 9:49 AM, L. V. Lammert l...@omnitec.net wrote:
At 10:41 AM 1/11/2012, Theo de Raadt wrote:
Have a 4.3 server [rest deleted]
There is a ton of documentation that makes it clear you are on your
own more than two releases back.
So, you're advocating incomplete
At 01:04 PM 1/11/2012, Barry Grumbine wrote:
Bite the bullet, upgrade, life is better at 5.0
Sorry, but *UPGRADING* isn't the question - the question is why
locate is not working properly. If nobody has ever seen such a
problem, it would be quite more forthright to just admit that than
Bite the bullet, upgrade, life is better at 5.0
...knew I forgot something.
There aren't many North American mirrors that go back to 4.2. I was
fortunate to find obsd.cec.mtu.edu which Nick Holland recently
notified us that he needs to take down very soon.
After Looking through all the
On Wed, Jan 11, 2012 at 14:17, L. V. Lammert l...@omnitec.net wrote:
At 01:04 PM 1/11/2012, Barry Grumbine wrote:
Bite the bullet, upgrade, life is better at 5.0
Sorry, but *UPGRADING* isn't the question - the question is why locate is
not working properly. If nobody has ever seen such a
On 01/11/2012 02:30 PM, Jeremy O'Brien wrote:
On Wed, Jan 11, 2012 at 14:17, L. V. Lammertl...@omnitec.net wrote:
At 01:04 PM 1/11/2012, Barry Grumbine wrote:
Bite the bullet, upgrade, life is better at 5.0
Sorry, but *UPGRADING* isn't the question - the question is why locate is
not
At 01:30 PM 1/11/2012, Jeremy O'Brien wrote:
4.3 was released May 1, 2008. That's almost 4 years old software. What
are you expecting here? Someone to check out the code from that
version and deeply inspect what may be causing your problem, that is
more than likely already fixed in a later
They were valid replies, but a straw man argument at best. I think he
would have preferred to hear something more like:
Yeah, I saw something similar happen on my systems running an older
release. I don't really remember the release, but I do remember the
problem eventually went away
On Wed, Jan 11, 2012 at 14:47, L. V. Lammert l...@omnitec.net wrote:
At 01:30 PM 1/11/2012, Jeremy O'Brien wrote:
4.3 was released May 1, 2008. That's almost 4 years old software. What
are you expecting here? Someone to check out the code from that
version and deeply inspect what may be
Hi,
Am 11.01.12 20:17, schrieb L. V. Lammert:
At 01:04 PM 1/11/2012, Barry Grumbine wrote:
Bite the bullet, upgrade, life is better at 5.0
Sorry, but *UPGRADING* isn't the question - the question is why locate
is not working properly.
No. You were advised to upgrade, since 4.3 is not
On Wed, 11 Jan 2012, Marian Hettwer wrote:
Hi,
Am 11.01.12 20:17, schrieb L. V. Lammert:
At 01:04 PM 1/11/2012, Barry Grumbine wrote:
Bite the bullet, upgrade, life is better at 5.0
Sorry, but *UPGRADING* isn't the question - the question is why locate
is not working properly.
No.
Time for today's how to debug a problem lesson.
On Wed, Jan 11, 2012 at 7:26 AM, L. V. Lammert l...@omnitec.net wrote:
Have a 4.3 server with a really weird problem: locate ONLY indexes one [user
file] partition! IOW, no binaries are indexed, nor is /usr/, /var, ..
Lesson #1: examine the
On Wed, 11 Jan 2012, Philip Guenther wrote:
Also, in order to help others when they encounter a similar issue,
please be sure to post what the problem and/or solution were once you
figure them out.
Philip Guenther
Amen! At least there's a chance it would turn up in the search engines.
On Wed, 11 Jan 2012, Philip Guenther wrote:
Lesson #1: examine the anomalous data for clues.
So, you're saying that
locate /usr | grep ^/usr | head
returns nothing but
Yep! As does locate /usr
locate /home | grep ^/home | head
returns something? (/home being a stand-in for
Also, in order to help others when they encounter a similar issue,
please be sure to post what the problem and/or solution were once you
figure them out.
Philip Guenther
On Wed, Jan 11, 2012 at 1:09 PM, L. V. Lammert l...@omnitec.net wrote:
On Wed, 11 Jan 2012, Philip Guenther wrote:
Lesson #1: examine the anomalous data for clues.
So, you're saying that
locate /usr | grep ^/usr | head
returns nothing but
Yep! As does locate /usr
locate /home |
L. V. Lammert wrote:
At 01:04 PM 1/11/2012, Barry Grumbine wrote:
Bite the bullet, upgrade, life is better at 5.0
Sorry, but *UPGRADING* isn't the question - the question is why
locate is not working properly. If nobody has ever seen such a
problem, it would be quite more forthright to just
On Wed, Jan 11, 2012, L. V. Lammert wrote:
At 01:30 PM 1/11/2012, Jeremy O'Brien wrote:
4.3 was released May 1, 2008. That's almost 4 years old software. What
are you expecting here? Someone to check out the code from that
version and deeply inspect what may be causing your problem, that is
Am 11.01.12 22:34, schrieb Ted Unangst:
On Wed, Jan 11, 2012, L. V. Lammert wrote:
At 01:30 PM 1/11/2012, Jeremy O'Brien wrote:
4.3 was released May 1, 2008. That's almost 4 years old software. What
are you expecting here? Someone to check out the code from that
version and deeply inspect
On Wed, Jan 11, 2012 at 3:02 PM, Marian Hettwer m...@kernel32.de wrote:
...
([foobar@bistromath] ~)$ time sudo /usr/libexec/locate.updatedb
Password:
Ah, but that's *not* how locate.updatedb is invoked by the cronjob!
There's a reason I called out the need to mimic that when trying to
replicate
On Wed, 11 Jan 2012, Philip Guenther wrote:
On Wed, Jan 11, 2012 at 3:02 PM, Marian Hettwer m...@kernel32.de wrote:
...
([foobar@bistromath] ~)$ time sudo /usr/libexec/locate.updatedb
Password:
Ah, but that's *not* how locate.updatedb is invoked by the cronjob!
There's a reason I called
Am 12.01.12 00:13, schrieb Philip Guenther:
On Wed, Jan 11, 2012 at 3:02 PM, Marian Hettwerm...@kernel32.de wrote:
...
([foobar@bistromath]~)$ time sudo /usr/libexec/locate.updatedb
Password:
Ah, but that's *not* how locate.updatedb is invoked by the cronjob!
There's a reason I called out
On Wed, Jan 11, 2012 at 3:18 PM, L. V. Lammert l...@omnitec.net wrote:
On Wed, 11 Jan 2012, Philip Guenther wrote:
...
Ah, but that's *not* how locate.updatedb is invoked by the cronjob!
There's a reason I called out the need to mimic that when trying to
replicate the problem while walking
On Wed, 11 Jan 2012, Philip Guenther wrote:
Agreed, .. but if locate.update does NOT run as root, that would seem to
indicate some problem other than permissions.
If you're saying what I think you're saying, then I disagree and think
your logic is backwards.
What user do you think
On 01/11/12 14:24, Barry Grumbine wrote:
Bite the bullet, upgrade, life is better at 5.0
...knew I forgot something.
There aren't many North American mirrors that go back to 4.2. I was
fortunate to find obsd.cec.mtu.edu which Nick Holland recently
notified us that he needs to take down
On Wed, Jan 11, 2012 at 4:08 PM, L. V. Lammert l...@omnitec.net wrote:
On Wed, 11 Jan 2012, Philip Guenther wrote:
Agreed, .. but if locate.update does NOT run as root, that would seem to
indicate some problem other than permissions.
If you're saying what I think you're saying, then I
79 matches
Mail list logo
