Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

freebsd-questions Digest, Vol 304, Issue 3

8 views
Skip to first unread message

freebsd-ques...@freebsd.org

unread,
Mar 29, 2010, 4:10:59 PM3/29/10
to freebsd-...@freebsd.org
Send freebsd-questions mailing list submissions to
freebsd-...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
or, via email, send a message with subject or body 'help' to
freebsd-ques...@freebsd.org

You can reach the person managing the list at
freebsd-que...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-questions digest..."


Today's Topics:

1. Re: server gnome disallow normal user to shutdown
(Alejandro Imass)
2. Re: procmail regex help ... sometimes works, sometimes
doesn't... (Mark Shroyer)
3. Re: When do binaries get removed? (Alejandro Imass)
4. Re: pure-ftpd with mysql authentication (m.anis)
5. freebsd-8 support for dell R710 SATA raid-0 (John)
6. Re: freebsd-8 support for dell R710 SATA raid-0 (Adam Vande More)
7. Re: freebsd-8 support for dell R710 SATA raid-0 (Adam Vande More)
8. Re: Routers, switches, and networking hardware (Lee Shackelford)
9. Custom Kernel to Memory Stick (Jay Hall)
10. Re: freebsd-8 support for dell R710 SATA raid-0 (krad)
11. Portsnap snapshot date in past abort (Darren Spruell)
12. Re: random FreeBSD panics (John Baldwin)
13. Re: FreeBSD 8 / amd64 / Xorg / nvidia GeForce 5200 (Tim Gustafson)
14. Re: Hardware RAID controller questions - 3Ware vs RocketRaid
(Andre Albsmeier)
15. Re: random FreeBSD panics (Masoom Shaikh)
16. Re: freebsd-8 support for dell R710 SATA raid-0 (John)
17. Re: random FreeBSD panics (Jeremy Chadwick)
18. Problem with quotas on root partition on FreeBSD 8.0 (M. Vale)
19. Send form to receive Cookies (n01)
20. Re: freebsd-update(8) under sparc64? Why is it not available?
(John Baldwin)
21. Re: freebsd-update(8) under sparc64? Why is it not available?
(Colin Percival)
22. Re: Marvell Yukon Driver for Hp notebook?? (Kaya Saman)
23. Re: random FreeBSD panics (John Baldwin)
24. Re: Marvell Yukon Driver for Hp notebook?? (Warren Block)
25. Re: [ HEADS UP ] Ports unstable for the next 10 days (Doug Barton)
26. Re: [ HEADS UP ] Ports unstable for the next 10 days (Doug Barton)
27. Re: Custom Kernel to Memory Stick (Jay Hall)
28. Create GMIRROR only one slice (??????? ????????)
29. Re: Marvell Yukon Driver for Hp notebook?? (Kaya Saman)
30. Re: [ HEADS UP ] Ports unstable for the next 10 days
(Adam Vande More)
31. Re: Routers, switches, and networking hardware (krad)
32. Re: Create GMIRROR only one slice (krad)


----------------------------------------------------------------------

Message: 1
Date: Mon, 29 Mar 2010 08:22:08 -0400
From: Alejandro Imass <a...@p2ee.org>
Subject: Re: server gnome disallow normal user to shutdown
To: n dhert <ndhe...@gmail.com>
Cc: freebsd-...@freebsd.org
Message-ID:
<a14066a01003290522w47e...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Mar 29, 2010 at 4:55 AM, n dhert <ndhe...@gmail.com> wrote:
> If a FreeBSD8.0/Gnome system is a server, with many individual users, I
> don't want a normal user to be able to do a restart or shutdown or hibernate
> etc... Now any user has the possibility to do that via System / Shutdown
> How to disallow that globally? (except for e.g. the users in the group
> wheel)

I think the option doesn't work even for wheel users. I mean it's
there but in my system it just logs the user out. Anyway you can
disble the menu option with gnome configuration.
http://www.freebsd.org/gnome/ and google things like this "customize
gnome desktop menus"

Best,
Alejandro Imass

> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
>


------------------------------

Message: 2
Date: Mon, 29 Mar 2010 08:22:22 -0400
From: Mark Shroyer <subscribe...@markshroyer.com>
Subject: Re: procmail regex help ... sometimes works, sometimes
doesn't...
To: freebsd-...@freebsd.org
Cc: pa...@pair.com
Message-ID: <4BB09B7E...@markshroyer.com>
Content-Type: text/plain; charset=ISO-8859-1

On 3/29/2010 3:27 AM, pa...@pair.com wrote:
>> From: "osdeii...@gmail.com" <xjyf...@gmail.com>
>> Reply-To: "osdeii...@gmail.com" <xjyf...@gmail.com>
>> Message-ID: <533pbxxy2oc>
>> To: me <m...@me.com>
>> Subject: Fw: \xb8\xf2\xad\xe8\xa5X\xa8\xd3\xbd\xe6~\xb1o\xb4\xa9\xa9f\xaa\xb1\xb5L\xaeM\xa4\xba\xaeg\xb2n\xa7o
>> X-Mailer: inhalation
>> Organization: Microsoft Outlook Express 6.00.2462.0000
>> Mime-Version: 1.0
>> Content-Type: multipart/alternative;
>> boundary="1-104247307-2712732737=:8213"
>> Status: RO
>> X-Status:
>> X-Keywords:
>> X-UID: 63502
>>
>> --1-104247307-2712732737=:8213
>> Content-Type: text/plain; charset="big5"
>> Content-Transfer-Encoding: quoted-printable
>
> [...]
>
> Is "Content-Type:" completely missing from the body of your first
> example? Do you have your examples flipped? I would have thought
> that first example would have delivered in your inbox & second one
> in your unreadable_messages one.

It's actually a single example of a multipart message; that blank line
followed by the random dashes and numbers delimits a part. I'm
wondering if Procmail is having trouble matching this because the
offending charset is specified in a multipart content header rather than
in the message headers.

--
Mark Shroyer
http://markshroyer.com/contact/


------------------------------

Message: 3
Date: Mon, 29 Mar 2010 08:39:58 -0400
From: Alejandro Imass <a...@p2ee.org>
Subject: Re: When do binaries get removed?
To: "Michael D. Norwick" <mnor...@centurytel.net>
Cc: freebsd-questions <freebsd-...@freebsd.org>
Message-ID:
<a14066a01003290539i6ed...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Mar 28, 2010 at 9:03 PM, Michael D. Norwick
<mnor...@centurytel.net> wrote:
> Good evening;
>
> I am using;
> $uname -r
> $8.0-RELEASE
> under Sun VirtualBox 3.1.6.
>
> I am a long time Debian GNU/Linux user who has just installed the above
> release. ═I have installed and used FreeBSD in years past but that was
> around the 5.x-RELEASE. ═I have had a time installing applications from the
> ports tree (a story for another day) and finally resorted to installing
> binaries from the install dvd to get the full working X distribution. ═I
> wanted to start with the 'minimal' set of packages and build from there. ═At
> the moment I have the distributed binaries installed and am
> compiling/installing gcc 4.4 and friends.
> I have the current FreeBSD handbook but it does not seem to have the answer
> to the following question.
> When building and installing an application from ports, how does the
> original binary or script, in /usr/bin, /usr/lib, /usr/etc..., from the
> distribution, get removed? ═The make install foo command does not appear to
> symlink the original application location to the new one in
> /usr/local/whatever. ═Does it even matter?
>


