Re: Upgrade path from 4.1?
On 2014-02-06, Chris Cappuccio ch...@nmedia.net wrote: Kenneth Westerback [kwesterb...@gmail.com] wrote: And, surprise!, boot blocks do change. 5.5 will be an example as things are rearranged and unified. But you can still use old bootblocks to run the new kernel as a bootstrap You can, but BEWARE! At least on some popular arch, serial console will not work.
Re: Upgrade path from 4.1?
On 07/02/14 01:54, Chris Cappuccio wrote: This is probably the time where most people would recommend against that since it is essentially a complete reinstall of all items to upgrade from pre-5.5 to 5.5 due to time_t ABI change. Chris Sorry but isn't the ABI time_t change http://www.openbsd.org/faq/current.html#20130813 included in 5.4? Or am I confused cause I run -current almost everywhere? What is this reinstall for 5.5 that all you people are talking about? If we're talking about the same thing then no reinstall is needed... regards, Giannis
Re: Upgrade path from 4.1?
On 07/02/14 8:46 AM, Kapetanakis Giannis wrote: On 07/02/14 01:54, Chris Cappuccio wrote: This is probably the time where most people would recommend against that since it is essentially a complete reinstall of all items to upgrade from pre-5.5 to 5.5 due to time_t ABI change. Chris Sorry but isn't the ABI time_t change http://www.openbsd.org/faq/current.html#20130813 included in 5.4? No, the time_t changes went in after the tree unlocked from the 5.4 release cycle. Or am I confused cause I run -current almost everywhere? What is this reinstall for 5.5 that all you people are talking about? If we're talking about the same thing then no reinstall is needed... Having to replace all binaries and remove all only binaries since there is no backwards compatibility is close enough to a reinstall. It is not literally a reinstall but its enough work that you don't want to do that very often. For a lot of people it'll also require being physically in front of a system to do an upgrade unlike most previous releases. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Upgrade path from 4.1?
Hi, I’ve recently was asked to take over the maintenance of an old OpenBSD machine, which has not been updated in the last 7 years. Currently the machine has been running for close to 1000 days on 4.1. It has been a while since I worked with OpenBSD (shame on me), and I’m really not sure what the best way would be to upgrade this machine, knowning I don’t have a serial or local access to the box. Can I do a 4.1 - 5.4 in one shot? thx! Davy
Re: Upgrade path from 4.1?
On 06/02/14 12:49, davy wrote: Hi, I’ve recently was asked to take over the maintenance of an old OpenBSD machine, which has not been updated in the last 7 years. Currently the machine has been running for close to 1000 days on 4.1. It has been a while since I worked with OpenBSD (shame on me), and I’m really not sure what the best way would be to upgrade this machine, knowning I don’t have a serial or local access to the box. Can I do a 4.1 - 5.4 in one shot? thx! Davy The upgrade path has to be 4.1 - 4.2 - 4.3 ... - 5.4 I would suggest Full Backup - Format - Install 5.4 - reconfigure the system to do the same staff G
Re: Upgrade path from 4.1?
Setup 'puppet', then you can reinstall every box, every release and have puppet configure everything in 10 mins! ;) Sorry, sound like I'm boasting! Haha, I just really love that we put in the initial effort to get puppet working even though we only have a small fleet of OBSD boxes as upgrades, scaling and change control is really easy (and so saves what little is left of my sanity) :) Andy On Thu 06 Feb 2014 11:24:43 GMT, Kapetanakis Giannis wrote: On 06/02/14 12:49, davy wrote: Hi, I’ve recently was asked to take over the maintenance of an old OpenBSD machine, which has not been updated in the last 7 years. Currently the machine has been running for close to 1000 days on 4.1. It has been a while since I worked with OpenBSD (shame on me), and I’m really not sure what the best way would be to upgrade this machine, knowning I don’t have a serial or local access to the box. Can I do a 4.1 - 5.4 in one shot? thx! Davy The upgrade path has to be 4.1 - 4.2 - 4.3 ... - 5.4 I would suggest Full Backup - Format - Install 5.4 - reconfigure the system to do the same staff G
Re: Upgrade path from 4.1?
Hi, davy wrote: Hi, I’ve recently was asked to take over the maintenance of an old OpenBSD machine, which has not been updated in the last 7 years. OpenBSD is stable, isn't it? :) Currently the machine has been running for close to 1000 days on 4.1. It has been a while since I worked with OpenBSD (shame on me), and I’m really not sure what the best way would be to upgrade this machine, knowning I don’t have a serial or local access to the box. Can I do a 4.1 - 5.4 in one shot? No. You should always do a one-by-one update. I got a tach in that too. You can skip perhaps one release, but not soo many. I had troubles with 5.2 - 5.4 which I was able to fix, but I would have spent less time by issuing upgrades... If you have enough disk-space, I'd just download all releases and using the very fine upgrade tool... the advantage is that you can keep the machine running at any moment and continue at a later stage, quick! Otherwise, backup, format, reinstall... Riccardo
Re: Upgrade path from 4.1?
On Thu, Feb 06, 2014 at 12:31:44PM +0100, Riccardo Mottola wrote: Hi, davy wrote: Hi, I?ve recently was asked to take over the maintenance of an old OpenBSD machine, which has not been updated in the last 7 years. OpenBSD is stable, isn't it? :) Currently the machine has been running for close to 1000 days on 4.1. It has been a while since I worked with OpenBSD (shame on me), and I?m really not sure what the best way would be to upgrade this machine, knowning I don?t have a serial or local access to the box. Can I do a 4.1 - 5.4 in one shot? No. You should always do a one-by-one update. I got a tach in that too. You can skip perhaps one release, but not soo many. I had troubles with 5.2 - 5.4 which I was able to fix, but I would have spent less time by issuing upgrades... If you have enough disk-space, I'd just download all releases and using the very fine upgrade tool... the advantage is that you can keep the machine running at any moment and continue at a later stage, quick! Otherwise, backup, format, reinstall... From 4.1, I'd recommend figuring out what's special, and reinstall to a snapshot. the time_t jump means you're going to have to reinstall base for 5.5 anyways, so save time.
Re: Upgrade path from 4.1?
On 02/06/14 05:49, davy wrote: Hi, I’ve recently was asked to take over the maintenance of an old OpenBSD machine, which has not been updated in the last 7 years. Currently the machine has been running for close to 1000 days on 4.1. It has been a while since I worked with OpenBSD (shame on me), and I’m really not sure what the best way would be to upgrade this machine, knowning I don’t have a serial or local access to the box. Can I do a 4.1 - 5.4 in one shot? thx! Davy You have a seven+ year old machine, with comparibly old disks. My suggestion: Build out a new machine using -current (yes, not 5.4. you have a big bump coming with 5.4 to 5.5, but if you install -current now, you are over the bump...then start back on releases/stable with 5.5). Configure the new machine exactly as you want it. Now, put it in service, decom the old machine...or minimum, swap the disks out of the old machine with these newly configured disks. This way, you never lose your functioning system...and you can freshen your hardware, too. Nick.
Re: Upgrade path from 4.1?
Hmm, you do have an excellent point there. Those disks, it's a miracle they 're still working. I'll think the re-start from bare metal is the best way forward. Thank you for your honest answers! At least I didn't get frustrated because of upgrade hell! :) 2014-02-06 Nick Holland n...@holland-consulting.net: On 02/06/14 05:49, davy wrote: Hi, I've recently was asked to take over the maintenance of an old OpenBSD machine, which has not been updated in the last 7 years. Currently the machine has been running for close to 1000 days on 4.1. It has been a while since I worked with OpenBSD (shame on me), and I'm really not sure what the best way would be to upgrade this machine, knowning I don't have a serial or local access to the box. Can I do a 4.1 - 5.4 in one shot? thx! Davy You have a seven+ year old machine, with comparibly old disks. My suggestion: Build out a new machine using -current (yes, not 5.4. you have a big bump coming with 5.4 to 5.5, but if you install -current now, you are over the bump...then start back on releases/stable with 5.5). Configure the new machine exactly as you want it. Now, put it in service, decom the old machine...or minimum, swap the disks out of the old machine with these newly configured disks. This way, you never lose your functioning system...and you can freshen your hardware, too. Nick.
Re: Upgrade path from 4.1?
On Thu, 6 Feb 2014, davy wrote: Can I do a 4.1 - 5.4 in one shot? Nope. One version at a time, .. though the better solution would be to do a fresh install and copy data. Lee
Re: Upgrade path from 4.1?
Shudder. NO! :-) Aside from the very valid hardware concerns Nick mentioned, there are too many flag days of various kinds strewn along that path. Skip them all, start fresh with a -current snapshot. Ken On 6 February 2014 05:49, davy davy.van.de.mo...@gmail.com wrote: Hi, I've recently was asked to take over the maintenance of an old OpenBSD machine, which has not been updated in the last 7 years. Currently the machine has been running for close to 1000 days on 4.1. It has been a while since I worked with OpenBSD (shame on me), and I'm really not sure what the best way would be to upgrade this machine, knowning I don't have a serial or local access to the box. Can I do a 4.1 - 5.4 in one shot? thx! Davy
Re: Upgrade path from 4.1?
Heck, even pkg_add won't be too happy. I've finally scraped a few compatibility items that were around 7 years ago, like support for @md5 checksums...
Re: Upgrade path from 4.1?
On Thu, 6 Feb 2014, Kenneth Westerback wrote: Shudder. NO! :-) Aside from the very valid hardware concerns Nick mentioned, there are too many flag days of various kinds strewn along that path. Skip them all, start fresh with a -current snapshot. Much better to start with new CD set, eh? Lee
Re: Upgrade path from 4.1?
On 6 February 2014 11:44, L. V. Lammert l...@omnitec.net wrote: On Thu, 6 Feb 2014, Kenneth Westerback wrote: Shudder. NO! :-) Aside from the very valid hardware concerns Nick mentioned, there are too many flag days of various kinds strewn along that path. Skip them all, start fresh with a -current snapshot. Much better to start with new CD set, eh? Well, that would imply waiting for May 1 or whenever the physical CD's are available. Starting now with a -current snapshot means getting everything working in the meantime and then ordering the new CD's and installing the -release (or -stable) files without worrying about flag days. We are very close to locking 5.5 so very little major will be changing between now and CD delivery. Ken Lee
Re: Upgrade path from 4.1?
On Thu, 6 Feb 2014, Kenneth Westerback wrote: Well, that would imply waiting for May 1 or whenever the physical CD's are available. 5.4 is available now, .. Starting now with a -current snapshot means getting everything working in the meantime and then ordering the new CD's and installing the Far better to recommend CD installs, .. -current or -release may require a tad more expertise to manage. Lee
Re: Upgrade path from 4.1?
L. V. Lammert [l...@omnitec.net] wrote: On Thu, 6 Feb 2014, davy wrote: Can I do a 4.1 - 5.4 in one shot? Nope. One version at a time, .. though the better solution would be to do a fresh install and copy data. I don't see why everyone recommends install one version at a time. It is insane. Except for the time_t bump, i'd just upgrade. With the bump, I'd either upgrade if it was a remote system, or do a fresh install. There may be gotchas that you can only figure out by replicating it locally first. But there is no requirement in OpenBSD to upgrade one version at a time that is just a total fucking waste of time and bandwidth.
Re: Upgrade path from 4.1?
L. V. Lammert [l...@omnitec.net] wrote: On Thu, 6 Feb 2014, davy wrote: Can I do a 4.1 - 5.4 in one shot? Nope. One version at a time, .. though the better solution would be to do a fresh install and copy data. What I'm recommending isn't really an upgrade so much as using the old box to bootstrap a newest snapshot. As long as the bootblocks are still compatible, you can do it.
Re: Upgrade path from 4.1?
On Thu, 6 Feb 2014, Chris Cappuccio wrote: I don't see why everyone recommends install one version at a time. It's not a recommendation, it is reality. Each upgrade is based on the previuos version - skipping versions is not supported. Lee
Re: Upgrade path from 4.1?
On Thu, 6 Feb 2014, Chris Cappuccio wrote: What I'm recommending isn't really an upgrade so much as using the old box to bootstrap a newest snapshot. As long as the bootblocks are still compatible, you can do it. Why? A clean build on a new machine would be the best solution in that case, .. then reconfigure with data from the old box/disk. Also, it is not good to recommend snapshots - most users do not need that level of complexity. CDs are a much better alternative, and give something back to the project. You DO purchase more than one set of CDs for every release, right? Lee
Re: Upgrade path from 4.1?
On 06/02/14 12:45 PM, L. V. Lammert wrote: On Thu, 6 Feb 2014, Chris Cappuccio wrote: I don't see why everyone recommends install one version at a time. It's not a recommendation, it is reality. Each upgrade is based on the previuos version - skipping versions is not supported. There is a difference between supported and supported. What Chris said is true. Its the difference between people blindly following how-to's and actually understanding what they're doing and this is not very complex at all. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: Upgrade path from 4.1?
On 6 February 2014 12:31, L. V. Lammert l...@omnitec.net wrote: On Thu, 6 Feb 2014, Kenneth Westerback wrote: Well, that would imply waiting for May 1 or whenever the physical CD's are available. 5.4 is available now, .. Starting now with a -current snapshot means getting everything working in the meantime and then ordering the new CD's and installing the Far better to recommend CD installs, .. -current or -release may require a tad more expertise to manage. Lee I violently disagree! And particularly in this case. Where it would be far better to avoid one whole upgrade cycle by getting the environment working with -current and moving to 5.5-stable safe in the knowledge that you don't have to re-check for flag days, configuration parsing changes, etc. Now, *buying* CD's is always highly recommended. The more the better! Ken
Re: Upgrade path from 4.1?
On Thu, Feb 06, 2014 at 11:45:52AM -0600, L. V. Lammert wrote: On Thu, 6 Feb 2014, Chris Cappuccio wrote: I don't see why everyone recommends install one version at a time. It's not a recommendation, it is reality. Each upgrade is based on the previuos version - skipping versions is not supported. Lee Nah, if you know what you're doing you can skip lots of versions. It's not recommmended because if you fuck up, well, you're on your own. Developers will laugh at you and not help (even more so than usual, I mean)
Re: Upgrade path from 4.1?
On 6 February 2014 12:40, Chris Cappuccio ch...@nmedia.net wrote: L. V. Lammert [l...@omnitec.net] wrote: On Thu, 6 Feb 2014, davy wrote: Can I do a 4.1 - 5.4 in one shot? Nope. One version at a time, .. though the better solution would be to do a fresh install and copy data. What I'm recommending isn't really an upgrade so much as using the old box to bootstrap a newest snapshot. As long as the bootblocks are still compatible, you can do it. And, surprise!, boot blocks do change. 5.5 will be an example as things are rearranged and unified. Ken
Re: Upgrade path from 4.1?
On 6 February 2014 12:40, Chris Cappuccio ch...@nmedia.net wrote: L. V. Lammert [l...@omnitec.net] wrote: On Thu, 6 Feb 2014, davy wrote: Can I do a 4.1 - 5.4 in one shot? Nope. One version at a time, .. though the better solution would be to do a fresh install and copy data. What I'm recommending isn't really an upgrade so much as using the old box to bootstrap a newest snapshot. As long as the bootblocks are still compatible, you can do it.
Re: Upgrade path from 4.1?
On Thu, 6 Feb 2014, Marc Espie wrote: Nah, if you know what you're doing you can skip lots of versions. It's not recommmended because if you fuck up, well, you're on your own. The OP gave no such indication, .. hence my recommendation for step-by-step or new machine. Developers will laugh at you and not help (even more so than usual, I mean) AND create a lot of troll fodder, .. best avoided. Lee
Re: Upgrade path from 4.1?
On Thu, Feb 06, 2014 at 13:03, L. V. Lammert wrote: On Thu, 6 Feb 2014, Marc Espie wrote: Nah, if you know what you're doing you can skip lots of versions. It's not recommmended because if you fuck up, well, you're on your own. The OP gave no such indication, .. hence my recommendation for step-by-step or new machine. well, none of 4.2, 4.3, 4.4, 4.5, , ... are supported now either, or even available on most ftp mirrors, so any problems encountered midway through will be met with the same response of try something newer.
Re: Upgrade path from 4.1?
Your best option would be to backup data and configs, and reinstall fresh. There are so many releases between 4.1 and 5.4 that you're going to spend a lot of time just to get to -current or -stable 5.4, while you're still gonna have to modify config files that have changes since 4.1 that it probably wouldn't be worth the time and effort. As far as skipping versions, first you're gonna have a lot of issues going straight from 4.1 to 5.4. If you just look at the changelogs between each version, you'll see a lot of things have been removed or considered defunct, and configuration for services may have changed dramatically (pf and softraid, for example). Do yourself the favor and save the headaches by just reloading fresh and porting over any configs. On Thu, Feb 6, 2014 at 4:49 AM, davy davy.van.de.mo...@gmail.com wrote: Hi, I've recently was asked to take over the maintenance of an old OpenBSD machine, which has not been updated in the last 7 years. Currently the machine has been running for close to 1000 days on 4.1. It has been a while since I worked with OpenBSD (shame on me), and I'm really not sure what the best way would be to upgrade this machine, knowning I don't have a serial or local access to the box. Can I do a 4.1 - 5.4 in one shot? thx! Davy
Re: Upgrade path from 4.1?
L. V. Lammert [l...@omnitec.net] wrote: On Thu, 6 Feb 2014, Chris Cappuccio wrote: I don't see why everyone recommends install one version at a time. It's not a recommendation, it is reality. Each upgrade is based on the previuos version - skipping versions is not supported. Because it takes a little more knowledge of what changes between releases. Nobody who uses OpenBSD in a serious capacity sits around upgrading from release to release. That advice is for people who follow directions for upgrading from each release to each successive release.
Re: Upgrade path from 4.1?
Kenneth Westerback [kwesterb...@gmail.com] wrote: And, surprise!, boot blocks do change. 5.5 will be an example as things are rearranged and unified. But you can still use old bootblocks to run the new kernel as a bootstrap You don't get the proper random seed functionality until you update your bootblocks, so obviously, do so. I'm not sure there was ever a release where old bootblocks wouldn't work with a new kernel, at least on amd64.
Re: Upgrade path from 4.1?
Back to reality... Let's suppose I have very old OpenBSD box
like it was written.
Usually data should be OK (ftp data, web data, DB data dump??...), but can
I just copy for example /etc/master.passwd to a new fresh installed 5.5-current?
I'm asking because one had to regenerate /etc/{pwd,spwd}.db files
(http://www.openbsd.org/faq/current.html#20130813)?
I think upgraded one by one is bizarre but one should know what
part of OS was involved in old data, so he can be sure such old
data are still usable.
Any advices where one should be careful if one is trying to import
data from very old OpenBSD to latest versions? (In current.html
there's at least rrdtool, but are there any others?)
jirib
Re: Upgrade path from 4.1?
Brad Smith [b...@comstyle.com] wrote: On 06/02/14 12:45 PM, L. V. Lammert wrote: On Thu, 6 Feb 2014, Chris Cappuccio wrote: I don't see why everyone recommends install one version at a time. It's not a recommendation, it is reality. Each upgrade is based on the previuos version - skipping versions is not supported. There is a difference between supported and supported. What Chris said is true. Its the difference between people blindly following how-to's and actually understanding what they're doing and this is not very complex at all. There are some complexities, and I have most of them memorized, so if someone wants to discuss how to do this on the list, just ask. I dare say this instruction set will even work for a jump from 4.1, although I wouldn't guarantee it :) So, to jump over the time_t bump remotely, I typically do something like: echo /usr/sbin/pwd_mkdb /etc/master.passwd /etc/rc.local cp /sbin/reboot /reboot mv /distloc/bsd.mp /bsd cd / rm -r /usr/X11R6 /usr/include /usr/share /var/log/lastlog /var/log/wtmp touch /var/log/lastlog /var/log/wtmp pkg_info -mq /root/pkg_list_manual pkg_info -q /root/pkg_list_full do anything else related to your ports like dump SQL database tables tar xzpf /distloc/base55.tgz now you can no longer run old binaries, goodbye! /reboot That's as far as you can go once the new ABI is unpacked over the old system!! Now when you reboot, you have an old set of /etc scripts, and non-functional compiler, X11, packages, etc. But you have a working base system that you can finish the rest with. Basic finish: cd / tar xzpf /distloc/comp55.tgz tar xzpf /distloc/man55.tgz tar xzpf /distloc/game55.tgz cd /dev ./MAKEDEV all installboot rootdisk0 And if you want X11 for server-only (no workstation) the also unpack xbase55 and xshare55. If you are sitting at a workstation, you're better off using bsd.rd and 'U'pgrade. Now you can replace all packages, upgrade /etc with sysmerge or by hand, and reinstall packages like so: pkg_add -z -l /root/pkg_list_manual pkg_add -za -l /root/pkg_list_full Also you are good to clean up old shared object crap out of /usr/lib. You can identify these because they will have old timestamps in ls -l. Now, reboot again and you are fully upgraded. Reinstall any SQL databases or whatever by hand too. I skipped a lot of the 'rm /usr/share/man/blah' crap because it's already removed in the rm -r step. But with the ABI change, you will want to clean out old binaries from /usr/bin, /usr/sbin, and so on. Honestly I've never used sysmerge and would probably benefit by learning it. I did steal the pkg_list idea from faq/current.html. That is always a good place to look when you're fucking around like this. If you have remote IPMI access, you might be better off just following the faq directions and doing bsd.rd upgrade. Beats me. I don't have IPMI. Most of the work involved here you have to do anyways, like dump/restore databases, reinstall packages, sysmerge or hand-merge /etc, and so on. Chris
Re: Upgrade path from 4.1?
On Thu, Feb 06, 2014 at 11:56:05AM -0600, L. V. Lammert wrote: On Thu, 6 Feb 2014, Chris Cappuccio wrote: What I'm recommending isn't really an upgrade so much as using the old box to bootstrap a newest snapshot. As long as the bootblocks are still compatible, you can do it. Why? A clean build on a new machine would be the best solution in that case, .. then reconfigure with data from the old box/disk. Also, it is not good to recommend snapshots - most users do not need that level of complexity. CDs are a much better alternative, and give something back to the project. You DO purchase more than one set of CDs for every release, right? Lee I DO NOT recommend going straight to -current, twice I have made that jump on my remote server only to find that the packages for something important suddenly don't work even though my -current box at home worked OK. Buy a CD. Do a fresh install. And since a special moment with lock showing up is soon to happen, then upgrading that to -current should work fine. But yes upgrade to 5.5 -current afterwards. Or wait a little and put -current at home/office and test and then install if OK. It never hurts to be careful. And backup everything before you turn off those disks since they are old. Old disks keep running but often can't restart from a stop. Chris Bennett
Re: Upgrade path from 4.1?
On Thu, Feb 6, 2014, at 04:07 PM, Chris Bennett wrote: It never hurts to be careful. And backup everything before you turn off those disks since they are old. Old disks keep running but often can't restart from a stop. If for some reason you do find yourself with disks that will not spin up again after being spun down, try leaving the box powered up at the failed boot screen for a time (at least 15 minutes, I recommend at least 30 minutes) before rebooting. This at least worked for me on a 200 megabyte disk in the 1990s (I fortunately have not had the problem since). -- Shawn K. Quinn skqu...@rushpost.com
Re: Upgrade path from 4.1?
Chris Bennett [chrisbenn...@bennettconstruction.us] wrote: On Thu, Feb 06, 2014 at 11:56:05AM -0600, L. V. Lammert wrote: On Thu, 6 Feb 2014, Chris Cappuccio wrote: What I'm recommending isn't really an upgrade so much as using the old box to bootstrap a newest snapshot. As long as the bootblocks are still compatible, you can do it. Why? A clean build on a new machine would be the best solution in that case, .. then reconfigure with data from the old box/disk. Also, it is not good to recommend snapshots - most users do not need that level of complexity. CDs are a much better alternative, and give something back to the project. You DO purchase more than one set of CDs for every release, right? Lee I DO NOT recommend going straight to -current, twice I have made that jump on my remote server only to find that the packages for something important suddenly don't work even though my -current box at home worked OK. It might help to report package problems. The current snapshots are now very close to what you are going to see in the 5.5 release. Buy a CD. Do a fresh install. And since a special moment with lock showing up is soon to happen, then upgrading that to -current should work fine. But yes upgrade to 5.5 -current afterwards. This is probably the time where most people would recommend against that since it is essentially a complete reinstall of all items to upgrade from pre-5.5 to 5.5 due to time_t ABI change. Or wait a little and put -current at home/office and test and then install if OK. It never hurts to be careful. And backup everything before you turn off those disks since they are old. Old disks keep running but often can't restart from a stop. Yeah keep backups any of this crazy stuff will drive you nuts when you fuck up all your data and can't figure out how to fix it. Chris
Re: Upgrade path from 4.1?
On Thu, Feb 06, 2014 at 03:54:17PM -0800, Chris Cappuccio wrote: It never hurts to be careful. And backup everything before you turn off those disks since they are old. Old disks keep running but often can't restart from a stop. Yeah keep backups any of this crazy stuff will drive you nuts when you fuck up all your data and can't figure out how to fix it. Chris Thats what vim and perl are for. :%s/fucked_up_data/good_data/g and perl automagically fixes any lost data. Voila! All is well again. ;-) Chris
