I have tracked down the issue. Not sure whether this is a PR issue or not...
On 2013-06-06, at 11:18 AM, Polytropon wrote:
On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
Strangely, it seems that I cannot boot single user, either
using boot -s from the boot loader
Hi Everyone,
On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
Strangely, it seems that I cannot boot single user, either
using boot -s from the boot loader, or using the boot menu.
When I get to the point where the root filesystem is mounted,
it hangs right after printing
Strangely, it seems that I cannot boot single user, either using boot -s from
the boot loader, or using the boot menu. When I get to the point where the
root filesystem is mounted, it hangs right after printing the message:
Trying to mount root from ufs:/dev/ada0s1a
Interestingly, there seems
[ Condensation of earlier comments below ]
On 2013-06-06, at 11:18 AM, Polytropon wrote:
On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
When I get to the point where the root filesystem is mounted,
it hangs right after printing the message:
Trying to mount root from ufs
Sorry to follow myself up . . .
On Wed, 12 May 2010, A. Wright wrote:
I just noticed, however, the following two interesting lines that
/var/log/messages seems to have acquired:
May 12 15:44:00 qemg kernel: ad8: FAILURE - SMART status=51READY,DSC,ERROR
error=4ABORTED
May 12
On Wed, 12 May 2010, Adam Vande More wrote:
On Wed, May 12, 2010 at 6:21 PM, A. Wright
and...@qemg.orgmailto:and...@qemg.org wrote:
As far as I can tell, it is a standard 512 byte sector. The
general lack of documentation with this drive (shipped in a
plastic coffin -- the only docs
I have a puzzler.
After postponing an upgrade from 7.2 to 8.0 for some time,
I now am attempting to make the transition.
In the 7.2 install, I have one dangerously dedicated disk used
only for backup (the accommodation of which is why I postponed
the install in the first place), as well as a
Bernt Hansson wrote:
I've got an usb flash disc kingston datatraveler DT150 64GB.
That I put pcbsd on to try, and now I can't seem to get it of the stick.
[ deletia ]
Errors when trying fdisk:
fdisk -BI /dev/da0
*** Working on device /dev/da0 ***
fdisk: invalid fdisk partition
On Mon, 4 May 2009, Olivier Nicole wrote:
Exactly which fonts are you having trouble with? I can tell you
whether I can reproduce the issue under 7.1.
Nothing exotic at all: cmr10.300.pk
The error message is:
$ xdvi memo
Note: overstrike characters may be incorrect.
xdvi: Wrong
[ snippage of question re: svn and cvs ]
On Tue, 31 Mar 2009, Chuck Robey wrote:
Andrew Wright wrote:
The primary advantage of using svn is that the _server_ uses a
different protocol to track objects.
I think that's unclear, you can't mean that just having the protocol be
different,
Sorry to follow-up my own note, but . . .
On Wed, 1 Apr 2009, Andrew Wright wrote:
[ further snippage of previous note ]
Strong Caveats:
o ***Early Adopter Warning***: There has not been (as far as I know) a
general call for people to move to this type of repository access except
for
On Thu, 19 Mar 2009, Jaime wrote:
I have a DLT tape drive in a FreeBSD system. With one of the tapes, I
can get tar -cvpf /dev/sa0 -C / . to work. With all the other
tapes, I can't.
Is there some kind of formatting process that I need to do? I tried
mt fsf 1 from this page:
I assume that
Hi All;
I regularly use dump(8) with snapshots to back up my server.
While this seems to have been working perfectly well so far,
upon (re)reading the man page for dump(8), I have noticed a
somewhat scary pair of lines in the paragraph describing
the option for -C cachesize (emphasis with
I regularly use dump(8) with snapshots to back up my server.
While this seems to have been working perfectly well so far,
Sorry to follow-up my own post; I just realized I hadn't mentioned
any version info. The docs I am reading are the ones associated
with 7.1-RELEASE; I haven't checked
On Sun, 1 Feb 2009, RW wrote:
***It is recommended that you always use this option when
dumping a snapshot.***
When you dump a snapshot there are, by definition, no changes between
passes. So it's saying that in that case there in no reason not to
cache.
Ah, that makes
The results of my investigation so far are below:
Filesystem stuff:
- it appears that FreeBSD and OpenBSD use the same partition
table format. Is this true? If so, I can potentially avoid
rebuilding an entire disk if I am right that ...
- FreeBSD can mount and read OpenBSD's version
16 matches
Mail list logo