Hi Michael,

I too come the Debian world, so here are some bullets that I've picked
up along the way:

1) FBSD make a clean separation of 'base' from everything else. I
personally think this is one of the greatest strengths of FBSD. You
may have or need stuff from the ports that's already in the base but
it doesn't matter, you can can have both versions. The base is /bin
/usr/bin /lib /usr/lib, etc. and _everything else_ is /usr/local -
when you upgrade the system this will make _a lot_ of sense.

2) There are certain things in base like sendmail for example that
should not be deinstalled just de-activated via conf, other include
bind, gcc, and several other things. There are many simple how-to's
into installing things that 'compete' with base, at least for the more
common things.

3) You can install binary packages or compile from the ports
collection. Large bulky packages like Xorg, Gnome, KDE, OpenOffice are
probably better installed from pre-compiled binaries with pkg_add,
much the same way as aptitude in Debian. Besides, there is little
customization and compiling options that are useful. But if you are
installing Apache for example, it makes sense to install from the
ports collection because you will get the chance to choose very
specific compile time options and the binary will be optimized for
your specific hardware. It doesn't matter if you install from ports or
binaries, the package registration is common, so if you add with
pckg_add you can remov from the ports directory and vice-versa.


Best,
Alejandro Imass


> Thank You,
> Michael D. Norwick
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
>


------------------------------

Message: 4
Date: Mon, 29 Mar 2010 19:59:04 +0700
From: "m.anis" <m.a...@arc.itb.ac.id>
Subject: Re: pure-ftpd with mysql authentication
To: freebsd-...@freebsd.org
Message-ID: <4BB0A418...@arc.itb.ac.id>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 29/03/2010 16:55, Jerry wrote:
> On Mon, 29 Mar 2010 11:28:49 +0700, m.anis<m.a...@arc.itb.ac.id>
> articulated:
>
>
>> Hi all,
>> I have problem with my pure-ftpd with mysql auth
>> I don't know where the error
>> I look on the database with phpmyadmin, and everything goes well
>>
>> here my config:
>> pureftpd-mysql.conf
>>
>> /MYSQLSocket /tmp/mysql.sock
>> MYSQLServer localhost
>> MYSQLPort 3306
>> MYSQLUser<mysqluser>
>> MYSQLPassword<mysqlpass>
>> MYSQLDatabase<mysqldb>
>>
>> /////
>>
>> pure-ftpd.conf
>>
>> [...]
>> ChrootEveryone yes
>> [...]
>> MySQLConfigFile /usr/local/etc/pure-ftpd/pureftpd-mysql.conf
>> [...]
>> CreateHomeDir yes
>> [...]
>>
> If you are unable to secure a suitable solution to your problem here,
> you might try the "pure-ftpd" mailing lists, available here:
>
> http://www.pureftpd.org/project/pure-ftpd/support
>
> I have used them in the past with great success.
>
>
Thanks a lot,
Sorry for trouble

--
--
Best Regards

------------------------------

Message: 5
Date: Mon, 29 Mar 2010 14:53:40 +0100
From: John <comp...@googlemail.com>
Subject: freebsd-8 support for dell R710 SATA raid-0
To: freebsd-...@freebsd.org
Cc: freebsd-...@freebsd.org
Message-ID: <20100329135340.GA85635@potato>
Content-Type: text/plain; charset=us-ascii

Hello list

I've run into a bit of an impasse with freebsd8 nd dell R710 server.
Basically it has 3x 2TB disks (SATA) connected to a LSI card (on the
order it is referred to as SAS6IR/PERC H200). I make the virtual disk on
the SATA card (raid0 gives about 5.4Tb) but freebsd, after sysinstall
loads and I set the timezone and keyboard, won't see the disk.

I am accessing the server remotely via IDRAC6. This means I have a great
deal of difficulty grabbing the console with alt-f2 on bootup.

I have the feeling that maybe I have to pass a parameter to freebsd boot
to make it see the virtual disk. Is this the cade? Or is the card just
pants? Or is it not possible to boot over 2Tb? Or perhaps I need to boot
a running system from a SD card, and then make the virtual disk?

Or is it a sysinstall issue? Or a card issue? Freebsd sees the card (at
least freebsd-9 did) but not the disk (same as freebsd-8)

FWIW CentOS won't see it either. Please help!
--
John - comp dot john at googlemail dot com
OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop
GPG: 0xF08A33C5


------------------------------

Message: 6
Date: Mon, 29 Mar 2010 08:31:59 -0600
From: Adam Vande More <amvan...@gmail.com>
Subject: Re: freebsd-8 support for dell R710 SATA raid-0
To: John <comp...@googlemail.com>
Cc: freebsd-...@freebsd.org, freebsd-...@freebsd.org
Message-ID:
<6201873e1003290731x148...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Mar 29, 2010 at 7:53 AM, John <comp...@googlemail.com> wrote:

> Hello list
>
> I've run into a bit of an impasse with freebsd8 nd dell R710 server.
> Basically it has 3x 2TB disks (SATA) connected to a LSI card (on the
> order it is referred to as SAS6IR/PERC H200). I make the virtual disk on
> the SATA card (raid0 gives about 5.4Tb) but freebsd, after sysinstall
> loads and I set the timezone and keyboard, won't see the disk.
>
> I am accessing the server remotely via IDRAC6. This means I have a great
> deal of difficulty grabbing the console with alt-f2 on bootup.
>
> I have the feeling that maybe I have to pass a parameter to freebsd boot
> to make it see the virtual disk. Is this the cade? Or is the card just
> pants? Or is it not possible to boot over 2Tb? Or perhaps I need to boot
> a running system from a SD card, and then make the virtual disk?
>
> Or is it a sysinstall issue? Or a card issue? Freebsd sees the card (at
> least freebsd-9 did) but not the disk (same as freebsd-8)
>
> FWIW CentOS won't see it either. Please help!
>

You'll need to use GPT partition instead of MBR if you're trying to boot
with a size > TB. AKAIK, sysinstall doesn't support this, requiring a more
"hands on" installation.

If you haven't considered it, it may be worthwhile to use ZFS. In that
scenario, you'd want to the controller to present the disks as JBOD and use
RAIDZ. Once again, sysinstall doesn't support this, but there are some good
FreeBSD wiki articles on it.

