Contributed by jose on from the upgrades-the-el-debarge-way dept.
Real hackers will say: "So what? 'cvs up' 'make build' 'vipw' .. and done. But, what about people having machines without compilers, not enough disk space, slow CPU, "impossible" source upgrade paths (like a.out to ELF on i386) or whatever reason cannot follow this way? What about all the installed packages/ports and so on. What about "leftovers" in /usr/lib and thelike?
Reinstall from scratch? Annoying, boring and time-wasting, too.
Enough of it: debardage aims to help one out of this situation. Upgrade your OpenBSD system without lots of hassle or boring repetitive tasks from one version to the next (or downgrade it.. ).
Upcoming features:
- Update all installed core system files (baseXX.tgz, compXX.tgz, ...)
- Merge /etc (and no, it's not using mergemaster)
- Update all installed packages/ports (since W^X, one should do that every time)
- Take care of existing 3rd party software, which was not installed as a package
- Remove unneeded/outdated binaries/libraries
- New bootloader/kernel
- ...
http://debardage.sysfive.org/ "
Now's a perfect time to test this as we approach 3.4's release. Go forth and test, and report your findings to the authors.
Update
Spoke to the author of the software, and this project is at a very alpha stage. This simply means that you shouldn't be surprised to see unimplemented functionality or bugs. Looks like the tool was announced a bit too early.
(Comments are closed)
By Tim Kornau () opti@openbsd.de on www.openbsd.de
Tim
Comments
By Michael Anuzis () on
By Nick () on
Comments
By Anonymous Coward () on
> If you are paranoid enough to run openbsd
That's not why I am using OpenBSD.
To the author of the tool:
"Copyright (c) 2003 sysfive.com GmbH" is not a valid copyright notice.
Comments
By Philipp () pb@ on mailto:pb@
cause it has 'Copyright' and '(c)' *sigh*
And now you think I've lost my copyright? go home ;)
Fixed anyway.. pend ants ...
//pb
By grey () on
>> To the author of the tool:
"Copyright (c) 2003 sysfive.com GmbH" is not a valid copyright notice.
Umm, you really might want to provide further elucidation when you state things like that. My guess is you didn't because you're just repeating what someone else has stated. Sooooo, in an attempt to find other people stating similar things I did some oracle consultation. After a bit of googling, I found a whole -FOUR- (one repeat, so really three) instances of the phrase "not a valid copyright notice" all apparently written by pedants none of whom appear to be a lawyer, who seem to think that (C) is not a close enough approximation to the actual copyright symbol. I think one even went so far as to say that such an approximation would never hold up in court. (Note, they didn't cite any case where such a problem actually arose)
On the contrary, I think that a court has much better things to do than deal with frivolous crap like that.
IANAL(BIPOOSMB), but if I recall correctly, under Berne and most similar (e.g. USA, Canadian) copyright provisions - you don't even need to explicitly claim copyright in order for that work to have copyright. However, the converse, namely - disclaiming rights provided by copyright (publish, modify, etc.) need to be explicitly stated. Moreover, even for the pedants out there the use of Copyright are perfectly valid. Tossing in a (C) or other additional information (e.g. OpenBSD rocks) somewhere within the document I would wager is not grounds for invalidating the copyright.
Now, while Disney might lobby some other insane changes to copyright enforcement in the future - I sincerely doubt that this approach will be one of them. It really sounds about as sensical as SCO's claims of invalidating the GPL due to copyright only allowing for one copy... Hey, I know - maybe SCO's lawyers should try this false claim on for size too since I'm sure there's plenty of (C) to be found in Linux (er... I mean misappropriated & stolen SCO code).
I really think that rumours and BS like this should die, or at the least - be backed up by some actual court cases if people are going to start claiming that such practices should be avoided.
Comments
By Anonymous Coward () on
I will rephrase:
"sysfive.com GmbH" is not a valid copyright holder. You need a {company}name there.
You can not say "copyright google.com", but you can say "copyright Google, Inc. whatever".
Comments
By Philipp Buehler () pb@ on http://debardage.sysfive.org
hehe.. well. the company name *IS* "sysfive.com"
and a GmbH is like Ltd.
Hamburg District Court: HRB 75948
Satisifed now?
//pb
Comments
By Anonymous Coward () on
Yes.
My mistake - should've checked what 'GmbH' stands for...
Comments
By Alejandro Belluscio () on
Comments
By tedu () on
right. they are all commies _or_ mud farmers. :)
Comments
By Anonymous Coward () on
By Anonymous Coward () on
Comments
By whoever () on
Comments
By krh () on
By Anonymous Coward () Wim on mailto:Wim
(of course to a certain extend, it is! ;)
Strange to see the whole world is considered to be US oriented.... there are more companies out there that don't have INC behind their name...
By Anonymous Coward () on
Comments
By grey () on
IANAL(BIPOOSMB)
I Am Not A Lawyer (But I Play One One Silly Message Boards).
I think my first iteration of BIPOOSMB was actually BIPOOSD or BIPOO/. but, I don't really post to /. so that didn't seem accurate.
Comments
By Anonymous Coward () on
By Anonymous Coward () on
By Philipp () pb@ on mailto:pb@
It's a lousy bunch of shell scripts.
It wont touch anything you do NOT have under
better control if you use the official OpenBSD
cdrom
You dont like it? Your thing. :)
//pb
By ansible () ansible at xnet dottage commage on mailto:ansible at xnet dottage commage
This is a good chance to document your system building. Make notes of all the files you had to tweak, what additional packages you had to install, etc.
If you have copies of these files in multiple, safe places, that can make disaster recovery much, much easier.
Also can help when deploying a new system that is similar to an existing one.
Comments
By Philipp () pb@ on mailto:pb@
All the collected data for building the upgrade
ISO can be used for documenting the current installation.
Actually - piece of cake :)