As I guessed, I am using standard, not DD mode. Despite of this I was unable
to boot, and even more: FreeBSD 8.0 sysinstall did not find any partitions
neither on the (g)mirror, hardware RAID I described above or any individual
disks part of the RAID. I had to use FreeBSD 7.2 livefs to copy my dat
On Sun, Jun 28, 2009 at 11:47 PM, Daniel Underwood wrote:
> Is there an effort to build a port of chromium for FreeBSD? I recently
> began using chromium on my Linux machine, and the HTML rendering speed
> is quite impressive.
>
> When it has the ability to synchronize bookmarks, I'll use it exclu
Hello,
At work we've a machine which is currently running FreeBSD 7.0 and we
would like to upgrade to 7.2
This machine has an esoteric embedded RAID controller, the "Intel SRCZCR
RAID adapter".
When I installed the machine one year ago I read the RELEASE Hardware
Notes to check whether thi
Julien Cigar wrote:
Hello,
At work we've a machine which is currently running FreeBSD 7.0 and we
would like to upgrade to 7.2
This machine has an esoteric embedded RAID controller, the "Intel SRCZCR
RAID adapter".
When I installed the machine one year ago I read the RELEASE Hardware
Notes
What are the meaning of the messages below when I boot 8.0-RELEASE-p1 and how
can I prevent that?
GEOM: ad6s1: geometry does not match label (255h,63s != 16h,63s).
...
GEOM: ad6s2: geometry does not match label (255h,63s != 16h,63s).
GEOM: ufsid/478e98a7fe5111d0: geometry does not match label (25
I see this too. I even went so far as to edit the labels
and start again and then I got the opposite:
geometry does not match label (16h,63s != 255h,63s)
..so I gave up. Google didnt turn anything up but I dont
see this on FreeBSD 7.x at all. Only 8
So far, it has not been any issue from what I
I liked using idled on 4.11 to kick off idle users as it allowed me to specify
which users can stay connected indefinitely, whereas sshd_config options
ClientAliveCountMax 0 and ClientAliveInterval 60 would kick everyone off after
an hour. I do have a couple of users that have a legitimate need
On Tue, Dec 08, 2009 at 10:21:34PM -0600, Peter Steele thus spake:
Ah, you _probably_ want to do 'make release' -- I have no experience with this
however to be much more help if that _is_ what you need.
Didn't know about that one. I'll have to check it out--thanks.
I started out doing this a
On Tue, 8 Dec 2009 18:25:43 -0500, Robert Huff wrote:
> I just generated new keys using the method specified the the article
> recommended by Giorgos, and I get the same result.
Oops. I was hoping that would help, but it was only a wild guess by
looking at the error message and the Google hits I
Add my name to the list--we get tons of these messages since upgrading to
8.0
-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Bernt Hansson
Sent: Wednesday, December 09, 2009 10:24 AM
To: J.D. Bronson
Cc: freebsd-
>I started out doing this a couple of months ago, and the project has been a
>wealth of experience and knowledge, to say the least.
>
>Once you are able to do manage building a release, you can actually build your
>own update server and distribute binary updates on your custom kernel.
Hmm, inter
What if we tried a custom kernel and removed these lines:
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
I think that might remove these 'errors'.
--
J.D. Bronson
Information Technology
___
On Tue, Dec 8, 2009 at 21:40, Tim Judd wrote:
> Because the livefs uses a MFSROOT system (allows you to make changes
> to the ram-based disk image after boot), you have to load kernel
> modules before the mfsroot is mounted. As an example..
>
> boot cd
> escape to loader prompt
> load /boot/kerne
Hi--
On Dec 9, 2009, at 10:44 AM, Peter Steele wrote:
> Add my name to the list--we get tons of these messages since upgrading to
> 8.0
This isn't new with 8.x; it's been around since 4.0, if not earlier.
For a long time, BIOSes using the older C/H/S addressing mechanism were limited
to ~8
Hi, I can't seem to get it to probe the printer. hp-setup says:
error: No devices found.
error: Error occured during interactive mode. Exiting.
dmesg|grep HP says:
ugen0: on
uhub0
The
http://hplipopensource.com/hplip-web/models/laserjet/hp_laserjet_p2035.html
page says a plugin is required, bu
> Date: Tue, 8 Dec 2009 22:00:29 +0100
> From: Polytropon
> Subject: Re: How do I create large partitions in FreeBSD?
> To: krad
> Cc: Peter Steele ,
> "freebsd-questions@freebsd.org"
>
> Message-ID: <20091208220029.2052102f.free...@edvax.de>
> Content-Type: text/plain; charset=US-ASCII
>
>
On Wed, 9 Dec 2009, Rich Winkel wrote:
Hi, I can't seem to get it to probe the printer. hp-setup says:
error: No devices found.
error: Error occured during interactive mode. Exiting.
Did you run hp-setup from the command line? The GUI has been broken for a
long time.
Can you find the printe
Hi All,
I need to compile a sound driver which need the include file "channel_if.h".
This file seems to be part of FreeBSD kernel definition. The only file I can
find
is "/usr/src/sys/dev/sound/pcm/channel_if.m".
It is similar to a header file but it seems that it should be modified
to have t
I tried FreeBSD 8.0 on a Dell i7 laptop, but the fan is constantly
spinning with maximal speed (and maximal noise).
dev.cpu.0.cx_supported lists only C1. Maybe this is related to
i386/135447 (but I am on 8.0/amd64 and not 7.2/i386).
Even with powerd reducing the frequency to the lowest availa
J.D. Bronson wrote:
> What if we tried a custom kernel and removed these lines:
>
> options GEOM_PART_GPT # GUID Partition Tables.
> options GEOM_LABEL # Provides labelization
>
> I think that might remove these 'errors'.
>
My kernel already has these rem
Well then so much for my idea of removing those options from the kernel.
Darn.
Well if they have 'been' there since earlier FreeBSD
I wonder why we never saw them until 8.x now ?
There must be some reason...
They do not appear to be anything but cosmetic but still
annoying and worrisome for peop
On Wed, 9 Dec 2009 11:42:31 -0800 (PST), James Phillips
wrote:
> I sort of followed the discussion as well. There was some
> disagreement about what "dangreously dedicated" means.
For comparison, I seem to remember that the two concepts
are called "compatibility mode" and "(dangerously) dedicat
On Tue, Dec 8, 2009 at 12:24 PM, Warren Block wrote:
> On Tue, 8 Dec 2009, Derrick Ryalls wrote:
>>
>> uname:
>>
>> FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec
>> 6 11:23:52 PST 2009 ryal...@example.com:/usr/obj/usr/src/sys/FRODO
>> amd64
>>
>> I have most things work
Hi,
I'm looking to buy a tape drive and am currently looking at USB 2.0 DAT tape
drives from HP. I searched the hardware compatibility list and cannot locate
any information tape drives except the disclaimer that SCSI tape drives do
work on SCSI controller cards that are recognized by the FreeBSD
Hi Doug,
> Does anyone have had positive or negative experience using these USB-based
> DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard)
I know that I am not really answering your question but here are a
couple of thoughts that came to my mind when reading your post:
- USB
Corey J. Bukolt wrote:
> Hello list,
>
> I have a FreeNAS box with a CF card for root, and 3 drives (soon to
> be 4) set up with encryption and raidz on top of them. A less than
> excellent detailed report of what I did is here:
> http://bit.ly/5BeZq8 This setup is a bit hackish as after the
> syst
> Hi Doug,
>
> > Does anyone have had positive or negative experience using
> these USB-based
> > DAT tape drives? Specifically, I am looking at the HP
> (Hewlett-Packard)
>
> I know that I am not really answering your question but here are a
> couple of thoughts that came to my mind when readi
On Wed, 9 Dec 2009 11:42:31 -0800 (PST)
James Phillips wrote:
> I sort of followed the discussion as well. There was some
> disagreement about what "dangreously dedicated" means. Does it mean
> getting rid of the DOS partition table (slices?) Or, does it mean
> creating a slice or disks with
RW wrote:
On Wed, 9 Dec 2009 11:42:31 -0800 (PST)
James Phillips wrote:
I sort of followed the discussion as well. There was some
disagreement about what "dangreously dedicated" means. Does it mean
getting rid of the DOS partition table (slices?) Or, does it mean
creating a slice or disks
On Wed, 09 Dec 2009 10:59:51 -0800
Chuck Swiger wrote:
> Hi--
>
> On Dec 9, 2009, at 10:44 AM, Peter Steele wrote:
> > Add my name to the list--we get tons of these messages since
> > upgrading to 8.0
>
> This isn't new with 8.x; it's been around since 4.0, if not earlier.
Something has ch
On Wed, Dec 9, 2009 at 8:33 PM, Rolf Nielsen
wrote:
> RW wrote:
>>
>> On Wed, 9 Dec 2009 11:42:31 -0800 (PST)
>> James Phillips wrote:
>>
>>
>>> I sort of followed the discussion as well. There was some disagreement
>>> about what "dangreously dedicated" means. Does it mean getting rid of the
>>>
On Thu, 10 Dec 2009 01:36:53 +
RW wrote:
> On Wed, 09 Dec 2009 10:59:51 -0800
> Chuck Swiger wrote:
>
> > Hi--
> >
> > On Dec 9, 2009, at 10:44 AM, Peter Steele wrote:
> > > Add my name to the list--we get tons of these messages since
> > > upgrading to 8.0
> >
> > This isn't new with
On Wed, 9 Dec 2009 17:09:05 -0800 , Doug Sampson wrote:
> All I just want to know is whether FBSD will recognize and work with the
> tape drive I posed in my previous email (the Hewlett-Packard StorageWorks
> Q1581SB DAT 160 Tape Drive). Will it be identified as /dev/da* something?
I would guess
On Thu, 10 Dec 2009 02:33:17 +0100, Rolf Nielsen
wrote:
> As far as I understand it, it's called Dangerously Dedicated because it
> may cause other systems not to recognise the disk.
Primarily, it's called "dedicated" (only) because it describes
a setting where a whole hard disk is dedicated to
On Wed, 9 Dec 2009 20:41:40 -0500, Maxim Khitrov wrote:
> On Wed, Dec 9, 2009 at 8:33 PM, Rolf Nielsen
> wrote:
> > As far as I understand it, it's called Dangerously Dedicated because it may
> > cause other systems not to recognise the disk. Consequently, newfs'ing a
> > slice without first part
Corey,
Umm...write a script perhaps?
Nobody else has taken a shot at this one yet, so I'll try. This is
just what I'd do. That said, it's probably not the best solution. It's
an idea. You may have to work out some bugs along the way.
In regards to interrupting the boot process, I don't think thi
On Wed, Dec 9, 2009 at 3:39 PM, Derrick Ryalls wrote:
> On Tue, Dec 8, 2009 at 12:24 PM, Warren Block wrote:
>> On Tue, 8 Dec 2009, Derrick Ryalls wrote:
>>>
>>> uname:
>>>
>>> FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec
>>> 6 11:23:52 PST 2009 ryal...@example.com:/u
Modulok wrote:
> Corey,
>
> Umm...write a script perhaps?
>
> Nobody else has taken a shot at this one yet, so I'll try. This is
> just what I'd do. That said, it's probably not the best solution.
> It's an idea. You may have to work out some bugs along the way.
>
> In regards to interrupting the b
Don't know if that loader.conf change affected this server, I disabled
APIC in loader.conf after finding it may be responsible for a slow clock
on this VMware guest FreeBSD install. I rebooted for the changes to take
affect and it goes now to a mountroot prompt, can't seem to load the
root part
Have this nat rule
rdr rl0 0.0.0.0/0 port 6355 -> 10.0.10.3 port 6355
I can see in the log that tcp packets are being redirected but udp
packets are not. Can not find any verbiage in man 5 0r 8 ipnat that
states rdr rule only matches on tcp packets. I thought tcp/udp packets
should be redirect
Hi,
Successfully upgraded from 7.2 to 8.0 but had my usual problem when
jumping major versions with the make delete-old target.
The problem being that it asks me to confirm deletion of each lib/file
with a "y" and a return. I've found that I never say "n" to any
deletion and it becomes very tedio
Frank Shute wrote:
Hi,
Successfully upgraded from 7.2 to 8.0 but had my usual problem when
jumping major versions with the make delete-old target.
The problem being that it asks me to confirm deletion of each lib/file
with a "y" and a return. I've found that I never say "n" to any
deletion and
> Is there a way to change the Makefile so that they all get deleted
> with just one "y" and a return? Or possibly use yes(1) to script it?
I often
yes | make delete-old
Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/ma
43 matches
Mail list logo