--
Adam Vande More


------------------------------

Message: 7
Date: Mon, 29 Mar 2010 08:39:58 -0600
From: Adam Vande More <amvan...@gmail.com>
Subject: Re: freebsd-8 support for dell R710 SATA raid-0
To: John <comp...@googlemail.com>
Cc: freebsd-...@freebsd.org, freebsd-...@freebsd.org
Message-ID:
<6201873e1003290739t588...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Mar 29, 2010 at 8:31 AM, Adam Vande More <amvan...@gmail.com>wrote:

>
>> FWIW CentOS won't see it either. Please help!
>>
>
>
> You'll need to use GPT partition instead of MBR if you're trying to boot
> with a size > TB. AKAIK, sysinstall doesn't support this, requiring a more
> "hands on" installation.
>
> If you haven't considered it, it may be worthwhile to use ZFS. In that
> scenario, you'd want to the controller to present the disks as JBOD and use
> RAIDZ. Once again, sysinstall doesn't support this, but there are some good
> FreeBSD wiki articles on it.
>

Opps, didn't read the RAID-0 bit, still try the GPT stuff, the 2TB MBR is a
hard limit. gstripe(8) would also be an option. With you're RAID-0, were
you looking of for read or write speed? You can still use RAIDZ and
outperform a straight stripe in most workloads if you make use of an ssd
based L2ARC and a ZIL for read and writes respectively.


--
Adam Vande More


------------------------------

Message: 8
Date: Mon, 29 Mar 2010 08:41:41 -0700
From: Lee Shackelford <lee_sha...@dot.ca.gov>
Subject: Re: Routers, switches, and networking hardware
To: Kurt Buff <kurt...@gmail.com>
Cc: ques...@freebsd.org
Message-ID:
<OF9E1E85B3.61B43097-ON882576...@dot.ca.gov>
Content-Type: text/plain; charset=ISO-8859-1

Dear Mr. Buff, Thank you for responding to my inquiry. Yours truly, Lee
Shackelford



Kurt Buff
<kurt.buff@gmail.
com> To
Lee Shackelford
03/26/2010 03:05 <lee_sha...@dot.ca.gov>
PM cc
ques...@freebsd.org
Subject
Re: Routers, switches, and
networking hardware






On Fri, Mar 26, 2010 at 14:46, Lee Shackelford
<lee_sha...@dot.ca.gov> wrote:
>
> Good afternoon, dear FreeBSD enthusiast. ═Is anyone aware of any brand
name
> of router, switch, or other similar networking hardware that is based on
> any variant of the BSD operating system? ═Any comments are appreciated.
> Yours truly, L e e _ S h a c k e l f o r d ═ ═AT ═ d o t ═ dot ═ c a
dot
> g o v

Unless memory fails me, F5, Juniper, and for sure Sidewinder (now
McAfee) firewalls, among others.

Kurt


------------------------------

Message: 9
Date: Mon, 29 Mar 2010 10:49:08 -0500
From: Jay Hall <jh...@socket.net>
Subject: Custom Kernel to Memory Stick
To: freebsd-...@freebsd.org
Message-ID: <03658C6E-697A-43C5...@socket.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes

Ladies and Gentlemen,

I have been asked to explore the possibility of booting FreeBSD from a
memory stick. This was not a problem; worked great when installed
from the distribution CD.

What would be the best way to get our custom configuration onto the
memory stick?

Thanks,

Jay


------------------------------

Message: 10
Date: Mon, 29 Mar 2010 16:57:08 +0100
From: krad <kra...@googlemail.com>
Subject: Re: freebsd-8 support for dell R710 SATA raid-0
To: Adam Vande More <amvan...@gmail.com>
Cc: John <comp...@googlemail.com>, freebsd-...@freebsd.org,
freebsd-...@freebsd.org
Message-ID:
<d36406631003290857v56b...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On 29 March 2010 15:39, Adam Vande More <amvan...@gmail.com> wrote:

> On Mon, Mar 29, 2010 at 8:31 AM, Adam Vande More <amvan...@gmail.com
> >wrote:
>
> >
> >> FWIW CentOS won't see it either. Please help!
> >>
> >
> >
> > You'll need to use GPT partition instead of MBR if you're trying to boot
> > with a size > TB. AKAIK, sysinstall doesn't support this, requiring a
> more
> > "hands on" installation.
> >
> > If you haven't considered it, it may be worthwhile to use ZFS. In that
> > scenario, you'd want to the controller to present the disks as JBOD and
> use
> > RAIDZ. Once again, sysinstall doesn't support this, but there are some
> good
> > FreeBSD wiki articles on it.
> >
>
> Opps, didn't read the RAID-0 bit, still try the GPT stuff, the 2TB MBR is a
> hard limit. gstripe(8) would also be an option. With you're RAID-0, were
> you looking of for read or write speed? You can still use RAIDZ and
> outperform a straight stripe in most workloads if you make use of an ssd
> based L2ARC and a ZIL for read and writes respectively.
>
>
> --
> Adam Vande More
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questi...@freebsd.org"
>


I think his problem is he cant see a device to partition in the first place?


------------------------------

Message: 11
Date: Mon, 29 Mar 2010 08:27:57 -0700
From: Darren Spruell <phatb...@gmail.com>
Subject: Portsnap snapshot date in past abort
To: FreeBSD <freebsd-...@freebsd.org>
Message-ID:
<839aec701003290827u7d2...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Receiving this recently:

Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Latest snapshot on server is older than what we already have!
Cowardly refusing to downgrade from Sun Mar 28 01:00:58 MST 2010
to Sat Mar 27 01:20:17 MST 2010.

