On 9/4/06, Ted Johnson <[EMAIL PROTECTED]> wrote:
I also did a search of the document you suggested
and it doesn't even have the word "close" in it, therefore, it would appear
to not address the issue. From your reply, I'm missing something obvious
here. But would you point it out anyway?
Fair
I recently installed 6.0, and there doesn't seem to be a vinum binary.
There is a gvinum binary, but it doesn't even implement all of the
commands in its own help screen.
I'm somewhat confused. Did I screw up my install, or is this normal?
Is there some kind of IP lawsuit over vinum or somethi
Anyone gotten this combo to work?
The heyu port doesn't compile (it thinks timezone is some external
integer or something, in fact it's a function defined in ).
When I run heyu2, I tell it to read from /dev/ttyd0 (that's the
correct kind of tty for a serial line, right?) and it prints this then
h
I put
start_vinum=YES
start_gvinum=YES
in /etc/rc.conf, per the handbook, and it doesn't appear that there
are any startup files for it, which means my filesystems won't boot.
Is there any code I can download to do this, or must I write it myself?
TIA
--
Scientia Est Potentia -- Eppur Si Muove
I also put these in /etc/loader.conf:
vinum.autostart="YES"
gvinum.autostart="YES"
Per the handbook. Neither seems to work.
Now I can't seem to get the disks started, and /dev/gvinum doesn't
exist, so I can't access my data. Can someone lend me a hand here?
The state of [g]vinum is completel
On 6/13/06, Peter A. Giessel <[EMAIL PROTECTED]> wrote:
#1) Do NOT attempt to use both vinum and gvinum at the same time. They
conflict with each other.
vinum doesn't exist in my fbsd distro.
#2) You don't say which version of FreeBSD you are using. (It matters
for which one [vinum/gvinum]
Prepare the disks:
Done:
# disklabel /dev/ad4s1
# /dev/ad4s1:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 398283401 16unused0 0
c: 3982834170unused0 0 # "raw" part,
don't edit
# disklabel /dev/ad4s1
# /dev/ad
On 6/20/06, Travis H. <[EMAIL PROTECTED]> wrote:
It was there last time... what happened?
My mistake. In fooling around with it I had set the state to
something invalid, and I thought that loader.conf went in /etc, not
/boot. I used "rm" on everything, saved, created via a
Hiya,
I finally resolved the source of my gvinum problems. Every time I
reboot, the plexes and volumes come up attached to one another, but
both are size zero and the subdisks exist but are not attached. Has
anyone a guess about the source of this problem?
Also, as an aside, I can add the subd
Hiya,
I'm trying to follow the instructions here:
http://www.mit.edu/~jik/3000cn/
And I don't have some of the drivers that Linux cups does. What cups
or ghostscript ports should I build to get the maximum number of
driver options? There are many of each.
Thanks!
--
Resolve is what distinguis
10 matches
Mail list logo
