freebsd-questions Digest, Vol 304, Issue 4
freebsd-ques...@freebsd.org
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: [ HEADS UP ] Ports unstable for the next 10 days (Doug Barton)
2. Re: random FreeBSD panics (Jeremy Chadwick)
3. Cannot load library
/usr/local/kde4/lib/kde4/konq_aboutpage.so: (Antonio Olivares)
4. Re: Custom Kernel to Memory Stick (Jay Hall)
5. Re: Custom Kernel to Memory Stick (Aiza)
6. Problem with shmget? (herbey zepeda)
7. Format error in /usr/ports/MOVED (Wil Hatfield)
8. Re: Enough Is Enough (Programmer In Training)
9. Re: Freebsd, postfix and push email (Tim Judd)
10. Re: Freebsd, postfix and push email (Adam Vande More)
11. Re: random FreeBSD panics (Anoop Kumar Narayanan)
12. /boot.config (Fbsd1)
13. Re: Marvell Yukon Driver for Hp notebook?? (Kaya Saman)
14. Re: Create GMIRROR only one slice (Matthew Seaman)
15. Re: Enough Is Enough (Matthew Seaman)
16. Re: Freebsd, postfix and push email (Matthew Seaman)
17. Re: Freebsd, postfix and push email (Jonathan McKeown)
18. Re: Create GMIRROR only one slice (krad)
----------------------------------------------------------------------
Message: 1
Date: Mon, 29 Mar 2010 12:32:36 -0700
From: Doug Barton <do...@FreeBSD.org>
Subject: Re: [ HEADS UP ] Ports unstable for the next 10 days
To: Adam Vande More <amvan...@gmail.com>
Cc: Garrett Cooper <yane...@gmail.com>, sta...@freebsd.org,
ques...@freebsd.org, freebs...@freebsd.org, Aristedes Maniatis
<a...@ish.com.au>
Message-ID: <4BB10054...@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1
On 03/29/10 12:21, Adam Vande More wrote:
> On Mon, Mar 29, 2010 at 1:11 PM, Doug Barton <do...@freebsd.org
> <mailto: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.
I'm sorry to repeat myself, but what you're describing is a result of
the fact that in the past the glob code for the -r option was broken. As
of version 2.20 it is no longer broken, and the * is not necessary
(although it won't hurt anything).
hope this helps,
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: 2
Date: Mon, 29 Mar 2010 13:30:48 -0700
From: Jeremy Chadwick <fre...@jdc.parodius.com>
Subject: Re: random FreeBSD panics
To: John Baldwin <j...@freebsd.org>
Cc: freebsd-...@freebsd.org, Masoom Shaikh
<masoom...@gmail.com>, freebsd...@freebsd.org, Ivan Voras
<ivo...@freebsd.org>, freebsd...@freebsd.org
Message-ID: <2010032920...@icarus.home.lan>
Content-Type: text/plain; charset=us-ascii
On Mon, Mar 29, 2010 at 02:27:34PM -0400, John Baldwin wrote:
> 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,
Thanks for the insights, they're greatly appreciated.
I went looking this morning to see how Linux addressed this issue (if at
all), and it's been discussed a few times in the past. The longest lkml
thread I could find that mentioned the problem was circa 2002. Probably
not worth reading as there was work done in 2009 to solve the issue.
http://lkml.indiana.edu/hypermail/linux/kernel/0204.1/index.html#161
Work done by RedHat in 2009 details how they implemented a lockless
version of their kernel ring buffer (similar to our system message
buffer, but probably a lot more complex):
http://lwn.net/Articles/340400/
http://lwn.net/Articles/340443/
Supposedly having multiple writers to the ring is 100% safe; no
interspersed output. Same goes for interrupt-generated stuff. There's
some comments in the technical document (2nd link) that imply there's an
individual ring buffer for each CPU; possibly per-CPU kernel message
buffers would solve our issue?
--
| 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: 3
Date: Mon, 29 Mar 2010 16:52:52 -0500
From: Antonio Olivares <olivar...@gmail.com>
Subject: Cannot load library
/usr/local/kde4/lib/kde4/konq_aboutpage.so:
To: freebsd-...@freebsd.org
Message-ID:
<75107331003291452i751...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Dear fellow FreeBSD users,
I have installed FreeBSD 8.0 and updated it to current p2
I try to use konqueror and I get
There was an error loading the module About-Page for Konqueror.
The diagnostics is:
Cannot load library /usr/local/kde4/lib/kde4/konq_aboutpage.so:
(Shared object "libjpeg.so.10" not found, required by "libkhtml.so.7")
I tried to install some ports and TeXLive from GoogleGroups page by
Romain, but apparently was unsuccessful.
I tried to install kile, and k3b and both not work because of error4
similar to the one konqueror gives. As regular user I cannot launch
terminal, I have to run as root in the meantime, is there any way to
fix this?
I have run FreeBSD before, with the release prior to jumping on KDE
4.X bandwagon, but my hardrive went down and stopped using it.
Thanks for any advice given to fix these issues.
Regards,
Antonio
------------------------------
Message: 4
Date: Mon, 29 Mar 2010 17:56:56 -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: <E02F9B77-613E-43AE...@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?
>
OK, I managed t get our custom configuration on to the memory stick
using dump. After getting everything configured, what I thought was
correctly, I am able to boot from the memory stick until it is time to
mount the root partition.
When mounting the root partition from /dev/da0s1a, I receive the
following message:
Trying to mount root from ufs:/dev/da0s1a
ROOT MOUNT ERROR:
If you have invalid mount options, reboot and first try the following
from the loader prompt:
I have tried the suggested courses of action without any success.
If I type ufs:/dev/da0s1a I receive the ROOT MOUNT ERROR again.
Following is what I have done to create the bootable memory stick.
Created two partitions on the memory stick each about 2 GB.
sysinstall was used for this.
Used bsdlabel to create the necessary labels on the memory stick.
sysinstall was used for this.
Ran newfs as on all of the labels. This was done from the command
prompt.
Once everything was created, I mounted the memory stick and created an
image of my working installation using dump.
boot0cfg was run on the memory stick. boot0cfg -v -B -o noupdate da0
Modified the fstab on the memory stick as follows
/dev/da0s1a / rw,noatime 0 0
Everything other than the operating system was left on the hard drive.
If anyone has any suggestions how to fix this, please let me know. I
am out of ideas. Or, if you can direct me to a howto, that would be
fine also.
Thanks for all your help and patience.
Jay
------------------------------
Message: 5
Date: Tue, 30 Mar 2010 07:30:47 +0800
From: Aiza <aiz...@comclark.com>
Subject: Re: Custom Kernel to Memory Stick
To: Jay Hall <jh...@socket.net>
Cc: freebsd-...@freebsd.org
Message-ID: <4BB13827...@comclark.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Jay Hall wrote:
> 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?
>
This is the procedure you want to follow.
http://forums.freebsd.org/showthread.php?t=11680
And for greater detail
http://forums.freebsd.org/showthread.php?t=11715
------------------------------
Message: 6
Date: Mon, 29 Mar 2010 20:26:34 -0400
From: herbey zepeda <zepeda...@gmail.com>
Subject: Problem with shmget?
To: freebsd-...@freebsd.org
Message-ID:
<49856ef1003291726x7ac...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
I'm trying to set up shared memory using a structure. Everything seems to
work fine when the memory creator creates it and the writer attaches to the
created memory segment. The problem is that when the data writer tries to
write or read in the shared memory segment, there is a segmentation fault
(core dumped) message and data is not read or written.
Following are the 3 files I'm using, the section that fails is
indicated almost at the end of the code.
any ideas?
thanks you
-------------------------
hzSharedMemoryMessageUnit.h
---------------------------
#include<string>
#define HZ_SHMEMFORDATAGRABBER 159 //start memory segments at 101
#define TEXT_SZ 256
struct shared_use_st
{
int memWrittenAndReadyToBeRead;
char some_text[TEXT_SZ];
};//hzSt;
-----------------
hzSharedMemorySetter.cpp
------------------------
#include <iostream>
#include <string>
#include <unistd.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
#include <errno.h>
#include "hzSharedMemoryMessageUnit.h"
using namespace std;
class hzNotifications
{
public:
void hzNotifyWhenError(const char* errorMsg,int exitCodeStrg);
};
void hzNotifications::hzNotifyWhenError(const char* errorMsg,int
exitCodeStrg)
{
cerr << errorMsg << endl;
exit(exitCodeStrg);
}
int main()
{
void *shared_memory=(void *)0;
struct shared_use_st *shared_stuff;
int shmid;
hzNotifications hzNotif;
shmid=shmget((key_t)HZ_SHMEMFORDATAGRABBER,sizeof(struct shared_use_st),
0666 | IPC_CREAT );
if(shmid==-1)
{
cerr <<"hz the error of shmget is: " << errno <<endl;
hzNotif.hzNotifyWhenError("hz shmget failed",EXIT_FAILURE);
}
cout <<"hz the size off sizeof(struct shared_use_st) is : " <<
sizeof(struct shared_use_st)<<endl;
shared_memory=shmat(shmid, (void *)0, 0);
if(shared_memory== (void *)-1)
{hzNotif.hzNotifyWhenError("hz shmat failed",EXIT_FAILURE);}
cout << "memory attached at " << (int)shared_memory << " with shmid= "<<
shmid << " and the common id is: " << HZ_SHMEMFORDATAGRABBER <<endl;
shared_stuff=(struct shared_use_st *)shared_memory;
shared_stuff->memWrittenAndReadyToBeRead=2;
sleep(20);
cout << "hz you wrote " << shared_stuff->memWrittenAndReadyToBeRead << "
from another process " << endl;
if(shmdt(shared_memory)==-1)
{hzNotif.hzNotifyWhenError("hz shmdt failed",EXIT_FAILURE);}
if(shmctl(shmid,IPC_RMID,0)==-1)
{hzNotif.hzNotifyWhenError("hz shmctl(IPC_RMID)
failed",EXIT_FAILURE);}
return 0;
}
----------------------------
hzSharedMemoryGetter.cpp
------------------------------
#include <iostream>
#include <string>
#include<string.h>
#include <unistd.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
#include <errno.h>
#include "hzSharedMemoryMessageUnit.h"
using namespace std;
class hzNotifications
{
public:
void hzNotifyWhenError(const char* errorMsg,int exitCodeStrg);
};
void hzNotifications::hzNotifyWhenError(const char* errorMsg,int
exitCodeStrg)
{
cerr << errorMsg << endl;
exit(exitCodeStrg);
}
int main()
{
/*
hzSetSharedMemory hzSm;
struct shared_use_st *shared_stuff;
shared_stuff=(struct shared_use_st
*)hzSm.hzAttachToExistingSharedMemoryChunk(HZ_SHMEMFORDATAGRABBER);
*/
//int running=1;
void *shared_memory=(void *)0;
struct shared_use_st *shared_stuff;
int shmid;
hzNotifications hzNotif;
shmid=shmget((key_t)HZ_SHMEMFORDATAGRABBER,sizeof(struct shared_use_st),
0666 | IPC_CREAT );
//shmid=shmget((key_t)HZ_SHMEMFORDATAGRABBER,0,0666 );
if(shmid==-1)
{
cerr <<"hz the error of shmget is: " << errno <<endl;
hzNotif.hzNotifyWhenError("hz shmget failed",EXIT_FAILURE);
}
cout <<"hz the size off sizeof(struct shared_use_st) is : " <<
sizeof(struct shared_use_st)<<endl;
shared_memory=shmat(shmid, (void *)0, 0);
if(shared_memory== (void *)-1)
{hzNotif.hzNotifyWhenError("hz shmat failed",EXIT_FAILURE);}
cout << "memory attached at " << (int)shared_memory << " with shmid= "<<
shmid << " and the common id is: " << HZ_SHMEMFORDATAGRABBER <<endl;
//printf ("hz the address of shared mem is : %d \n
",(int)shared_memory);
if(shmdt(shared_memory)==-1)
{hzNotif.hzNotifyWhenError("hz shmdt failed",EXIT_FAILURE);}
shared_stuff=(struct shared_use_st *)shared_memory;
printf("hz value in struct is: %d
\n",shared_stuff->memWrittenAndReadyToBeRead);
-------IT FAILS HERE
shared_stuff->memWrittenAndReadyToBeRead=10; //------------ IT FAILS
HERE!!!!!!!!
-------IT FAILS HERE
cout << "program completed" <<endl;
return 0;
}
------------------------------
Message: 7
Date: Mon, 29 Mar 2010 16:57:51 -0700
From: "Wil Hatfield" <fre...@hyperconx.com>
Subject: Format error in /usr/ports/MOVED
To: <freebsd-...@freebsd.org>
Message-ID: <026b01cacf9b$a4438790$ecca96b0$@com>
Content-Type: text/plain; charset="US-ASCII"
#pkgdb -F
Errors with: 'portsdb: MOVED file format error'
Find in /usr/ports/MOVED at very bottom
www/trac-webadmin|2010-03-30|Incorporated to www/trac
change to:
www/trac-webadmin||2010-03-30|Incorporated to www/trac
--
Wil Hatfield
HyperConX Customer Care
HyperConX International - http://www.hyperconx.com
1.877.290.2446 - Toll Free in the US and Canada
1.209.751.4706 - International direct
Premium e-commerce hosting, fully PCI Compliant, 24/7
technical support, 99.9% uptime and 30 day money back
guarantees, toll free support lines for your convenience,
great low cost packages to choose from. Everything your
business needs to succeed.
Host with the Pros so you can sell like one!
------------------------------
Message: 8
Date: Mon, 29 Mar 2010 20:58:13 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: Enough Is Enough
To: freebsd-...@freebsd.org
Message-ID: <4BB15AB5...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="utf-8"
On 03/28/10 09:46, Sergio de Almeida Lenzi wrote:
<snip>
> this scripts outputs the commands needed to fix the system
I'm having some problems with the script.
> watch out
> ==================================
> #!/bin/sh
>
> endp() {
> rm -f $t
> exit $1
> }
>
> t=/tmp/$$
>
> if [ $# -ne 1 ]
> then
> echo use $0 library
> endp 1
> fi
>
> lib=$1
>
> find /usr/local/bin /usr/local/lib -name -type f | \
Is the 'f' a typo? I had to remove it because find kept on erroring on it.
> while read x
> do
> grep $lib $x | \
> awk '{print $3}' | \
> while read y
> do
> pkg_info -W $y >> $t
> done
> done
> awk '{print $NF}' $t | sort -u > /tmp/buildpkglist
> echo nice portmaster -Bdg `cat /tmp/buildpkglist`
> endp 0
The final output (after removing the stray 'f'):
./portmaster-script jpeg
awk: can't open file /tmp/42352
source line number 1
nice portmaster -Bdg
ran as regular user and root to no different affect.
I switched out all instances of awk for grep with the following result:
./portmaster-script jpeg
grep: /tmp/42436: No such file or directory
nice portmaster -Bdg
Thanks for the suggestion, but this script doesn't seem to work on my
system and I can't seem to figure out what exactly is causing it to fail.
--
Yours In Christ,
PIT
Emails are not formal business letters, whatever businesses may want.
Original content copyright under the OWL http://owl.apotheon.org
Please do not CC me. If I'm posting to a list it is because I am subscribed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20100330/06f121d2/signature-0001.pgp
------------------------------
Message: 9
Date: Mon, 29 Mar 2010 19:01:27 -0700
From: Tim Judd <taj...@gmail.com>
Subject: Re: Freebsd, postfix and push email
To: per...@pluto.rain.com
Cc: freebsd-...@freebsd.org, rg.l...@rzweb.com
Message-ID:
<ade45ae91003291901w7e2...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 3/27/10, per...@pluto.rain.com <per...@pluto.rain.com> wrote:
> Tim Judd <taj...@gmail.com> wrote:
>> On 3/27/10, Ron (Lists) <rg.l...@rzweb.com> wrote:
>> > Is there a way to get my freebsd/postfix setup to send push
>> > notifications to an iPhone ... I know it can be done with
>> > Exchange and ActiveSync, but I don't want to run any kind of
>> > exchange server.
>>
>> Wouldn't push email be a function of your POP3 or IMAP server?
>> FreeBSD and Postfix are neither of those.
>
> Er, no. POP3 and IMAP are "pull" services, wherein the client
> polls the server periodically for any newly-arrived messages.
> A client-level "push" service would need to operate similarly
> to biff(1)/comsat(8).
>
I've never heard of either, but when I configure my IMAP server and
put any mail client to it, as soon as a mail is delivered, the mail
client is notified.
I don't use biff or comsat or anything similar. mine is a simple IMAP
server pushing it.
I'm anxious to really hear what this is... I don't have any POP3/IMAP
enabled smartphones to test with.
--Tim
------------------------------
Message: 10
Date: Mon, 29 Mar 2010 20:36:42 -0600
From: Adam Vande More <amvan...@gmail.com>
Subject: Re: Freebsd, postfix and push email
To: Tim Judd <taj...@gmail.com>
Cc: per...@pluto.rain.com, freebsd-...@freebsd.org,
rg.l...@rzweb.com
Message-ID:
<6201873e1003291936h34b...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Mar 29, 2010 at 8:01 PM, Tim Judd <taj...@gmail.com> wrote:
> I've never heard of either, but when I configure my IMAP server and
> put any mail client to it, as soon as a mail is delivered, the mail
> client is notified.
>
> I don't use biff or comsat or anything similar. mine is a simple IMAP
> server pushing it.
>
>
>
> I'm anxious to really hear what this is... I don't have any POP3/IMAP
> enabled smartphones to test with.
>
Most pop3/imap clients have check for new mail option, eg the gmail app for
the blackberry and every gui client I can think of.
--
Adam Vande More
------------------------------
Message: 11
Date: Tue, 30 Mar 2010 08:47:17 +0530
From: Anoop Kumar Narayanan <anoo...@gmail.com>
Subject: Re: random FreeBSD panics
To: freebsd-...@freebsd.org
Message-ID:
<7ff5545f1003292017k76...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Sun, Mar 28, 2010 at 5:33 PM, Gary Jennejohn
<gary.je...@freenet.de> wrote:
> On Sun, 28 Mar 2010 11:18:59 +0000
> Masoom Shaikh <masoom...@gmail.com> wrote:
>
>> On Sun, Mar 28, 2010 at 10:32 AM, Ivan Voras <ivo...@freebsd.org> wrote:
>> > 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 :(
>> >
>> > I wild shot - did you try disabling superpages?
>> >
>> > _______________________________________________
>> > freebsd-...@freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> > To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
>> >
>>
>> umm, how do I do that ?
>>
>
> Add this to /boot/loader.conf
> vm.pmap.pg_ps_enabled="0"
I keep getting RW errors while writing into an USB drive, wondering if
its the same problem is related to your reply ?
USB mass storage driver seems to be broken.
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Kingston DataTraveler 2.0 1.00> Removable Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: 1940MB (3973120 512 byte sectors: 255H 63S/T 247C)
info: [drm] Num pipes: 2
info: [drm] Loading R300 Microcode
info: [drm] Num pipes: 2
g_vfs_done():da0s1[WRITE(offset=648923648, length=32768)]error = 5
g_vfs_done():da0s1[WRITE(offset=648956416, length=32768)]error = 5
g_vfs_done():da0s1[WRITE(offset=648989184, length=32768)]error = 5
g_vfs_done():da0s1[WRITE(offset=649021952, length=65536)]error = 5
g_vfs_done():da0s1[WRITE(offset=649087488, length=32768)]error = 5
bye,
-Anoop
>
> --
> Gary Jennejohn
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
>
------------------------------
Message: 12
Date: Tue, 30 Mar 2010 13:55:35 +0800
From: Fbsd1 <fb...@a1poweruser.com>
Subject: /boot.config
To: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <4BB19257...@a1poweruser.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
During the boot process I want to change the device used to boot from.
From the default 0:ad(0,a)/boot/loader
to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick.
Here is the problem, the bios have no option to boot from USB device.
So thinking let the bios point to first drive to start the boot process
and have a /boot.config file to redirect to booting from the USB stick.
I am assuming the '0' zero will mean the first USB device.
Is there any command i can use to verify the single USB stick is the 0
device?
Is this concept valid?
------------------------------
Message: 13
Date: Tue, 30 Mar 2010 09:39:45 +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: <4BB19CB1...@netscape.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>>
>> 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
>>
Line goes as follows:
none2:pci0:133:0:0:
class=0x020000 card=0x30e8103c chip=0x45711ab rev=0x00 hdr=0x00
>
>> 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 just performed a re-install...... nothing lost so is ok.
>
Kaya
------------------------------
Message: 14
Date: Tue, 30 Mar 2010 08:04:48 +0100
From: Matthew Seaman <m.se...@infracaninophile.co.uk>
Subject: Re: Create GMIRROR only one slice
To: krad <kra...@googlemail.com>
Cc: freebsd-...@freebsd.org, ??????? ????????
<dbeh...@gmail.com>
Message-ID: <4BB1A290...@infracaninophile.co.uk>
Content-Type: text/plain; charset=UTF-8
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29/03/2010 21:10:42, krad wrote:
> You will need to newfs the gmirror device
> after that so backup the data currently on /, then copy it back afterwards.
This is counter to all my experience of dealing with gmirror -- it's
carefully designed so that the metadata it writes to the drive
*doesn't* interfere with the filesystem. While it is always a good
idea to have backups, I do not believe that destroying and recreating
the filesystem should be necessary.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuxopAACgkQ8Mjk52CukIxvZwCaAgTijPzbHoL5whM6F3GQax2N
eN4An3/HZSRgUml7jy+IpYRyK0rEfGRr
=e+4T
-----END PGP SIGNATURE-----
------------------------------
Message: 15
Date: Tue, 30 Mar 2010 08:27:21 +0100
From: Matthew Seaman <m.se...@infracaninophile.co.uk>
Subject: Re: Enough Is Enough
To: Programmer In Training <p...@joseph-a-nagy-jr.us>
Cc: freebsd-...@freebsd.org
Message-ID: <4BB1A7D9...@infracaninophile.co.uk>
Content-Type: text/plain; charset=UTF-8
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30/03/2010 02:58:13, Programmer In Training wrote:
>> find /usr/local/bin /usr/local/lib -name -type f | \
> Is the 'f' a typo? I had to remove it because find kept on erroring on it.
There is a typo, but it's to do with the -name predicate. -name needs
an argument -- but as the quoted script seems to be trying to scan for
the libraries linked to be everything in ${PREFIX}/bin and
${PREFIX}/lib you don't need to filter by name at all. Just use:
find /usr/local/bin /usr/local/lib -type f | \
'-type f' says 'only regular files, not directories or sym-links'
Note that using grep(1) to work out what a binary links to is
exceedingly bizarre. ldd(1) is the correct tool for that job.
In any case, there are better solutions to this problem: try using the
sysutils/libchk port.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuxp9kACgkQ8Mjk52CukIzmqgCfVX1vLd0TW/AZ01SLEVtKUvPP
nEwAnjFHrOj+CdtF09CqC6/VAaoP2ERP
=Tlgk
-----END PGP SIGNATURE-----
------------------------------
Message: 16
Date: Tue, 30 Mar 2010 08:31:00 +0100
From: Matthew Seaman <m.se...@infracaninophile.co.uk>
Subject: Re: Freebsd, postfix and push email
To: Tim Judd <taj...@gmail.com>
Cc: per...@pluto.rain.com, freebsd-...@freebsd.org,
rg.l...@rzweb.com
Message-ID: <4BB1A8B4...@infracaninophile.co.uk>
Content-Type: text/plain; charset=UTF-8
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30/03/2010 03:01:27, Tim Judd wrote:
> I've never heard of either, but when I configure my IMAP server and
> put any mail client to it, as soon as a mail is delivered, the mail
> client is notified.
That's the IDLE extension to IMAPv4 -- it's not a push protocol as
such: the client still has to log into the server rather than vice
versa, but once the client has read all the available e-mail, it can
put itself into an idle state, and the server will wake it up as soon
as any new e-mail comes in.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuxqLQACgkQ8Mjk52CukIx6IgCfSDPdb2LrxBDJZ+csTQfn73lB
+mMAniO4pq4K9gFEZ1SU53OrJOie9kaQ
=oVgM
-----END PGP SIGNATURE-----
------------------------------
Message: 17
Date: Tue, 30 Mar 2010 11:14:05 +0200
From: Jonathan McKeown <j.mc...@ru.ac.za>
Subject: Re: Freebsd, postfix and push email
To: freebsd-...@freebsd.org
Message-ID: <201003301114.0...@ru.ac.za>
Content-Type: text/plain; charset="utf-8"
On Tuesday 30 March 2010 09:31:00 Matthew Seaman wrote:
> On 30/03/2010 03:01:27, Tim Judd wrote:
> > I've never heard of either, but when I configure my IMAP server and
> > put any mail client to it, as soon as a mail is delivered, the mail
> > client is notified.
>
> That's the IDLE extension to IMAPv4 -- it's not a push protocol as
> such: the client still has to log into the server rather than vice
> versa, but once the client has read all the available e-mail, it can
> put itself into an idle state, and the server will wake it up as soon
> as any new e-mail comes in.
Yes. In fact, one of the nice things about IMAPrev4 as a protocol is that the
server is allowed (in fact, required by rfc3501) to notify the client if the
mailbox size increases while executing any command, by sending an EXISTS
response which the client is required to handle. IDLE is just a command that
takes a long time to execute (specifically, until the client ends it or the
server's time limit is reached) so that the server has to send EXISTS
responses whenever mail comes in.
Jonathan
------------------------------
Message: 18
Date: Tue, 30 Mar 2010 12:26:00 +0100
From: krad <kra...@googlemail.com>
Subject: Re: Create GMIRROR only one slice
To: Matthew Seaman <m.se...@infracaninophile.co.uk>
Cc: freebsd-...@freebsd.org, ??????? ????????
<dbeh...@gmail.com>
Message-ID:
<d36406631003300426q1d8...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
2010/3/30 Matthew Seaman <m.se...@infracaninophile.co.uk>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 29/03/2010 21:10:42, krad wrote:
> > You will need to newfs the gmirror device
> > after that so backup the data currently on /, then copy it back
> afterwards.
>
> This is counter to all my experience of dealing with gmirror -- it's
> carefully designed so that the metadata it writes to the drive
> *doesn't* interfere with the filesystem. While it is always a good
> idea to have backups, I do not believe that destroying and recreating
> the filesystem should be necessary.
>
> Cheers,
>
> Matthew
>
> - --
> Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
> Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
> Kent, CT11 9PW
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkuxopAACgkQ8Mjk52CukIxvZwCaAgTijPzbHoL5whM6F3GQax2N
> eN4An3/HZSRgUml7jy+IpYRyK0rEfGRr
> =e+4T
> -----END PGP SIGNATURE-----
>
Im pretty sure that it will nick the last sector from the slice, so you will
at least need to fsck it. If its a production system i would always go for
the cleaner approach as well and newfs is about as clean as it gets.
------------------------------
End of freebsd-questions Digest, Vol 304, Issue 4
*************************************************