I recall in other systems' package management repository update
schemes seeing similar metadata errors and I've always felt it may be
due to the caching on a transparent HTTP proxy on the network egress.
Is the above likely due to such a situation? If so, is there a
canonical "fix" for the issue (configuring cacheability on mirrors,
configuration/tuning on proxies, options that may be passed on client
side to signal bypass of cache?

Or am I completely off base on this one?

FreeBSD 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Jan 5 21:11:58
UTC 2010 ro...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64

# /etc/portsnap.conf
SERVERNAME=portsnap.FreeBSD.org
KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
INDEX INDEX-6 DESCRIBE.6
INDEX INDEX-7 DESCRIBE.7
INDEX INDEX-8 DESCRIBE.8

--
Darren Spruell
phatb...@gmail.com


------------------------------

Message: 12
Date: Mon, 29 Mar 2010 10:48:44 -0400
From: John Baldwin <j...@freebsd.org>
Subject: Re: random FreeBSD panics
To: freebsd...@freebsd.org
Cc: Masoom Shaikh <masoom...@gmail.com>, freebsd-questions
<freebsd-...@freebsd.org>
Message-ID: <20100329104...@freebsd.org>
Content-Type: Text/Plain; charset="iso-8859-15"

On Sunday 28 March 2010 4:28:29 am Masoom Shaikh wrote:
> Hello List,
>
> I was a happy FreeBSD user, just before I installed FreeBSD8.0-RC1. Since
> then, system randomly just freezes, and there is no option other than hard
> boot. I guessed this will get solved in 8.0-RELEASE, but it was not :(
>
> Many times I get vmcore files, not always. I have dumpdev set to AUTO in my
> rc.conf. Almost every time it just fsck's the file-system on reboot. I have
> not lost any files though. This is a Dell Inspiron 1525 Laptop with 1GB ram,
> Intel Core2 Duo T5500 with ATI Radeon X1400 card. The installation in
> question is KDE4 from ports, with radeon/ati driver.
>
> I felt the problem is with wpi driver, then suspected dri driver of X. Then
> I observed system freezes even if none of this is installed. e.g. if it is
> under some load, like building a port and simultaneously fetching something
> over network it hangs, and hangs hard. This persuaded me to think something
> is wrong in kernel scheduling itself. May be it is lost in some deadlock,
> etc... Thus last weekend I thought I would see how immediate previous
> version i.e. FreeBSD-7.3-RELEASE would behave.
>
> I reinstalled FreeBSD7.1 from iso images, svn up'ed FreeBSD7.3 source, did
> the normal buildworld, buildkernel, installkernel, installworld cycle.
> Unfortunatly this kernel is naughty as well ;-), it also freezes with same
> stubbornness. But difference is this time I happen to catch something
> interesting.
>
> It panics on NMI, fatal trap 19 while in kernel mode. Loaded the vmcore file
> in kgdb and got the backtrace. I obtained vmcore files on two occasions. I
> have attached both the back traces. This error most likely suggests hardware
> error in RAM, but Windox7 and XP boot just fine and never caused any errors.

Yes, and note that the chipset has set a register to indicate a RAM parity
error as well, so it is not a random NMI. Have you checked your BIOS' event
log? You may also want to try running with machine checks enabled
(hw.mca.enabled=1 in loader.conf, but it would have to be on very recent 7/8-
stable) to see if you get machine checks for ECC errors. OTOH, if you do not
have ECC memory then this will probably not help.

> To verify if I have errors in my RAM I let run sysutils/memtest86+
> overnight, to double verify I also executed Windows Memory Diagnostic test
> for four times. None of them reported errors. Can anyone here suggest any
> solution.

You can still have bad RAM even if those do not fail.

--
John Baldwin


------------------------------

Message: 13
Date: Mon, 29 Mar 2010 09:21:11 -0700 (PDT)
From: Tim Gustafson <t...@soe.ucsc.edu>
Subject: Re: FreeBSD 8 / amd64 / Xorg / nvidia GeForce 5200
To: freebsd-...@freebsd.org
Message-ID:
<1906563839.1220412698...@mail-01.cse.ucsc.edu>
Content-Type: text/plain; charset=utf-8

> Did you try xrandr? It should report multiple heads (run the command
> without arguments). You can then enable the second monitor using
> something like: xrandr --output DVI1 --auto

xrandr only saw one head.

*sigh*

I just ordered a more modern nVidia card that is supported by the current driver. :)

Tim Gustafson
Baskin School of Engineering
UC Santa Cruz
t...@soe.ucsc.edu
831-459-5354


------------------------------

Message: 14
Date: Mon, 29 Mar 2010 18:46:08 +0200
From: Andre Albsmeier <Andre.A...@siemens.com>
Subject: Re: Hardware RAID controller questions - 3Ware vs RocketRaid
To: Andy Wodfer <wod...@gmail.com>
Cc: freebsd-questions <freebsd-...@freebsd.org>
Message-ID: <20100329164...@curry.mchp.siemens.de>
Content-Type: text/plain; charset=us-ascii

On Thu, 18-Mar-2010 at 09:37:32 +0100, Andy Wodfer wrote:
> Hi,
> We're setting up two backup servers where each server will have about 4TB of
> harddrives (for now) connected (4x1TB and 8x500GB drives). Last night we ran
> into trouble with the 3ware controllers we have (9650SE-8LPML) because we
> couldn't create a larger RAID5 than 1.99TB.

I can only speak for a 9690SA-8I, but this thing is amazing.
It handles FSs over 2TB pretty well:

twa0: <3ware 9000 series Storage Controller> port 0xc800-0xc8ff mem 0xfa000000-0xfbffffff,0xfeaff000-0xfeafffff irq 16 at device 0.0 on pci4
twa0: [ITHREAD]
twa0: INFO: (0x15: 0x1300): Controller details:: Model 9690SA-8I, 128 ports, Firmware FH9X 4.10.00.007, BIOS BE9X 4.08.00.002

And with 8 1TB in a RAID5 drives it gives me:

da0 at twa0 bus 0 target 0 lun 0
box:~>diskinfo /dev/da0
/dev/da0 512 6999924277248 13671727104 851025 255 63

-Andre

>
> We are going to use FreeBSD 8.0 and Bacula, but first we obviously need to
> create a working RAID.
>
> My questions are:
>
> - Are HighPoint RocketRaid controllers a good alternative to 3ware
> controllers? Are RocketRaid controllers true hardware RAID?
>
> - What should we look for in a RAID controller spec to see that it has
> support for larger than 2TB RAIDs?
>
> I've been looking at these:
> http://www.highpoint-tech.com/USA_new/series_rr2300.htm
> http://www.highpoint-tech.com/USA_new/series_rr3500.htm
>
> Any FreeBSD recommendations? Or perhaps for another 3ware controller?
>
> We're using SATAII drives.
>
> Thanks for your help!
>
> Best regards,
> Andreas
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"

--
I am forced by company policy to use Micro$oft products.
I am not responsible for this choice and decline any
responsibility for any harm which may be caused by it.


------------------------------

Message: 15
Date: Mon, 29 Mar 2010 17:01:02 +0000
From: Masoom Shaikh <masoom...@gmail.com>
Subject: Re: random FreeBSD panics
To: Ivan Voras <ivo...@freebsd.org>
Cc: freebsd...@freebsd.org, freebsd...@freebsd.org,
freebsd-...@freebsd.org
Message-ID:
<b10011eb1003291001u767...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras <ivo...@freebsd.org> wrote:
> On 28 March 2010 16:42, Masoom Shaikh <masoom...@gmail.com> wrote:
>
>> lets assume if this is h/w problem, then how can other OSes overcome
>> this ? is there a way to make FreeBSD ignore this as well, let it
>> result in reasonable performance penalty.
>
> Very probably, if only we could detect where the problem is.
> Try adding "options ═ ═ PRINTF_BUFR_SIZE=128" to the kernel

this option is already there

