Re: preserving editor files
- Original Message - From: Jean-FranC'ois SIMON Sent: 09/08/10 08:50 PM To: openbsd-misc Subject: preserving editor files Hi All, At start-up the OS stays several minutes on preserving editor files. Could you please inform me what to do about this what is the system then doing ? Is it normal ? Thanks regards By me happens this when the machine on which is the ntpd is running, is not available, no network or hasnot booted up yet. Yes, it waits several minutes.
Re: major bump note in faq/current.html
Can we ask in the future something similar at src/*/shlib_version major
bumps?
to avoid ``pkg_add -u'' complaining about bad
major/minor I do the following:
- check that my mirror is up to date
ie ``ls'' to make sure all files belong
to the same snap
you mean: all files=${mirror}/pub/OpenBSD/snapshots/${arch}/* ?
You don't care comparing the 3 date (major bump, base sets, packages)?
- update to base (using the installer or just
reboot and untar base file sets)
Yes.
- apply changes in current.html
Yes + sysmerge -s etc47.tgz, sysmerge -x xetc47.tgz
- pkg_add -ui
this should always work and you don't have to care about
bumps.
Always or almost always? It doesn't depends on major bump?
Major bumps are infrequent, but sometimes happen.
Re: major bump note in faq/current.html
Thank you for the polite answers. On Thu, May 27, 2010 at 10:58 AM, Charles Smith chasm_...@gmx.com wrote: Can we ask in the future something similar at src/*/shlib_version major bumps? Can we ask in the present that you actually describe what problem you're trying to solve when you suggest extra work? You know, we just might be able to come up with an easier way to solve your problem. Philip Guenther Sure, sorry for fault. Of course I read the sources-changes@ maillist among others. This is the sole place, where from what i hear about major bumps. In most times i remember, but yesterday i forgot and so pkg_add -ui failed. Besides forgetfulness it can be missing time to read sources-changes@, so bad timing to upgrade. Together with sloppy reading the commit log messages. Is this would redundancy? Not practical? I thought maybe some people can more easily review/look back faq/current.html, which is more short, than the lot of mails on sources-changes@ without informative subjects. pkg_add -ui fail is enough practical. Yes, so current.html grows fat, and at 4.8 release must remove these notes. This is drawback. How many major bumps are yearly? 4-6? Of course yours decision.
Re: major bump note in faq/current.html
Or maybe just send a heads up mail to m...@.
Re: major bump note in faq/current.html
Nowadays I'm using snapshots, but it can be current also, it is imo unimportant within aspect. Sometimes, seldom, I see on sources-changes@ major bumps. I mark the precise date, when the major bump happened. At the next upgrade i pay big attention that my base system must correspond with snapshots packages. Not newer, not older, but accurately identical. I accomplish my upgrade only when the prebuilt packages get ready (after the marked date, with new major). I wouldn't undertake to build from ports my all (or some) installed packages. This was the very first occasion, that i forgot about major bump, and after the unguarded upgrade pkg_add -ui of course told it, because the prebuilt packages was made with the old major base system. My starting point was 05.12 base system, packages 05.13 or 05.20. Major bump happened at 05.21 and 05.26. My end point 05.27 base system and 05.25 packages: conflict because the intermediate major bump (05.26). If no claim seperate noting major bumps, I accept and solve, and we forget the idea. No problem. Or I'm misunderstanding something? Thank you for the nice answers.
Re: major bump note in faq/current.html
- Original Message - From: Vadim Zhukov 2010/5/28 Charles Smith chasm_...@gmx.com: Or maybe just send a heads up mail to m...@. You do not need to bother about ABI changes if you're using -STABLE(thanks to developers). And if you're using -CURRENT, you'redefinitely advised to monitor source-changes@, no?-- WBR, Vadim Zhukov Yes, it remains this solution.
major bump note in faq/current.html
Can we ask in the future something similar at src/*/shlib_version major bumps? Index: current.html === RCS file: /cvs/www/faq/current.html,v retrieving revision 1.221 diff -u -r1.221 current.html --- current.html 27 May 2010 14:11:42 - 1.221 +++ current.html 27 May 2010 17:48:08 - @@ -43,6 +43,7 @@ lia href=#201005252010/05/25 - new config(8) for kernel builds/a lia href=#201005262010/05/26 - gcc4 for amd64 and sparc64/a lia href=#20100526a2010/05/26 - f77 moved to ports/a +lia href=#20100526b2010/05/26 - major bump/a !-- New additions go on the bottom, please -- /ul @@ -234,6 +235,12 @@ /usr/share/man/cat1/f77.0 /usr/share/man/cat1/g77.0 /b/pre/blockquote +a name=20100526b/a +h32010/05/26 - Major bump/h3 +Major bump at 2010.05.26 14:39 UTC. +Pay attention: snapshots packages must be correspond with snapshots sets at major level. +See: a href=http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libc/shlib_version;cvsweb/a +and a href=http://marc.info/?l=openbsd-cvsm=127488492723928w=2;commit log message/a. hr a href= index.htmlimg height= 24 width= 24 src= ../images/back.gif border= 0 alt=[back]/a
minor bump is src/.../shlib_version
Good afternoon! When there is a major bump in src/.../shlib_version files, snapshots sets must be correspond with snapshots packages. For example: src/lib/libkrb5/shlib_version src/gnu/lib/libiberty/shlib_version src/lib/libc/shlib_version src/lib/libm/shlib_version Maybe with minor bump too? At UTC 2009.06.26 21:06 and 21:09 there was minor bump in src/lib/libc/shlib_version and src/lib/libm/shlib_version. i386 packages are from 2009.10.26 beforenoon.
root.mail at Nov 1
Index: src/etc/root/root.mail === RCS file: /cvs/src/etc/root/root.mail,v retrieving revision 1.87 diff -u -r1.87 root.mail --- src/etc/root/root.mail 24 Jun 2009 06:46:07 - 1.87 +++ src/etc/root/root.mail 30 Sep 2009 14:03:07 - @@ -1,6 +1,6 @@ -From dera...@do-not-reply.openbsd.org Thu Oct 1 06:46:46 MDT 2009 +From dera...@do-not-reply.openbsd.org Sun Nov 1 06:46:46 MDT 2009 Return-Path: root -Date: Oct 1 06:46:46 MDT 2009 +Date: Nov 1 06:46:46 MDT 2009 From: dera...@do-not-reply.openbsd.org (Theo de Raadt) To: root Subject: Welcome to OpenBSD 4.6!
Re: root.mail at Nov 1
--- On Wed, 9/30/09, Miod Vallat m...@online.fr wrote: It's too late for this. Yes, I have realised this too after sending. Sorry for the noise.
vendor list (was: dmesg IBM x3650 OpenBSD 4.3 )
to create a web section listing the reasonable and bastard vendors? I think it would be useful in two points: * helps to OpenBSD community to choose the right hardware * make good or bad publicity depending on real vendor's position Anyway it's only an idea. +1 I very like the idea.
Re: neomagic and the needs-update entries
--- On Sat, 7/12/08, Charles Smith [EMAIL PROTECTED] wrote: From: Charles Smith [EMAIL PROTECTED] Subject: neomagic and the needs-update entries To: misc@openbsd.org Date: Saturday, July 12, 2008, 6:09 PM Good afternoon! In xenocara/MODULES file a needs-update entry, eg by neomagic, can provoke errors, like PR pending/5836 [0]? The PR in short: On i386 ThinkPad 600X (NeoMagic 256ZX NM2360) doesn't work WindowMaker since 2008.04.10 (or before too, that was my first test after 4.3 RELEASE branch fork.) With 4.3 RELEASE works. The very odd thing: cwm, fvwm; and icewm from ports work. All application works, that I use. WindowMaker didn't change since 2007.09.15. After branch fork in xenocara/MODULES file the neomagic has been updated two times: on 2008.03.19 from 1.1.1 to 1.2.0 and on 2008.05.21 to 1.2.1. In xenocara/driver/xf86-video-neomagic/ directory remained 1.1.1. The needs-update appeared with 1.2.0. Are they not in sync? Is this rate major update? Are the needs-update entries like as public todo lists? [0]: http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=5836 Synopsis and Subject: wmaker on ThinkPad600X Fatal server error These found today: [1] [2] On FreeBSD 7.0 X.org 7.3. ThinkPad600 Neomagic Wmaker and GNUStep application problem. icewm works. Very likewise than by me on OpenBSD. I don't know if it helps. [1] http://permalink.gmane.org/gmane.os.freebsd.questions/225666 [2] http://permalink.gmane.org/gmane.os.freebsd.questions/225665
neomagic and the needs-update entries
Good afternoon! In xenocara/MODULES file a needs-update entry, eg by neomagic, can provoke errors, like PR pending/5836 [0]? The PR in short: On i386 ThinkPad 600X (NeoMagic 256ZX NM2360) doesn't work WindowMaker since 2008.04.10 (or before too, that was my first test after 4.3 RELEASE branch fork.) With 4.3 RELEASE works. The very odd thing: cwm, fvwm; and icewm from ports work. All application works, that I use. WindowMaker didn't change since 2007.09.15. After branch fork in xenocara/MODULES file the neomagic has been updated two times: on 2008.03.19 from 1.1.1 to 1.2.0 and on 2008.05.21 to 1.2.1. In xenocara/driver/xf86-video-neomagic/ directory remained 1.1.1. The needs-update appeared with 1.2.0. Are they not in sync? Is this rate major update? Are the needs-update entries like as public todo lists? [0]: http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=5836 Synopsis and Subject: wmaker on ThinkPad600X Fatal server error
yacc rebuild
Good afternoon! So, before the next make build I must rebuild the yacc alone. I would like to know how can I rebuild yacc. I searched in old errata patches, Makefiles, bsd.*.mk files. In my previous logfile (2008.07.07/src_make_build) I see, that by yacc the make cleandir is used: rm -f yacc.cat1 ... rm -f .depend ...tags So is this correct? cd usr.bin/yacc make obj make cleandir make depend make make install In general, how can I ascertain, what kind of make Phony Targets must I use? I didn't read through the whole stuff (docs, all Makefiles, etc) yet, so I rejoice at a link too. Thank You!
