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 Fri, Jun 4, 2010 at 10:14 AM, Otto Moerbeek o...@drijf.net wrote:
On Fri, Jun 04, 2010 at 09:51:16AM +0200, Markus Hennecke wrote:
Am 03.06.2010 23:52, schrieb Ted Unangst:
On Thu, Jun 3, 2010 at 5:21 PM, Christopher Zimmermann
madro...@zakweb.de wrote:
Are you sure this is a problem in
[IMAGE]
Mayores informes responda este correo electrC3nico con los siguientes
datos.
Empresa:
Nombre:
TelC)fono:
Email:
NC:mero de Interesados:
Y en breve le haremos llegar la informaciC3n completa del evento.
O bien comunCquense a nuestros telC)fonos un ejecutivo con gusto le
atenderC!
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
Hello,
I know this is a FAQ, and perhaps I'll be blamed for asking it again...
cc -O2 -pipe -g -DHAVE_CONFIG_H -I/usr/src/gnu/lib/libiberty/src
-I/usr/src/gnu/lib/libiberty/include -I/usr/src/gnu/lib/libiberty/obj
-c /usr/src/gnu/lib/libiberty/src/hex.c -o
hex.o
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, 5 Jun 2010 13:25:26 +0300 Gregory Edigarov
g...@bestnet.kharkov.ua wrote:
Stop in /usr/src/gnu/lib/libiberty (line 92 of /usr/share/mk/sys.mk).
# uname -a
OpenBSD edigarov.sa.net.ua 4.7 GENERIC#16 amd64
This happen while i am trying to build from sources. The system is
the latest
Hello all,
I was using pf's (OBSD 4.6) binat for openvpn purposes with
192.168.0.0/24 binatted to 192.0.2.0/24 since I can't renumber the local
LAN to avoid the overlap.
This doesn't work with current:
match on tun0 from 192.168.0.0/24 to any binat-to 192.0.2.0/24
for the entire subnet any more.
Paolo,
You may need to use the bitmask directive.
bitmask - grafts the network portion of the pool address over top of
the address that is being modified (source address for nat-to rules,
destination address for rdr-to rules).
Example: if the address pool is 192.0.2.1/24 and the address being
On OpenBSD 4.7 I need to rewrite all of my old pf.conf, why this happens in
the PF?
Thanks
On Sat, Jun 5, 2010 at 11:44 AM, Kleber Rocha kli...@gmail.com wrote:
On OpenBSD 4.7 I need to rewrite all of my old pf.conf, why this happens in
the PF?
This has been discussed repeatedly since pf changes hit CURRENT. Search the
archives.
First major change in 6-7 years, I'd say it's doing pretty good
On 6/5/10, Kleber Rocha kli...@gmail.com wrote:
On OpenBSD 4.7 I need to rewrite all of my old pf.conf, why this happens in
the PF?
Thanks
--
Sent from my mobile device
http://www.glumbert.com/media/shift
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
Pioneiros da RegressC#o em Portugal
A AlmaSoma tem o prazer de anunciar Hans TenDam e Morris Netherton em
Lisboa, responsC!veis maiores pelo desenvolvimento da Terapia
Regressiva no mundo. Em Junho e Julho, os meses do jacarandC! em flor,
o logC3tipo da AlmaSoma.
Hans TenDam
HistC3rias de
Use of uninitialized value $_ in substitution (s///) at
/usr/libdata/perl5/OpenBSD/ProgressMeter/Term.pm line 130.
Use of uninitialized value $_ in substitution (s///) at
/usr/libdata/perl5/OpenBSD/ProgressMeter/Term.pm line 131.
Use of uninitialized value $_ in substitution (s///) at
Hello,
I just tried to upgrade my machine to 4.7 (release) and it IDs my hard
drives differently than 4.6 did. That is, when asked (during upgrade)
which disk the root partition is on it offers: sd0 wd0 wd1 wd2.
However, what I'm expecting is: wd0 wd1 wd2 wd3
Thus, fsck fails and therefore the
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.
On Sun, Jun 6, 2010 at 5:14 AM, Neal Hogan nealho...@gmail.com wrote:
Hello,
I just tried to upgrade my machine to 4.7 (release) and it IDs my hard
drives differently than 4.6 did. That is, when asked (during upgrade)
which disk the root partition is on it offers: sd0 wd0 wd1 wd2.
However,
On Sat, Jun 5, 2010 at 5:27 PM, Edho P Arief edhopr...@gmail.com wrote:
On Sun, Jun 6, 2010 at 5:14 AM, Neal Hogan nealho...@gmail.com wrote:
Hello,
I just tried to upgrade my machine to 4.7 (release) and it IDs my hard
drives differently than 4.6 did. That is, when asked (during upgrade)
On Sat, Jun 05, 2010 at 05:50:39PM -0500, Neal Hogan wrote:
On Sat, Jun 5, 2010 at 5:27 PM, Edho P Arief edhopr...@gmail.com wrote:
On Sun, Jun 6, 2010 at 5:14 AM, Neal Hogan nealho...@gmail.com wrote:
Hello,
I just tried to upgrade my machine to 4.7 (release) and it IDs my hard
drives
2010/6/6 Neal Hogan nealho...@gmail.com:
Hello,
I just tried to upgrade my machine to 4.7 (release) and it IDs my hard
drives differently than 4.6 did. That is, when asked (during upgrade)
which disk the root partition is on it offers: sd0 wd0 wd1 wd2.
However, what I'm expecting is: wd0 wd1
On Sat, Jun 5, 2010 at 6:08 PM, Vadim Zhukov persg...@gmail.com wrote:
2010/6/6 Neal Hogan nealho...@gmail.com:
Hello,
I just tried to upgrade my machine to 4.7 (release) and it IDs my hard
drives differently than 4.6 did. That is, when asked (during upgrade)
which disk the root partition is
On Sat, Jun 5, 2010 at 4:27 PM, Neal Hogan nealho...@gmail.com wrote:
On Sat, Jun 5, 2010 at 6:08 PM, Vadim Zhukov persg...@gmail.com wrote:
2010/6/6 Neal Hogan nealho...@gmail.com:
...
As it was already pointed, one disk is connected to AHCI-compatible
controller.
ahci0 at pci0 dev 17
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
Hi,
Is this applicable to OpenBSD also? ( I guess yes )
http://www.reddit.com/comments/cb3n0/are_you_a_canadian_linux_user_youre_about_to/
Canadian DMCA, eh?
On Sat, Jun 5, 2010 at 7:07 PM, Philip Guenther guent...@gmail.com wrote:
On Sat, Jun 5, 2010 at 4:27 PM, Neal Hogan nealho...@gmail.com wrote:
On Sat, Jun 5, 2010 at 6:08 PM, Vadim Zhukov persg...@gmail.com wrote:
2010/6/6 Neal Hogan nealho...@gmail.com:
...
As it was already pointed, one
Don't act like this is normal.
It is normal.
Where in the archives has this been reported?
Why did it have to be reported?
You expect every semantic of the way our kernel behaves to be
reported ... in the archives?
In your dreams..
Like I said, I appreciate the difference and the
On Sat, Jun 5, 2010 at 9:38 PM, Theo de Raadt dera...@cvs.openbsd.org
wrote:
Don't act like this is normal.
It is normal.
I had not determined that. . . I did not see where somebody's HDDs
were interpreted differently.
Where in the archives has this been reported?
Why did it have to be
On 6/5/10 10:56 PM, Neal Hogan wrote:
I had not determined that. . . I did not see where somebody's HDDs
were interpreted differently.
Hi Neal,
It's not the HHD that is interpreted differently, it's the changes and
improvement to the controller that is better supported in 4.7 then before.
47 matches
Mail list logo