> configuration file if you can, to see if you can get a less mangled
> log outout.
>


------------------------------

Message: 16
Date: Mon, 29 Mar 2010 18:23:52 +0100
From: John <comp...@googlemail.com>
Subject: Re: freebsd-8 support for dell R710 SATA raid-0
To: krad <kra...@googlemail.com>
Cc: Adam Vande More <amvan...@gmail.com>,
freebsd-...@freebsd.org, freebsd-...@freebsd.org
Message-ID: <20100329172352.GA85779@potato>
Content-Type: text/plain; charset=us-ascii

On Mon, Mar 29, 2010 at 04:57:08PM +0100, krad wrote:
>
> I think his problem is he cant see a device to partition in the first
> place?

This is correct.
--
John - comp dot john at googlemail dot com
OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop
GPG: 0xF08A33C5


------------------------------

Message: 17
Date: Mon, 29 Mar 2010 10:30:38 -0700
From: Jeremy Chadwick <fre...@jdc.parodius.com>
Subject: Re: random FreeBSD panics
To: Masoom Shaikh <masoom...@gmail.com>
Cc: freebsd...@freebsd.org, freebsd...@freebsd.org, Ivan
Voras <ivo...@freebsd.org>, freebsd-...@freebsd.org
Message-ID: <2010032917...@icarus.home.lan>
Content-Type: text/plain; charset=iso-8859-1

On Mon, Mar 29, 2010 at 05:01:02PM +0000, Masoom Shaikh wrote:
> On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras <ivo...@freebsd.org> wrote:
> > On 28 March 2010 16:42, Masoom Shaikh <masoom...@gmail.com> wrote:
> >
> >> lets assume if this is h/w problem, then how can other OSes overcome
> >> this ? is there a way to make FreeBSD ignore this as well, let it
> >> result in reasonable performance penalty.
> >
> > Very probably, if only we could detect where the problem is.
> > Try adding "options ═ ═ PRINTF_BUFR_SIZE=128" to the kernel
>
> this option is already there

The key word in Ivan's phrase is "less mangled". Neither use of or
increasing PRINTF_BUFR_SIZE solves the problem of interspersed console
output. I've been ranting/raving about this problem for years now; it
truly looks like a mutex lock issue (or lack of such lock), but I've
been told numerous times that isn't the case.

To developers: what incentives would help get this issue well-needed
attention? This problem makes kernel debugging, panic analysis, and
other console-oriented viewing basically impossible.

--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

------------------------------

Message: 18
Date: Mon, 29 Mar 2010 18:17:12 +0100
From: "M. Vale" <maur...@gmail.com>
Subject: Problem with quotas on root partition on FreeBSD 8.0
To: freebsd-...@freebsd.org
Message-ID:
<85d001331003291017p588...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

Hi, on FreeBSD 8.0 (i386 or AMD64) if we configure to use quotas on root
partition.

It stops on boot with the following message:

Trying to mount root from ufs:/dev/ad0s1a
mount option <userquota> is unknown
mount option <groupquota> is unknown
ROOT MOUNT ERROR: mount option <groupquota> is unknown
If you have invalid mount options, reboot, and first try the following from
the loader prompt:

set vfs.root.mountfrom.options=rw

and then remove invalid mount options from /etc/fstab.

Loader variables:
vfs.root.mountfrom=ufs:/dev/ad0s1a
vfs.root.mountfrom.options=rw,userquota,groupquota,acls

Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
eg. ufs:/dev/da0s1a
eg. cd9660:/dev/acd0
This is equivalent to: mount -t cd9660 /dev/acd0 /

? List valid disk boot devices
<empty line> Abort manual input

mountroot>


If i do:

ufs:/dev/ad0s1a

Then the boot continues and it mount the quotas ok. but if I reboot the same
thing happen again.

This only occurs on FreeBSD 8.

Does anyone have a clue about the problem ?

Best Regards


------------------------------

Message: 19
Date: Mon, 29 Mar 2010 17:45:59 +0400
From: n01 <n...@list.ru>
Subject: Send form to receive Cookies
To: freebsd-...@freebsd.org
Message-ID: <E1NwFHz-0008TA...@f141.mail.ru>
Content-Type: text/plain; charset=koi8-r

Hi Guys,
Goal:
To get cookies from https://www.vip-computers.com/uk/login.aspx by filling in Login, Password and ticking the box remember me.

How it was done before:
I have tried lynx to do that but now it's (as I assume) blocked by their hosting provider.

Question:
Any other way to do that?

Tried:
curl -D /auto/cookies.txt --data-urlencode
"ctl00$ctl00$content1$Content1$txtUser=username&ctl00$ctl00$content1$Content1$txtPass=password&ctl00$ctl00$content1$Content1$btnLogin=Login" https://www.vip-
computers.com/uk/login.aspx (Failed)

wget --cookies=on --keep-session-cookies --save-cookies=/auto/cookies.txt --post-
data="ctl00$ctl00$content1$Content1$txtUser=username&ctl00$ctl00$content1$Content1$txtPass=password" https://www.vip-computers.com/uk/login.aspx (Failed)


------------------------------

Message: 20
Date: Mon, 29 Mar 2010 12:08:10 -0400
From: John Baldwin <j...@freebsd.org>
Subject: Re: freebsd-update(8) under sparc64? Why is it not available?
To: freebsd...@freebsd.org
Cc: Mark Linimon <lin...@lonesome.com>, kens...@freebsd.org,
FreeBSD-...@freebsd.org, Colin Percival <cper...@freebsd.org>,
Marius Strobl <mar...@alchemy.franken.de>
Message-ID: <20100329120...@freebsd.org>
Content-Type: Text/Plain; charset="iso-8859-1"

On Friday 26 March 2010 11:00:28 am Colin Percival wrote:
> I think the best approach towards having FreeBSD Update support for
> sparc64 is to get release cross-building working; that way we would
> be able to use amd64 hardware, which I think we can safely assume
> will continue to be available in ever-increasing speeds.

Err, release cross-building does work AFAIK. ru@ worked on it many years ago.
Have you tried it and run into problems?

--
John Baldwin


------------------------------

Message: 21
Date: Mon, 29 Mar 2010 09:20:55 -0700
From: Colin Percival <cper...@freebsd.org>
Subject: Re: freebsd-update(8) under sparc64? Why is it not available?
To: John Baldwin <j...@freebsd.org>
Cc: Mark Linimon <lin...@lonesome.com>,
FreeBSD-...@freebsd.org, freebsd...@freebsd.org,
kens...@freebsd.org, Marius Strobl <mar...@alchemy.franken.de>
Message-ID: <4BB0D367...@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1

