Why wouldn't you simply update your 8.1 to 8.4?
2013/7/27 Conny Andersson atar...@telia.com
Hi,
I have a workstation with two factory installed hard disks. The first
disk, ada0, is occupied by a Windows 7 Pro OS (mainly kept for the three
year warranty of the workstation as Dell techs
On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote:
Hi,
I have a workstation with two factory installed hard disks. The first disk,
ada0, is occupied by a Windows 7 Pro OS (mainly kept for the three year
warranty of the workstation as Dell techs mostly speak the Microsoft
On 28/07/2013 06:54, Polytropon wrote:
And here, kids, you can see the strength of open source
operating system: You can see _why_ something happens. :-)
Too true!
On Sat, 27 Jul 2013 20:35:09 +0100, Frank Leonhardt wrote:
On 27/07/2013 19:57, David Noel wrote:
So the system panics in
Ok folks, thanks again for all the help. Using the feedback I
submitted a PR (#180894) --
http://www.freebsd.org/cgi/query-pr.cgi?pr=180894. I also submitted a
follow-up to it with Frank's code and notes. What next? I don't really
know what happens from here, but I'm guessing/hoping that someone's
On 28/07/2013 06:38, David Noel wrote:
Ok folks, thanks again for all the help. Using the feedback I
submitted a PR (#180894) --
http://www.freebsd.org/cgi/query-pr.cgi?pr=180894. I also submitted a
follow-up to it with Frank's code and notes. What next? I don't really
know what happens from
On Sun, 28 Jul 2013, Frank Leonhardt wrote:
So it boils down to:
a) Leave is is, as it can detect when the kernel has trashed its vnode table;
or
b) It's probably caused by expected FS corruption, so handle it gracefully.
It would be good to log a system error message like filesystem may
On Sun, 28 Jul 2013, Polytropon wrote:
On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote:
A very important question is if sysinstall's option Install the FreeBSD
Boot Manager detects that I have a FreeBSD 8.3 and detect it as slice 2 on
disk 1?
I'm not sure I'm following you
On Sun, 28 Jul 2013 08:18:39 -0600 (MDT), Warren Block wrote:
On Sun, 28 Jul 2013, Polytropon wrote:
On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote:
A very important question is if sysinstall's option Install the FreeBSD
Boot Manager detects that I have a FreeBSD 8.3 and
On 07/27/13 21:12, cpghost wrote:
A more robust file system would halt all processes, and perform
an in-kernel fsck on the filesystem and its internal (in-memory)
structures to repair the damage... and THEN resume the processes.
However, this is a major project, and we don't have a
On Sun, 28 Jul 2013, Polytropon wrote:
On Sun, 28 Jul 2013 08:18:39 -0600 (MDT), Warren Block wrote:
On Sun, 28 Jul 2013, Polytropon wrote:
On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote:
A very important question is if sysinstall's option Install the FreeBSD
Boot Manager
In freebsd-questions Digest, Vol 477, Issue 8, Message: 10
On Sat, 27 Jul 2013 19:39:30 +0200 (CEST) Conny Andersson atar...@telia.com
wrote:
Hi,
I have a workstation with two factory installed hard disks. The first disk,
ada0, is occupied by a Windows 7 Pro OS (mainly kept for the
Hi Ian,
Thank you for all of your advices regarding my questions. I have been using
FreeBSD for more than ten years, but I never heard of sade (sysadmins disk
editor). That is one of the joyful things with running FreeBSD/Unix; there
is always something earlier unheard of to explore. And,
Hi Peter,
I need much more disk space for the FreeBSD 8.4-RELEASE, so I will need the
space of the two 'old' slices.
Thanks,
Conny
On Sun, 28 Jul 2013, Peter Andreev wrote:
Why wouldn't you simply update your 8.1 to 8.4?
2013/7/27 Conny Andersson atar...@telia.com
Hi,
I have a
Hi Warren and Polytropon,
A few minutes ago I booted up from a FreeBSD-8.4-RELEASE-amd64-memstick.img
to experience that it is sysinstall that is used in that release.
Next, I did a 'dummy' custom installation. And, as I supposed sysinstall
recognized disk ada0 as ad4 and disk ada1 as ad6.
Help! I just used freebsd-update to upgrade a system to FreeBSD
9.1-RELEASE-p5 to close the latest security holes. I then rebuilt
my custom kernel and tried to reboot. I'm now getting the message
Can't work out which disk we are booting from.
Guessed BIOS device 0x not found by probes,
On Sun, 28 Jul 2013, Conny Andersson wrote:
Hi Warren and Polytropon,
A few minutes ago I booted up from a FreeBSD-8.4-RELEASE-amd64-memstick.img
to experience that it is sysinstall that is used in that release.
Next, I did a 'dummy' custom installation. And, as I supposed sysinstall
On Jul 28, 2013, at 12:55 PM, Conny Andersson wrote:
Hi Ian,
Thank you for all of your advices regarding my questions. I have been using
FreeBSD for more than ten years, but I never heard of sade (sysadmins disk
editor). That is one of the joyful things with running FreeBSD/Unix; there
On Sun, 28 Jul 2013 22:23:38 +, Teske, Devin wrote:
In this case, sade is (or was) a direct by-product of the death
of sysinstall(8). It only exists in 9 or higher.
% which sade
/usr/sbin/sade
System is FreeBSD 8.2-STABLE of August 2011. I think sade has
been introduced in a v8 version of
Hi Devin,
Apropos sade (sysadmins disk editor). I have it at /usr/sbin/sade and I am
running a FreeBSD 8.3. I also mounted FreeBSD 8.1 and FreeBSD 8.2 and found
sade at /usr/sbin/ even in these older FreeBSDs.
Regards,
Conny
On Sun, 28 Jul 2013, Teske, Devin wrote:
In this case, sade is
On 29/07/2013 08:23, Polytropon wrote:
On Sun, 28 Jul 2013 22:23:38 +, Teske, Devin wrote:
In this case, sade is (or was) a direct by-product of the death
of sysinstall(8). It only exists in 9 or higher.
% which sade
/usr/sbin/sade
System is FreeBSD 8.2-STABLE of August 2011. I think
20 matches
Mail list logo
