On 6/06/2010, at 1:27 PM, Uwe Dippel wrote:
Philip Guenther guenther at gmail.com writes:
You now have and now it
seems the core discussion is just about whether (or where) an
additional rm -rf /usr/obj/* should be added to help people that
know enough to set up the source tree for
On Jun 05 12:25:03, Uwe Dippel wrote:
Philip Guenther guenther at gmail.com writes:
Please point to the part of the Upgrade Guide which talks about
building from source, untarring the src tar file, or applying errata.
I can't seem to find any such reference, but I'm sure it's in there
patrick keshishian wrote:
On Fri, Jun 4, 2010 at 7:49 PM, Jacob Meuser jake...@sdf.lonestar.org
wrote:
I'm still curious how anything left in /usr/obj can be anything
but a possible problem after updating system binaries and sources
to a new release. especially for people who are just
Jacob Meuser wrote:
...
On 5/06/2010, at 7:31 AM, Nick Holland wrote:
a patch to the upgrade guide would be wrong.
The problem is the patching process (a special case of the userland build
process) assumes a clean obj dir. This has nothing to do with upgrades. If
you try to rebuild the same
IF YOU DON'T KNOW WHAT YOUR ARE DOING, INSTALL A NEW SNAPSHOT
Theo de Raadt wrote:
Miod, Dale, Kurt, Kettenis and I am quite often the first people to
deal with bumping systems forward over bumps. Some bumps are so
difficult that after they are done the rest of us jump over them using
On 5/06/2010, at 5:51 PM, Theo de Raadt wrote:
On Fri, Jun 4, 2010 at 7:49 PM, Jacob Meuser jake...@sdf.lonestar.org
wrote:
I'm still curious how anything left in /usr/obj can be anything
but a possible problem after updating system binaries and sources
to a new release. especially for
On Jun 04 16:22:35, Uwe Dippel wrote:
Jacob Meuser jakemsr at sdf.lonestar.org writes:
oh good grief. you had a dirty /usr/obj.
just look at the pfctl snippet of the log you posted. do you see pfctl
being built? do you see pfctl being installed from /usr/obj?
Oh, yes. So the
On Sat, Jun 05, 2010 at 06:48:18PM +1200, Richard Toohey wrote:
But I don't understand what he's doing differently to me. A new release is
out, you want to upgrade from the previous release to the new one, and
then you want to apply the errata patches.
Look, there are several flaws to the way
On 5/06/2010, at 7:45 PM, Jan Stary wrote:
On Jun 04 16:22:35, Uwe Dippel wrote:
Jacob Meuser jakemsr at sdf.lonestar.org writes:
oh good grief. you had a dirty /usr/obj.
just look at the pfctl snippet of the log you posted. do you see pfctl
being built? do you see pfctl being installed
On Sat, Jun 05, 2010 at 01:49:46AM -0400, Tony Abernethy wrote:
Jacob Meuser wrote:
...
On 5/06/2010, at 7:31 AM, Nick Holland wrote:
a patch to the upgrade guide would be wrong.
The problem is the patching process (a special case of the userland build
process) assumes a clean obj dir.
On 5/06/2010, at 8:14 PM, Marc Espie wrote:
On Sat, Jun 05, 2010 at 06:48:18PM +1200, Richard Toohey wrote:
But I don't understand what he's doing differently to me. A new release
is
out, you want to upgrade from the previous release to the new one, and
then you want to apply the errata
Jacob Meuser wrote:
On Sat, Jun 05, 2010 at 01:49:46AM -0400, Tony Abernethy wrote:
Jacob Meuser wrote:
...
On 5/06/2010, at 7:31 AM, Nick Holland wrote:
a patch to the upgrade guide would be wrong.
The problem is the patching process (a special case of the userland build
process) assumes
On Sat, Jun 05, 2010 at 05:13:19AM -0400, Tony Abernethy wrote:
All I need to break any automated system you devise is to have some programs
that I compile myself and use the system directories to hold the sources etc.
then you are on your own, not someone who is just following the
Jacob Meuser wrote:
On Sat, Jun 05, 2010 at 05:13:19AM -0400, Tony Abernethy wrote:
All I need to break any automated system you devise is to have
some programs that I compile myself and use the system directories
to hold the sources etc.
then you are on your own, not someone who is just
Tony Abernethy tony at servasoftware.com writes:
Might be better to read and comprehend ``man patch'' before assuming
limitations on the scope of patch's reach.
It is always so nice to trample on the person lying on the ground, ain't it!
Where in 'man patch' is the underlying problem
wtf are you talking about tony?
have you even read the upgrade guide?
have you read any of this thread, at all, or did you see some long
thread on misc@ and decide to jump in?
we have users that say they follow the install and upgrade guides to the
letter and they get fucked.
there is a
Jacob Meuser wrote:
we have users that say they follow the install and upgrade guides to the
letter and they get fucked.
there is a problem.
they don't even know /usr/obj exists.
What they say. What they did. Two different things.
There's lots of things they do not know about.
I fail to
what a totally useless bunch of misc traffic only because a drunk OpenBSD
user did not remove /usr/obj before building shit
Theo de Raadt wrote:
If [you] don't know what you are doing, install a new snapshot.
We do this frequently. Works very well. bsd.rd makes it easy to move to
a new snapshot. We buy -release CDs too, but seldom open them.
Brad
Philip Guenther guenther at gmail.com writes:
Please point to the part of the Upgrade Guide which talks about
building from source, untarring the src tar file, or applying errata.
I can't seem to find any such reference, but I'm sure it's in there
somewhere, because you originally said that
On Sat, Jun 05, 2010 at 06:48:18PM +1200, Richard Toohey wrote:
On 5/06/2010, at 5:51 PM, Theo de Raadt wrote:
On Fri, Jun 4, 2010 at 7:49 PM, Jacob Meuser jake...@sdf.lonestar.org
wrote:
I'm still curious how anything left in /usr/obj can be anything
but a possible problem after
On Sat, Jun 5, 2010 at 5:25 AM, Uwe Dippel udip...@gmail.com wrote:
Philip Guenther guenther at gmail.com writes:
Please point to the part of the Upgrade Guide which talks about
building from source, untarring the src tar file, or applying errata.
I can't seem to find any such reference, but
I was following the Upgrade Guide to the dot, following
Applying patches in OpenBSD to the dot,
This thread perhaps wouldn't have happened if you hadn't waited until
your 13th message to describe that last part. You now have and now it
seems the core discussion is just about whether (or
Perhaps every section of the FAQ begin with an exhortation
to read the entire FAQ.
I am flabbergasted that someone who runs a 'production' box
would put themeselves in this position.
Philip Guenther guenther at gmail.com writes:
You now have and now it
seems the core discussion is just about whether (or where) an
additional rm -rf /usr/obj/* should be added to help people that
know enough to set up the source tree for building/patching by
untaring src.tar.gz but don't
So, no diff here, but a suggestion:
If one needs to avoid stale stuff lying around in /usr/obj at applying a
patch,
the only logical consequence is, to clean out all /obj totally, even before
applying a single patch.
If I am correct, the instructions should be clear for
On Thu, Jun 3, 2010 at 7:18 PM, Richard Toohey
richardtoo...@paradise.net.nz wrote:
OK, I've tried it and cannot reproduce what you see. I've never done
an upgrade from bsd.rd before, so wanted to give it a go.
Obviously something different with your set-up, or where you got the files
from,
On Fri, Jun 4, 2010 at 2:18 PM, Uwe Dippel udip...@gmail.com wrote:
5. reboot after patching - old files and wrong timestamps - bummer, as
Theo might say.
Sorry, guys, (too quick as too often), just cat-grep pfctl shows where
the old one comes in:
pfctl: pf already enabled
# ls -l # ls -l
On Thu, Jun 3, 2010 at 11:18 PM, Uwe Dippel udip...@gmail.com wrote:
On Thu, Jun 3, 2010 at 7:18 PM, Richard Toohey
richardtoo...@paradise.net.nz wrote:
OK, I've tried it and cannot reproduce what you see. I've never done
an upgrade from bsd.rd before, so wanted to give it a go.
Obviously
On 4/06/2010, at 6:41 PM, patrick keshishian wrote:
On Thu, Jun 3, 2010 at 11:18 PM, Uwe Dippel udip...@gmail.com wrote:
On Thu, Jun 3, 2010 at 7:18 PM, Richard Toohey
richardtoo...@paradise.net.nz wrote:
OK, I've tried it and cannot reproduce what you see. I've never done
an upgrade from
On Fri, Jun 4, 2010 at 2:41 PM, patrick keshishian pkesh...@gmail.com wrote:
you mean applying the errata47.html patches? If so, are you certain
your source tree is tagged OPENBSD_4_7 and not anything else?
Do I understand you correctly? I am not building releases. I am
installing/downloading
On Fri, Jun 4, 2010 at 3:00 PM, Richard Toohey
richardtoo...@paradise.net.nz wrote:
I think we are getting closer, aren't we?
So, NOTHING to do with the actual upgrade, is it?
No absolutely nothing. I withdraw the subject with regret. At least
the 'base47'-part thereof.
Or the
On Fri, Jun 04, 2010 at 03:55:53PM +0800, Uwe Dippel wrote:
On Fri, Jun 4, 2010 at 2:41 PM, patrick keshishian pkesh...@gmail.com wrote:
you mean applying the errata47.html patches? If so, are you certain
your source tree is tagged OPENBSD_4_7 and not anything else?
Do I understand you
On Fri, Jun 4, 2010 at 12:55 AM, Uwe Dippel udip...@gmail.com wrote:
On Fri, Jun 4, 2010 at 2:41 PM, patrick keshishian pkesh...@gmail.com wrote:
you mean applying the errata47.html patches? If so, are you certain
your source tree is tagged OPENBSD_4_7 and not anything else?
Do I understand
On Fri, Jun 4, 2010 at 4:32 PM, patrick keshishian pkesh...@gmail.com wrote:
Where did you get those tar-balls from? Those are most likely not 4.7 sources.
I gave the potential link and their md5 sums further up. Our link here
is sooo slooow; I *am* currently downloading the archives from
On Fri, Jun 4, 2010 at 4:22 PM, Eric Faurot e...@faurot.net wrote:
Don't you have old stuff lying around in /usr/obj that gets installed
over your new binaries?
That's probably the critical question now. Though, sorry to say, there
is nowhere written that you have to rm -Rf it, when you
-
On 4/06/2010, at 8:33 PM, Uwe Dippel wrote:
On Fri, Jun 4, 2010 at 4:22 PM, Eric Faurot e...@faurot.net wrote:
Don't you have old stuff lying around in /usr/obj that gets installed
over your new binaries?
That's probably the critical question now. Though, sorry to say, there
is nowhere
On Fri, Jun 04, 2010 at 04:40:28PM +0800, Uwe Dippel wrote:
On Fri, Jun 4, 2010 at 4:32 PM, patrick keshishian pkesh...@gmail.com wrote:
Where did you get those tar-balls from? Those are most likely not 4.7
sources.
I gave the potential link and their md5 sums further up. Our link here
On Fri, Jun 04, 2010 at 04:33:34PM +0800, Uwe Dippel wrote:
When you are under 'quality control', and responsible for the
uptime of a system, you would never do anything out of the scope of
instructions, naturally. especially not some rm -Rf * in a directory
of your arbitrary choice. ;)
if
On Fri, Jun 04, 2010 at 04:33:34PM +0800, Uwe Dippel wrote:
When you are under 'quality control', and responsible for the
uptime of a system, you would never do anything out of the scope of
instructions, naturally. especially not some rm -Rf * in a directory
of your arbitrary choice. ;)
On Fri, 4 Jun 2010, Jan Stary wrote:
'rm -rf /usr/obj/*' is not your arbitrary choice,
it's a documented step when building the system.
http://www.openbsd.org/faq/faq5.html#BldUserland
Also documented there is keeping /usr/obj/ in its own partition and using
'newfs' to zap everything more
Jacob Meuser jakemsr at sdf.lonestar.org writes:
oh good grief. you had a dirty /usr/obj.
just look at the pfctl snippet of the log you posted. do you see pfctl
being built? do you see pfctl being installed from /usr/obj?
Oh, yes. So the blame is on my side, I guess. Mea culpa maxima!
I
Might be better to read and comprehend ``man patch'' before assuming
limitations on the scope of patch's reach.
-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf
Of Uwe Dippel
Sent: Friday, June 04, 2010 11:23 AM
To: misc@openbsd.org
Subject:
On Fri, Jun 04, 2010 at 04:22:35PM +, Uwe Dippel wrote:
Still, may I suggest, that the next Upgrade Guide gets an extra line, with a
remark pointing out the existence of /usr/obj; and the suggestion to clean it?
you can't supply a patch? can't even attempt one? all these posts and
time
* Uwe Dippel udip...@gmail.com [2010-06-04 18:26]:
I didn't know that the object directories need to be cleaned manually.
this should not be needed assuming system time didn't jump. it is
still good practice tho.
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services,
Jacob Meuser wrote:
On Fri, Jun 04, 2010 at 04:22:35PM +, Uwe Dippel wrote:
Still, may I suggest, that the next Upgrade Guide gets an extra line, with a
remark pointing out the existence of /usr/obj; and the suggestion to clean it?
you can't supply a patch? can't even attempt one? all
snip
Clearing the obj
directory as part of the upgrade is like flushing your toilet based on the
date -- may help, but after a while, things start to stink. It isn't the
general (or proper) solution.
oops.
What's the recommended procedure for this?
-B
On Fri, Jun 4, 2010 at 9:22 AM, Uwe Dippel udip...@gmail.com wrote:
...
Still, may I suggest, that the next Upgrade Guide gets an extra line, with a
remark pointing out the existence of /usr/obj; and the suggestion to clean it?
Please point to the part of the Upgrade Guide which talks about
On 5/06/2010, at 7:31 AM, Nick Holland wrote:
Jacob Meuser wrote:
On Fri, Jun 04, 2010 at 04:22:35PM +, Uwe Dippel wrote:
Still, may I suggest, that the next Upgrade Guide gets an extra line, with
a
remark pointing out the existence of /usr/obj; and the suggestion to clean
it?
you can't
On Sat, Jun 05, 2010 at 10:29:57AM +1200, Richard Toohey wrote:
On 5/06/2010, at 7:31 AM, Nick Holland wrote:
Jacob Meuser wrote:
On Fri, Jun 04, 2010 at 04:22:35PM +, Uwe Dippel wrote:
Still, may I suggest, that the next Upgrade Guide gets an extra line, with
a
remark pointing out
On Fri, Jun 04, 2010 at 10:31:22PM -0700, patrick keshishian wrote:
On Fri, Jun 4, 2010 at 7:49 PM, Jacob Meuser jake...@sdf.lonestar.org
wrote:
I'm still curious how anything left in /usr/obj can be anything
but a possible problem after updating system binaries and sources
to a new
On Fri, Jun 4, 2010 at 7:49 PM, Jacob Meuser jake...@sdf.lonestar.org
wrote:
I'm still curious how anything left in /usr/obj can be anything
but a possible problem after updating system binaries and sources
to a new release. especially for people who are just following
the directions as
Theo de Raadt deraadt at cvs.openbsd.org writes:
A chit-chat on a public mailing list isn't going to find this supposed
bug. Why discuss it? Why not just keep prove it happened.
Yes, Theo. Though: How? This is what I tried to find out.
I showed the list if files. Do you assume I tinkered
Theo de Raadt deraadt at cvs.openbsd.org writes:
A chit-chat on a public mailing list isn't going to find this supposed
bug. Why discuss it? Why not just keep prove it happened.
Yes, Theo. Though: How? This is what I tried to find out.
I showed the list if files. Do you assume I
Uwe Dippel wrote:
drill it down to some 70 files being of the previous
version.
It might be tiring, but what evidence do you want?
The error message(s) you are suppressing (or maybe didn't see)
About the only way you can get some files but not all files
from a tarball is some fatal error in
On Thu, Jun 3, 2010 at 3:20 PM, Tony Abernethy t...@servasoftware.com wrote:
The error message(s) you are suppressing (or maybe didn't see)
About the only way you can get some files but not all files
from a tarball is some fatal error in the extraction of the
tarball. Any such error tends to
On 3/06/2010, at 8:42 PM, Uwe Dippel wrote:
[cut]
No, that seriously turns me off. I have given everything in detail
that I came across, I have not been silent about any additional
message, any unusual activity. I have stated a few times that I
followed the upgrade procedure to the dot, I
On Jun 03 16:42:58, Uwe Dippel wrote:
On Thu, Jun 3, 2010 at 3:20 PM, Tony Abernethy t...@servasoftware.com wrote:
The error message(s) you are suppressing (or maybe didn't see)
About the only way you can get some files but not all files
from a tarball is some fatal error in the
On 3/06/2010, at 9:02 PM, Richard Toohey wrote:
On 3/06/2010, at 8:42 PM, Uwe Dippel wrote:
[cut]
No, that seriously turns me off. I have given everything in detail
that I came across, I have not been silent about any additional
message, any unusual activity. I have stated a few times that
On 2010-06-03, Uwe Dippel udip...@gmail.com wrote:
No, that seriously turns me off. I have given everything in detail
that I came across,
The problem is obviously relating to something that you didn't
come across otherwise you wouldn't be posting here - if you can post
logs this will give more
Getting closer ...
Extracted the archive being used for the upgrade to amd64 into my
user-directory and calculated all 7484 md5 for the files included in
base47, and redirected those into a file.
Then, I calculated all the md5 for the files *installed* in the upgraded
machine; the file names
Now, with
$ diff md5sums_archive md5sums_install | grep ^ | cut -d ' ' -f2
these are the files different on amd64, between what the archive
supplied, and what the installer left behind:
./usr/lib/libasn1.so.17.0
./usr/lib/libcom_err.so.17.0
./usr/lib/libcrypto.so.18.0
On 06/01/10 23:25, Uwe Dippel wrote:
...
There is one more machine (amd64) that needs to be upgraded. Before I do
this, I rather solicit suggestions on how to log the upgrade process,
debug it, or otherwise.
serial console.
Log everything from the first chars out the serial port to the
Nick Holland nick at holland-consulting.net writes:
There is one more machine (amd64) that needs to be upgraded. Before I do
this, I rather solicit suggestions on how to log the upgrade process,
debug it, or otherwise.
serial console.
Log everything from the first chars out the serial
On Wed, Jun 02, 2010 at 02:42:53PM +, Uwe Dippel wrote:
Nick Holland nick at holland-consulting.net writes:
There is one more machine (amd64) that needs to be upgraded. Before I do
this, I rather solicit suggestions on how to log the upgrade process,
debug it, or otherwise.
Based on the latest results, the problem seems to exist only for most of the
/sbin files. So, the upgrade runs through as programmed.
With a public mirror, it will take hours. I really hope SHA256 is good
enough to
confirm the integrity of the archives. Serial console seems a good
[I consider it better to open a new thread, since the title, and part of
the content, of the previous one was superseded.]
Having upgraded one machine (amd64) from 4.6 to 4.7, using the normal
upgrade procedure as outlined in http://openbsd.org/faq/upgrade47.html
to the dot, after the reboot
67 matches
Mail list logo