John Baldwin wrote:
> On Friday 26 March 2010 11:00:28 am Colin Percival wrote:
>> I think the best approach towards having FreeBSD Update support for
>> sparc64 is to get release cross-building working; that way we would
>> be able to use amd64 hardware, which I think we can safely assume
>> will continue to be available in ever-increasing speeds.
>
> Err, release cross-building does work AFAIK. ru@ worked on it many years ago.
> Have you tried it and run into problems?

Cross-building "works" in the sense of finishing with something which looks
like a release; but when I tried it a few years ago (when I was writing the
current generation of freebsd-update) there were some files which built
differently for cross vs. native builds. IIRC it wasn't a huge number of
files, though.

--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid


------------------------------

Message: 22
Date: Mon, 29 Mar 2010 21:27:47 +0300
From: Kaya Saman <Sama...@netscape.net>
Subject: Re: Marvell Yukon Driver for Hp notebook??
To: freebsd-...@freebsd.org
Message-ID: <4BB0F123...@netscape.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Well.... I managed to go to Marvell and get the FreeBSD 7.0 x64 driver
and use my USB key to get the driver into the machine:

mount_msdosfs /dev/da0s1 /mnt/usb

I then installed it using the instructions provided in the README.txt
file and now I can't even boot BSD any more :-(

I get total kernel panic with a complete system lockup.

I'm not sure if I will be able to recover from this or if I will need a
total re-install but so far BSD seems completely hosed on my machine :-(

Regards,

Kaya

On 03/29/2010 07:20 AM, Kaya Saman wrote:
> Thanks for the response Warren!!
>
>
>> Does the card show up in ifconfig?
>
> No.
>
>>
>> If not, do a 'pciconf -lv' to find out which particular hardware you
>> have.
>
> pciconf -lv says
>
> Vendor: Marvell Semiconductor (Was Galileo Technology LTD)
> Class: Network
> Subclass: Ethernet
>
>>
>> -Warren Block * Rapid City, South Dakota USA
>> _______________________________________________
>> freebsd-...@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "freebsd-questi...@freebsd.org"
>
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questi...@freebsd.org"

------------------------------

Message: 23
Date: Mon, 29 Mar 2010 14:27:34 -0400
From: John Baldwin <j...@freebsd.org>
Subject: Re: random FreeBSD panics
To: freebsd...@freebsd.org
Cc: freebsd...@freebsd.org, Masoom Shaikh
<masoom...@gmail.com>, Ivan Voras <ivo...@freebsd.org>, Jeremy
Chadwick <fre...@jdc.parodius.com>, freebsd-...@freebsd.org
Message-ID: <20100329142...@freebsd.org>
Content-Type: Text/Plain; charset="iso-8859-1"

On Monday 29 March 2010 1:30:38 pm Jeremy Chadwick wrote:
> On Mon, Mar 29, 2010 at 05:01:02PM +0000, Masoom Shaikh wrote:
> > On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras <ivo...@freebsd.org> wrote:
> > > On 28 March 2010 16:42, Masoom Shaikh <masoom...@gmail.com> wrote:
> > >
> > >> lets assume if this is h/w problem, then how can other OSes overcome
> > >> this ? is there a way to make FreeBSD ignore this as well, let it
> > >> result in reasonable performance penalty.
> > >
> > > Very probably, if only we could detect where the problem is.
> > > Try adding "options PRINTF_BUFR_SIZE=128" to the kernel
> >
> > this option is already there
>
> The key word in Ivan's phrase is "less mangled". Neither use of or
> increasing PRINTF_BUFR_SIZE solves the problem of interspersed console
> output. I've been ranting/raving about this problem for years now; it
> truly looks like a mutex lock issue (or lack of such lock), but I've
> been told numerous times that isn't the case.
>
> To developers: what incentives would help get this issue well-needed
> attention? This problem makes kernel debugging, panic analysis, and
> other console-oriented viewing basically impossible.

I was recently going to look at it. The somewhat drastic approach I was going
to take was to add a simple serializing lock around trap_fatal() and a few
other places that do similar block prints (e.g. mca_log()). One of the issues
with fixing this in printf itself is that you'd want probably want to
serialize complete lines of text on a per-thread basis. You would want to be
able to accumulate this line of text across multiple calls to printf (think of
it as line-buffering ala stdio). However, some folks may be nervous about
printf not printing things immediately.

The other issue is that lots of code assumes it can call printf from anywhere
and everywhere. Mostly this just means that if you add locking and line-
buffering to printf(9) you have to be very careful to make sure it works in
odd places. Probably a lot of this could be solved by deferring things like
trap_fatal() until panic() has already been called (which is bde's preferred
solution I think).

--
John Baldwin


------------------------------

Message: 24
Date: Mon, 29 Mar 2010 13:05:19 -0600 (MDT)
From: Warren Block <wbl...@wonkity.com>
Subject: Re: Marvell Yukon Driver for Hp notebook??
To: Kaya Saman <Sama...@netscape.net>
Cc: freebsd-...@freebsd.org
Message-ID: <alpine.BSF.2.00.1...@wonkity.com>
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII

On Mon, 29 Mar 2010, Kaya Saman wrote:
> On 03/29/2010 07:20 AM, Kaya Saman wrote:
>> Thanks for the response Warren!!
>>
>>> Does the card show up in ifconfig?
>>
>> No.
>>
>>> If not, do a 'pciconf -lv' to find out which particular hardware you have.
>>
>> pciconf -lv says
>>
>> Vendor: Marvell Semiconductor (Was Galileo Technology LTD)
>> Class: Network
>> Subclass: Ethernet

[please don't top-post, it makes responding more work]

What is needed is the line just before the Vendor, with the card and
chip IDs. Then compare it against the list of cards the FreeBSD msk
driver supports:

http://www.freebsd.org/cgi/man.cgi?query=msk&apropos=0&sektion=0&manpath=FreeBSD+8.0-RELEASE&format=html

> Well.... I managed to go to Marvell and get the FreeBSD 7.0 x64 driver and
> use my USB key to get the driver into the machine:

Wait, the (binary|proprietary?) driver for FreeBSD 7.0 is almost
certainly not going to work on FreeBSD 8.0.

> I then installed it using the instructions provided in the README.txt file
> and now I can't even boot BSD any more :-(
>
> I get total kernel panic with a complete system lockup.
>
> I'm not sure if I will be able to recover from this or if I will need a total
> re-install but so far BSD seems completely hosed on my machine :-(

You may be able to unload that kernel module before booting. If it's a
kernel module; don't know. The one Marvell card I have in a notebook is
supported by the open FreeBSD msk driver thanks to Pyun YongHyeon.

-Warren Block * Rapid City, South Dakota USA


------------------------------

Message: 25
Date: Mon, 29 Mar 2010 12:09:57 -0700
From: Doug Barton <do...@FreeBSD.org>
Subject: Re: [ HEADS UP ] Ports unstable for the next 10 days
To: Aristedes Maniatis <a...@ish.com.au>
Cc: sta...@freebsd.org, ques...@freebsd.org,
freebs...@freebsd.org
Message-ID: <4BB0FB05...@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1

On 03/29/10 02:27, Aristedes Maniatis wrote:
> On 29/03/10 7:04 PM, Doug Barton wrote:
>>>> portmaster -r graphics/png
>> That won't work, the man page clearly says that it has to be a port
>> directory or glob pattern from /var/db/pkg. The "glob pattern" bit of
>> that was (unfortunately) broken up till version 2.20, which I just
>> committed.
>
> I'm confused. The manual actually says:
>
> [-R] -r name/glob of port in /var/db/pkg
>
>
> When I try your suggestion I get this:
>
> # portmaster -r png-
>
> ===>>> No valid installed port, or port directory given
> ===>>> Try portmaster --help

Are you using portmaster version 2.20?

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

------------------------------

Message: 26
Date: Mon, 29 Mar 2010 12:11:58 -0700
From: Doug Barton <do...@FreeBSD.org>
Subject: Re: [ HEADS UP ] Ports unstable for the next 10 days
To: Garrett Cooper <yane...@gmail.com>
Cc: sta...@freebsd.org, ques...@freebsd.org,
freebs...@freebsd.org, Aristedes Maniatis <a...@ish.com.au>
Message-ID: <4BB0FB7E...@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1

On 03/29/10 02:53, Garrett Cooper wrote:
> Besides, when I read `glob' I don't think `regular expression'. A
> glob is a simplified extension of regular expressions,

I wasn't going for a rigorous definition here. :) However, "simplified"
is the correct idea.

> The previous method I described works, and works well:
>
> portmaster -r 'png-*'

Right, that will work, but the * isn't necessary. Portmaster will strip
it internally in any case.

> Not sure why graphics/png doesn't work though; hrrm...

The -r option is only relevant to an installed port.


Doug

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

------------------------------

Message: 27
Date: Mon, 29 Mar 2010 14:14:12 -0500
From: Jay Hall <jh...@socket.net>
Subject: Re: Custom Kernel to Memory Stick
To: Jay Hall <jh...@socket.net>
Cc: freebsd-...@freebsd.org
Message-ID: <595AE04E-B7B3-4F79...@socket.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes


On Mar 29, 2010, at 10:49 AM, Jay Hall wrote:
>
> What would be the best way to get our custom configuration onto the
> memory stick?

Ladies and Gentlemen,

This is what I have done, but now I cannot mount the memory stick.

I create an image of the s1a partition where the kernel I want to copy
resides
dd if=/dev/ad0s1a of=/home/hallja/s1aimage bs=2048k

After preparing the memory stick I use the following command to
transfer the image to the memory stick
dd if=/home/hallja/ s1aimage of=/dev/da0s1a bs=2048k

I am able to mount the memory stick without any problem before I add
the image. After adding the image, I try to mount the memory stick
using

mount /dev/da0s1a /mnt1

And, I receive the following message

mount: /dev/da0s1a : Operation not permitted

Any suggestions would be greatly appreciated.

Thanks,


Jay


------------------------------

Message: 28
Date: Tue, 30 Mar 2010 00:19:06 +0600
From: ??????? ???????? <dbeh...@gmail.com>
Subject: Create GMIRROR only one slice
To: freebsd-...@freebsd.org
Message-ID:
<7aaa60421003291119s53e...@mail.gmail.com>
Content-Type: text/plain; charset=KOI8-R

---------- Пересланное сообщение ----------
От кого: Дмитрий Бехтерев <dbeh...@gmail.com>
Дата: 25 марта 2010 г. 19:03
Тема: Create GMIRROR only one slice
Кому: freebs...@freebsd.org


Hello all!
I have problem with creating GMIRROR on select slice. So, I have two slice:
ls /dev | grep ad4
ad4
ad4s1
ad4s1a
ad4s1b
ad4s1c
ad4s2
ad4s2p1

fdisk /dev/ad4
...
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 29350692 (14331 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 29350755, size 595786590 (290911 Meg), flag 0
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>

On first slice I created ufs slice and on second - ZFS pool (I build it with
glabel):
mount
/dev/ad4s1a on / (ufs, local)
devfs on /dev (devfs, local)
tank on /tank (zfs, local)
tank/usr on /usr (zfs, local)
...
tank/var on /var (zfs, local)

glabel list
Geom name: ad4s2p1
...

I want GMIRROR'ing /dev/ad4s1:
gmirror label -v -b round-robin gm0 /dev/ad4s1
but I get error "Operation not permitted" (although I set sysctl
kern.geom.debugflags=16).
MY OS: FreeBSD 7.3 Stable.
What should I do to do this?
Thanks all.


------------------------------

Message: 29
Date: Mon, 29 Mar 2010 22:42:09 +0300
From: Kaya Saman <Sama...@netscape.net>
Subject: Re: Marvell Yukon Driver for Hp notebook??
To: Warren Block <wbl...@wonkity.com>
Cc: freebsd-...@freebsd.org
Message-ID: <4BB10291...@netscape.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 03/29/2010 10:05 PM, Warren Block wrote:
> On Mon, 29 Mar 2010, Kaya Saman wrote:
>> On 03/29/2010 07:20 AM, Kaya Saman wrote:
>>> Thanks for the response Warren!!
>>>
>>>> Does the card show up in ifconfig?
>>>
>>> No.
>>>
>>>> If not, do a 'pciconf -lv' to find out which particular hardware
>>>> you have.
>>>
>>> pciconf -lv says
>>>
>>> Vendor: Marvell Semiconductor (Was Galileo Technology LTD)
>>> Class: Network
>>> Subclass: Ethernet
>
> [please don't top-post, it makes responding more work]

Sorry!

When you mean 'top post' do you mean writing something after replying or
posting at the 'top' of the original information??? Apologies am
unfamiliar with the term!

>
> What is needed is the line just before the Vendor, with the card and
> chip IDs. Then compare it against the list of cards the FreeBSD msk
> driver supports:
>
> http://www.freebsd.org/cgi/man.cgi?query=msk&apropos=0&sektion=0&manpath=FreeBSD+8.0-RELEASE&format=html
>

I will try to obtain this tomorrow as I left the CD at work :-(

>
>> Well.... I managed to go to Marvell and get the FreeBSD 7.0 x64
>> driver and use my USB key to get the driver into the machine:
>
> Wait, the (binary|proprietary?) driver for FreeBSD 7.0 is almost
> certainly not going to work on FreeBSD 8.0.

Yeah I messed the system up completely now and attempted to recover it
with FreeSBIE based on BSD 6.0 which doesn't even start for some strange
reason. Can't mount the CD it says?? Any other system I've tried manages.

>
>> I then installed it using the instructions provided in the README.txt
>> file and now I can't even boot BSD any more :-(
>>
>> I get total kernel panic with a complete system lockup.
>>
>> I'm not sure if I will be able to recover from this or if I will need
>> a total re-install but so far BSD seems completely hosed on my
>> machine :-(
>
> You may be able to unload that kernel module before booting. If it's
> a kernel module; don't know. The one Marvell card I have in a
> notebook is supported by the open FreeBSD msk driver thanks to Pyun
> YongHyeon.
>
> -Warren Block * Rapid City, South Dakota USA

If I could just mount the hard drive I could remove the statement in
/boot/modules.conf

Unfortunately all I have available to me is Linux and Windows 7 which I
don't think will be much use!

Kaya


------------------------------

Message: 30
Date: Mon, 29 Mar 2010 13:21:42 -0600
From: Adam Vande More <amvan...@gmail.com>
Subject: Re: [ HEADS UP ] Ports unstable for the next 10 days
To: Doug Barton <do...@freebsd.org>
Cc: Garrett Cooper <yane...@gmail.com>, sta...@freebsd.org,
ques...@freebsd.org, freebs...@freebsd.org, Aristedes Maniatis
<a...@ish.com.au>
Message-ID:
<6201873e1003291221t143...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Mar 29, 2010 at 1:11 PM, Doug Barton <do...@freebsd.org> wrote:

> Right, that will work, but the * isn't necessary. Portmaster will strip
> it internally in any case.
>

Those type of examples in the man pages and UPDATING have never worked for
me in tcsh, I've always had to glob it like Garret stated.


> pkg_info |grep png
linux-f10-png-1.2.37 RPM of the PNG lib (Linux Fedora 10)
png-1.2.42 Library for manipulating PNG images
scr2png-1.2_3 Converts the output of "vidcontrol -p" to PNG
> portmaster -r png-
===>>> No valid installed port, or port directory given
===>>> Try portmaster --help
> portmaster -r 'png-*'
===>>> Currently installed version: png-1.2.42
===>>> Port directory: /usr/ports/graphics/png
===>>> Gathering distinfo list for installed ports
===>>> Launching 'make checksum' for graphics/png in background
===>>> Gathering dependency list for graphics/png from ports
===>>> No dependencies for graphics/png
===>>> Checking ports that depend on png-1.2.42
===>>> Launching child to update akonadi-1.2.1_1
^C
===>>> Build/Install for graphics/png exiting due to signal


--
Adam Vande More


------------------------------

Message: 31
Date: Mon, 29 Mar 2010 21:03:09 +0100
From: krad <kra...@googlemail.com>
Subject: Re: Routers, switches, and networking hardware
To: Lee Shackelford <lee_sha...@dot.ca.gov>
Cc: Kurt Buff <kurt...@gmail.com>, ques...@freebsd.org
Message-ID:
<d36406631003291303k43f...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On 29 March 2010 16:41, Lee Shackelford <lee_sha...@dot.ca.gov> wrote:

> Dear Mr. Buff, Thank you for responding to my inquiry. Yours truly, Lee
> Shackelford
>
>
>
> Kurt Buff
> <kurt.buff@gmail.
> com> To
> Lee Shackelford
> 03/26/2010 03:05 <lee_sha...@dot.ca.gov>
> PM cc
> ques...@freebsd.org
> Subject
> Re: Routers, switches, and
> networking hardware
>
>
>
>
>
>
>
>
>
>
> On Fri, Mar 26, 2010 at 14:46, Lee Shackelford
> <lee_sha...@dot.ca.gov> wrote:
> >
> > Good afternoon, dear FreeBSD enthusiast. Is anyone aware of any brand
> name
> > of router, switch, or other similar networking hardware that is based on
> > any variant of the BSD operating system? Any comments are appreciated.
> > Yours truly, L e e _ S h a c k e l f o r d AT d o t dot c a
> dot
> > g o v
>
> Unless memory fails me, F5, Juniper, and for sure Sidewinder (now
> McAfee) firewalls, among others.
>
> Kurt
>
>
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questi...@freebsd.org"
>

and its all down to licensing


------------------------------

Message: 32
Date: Mon, 29 Mar 2010 21:10:42 +0100
From: krad <kra...@googlemail.com>
Subject: Re: Create GMIRROR only one slice
To: ??????? ???????? <dbeh...@gmail.com>
Cc: freebsd-...@freebsd.org
Message-ID:
<d36406631003291310x150...@mail.gmail.com>
Content-Type: text/plain; charset=KOI8-R

2010/3/29 Дмитрий Бехтерев <dbeh...@gmail.com>

> ---------- Пересланное сообщение ----------
> От кого: Дмитрий Бехтерев <dbeh...@gmail.com>
> Дата: 25 марта 2010 г. 19:03
> Тема: Create GMIRROR only one slice
> Кому: freebs...@freebsd.org
>
>
> Hello all!
> I have problem with creating GMIRROR on select slice. So, I have two slice:
> ls /dev | grep ad4
> ad4
> ad4s1
> ad4s1a
> ad4s1b
> ad4s1c
> ad4s2
> ad4s2p1
>
> fdisk /dev/ad4
> ...
> The data for partition 1 is:
> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
> start 63, size 29350692 (14331 Meg), flag 80 (active)
> beg: cyl 0/ head 1/ sector 1;
> end: cyl 1023/ head 254/ sector 63
> The data for partition 2 is:
> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
> start 29350755, size 595786590 (290911 Meg), flag 0
> beg: cyl 1023/ head 255/ sector 63;
> end: cyl 1023/ head 254/ sector 63
> The data for partition 3 is:
> <UNUSED>
> The data for partition 4 is:
> <UNUSED>
>
> On first slice I created ufs slice and on second - ZFS pool (I build it
> with
> glabel):
> mount
> /dev/ad4s1a on / (ufs, local)
> devfs on /dev (devfs, local)
> tank on /tank (zfs, local)
> tank/usr on /usr (zfs, local)
> ...
> tank/var on /var (zfs, local)
>
> glabel list
> Geom name: ad4s2p1
> ...
>
> I want GMIRROR'ing /dev/ad4s1:
> gmirror label -v -b round-robin gm0 /dev/ad4s1
> but I get error "Operation not permitted" (although I set sysctl
> kern.geom.debugflags=16).
> MY OS: FreeBSD 7.3 Stable.
> What should I do to do this?
> Thanks all.
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questi...@freebsd.org"
>

Dont boot into the os, create the gmirror from the fixit mode of a cd, or
build a usb stick with freebsd on. You will need to newfs the gmirror device
after that so backup the data currently on /, then copy it back afterwards.

I have to ask, as you are using zfs why not just do a zfs root? If you do
decide to go for this option, use gpart to create gpt layouts, as you wont
run into partition size limitations if you upgrade the drives to big ones in
the future


------------------------------


End of freebsd-questions Digest, Vol 304, Issue 3
*************************************************

0 new messages