Date: Wed, 21 Jan 2009 02:54:10 -0800 From: "I Hate SPAM via RT" <support@aebc.com> To: freebsd-questions@freebsd.org Subject: [SpamCop (66.51.128.45) id:3804161220][Trouble Ticket #190335] AutoReply: freebsd-questi.. Message-ID: <rt-3.8.2-24798-1232535250-230.190335-6-0@tracker2.aebc.com> In-Reply-To: <rid_3804161220@msgid.spamcop.net> References: <RT-Ticket-190335@tracker2.aebc.com> <rid_3804161220@msgid.spamcop.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[ SpamCop V2 ] This message is brief for your comfort. Please use links below for details. Unsolicited bounce from: 66.51.128.45 http://www.spamcop.net/w3m?i=z3804161220z6e70bfcff2bd738f22bff703440b764fz 66.51.128.45 appears to be sending unsolicited bounces, please see: http://www.spamcop.net/fom-serve/cache/329.html [ Offending message ] X-Claws-Bogosity: Ham, spamicity=0 [whitelisted] X-Apparently-To: gesbbb@yahoo.com via 68.142.207.115; Tue, 20 Jan 2009 22:41:07 -0800 X-YMailISG: .Dv8j18WLDtuJNxtWLhDpf5mpeWFUghNdv_egb_0fiZXg1RCIX735NHbTO4clF89wN6gneANUXqOut8aaecrNre7XPBoTfchA4NFlU0TRJqOCLU_mg0l5Z0_qbqu8xMJfpRn3An.qvcED777FwkCZQVEXN5Qa0vSW3Nm5cqisI_itxdD2dWcDmVt0oPwAE87AbDClIGtYWvkHHwS2kDGt_cGFpaZnbBIkxYHVXnWFcg8F8XH6v3K1DET2NtH5Am8wwm9un5sIVnxKYalYMlU7HHXa1itu7PXH7LbJRG3by.ydjpQN7TXysv8lExiTgdk4Kczs69igNPnXubTNINHACSpnufW_Sw- X-Originating-IP: [69.147.83.53] Authentication-Results: mta324.mail.re4.yahoo.com from=freebsd.org; domainkeys=neutral (no sig) Received: from 69.147.83.53 (EHLO mx2.freebsd.org) (69.147.83.53) by mta324.mail.re4.yahoo.com with SMTP; Tue, 20 Jan 2009 22:41:06 -0800 Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 8968B15F523; Wed, 21 Jan 2009 06:40:24 +0000 (UTC) (envelope-from owner-freebsd-questions@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 755D71065694; Wed, 21 Jan 2009 06:40:24 +0000 (UTC) (envelope-from owner-freebsd-questions@freebsd.org) Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B8901065676 for <freebsd-questions@freebsd.org>; Wed, 21 Jan 2009 06:40:06 +0000 (UTC) (envelope-from apache@tracker2.aebc.com) Received: from tracker2.aebc.com (xx6651128045.cipherkey.com [66.51.128.45]) by mx1.freebsd.org (Postfix) with ESMTP id 088C88FC34 for <freebsd-questions@freebsd.org>; Wed, 21 Jan 2009 06:40:05 +0000 (UTC) (envelope-from apache@tracker2.aebc.com) Received: from tracker2.aebc.com (localhost.localdomain [127.0.0.1]) by tracker2.aebc.com (Postfix) with ESMTP id AFD4D6768C8 for <freebsd-questions@freebsd.org>; Tue, 20 Jan 2009 22:38:41 -0800 (PST) Received: (from apache@localhost) by tracker2.aebc.com (8.13.8/8.13.8/Submit) id n0L6cfin026492; Tue, 20 Jan 2009 22:38:41 -0800 From: "AEBC Support via RT" <support@aebc.com> In-Reply-To: <20090121063945.784F710656C2@hub.freebsd.org> References: <RT-Ticket-190335@tracker2.aebc.com> <20090121063945.784F710656C2@hub.freebsd.org> Message-ID: <rt-3.8.2-24799-1232519921-72.190335-3-0@tracker2.aebc.com> Precedence: bulk X-RT-Loop-Prevention: tracker2.aebc.com RT-Ticket: tracker2.aebc.com #190335 Managed-by: RT 3.8.2 (http://www.bestpractical.com/rt/) RT-Originator: freebsd-questions@freebsd.org Auto-Submitted: auto-replied To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Tue, 20 Jan 2009 22:38:41 -0800 Subject: [Trouble Ticket #190335] AutoReply: freebsd-questions Digest, Vol 246, Issue 26 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Reply-To: support@aebc.com List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> Sender: owner-freebsd-questions@freebsd.org Errors-To: owner-freebsd-questions@freebsd.org Thank you for contacting us. This message has been automatically generated in response to the creation of a trouble ticket regarding: "freebsd-questions Digest, Vol 246, Issue 26", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Trouble Ticket #190335]. Please include the string: [Trouble Ticket #190335] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, support@aebc.com ------------------------------------------------------------------------- Send freebsd-questions mailing list submissions to freebsd-questions@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-questions-request@freebsd.org You can reach the person managing the list at freebsd-questions-owner@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. [Trouble Ticket #190268] AutoReply: freebsd-questions Digest, Vol 246, Issue 25 (AEBC Support via RT) 2. Re: Way to prune/limit the ZFS zpool history? (Geoff Fritz) 3. Problem with libperl (Warren Liddell) 4. how do you boot freebsd-ia64 from disk? (Kendall Shaw) 5. 8 current mount of glabel root failed (michael) 6. source of uname information (Robert Huff) 7. Re: kvm switch (Chad Perrin) ---------------------------------------------------------------------- Message: 1 Date: Tue, 20 Jan 2009 20:29:51 -0800 From: "AEBC Support via RT" <support@aebc.com> Subject: [Trouble Ticket #190268] AutoReply: freebsd-questions Digest, Vol 246, Issue 25 To: freebsd-questions@freebsd.org Message-ID: <rt-3.8.2-16534-1232512191-1270.190268-3-0@tracker2.aebc.com> Content-Type: text/plain; charset="utf-8" Thank you for contacting us. This message has been automatically generated in response to the creation of a trouble ticket regarding: "freebsd-questions Digest, Vol 246, Issue 25", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Trouble Ticket #190268]. Please include the string: [Trouble Ticket #190268] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, support@aebc.com ------------------------------------------------------------------------- Send freebsd-questions mailing list submissions to freebsd-questions@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-questions-request@freebsd.org You can reach the person managing the list at freebsd-questions-owner@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. [Trouble Ticket #190165] AutoReply: freebsd-questions Digest, Vol 246, Issue 24 (AEBC Support via RT) 2. Newbie: offline package use / XFCE. (Thomas W. Holloway) 3. Re: Newbie: offline package use / XFCE. (Manolis Kiagias) 4. Motherboard support (Graeme Dargie) 5. Re: fdisk -B (Robert Marella) 6. Way to prune/limit the ZFS zpool history? (Geoff Fritz) 7. Re: Newbie: offline package use / XFCE. (Polytropon) 8. Re: Newbie: offline package use / XFCE. (Peter Ulrich Kruppa) 9. Re: Way to prune/limit the ZFS zpool history? (Dan Nelson) 10. Re: Edit user groups (Tim Judd) 11. Re: unable to logon after updating ports collection - Freebsd 7.1 stable (Tim Judd) ---------------------------------------------------------------------- Message: 1 Date: Tue, 20 Jan 2009 14:29:26 -0800 From: "AEBC Support via RT" <support@aebc.com> Subject: [Trouble Ticket #190165] AutoReply: freebsd-questions Digest, Vol 246, Issue 24 To: freebsd-questions@freebsd.org Message-ID: <rt-3.8.2-23288-1232490566-1972.190165-3-0@tracker2.aebc.com> Content-Type: text/plain; charset="utf-8" Thank you for contacting us. This message has been automatically generated in response to the creation of a trouble ticket regarding: "freebsd-questions Digest, Vol 246, Issue 24", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Trouble Ticket #190165]. Please include the string: [Trouble Ticket #190165] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, support@aebc.com ------------------------------------------------------------------------- Send freebsd-questions mailing list submissions to freebsd-questions@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-questions-request@freebsd.org You can reach the person managing the list at freebsd-questions-owner@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. Permanent Delivery Failure (MDaemon at mail.mcitsh.com) 2. Permanent Delivery Failure (MDaemon at mail.mcitsh.com) 3. Permanent Delivery Failure (MDaemon at mail.mcitsh.com) 4. Re: slices to "dangerously dedicated" (Jerry McAllister) 5. Re: Edit user groups (Jerry McAllister) 6. Re: Edit user groups (Steve Bertrand) 7. fdisk -B (Robert) 8. Re: Edit user groups (Bill Moran) 9. [Trouble Ticket #190137] AutoReply: freebsd-questions Digest, Vol 246, Issue 23 (AEBC Support via RT) 10. Re: Edit user groups (Akenner) 11. Re: slices to "dangerously dedicated" (Wojciech Puchar) 12. Re: fdisk -B (Wojciech Puchar) 13. Re: slices to "dangerously dedicated" (Maxim Khitrov) 14. Re: switching bsdlabel's label (Wojciech Puchar) 15. Re: Edit user groups (Clifton Royston) ---------------------------------------------------------------------- Message: 1 Date: Wed, 21 Jan 2009 02:45:01 +0700 From: "MDaemon at mail.mcitsh.com" <MDaemon@mail.mcitsh.com> Subject: Permanent Delivery Failure To: questions@freebsd.org Message-ID: <MDAEMON7375200901210245.AA4501921@mail.mcitsh.com> Content-Type: text/plain; charset="iso-8859-1" The attached message had PERMANENT fatal delivery errors! After one or more unsuccessful delivery attempts the attached message has been removed from the mail queue on this server. The number and frequency of delivery attempts are determined by local configuration parameters. YOUR MESSAGE WAS NOT DELIVERED TO ONE OR MORE RECIPIENTS! Failed address: vodete@lpqa.info --- Session Transcript --- Wed 2009-01-21 02:45:01: Parsing message <xxxxxxxxxxxxxxxxxxxxxxxx\pd50000582628.msg> Wed 2009-01-21 02:45:01: * From: questions@freebsd.org Wed 2009-01-21 02:45:01: * To: vodete@lpqa.info Wed 2009-01-21 02:45:01: * Subject: =?windows-1251?B?z/Do5ews8+Lu6/zt5e3o5Szi++3z5uTl7e375SDv8O7j8+v7?= Wed 2009-01-21 02:45:01: * Message-ID: <005001c97b9c$ff77b363$d3a58f0c@ejhqluzrpz> Wed 2009-01-21 02:45:01: Attempting SMTP connection to [lpqa.info] Wed 2009-01-21 02:45:01: Resolving MX records for [lpqa.info] (DNS Server: 203.146.251.198)... Wed 2009-01-21 02:45:01: * Name server reports domain name unknown Wed 2009-01-21 02:45:01: Attempting SMTP connection to [lpqa.info:25] Wed 2009-01-21 02:45:01: Resolving A record for [lpqa.info] (DNS Server: 203.146.251.198)... Wed 2009-01-21 02:45:01: * Name server reports domain name unknown --- End Transcript --- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/octet-stream Size: 4712 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20090120/33402081/attachment-0001.obj ------------------------------ Message: 2 Date: Wed, 21 Jan 2009 02:45:07 +0700 From: "MDaemon at mail.mcitsh.com" <MDaemon@mail.mcitsh.com> Subject: Permanent Delivery Failure To: questions@freebsd.org Message-ID: <MDAEMON7379200901210245.AA4507000@mail.mcitsh.com> Content-Type: text/plain; charset="iso-8859-1" The attached message had PERMANENT fatal delivery errors! After one or more unsuccessful delivery attempts the attached message has been removed from the mail queue on this server. The number and frequency of delivery attempts are determined by local configuration parameters. YOUR MESSAGE WAS NOT DELIVERED TO ONE OR MORE RECIPIENTS! Failed address: vodeneev@ua.fm --- Session Transcript --- Wed 2009-01-21 02:45:01: Parsing message <xxxxxxxxxxxxxxxxxxxxxxxx\pd50000582629.msg> Wed 2009-01-21 02:45:01: * From: questions@freebsd.org Wed 2009-01-21 02:45:01: * To: vodeneev@ua.fm Wed 2009-01-21 02:45:01: * Subject: =?windows-1251?B?z/Do5ews8+Lu6/zt5e3o5Szi++3z5uTl7e375SDv8O7j8+v7?= Wed 2009-01-21 02:45:01: * Message-ID: <005001c97b9c$ff77b363$d3a58f0c@ejhqluzrpz> Wed 2009-01-21 02:45:01: Attempting SMTP connection to [ua.fm] Wed 2009-01-21 02:45:01: Resolving MX records for [ua.fm] (DNS Server: 203.146.251.198)... Wed 2009-01-21 02:45:01: * P=005 S=002 D=ua.fm TTL=(198) MX=[mx3.ua.fm] {91.197.130.8} Wed 2009-01-21 02:45:01: * P=010 S=003 D=ua.fm TTL=(198) MX=[mx4.ua.fm] {91.198.36.33} Wed 2009-01-21 02:45:01: * P=020 S=000 D=ua.fm TTL=(198) MX=[mx1.ua.fm] {91.198.36.11} Wed 2009-01-21 02:45:01: * P=020 S=001 D=ua.fm TTL=(198) MX=[mx2.ua.fm] {91.198.36.8} Wed 2009-01-21 02:45:01: Attempting SMTP connection to [91.197.130.8:25] Wed 2009-01-21 02:45:01: Waiting for socket connection... Wed 2009-01-21 02:45:01: * Connection established (127.0.0.1:3016 -> 91.197.130.8:25) Wed 2009-01-21 02:45:01: Waiting for protocol to start... Wed 2009-01-21 02:45:02: <-- 220 out01.mi6.kiev.ua ESMTP Exim 4.69 Tue, 20 Jan 2009 21:44:42 +0200 Wed 2009-01-21 02:45:02: --> HELO mail.mcitsh.com Wed 2009-01-21 02:45:03: <-- 250 out01.mi6.kiev.ua Hello mail.mcitsh.com [202.93.61.138] Wed 2009-01-21 02:45:03: --> MAIL From:<questions@freebsd.org> Wed 2009-01-21 02:45:03: <-- 250 OK Wed 2009-01-21 02:45:03: --> RCPT To:<vodeneev@ua.fm> Wed 2009-01-21 02:45:04: <-- 550 User not found. See http://mail.i.ua/err/2/ Wed 2009-01-21 02:45:04: --> QUIT --- End Transcript --- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/octet-stream Size: 4708 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20090120/97504636/attachment-0001.obj ------------------------------ Message: 3 Date: Wed, 21 Jan 2009 02:45:22 +0700 From: "MDaemon at mail.mcitsh.com" <MDaemon@mail.mcitsh.com> Subject: Permanent Delivery Failure To: questions@freebsd.org Message-ID: <MDAEMON7395200901210245.AA4522671@mail.mcitsh.com> Content-Type: text/plain; charset="iso-8859-1" The attached message had PERMANENT fatal delivery errors! After one or more unsuccessful delivery attempts the attached message has been removed from the mail queue on this server. The number and frequency of delivery attempts are determined by local configuration parameters. YOUR MESSAGE WAS NOT DELIVERED TO ONE OR MORE RECIPIENTS! Failed address: vodgosp@carrier.kiev.ua --- Session Transcript --- Wed 2009-01-21 02:45:01: Parsing message <xxxxxxxxxxxxxxxxxxxxxxxx\pd50000582627.msg> Wed 2009-01-21 02:45:01: * From: questions@freebsd.org Wed 2009-01-21 02:45:01: * To: vodgosp@carrier.kiev.ua Wed 2009-01-21 02:45:01: * Subject: =?windows-1251?B?z/Do5ews8+Lu6/zt5e3o5Szi++3z5uTl7e375SDv8O7j8+v7?= Wed 2009-01-21 02:45:01: * Message-ID: <005001c97b9c$ff77b363$d3a58f0c@ejhqluzrpz> Wed 2009-01-21 02:45:01: Attempting SMTP connection to [carrier.kiev.ua] Wed 2009-01-21 02:45:01: Resolving MX records for [carrier.kiev.ua] (DNS Server: 203.146.251.198)... Wed 2009-01-21 02:45:01: * P=010 S=000 D=carrier.kiev.ua TTL=(3) MX=[mx.lucky.net] {62.244.55.219} Wed 2009-01-21 02:45:01: * P=010 S=001 D=carrier.kiev.ua TTL=(3) MX=[mx.lucky.net] {193.193.193.137} multi-homed Wed 2009-01-21 02:45:01: * P=010 S=002 D=carrier.kiev.ua TTL=(3) MX=[mx.lucky.net] {62.244.55.218} multi-homed Wed 2009-01-21 02:45:01: Attempting SMTP connection to [62.244.55.219:25] Wed 2009-01-21 02:45:01: Waiting for socket connection... Wed 2009-01-21 02:45:01: * Connection established (127.0.0.1:3013 -> 62.244.55.219:25) Wed 2009-01-21 02:45:01: Waiting for protocol to start... Wed 2009-01-21 02:45:16: <-- 220 c.mx.lucky.net ESMTP (incoming mail server) Tue, 20 Jan 2009 21:45:02 +0200 (EET) Wed 2009-01-21 02:45:16: --> HELO mail.mcitsh.com Wed 2009-01-21 02:45:17: <-- 250 c.mx.lucky.net Hello mail.mcitsh.com [202.93.61.138], pleased to meet you Wed 2009-01-21 02:45:17: --> MAIL From:<questions@freebsd.org> Wed 2009-01-21 02:45:18: <-- 250 2.1.0 <questions@freebsd.org>... Sender ok Wed 2009-01-21 02:45:18: --> RCPT To:<vodgosp@carrier.kiev.ua> Wed 2009-01-21 02:45:18: <-- 550 5.1.1 <vodgosp@carrier.kiev.ua>... User unknown Wed 2009-01-21 02:45:18: --> QUIT --- End Transcript --- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/octet-stream Size: 4726 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20090120/6a2fb352/attachment-0001.obj ------------------------------ Message: 4 Date: Tue, 20 Jan 2009 15:24:08 -0500 From: Jerry McAllister <jerrymc@msu.edu> Subject: Re: slices to "dangerously dedicated" To: Robert Huff <roberthuff@rcn.com> Cc: questions@freebsd.org Message-ID: <20090120202408.GA57664@gizmo.acns.msu.edu> Content-Type: text/plain; charset=us-ascii On Tue, Jan 20, 2009 at 02:47:24PM -0500, Robert Huff wrote: > > Suppose I have a disk which was - for various reasons - lebeled > using slices. > Is it possible to change it to "dangerously dedicated" without > backup-wipe-relabel-restore cycle? > Not really. And why would you want to? Just leave it. You will gain nothing by the change. ////jerry > > Robert Huff > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" ------------------------------ Message: 5 Date: Tue, 20 Jan 2009 15:28:27 -0500 From: Jerry McAllister <jerrymc@msu.edu> Subject: Re: Edit user groups To: Akenner <SlackWareWolf@comcast.net> Cc: questions@freebsd.org Message-ID: <20090120202827.GB57664@gizmo.acns.msu.edu> Content-Type: text/plain; charset=us-ascii On Tue, Jan 20, 2009 at 03:09:16PM -0500, Akenner wrote: > Hi, > > I'm using FreeBSD 7.1-RELEASE and I have multiple user accounts set up. > I made about 4 for myself to use and do various testing with, and made > some for my Wife as well because She knows UNIX better than I do anyway heh. > > Anyway, one of the things I forgot about, was that FreeBSD by default > doesn't allow just anyone to use su. > > I come from mainly using Linux, where you can log in and then whenever > you need to open a root xterm or even a root shell, you just type the > password and go. I looked up how to do this but most of my results came > back with setting up user accounts, and other things. I did add another > user that was in the wheel group so I could do it, but I'd really like > to be able to add my main user account to the wheel group so I can su > from this one instead of doing su otheruser and then su again to root. > > I found while searching for this something that MIGHT be what I'm > looking for, but after reading it over, it seems I'd have to read > through the whole man page first and then, it could be bad if I mistype > something, or I could even screw up an account, which I can't risk. > > Is there an exact way to take a user account on my system, and add it to > the wheel group? Just edit the /etc/group file and put that user in that group. That is the normal way of doing it. I would not suggest making wheel be the primary group for any other than root accounts. ////jerry > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" ------------------------------ Message: 6 Date: Tue, 20 Jan 2009 15:31:09 -0500 From: Steve Bertrand <steve@ibctech.ca> Subject: Re: Edit user groups To: Akenner <SlackWareWolf@comcast.net> Cc: questions@freebsd.org Message-ID: <4976348D.4010502@ibctech.ca> Content-Type: text/plain; charset=ISO-8859-1 Akenner wrote: > Hi, > > I'm using FreeBSD 7.1-RELEASE and I have multiple user accounts set up. > I made about 4 for myself to use and do various testing with, and made > some for my Wife as well because She knows UNIX better than I do anyway > heh. > > Anyway, one of the things I forgot about, was that FreeBSD by default > doesn't allow just anyone to use su. > > I come from mainly using Linux, where you can log in and then whenever > you need to open a root xterm or even a root shell, you just type the > password and go. I looked up how to do this but most of my results came > back with setting up user accounts, and other things. I did add another > user that was in the wheel group so I could do it, but I'd really like > to be able to add my main user account to the wheel group so I can su > from this one instead of doing su otheruser and then su again to root. > > I found while searching for this something that MIGHT be what I'm > looking for, but after reading it over, it seems I'd have to read > through the whole man page first and then, it could be bad if I mistype > something, or I could even screw up an account, which I can't risk. > > Is there an exact way to take a user account on my system, and add it to > the wheel group? Yes. # ee /etc/group ...and add your username to the list of users after the wheel group. For instance, by default, the entry will appear as such: wheel:*:0:root ...and if my username is steve, you will append the line like this: wheel:*:0:root,steve ...then hit ESC, then ENTER twice. Steve ------------------------------ Message: 7 Date: Tue, 20 Jan 2009 12:28:30 -0800 From: Robert <traveling08@cox.net> Subject: fdisk -B To: freebsd-questions@freebsd.org <freebsd-questions@freebsd.org> Message-ID: <20090120122830.096ca40e@debian.shasta204.local> Content-Type: text/plain; charset=US-ASCII I have a server that has five drives in it. Two drives ad4 and ad6 are arranged with gmirror as the operating system (7.1 Stable). The FreeBSD boot manager is installed for this mirror and I would like to remove it and use the standard FreeBSD MBR ...without messing anything up. Can I perform the fdisk -B /dev/ad4 followed by fdisk -B /dev/ad6 from a livefs disk? Maybe fdisk -B /dev/mirror/gm0? I have backups but everything is running very nice right now. I don't reboot very often but I _would_ like to get rid of the boot manager Thank you Robert ------------------------------ Message: 8 Date: Tue, 20 Jan 2009 15:28:35 -0500 From: Bill Moran <wmoran@potentialtech.com> Subject: Re: Edit user groups To: Akenner <SlackWareWolf@comcast.net> Cc: questions@freebsd.org Message-ID: <20090120152835.aea0b37d.wmoran@potentialtech.com> Content-Type: text/plain; charset=US-ASCII In response to Akenner <SlackWareWolf@comcast.net>: > Hi, > > I'm using FreeBSD 7.1-RELEASE and I have multiple user accounts set up. > I made about 4 for myself to use and do various testing with, and made > some for my Wife as well because She knows UNIX better than I do anyway heh. > > Anyway, one of the things I forgot about, was that FreeBSD by default > doesn't allow just anyone to use su. > > I come from mainly using Linux, where you can log in and then whenever > you need to open a root xterm or even a root shell, you just type the > password and go. I looked up how to do this but most of my results came > back with setting up user accounts, and other things. I did add another > user that was in the wheel group so I could do it, but I'd really like > to be able to add my main user account to the wheel group so I can su > from this one instead of doing su otheruser and then su again to root. > > I found while searching for this something that MIGHT be what I'm > looking for, but after reading it over, it seems I'd have to read > through the whole man page first and then, it could be bad if I mistype > something, or I could even screw up an account, which I can't risk. > > Is there an exact way to take a user account on my system, and add it to > the wheel group? man pw Specifically: pw usermod -n username -G wheel or pw groupmod -n wheel -m username -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ------------------------------ Message: 9 Date: Tue, 20 Jan 2009 12:24:31 -0800 From: "AEBC Support via RT" <support@aebc.com> Subject: [Trouble Ticket #190137] AutoReply: freebsd-questions Digest, Vol 246, Issue 23 To: freebsd-questions@freebsd.org Message-ID: <rt-3.8.2-24796-1232483070-1333.190137-3-0@tracker2.aebc.com> Content-Type: text/plain; charset="utf-8" Thank you for contacting us. This message has been automatically generated in response to the creation of a trouble ticket regarding: "freebsd-questions Digest, Vol 246, Issue 23", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Trouble Ticket #190137]. Please include the string: [Trouble Ticket #190137] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, support@aebc.com ------------------------------------------------------------------------- Send freebsd-questions mailing list submissions to freebsd-questions@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-questions-request@freebsd.org You can reach the person managing the list at freebsd-questions-owner@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: unable to logon after updating ports collection - Freebsd 7.1 stable (Boris Samorodov) 2. Re: unable to logon after updating ports collection - Freebsd 7.1 stable (Bert-Jan) 3. Re: tar fails on FreeBSD 7 and passes on FreeBSD 6 for the same input (David Wolfskill) 4. Re: Large raid arrays (Matias Surdi) 5. Portupgrade thru SSH session (Jos Chrispijn) 6. Re: kvm switch (Mike Clarke) 7. Re: Portupgrade thru SSH session (Josh Carroll) 8. Re: Portupgrade thru SSH session (Ron Wilhoite) 9. stable-supfile --> freebsd-update (Roy Stuivenberg) 10. How to auto-logout after XXX idle? (lhmwzy) 11. telnet to mbmon (DA Forsyth) 12. Re: Large raid arrays (Wojciech Puchar) 13. Re: Large raid arrays (Wojciech Puchar) 14. switching bsdlabel's label (Eduardo Meyer) 15. Re: Large raid arrays (Matias Surdi) 16. NetBSD networking question (Shawn Hoffman) 17. Re: switching bsdlabel's label (Patrick M. Hausen) 18. Strange nvidia GeForce 9800GT--harddrive conflict? (Jakub T) 19. Permanent Delivery Failure (MDaemon at mail.mcitsh.com) 20. Re: switching bsdlabel's label (Eduardo Meyer) 21. ASL 2.0 based software contribution to FreeBSD code base (Saifi Khan) 22. Re: switching bsdlabel's label (David Wolfskill) 23. Re: switching bsdlabel's label (Jerry McAllister) 24. Re: Cannot perform user mounts after upgrade (Lowell Gilbert) 25. Re: DUMP: read error: Bad address (Lowell Gilbert) 26. Re: Port 7070 (Lowell Gilbert) 27. Re: NetBSD networking question (Andrew Gould) 28. Re: Cannot perform user mounts after upgrade (Roland Smith) 29. Re: DUMP: read error: Bad address (Chris Jones) 30. slices to "dangerously dedicated" (Robert Huff) 31. Re: slices to "dangerously dedicated" (Chuck Swiger) 32. Edit user groups (Akenner) 33. Permanent Delivery Failure (MDaemon at mail.mcitsh.com) ---------------------------------------------------------------------- Message: 1 Date: Tue, 20 Jan 2009 15:45:38 +0300 From: Boris Samorodov <bsam@ipt.ru> Subject: Re: unable to logon after updating ports collection - Freebsd 7.1 stable To: "Roy Stuivenberg" <roys1012@gmail.com> Cc: freebsd-questions@freebsd.org Message-ID: <47622685@ipt.ru> Content-Type: text/plain; charset=us-ascii "Roy Stuivenberg" <roys1012@gmail.com> writes: > After I completed my Freebsd 7.1 stable, and updated all the ports, I got > prompted with another logonscreen. > Whatever I try, I can't login with my useraccount and even not logon as > root. > This happened severall times now, the only way was to reinstall everything, > and I was hoping to resolve this by completly finish upgrading the ports. > And .. again the same problem. > I'm really hoping to get some answers that will solve this problem, maybe > someone had to deal with this issue before ?? > I will not give up, because Freebsd stole my heart. The problem has nothing to do with ports. To restore your root/user logins: . boot into single user mode; . set a new root password; . set a new user password; . boot into multiuser mode; . login and have fun. WBR -- bsam ------------------------------ Message: 2 Date: Tue, 20 Jan 2009 14:15:08 +0100 (CET) From: "Bert-Jan" <info@bert-jan.com> Subject: Re: unable to logon after updating ports collection - Freebsd 7.1 stable To: "Boris Samorodov" <bsam@ipt.ru> Cc: Roy Stuivenberg <roys1012@gmail.com>, freebsd-questions@freebsd.org Message-ID: <06bb5927cefec26ba5797915637b8a95.squirrel@admin.bert-jan.com> Content-Type: text/plain;charset=iso-8859-1 > "Roy Stuivenberg" <roys1012@gmail.com> writes: > >> After I completed my Freebsd 7.1 stable, and updated all the ports, I >> got >> prompted with another logonscreen. >> Whatever I try, I can't login with my useraccount and even not logon as >> root. >> This happened severall times now, the only way was to reinstall >> everything, >> and I was hoping to resolve this by completly finish upgrading the >> ports. >> And .. again the same problem. >> I'm really hoping to get some answers that will solve this problem, >> maybe >> someone had to deal with this issue before ?? >> I will not give up, because Freebsd stole my heart. > > The problem has nothing to do with ports. To restore your root/user > logins: > . boot into single user mode; > . set a new root password; > . set a new user password; > . boot into multiuser mode; > . login and have fun. > > > WBR > -- > bsam > _______________________________________________ I've had the same thing happen to me not 2 weeks ago after upgrading a server from 7.0-RC2 to 7.1-RELEASE with freebsd-update. For me the problem had nothing to do with ports but with the update itself, because it replaced my pwd.db and spwd.db with the default ones (root with no password, no user accounts) and since ssh doesn't accept root logins I ended up going to the datacenter and copying the backups of those db's back. Then everything was fine again. Very strange they got replaced though.. Sounds like you've had something similar happen to you. Hopefully your machine isn't too far away. Bert-Jan ------------------------------ Message: 3 Date: Tue, 20 Jan 2009 04:49:03 -0800 From: David Wolfskill <david@catwhisker.org> Subject: Re: tar fails on FreeBSD 7 and passes on FreeBSD 6 for the same input To: chandra reddy <creddym@gmail.com> Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Message-ID: <20090120124903.GH17567@albert.catwhisker.org> Content-Type: text/plain; charset="us-ascii" On Tue, Jan 20, 2009 at 01:24:41PM +0530, chandra reddy wrote: > Hi, > > I am getting the following error when i run tar on a directory. > > [chandra@home]$ tar zcf config-xsl.tar config-xsl/9.6 > > tar: Cannot open directory > config-xsl/9.6/configuration/protocols/mpls/label-switched-path/oam/bfd-liveness-detection/detection-time: > No such file or directory > tar: Cannot open directory > ... > FreeBSD chandra 7.1-RC1 FreeBSD 7.1-RC1 #0: Sun Dec 7 05:57:33 UTC 2008 > root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > I have debugged libc and found that system call "fstafs" is failing and > returning -1. I believe you will find that the system call is "fstatfs". > Can any one help me what is the real problem here and how to fix it? A subsequent message of your verified that the hierarchy being read was on an NFS-mounted file system. Perchance, was that NFS mount managwed by amd(8)? If so, while I do not have a "fix" for you, I am relieved to see someone else finally report these symptoms. Please see <http://docs.FreeBSD.org/cgi/mid.cgi?20081203001538.GC96383>; for an archived copy of my initial message in a thread reporting this. There is additional detail (including kernel trace information & how-to-repeat instructions) in subsequent messages in the thread. Also mentioned is a circumvention -- basically, crippling amd(8) so it no longer attempts to unmount() a file system. However, I was unable to re-create the symptoms at home -- only at work. A colleague at work was able to re-create the symptoms, and was intending to experiment a bit more, but he's been busy with other things recently. Please contact me (off-list, if you prefer), and we can discuss additional details. Peace, david -- David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20090120/2d10270f/attachment-0001.pgp ------------------------------ Message: 4 Date: Tue, 20 Jan 2009 12:32:31 +0100 From: Matias Surdi <matiassurdi@gmail.com> Subject: Re: Large raid arrays To: Frederique Rijsdijk <frederique@isafeelin.org> Cc: freebsd-questions@freebsd.org Message-ID: <4975B64F.20207@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Frederique Rijsdijk escribi���������������������������: > Matias Surdi wrote: >> Matias Surdi escribi���������������������������: >>> Hi, >>> >>> I've a host with two large (2Tb and 4 Tb) hardware raid5 arrays. >>> >>> For the backup system we are using, I need to join them to make 1 >>> logical device. >>> >>> What would you recomment? ccd or vinum? >>> >>> >> Some comments that may help in the decision: >> >> - Reliability/resistance to power failures are the most important factor. >> >> - It doesn't require high performance or high speed. >> > > Either gconcat or ZFS, depending which version of FreeBSD you're running. > > gconcat label -v data /dev/raid1 /dev/raid2 > newfs /dev/concat/data > mkdir /mnt/data && mount /dev/concat/data /mnt/data > df -h /mnt/data > > or > > zpool create data /dev/raid1 /dev/raid2 > df -h /data > > > > -- Frederique > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > ZFS was a disaster. That is what we were using until today, when the power went off and the zfs pool ended up corrupted and irrecoverable. Three other times we had power failures, the zpool ended with some errors. But, all the times, the UFS partitions remained intact. I won't use ZFS for a long time. ------------------------------ Message: 5 Date: Tue, 20 Jan 2009 15:10:13 +0100 From: Jos Chrispijn <jos@webrz.net> Subject: Portupgrade thru SSH session To: freebsd-questions@freebsd.org Message-ID: <4975DB45.1040407@webrz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Can someone tell me what I should attend for when I am disconnected in the middle of a portupgrade and the terminal session is aborted? The portupgrade was halted by a [yes/no] prompt, on which I had to react. Unfortunately being not present and I having not set my Putty keepalive session timeperiod I was disconnected due to no activity on this system prompt $-|. What I did after having logged on again was deleting that specific ruby process and some tty processes. Perhaps I should delete some other temp files as well? Thanks, Jos Chrispijn ------------------------------ Message: 6 Date: Tue, 20 Jan 2009 14:10:26 +0000 From: Mike Clarke <jmc-freebsd2@milibyte.co.uk> Subject: Re: kvm switch To: freebsd-questions@freebsd.org Message-ID: <200901201410.26629.jmc-freebsd2@milibyte.co.uk> Content-Type: text/plain; charset="iso-8859-1" On Tuesday 20 January 2009, Olivier Nicole wrote: > I have been using Aten KVM switches for years and been very happy > with them. [snip] > To my knowledge it works with 3 button mouses (all mouses nowdays > have 3 buttons). I have an Aten CS64A PS/2 4 port KVM <http://preview.tinyurl.com/yte4et>; and it works fine with my 3 button mouse, supporting all 3 buttons and the scroll wheel. I've had FreeBSD, linux, Win98, XP and Vista boxes running through it at various times over the last 2 years and it's always worked just fine. My only minor niggle was that if I booted my FreeBSD box while the monitor was connected to one of the other boxes then KDE started up in 1024x768 mode instead if the monitor's default 1280x1024 mode. But that was easily sorted with a minor tweak to xorg.conf. -- Mike Clarke ------------------------------ Message: 7 Date: Tue, 20 Jan 2009 10:17:19 -0500 From: Josh Carroll <josh.carroll@gmail.com> Subject: Re: Portupgrade thru SSH session To: Jos Chrispijn <jos@webrz.net> Cc: freebsd-questions@freebsd.org Message-ID: <8cb6106e0901200717u717a0734r933f4337658fffd5@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 20, 2009 at 9:10 AM, Jos Chrispijn <jos@webrz.net> wrote: > Can someone tell me what I should attend for when I am disconnected in the > middle of a portupgrade and the terminal session is aborted? > The portupgrade was halted by a [yes/no] prompt, on which I had to react. > Unfortunately being not present and I having not set my Putty keepalive > session timeperiod I was disconnected due to no activity on this system > prompt $-|. > What I did after having logged on again was deleting that specific ruby > process and some tty processes. Perhaps I should delete some other temp > files as well? For future runs, you might consider using something like screen (/usr/ports/sysutils/screen) so you can resume the session later, should you get disconnected. Josh ------------------------------ Message: 8 Date: Tue, 20 Jan 2009 09:44:05 -0500 From: Ron Wilhoite <ronw@bals.org> Subject: Re: Portupgrade thru SSH session To: Jos Chrispijn <jos@webrz.net> Cc: freebsd-questions@freebsd.org Message-ID: <4975E335.5070703@bals.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 01/20/2009 09:10 AM Jos Chrispijn wrote: > Can someone tell me what I should attend for when I am disconnected in > the middle of a portupgrade and the terminal session is aborted? > The portupgrade was halted by a [yes/no] prompt, on which I had to > react. Unfortunately being not present and I having not set my Putty > keepalive session timeperiod I was disconnected due to no activity on > this system prompt $-|. > What I did after having logged on again was deleting that specific ruby > process and some tty processes. Perhaps I should delete some other temp > files as well? Before I learned to run portupgrade in a screen session, I never had a problem just running portupgrade again. If I recall correctly the index needed to be rebuilt at times, but portupgrade gave a helpful message telling me that. Ron Wilhoite ------------------------------ Message: 9 Date: Tue, 20 Jan 2009 15:23:58 +0000 From: "Roy Stuivenberg" <roys1012@gmail.com> Subject: stable-supfile --> freebsd-update To: freebsd-questions@freebsd.org Message-ID: <b9079c480901200723q5596d6b8q198f2aff8deaf41d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hello, I wanted to send a follow up on my message, because I did not provide much info ... ********** Hello, After I completed my Freebsd 7.1 stable, and updated all the ports, I got prompted with another logonscreen. Whatever I try, I can't login with my useraccount and even not logon as root. This happened severall times now, the only way was to reinstall everything, and I was hoping to resolve this by completly finish upgrading the ports. And .. again the same problem. I'm really hoping to get some answers that will solve this problem, maybe someone had to deal with this issue before ?? ************* Follow up ===> My problem has something to do with gnome2 I guess. You see, I can logon, except in graphical user mode. This happend after complete update (gnome2 included) I get a different logon prompt, and then I already know I won't be able to logon. Only this time I was hoping an upgrade of all the ports would help me .. and it didn't. I really hope I will find or get an answer to this problem. Regards, Roy. ------------------------------ Message: 10 Date: Tue, 20 Jan 2009 23:10:25 +0800 From: lhmwzy <lhmwzy@gmail.com> Subject: How to auto-logout after XXX idle? To: freebsd-questions@freebsd.org Message-ID: <78fb9d960901200710r27911b0cheaddfd3769abe7d3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 When ssh to a sever,how to auto-logout after XXX idle? in tcsh,I know to set autologout=X How in the default /bin/sh shell to autologut? ------------------------------ Message: 11 Date: Tue, 20 Jan 2009 17:42:02 +0200 From: "DA Forsyth" <d.forsyth@ru.ac.za> Subject: telnet to mbmon To: freebsd-questions@freebsd.org Message-ID: <49760CEA.3417.1479BC08@d.forsyth.ru.ac.za> Content-Type: text/plain; charset=US-ASCII Hiya I am using mbmon in telnet mode to monitor some print servers remotely. REvcently I moved the monitoring form one server to another, but now the telnet probe only works from the command line. Any probe originating from a cron job gets no data in the reply (normally via mrtg, but I tried a direct telnet call as a cron job and it also got no data as a reply). Yes, the connection is made. mbmon is running on the targets. This is affecting 3 target print servers. I tried running the probe on the original server and it worked as usual. where to look? -- DA Fo rsyth Network Supervisor Principal Technical Officer -- Institute for Water Research http://www.ru.ac.za/institutes/iwr/ ------------------------------ Message: 12 Date: Tue, 20 Jan 2009 16:47:21 +0100 (CET) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Subject: Re: Large raid arrays To: Matias Surdi <matiassurdi@gmail.com> Cc: freebsd-questions@freebsd.org Message-ID: <20090120164719.B18283@wojtek.tensor.gdynia.pl> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed gconcat On Tue, 20 Jan 2009, Matias Surdi wrote: > Hi, > > I've a host with two large (2Tb and 4 Tb) hardware raid5 arrays. > > For the backup system we are using, I need to join them to make 1 logical > device. > > What would you recomment? ccd or vinum? > > > Thanks a lot for your suggestions. > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > ------------------------------ Message: 13 Date: Tue, 20 Jan 2009 16:48:45 +0100 (CET) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Subject: Re: Large raid arrays To: Matias Surdi <matiassurdi@gmail.com> Cc: freebsd-questions@freebsd.org Message-ID: <20090120164747.J18283@wojtek.tensor.gdynia.pl> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed >> > > > ZFS was a disaster. > > That is what we were using until today, when the power went off and the zfs > pool ended up corrupted and irrecoverable. normal. > > Three other times we had power failures, the zpool ended with some errors. > > But, all the times, the UFS partitions remained intact. indeed. and fsck time can be fast if you correctly set up block size and amount of inodes. i mean not too much inodes and large blocks (32-64K) if you store mostly big files. > I won't use ZFS for a long time. i would recommend never. ------------------------------ Message: 14 Date: Tue, 20 Jan 2009 13:24:27 -0200 From: Eduardo Meyer <dudu.meyer@gmail.com> Subject: switching bsdlabel's label To: questions@freebsd.org, stable@freebsd.org Message-ID: <d3ea75b30901200724o4bc9b515y71733fcb2f5808f9@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hello, I have a certain disk where da0s1a and da0s1d are inverted. By some reason someone labelled root as 'd' and home as 'a'. Can I just bsdlabel -n da0s1 > savedabel.txt Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) -- =========== Eduardo Meyer pessoal: dudu.meyer@gmail.com profissional: ddm.farmaciap@saude.gov.br ------------------------------ Message: 15 Date: Tue, 20 Jan 2009 17:19:31 +0100 From: Matias Surdi <matiassurdi@gmail.com> Subject: Re: Large raid arrays To: freebsd-questions@freebsd.org Message-ID: <gl4tii$skm$1@ger.gmane.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Wojciech Puchar escribi���������������������������: > gconcat > > On Tue, 20 Jan 2009, Matias Surdi wrote: > >> Hi, >> >> I've a host with two large (2Tb and 4 Tb) hardware raid5 arrays. >> >> For the backup system we are using, I need to join them to make 1 >> logical device. >> >> What would you recomment? ccd or vinum? >> >> >> Thanks a lot for your suggestions. >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > I've finally set it up with gconcat and works great. Many thanks for your help guys. ------------------------------ Message: 16 Date: Tue, 20 Jan 2009 11:26:47 -0500 From: "Shawn Hoffman" <shoffman@logikos.com> Subject: NetBSD networking question To: <freebsd-questions@freebsd.org> Message-ID: <A6363BE436C7C54B8105C2866E6A0C8E01F0E438@newclavius.logikos.com> Content-Type: text/plain; charset="us-ascii" Hello, my name is Shawn Hoffman, and I am the Staffing Manager for Logikos Inc. Logikos is a product software development firm located in Fort Wayne, Indiana. I am contacting you in hopes that you might be able to offer suggestions as to where we might find a contract NetBSD Administrator. We are beginning a project for a client that necessitates this background. Is there someone you know who might have an interest in a contract opportunity of this sort? If so, I would appreciate any assistance your network of contacts may offer. Thank you. Shawn Hoffman - Staffing Manager Logikos Inc, 2914 Independence Drive Fort Wayne, IN 46808 260-483-3638 260-484-5268 fax shoffman@logikos.com ------------------------------ Message: 17 Date: Tue, 20 Jan 2009 17:13:56 +0100 From: "Patrick M. Hausen" <hausen@punkt.de> Subject: Re: switching bsdlabel's label To: Eduardo Meyer <dudu.meyer@gmail.com> Cc: stable@freebsd.org, questions@freebsd.org Message-ID: <20090120161355.GA28525@hugo10.ka.punkt.de> Content-Type: text/plain; charset=iso-8859-1 Hello, On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote: > I have a certain disk where da0s1a and da0s1d are inverted. By some > reason someone labelled root as 'd' and home as 'a'. > > Can I just > > bsdlabel -n da0s1 > savedabel.txt > > Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) Why not simply use bsdlabel -e da0s1? Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: J���������������������������rgen Egeling AG Mannheim 108285 ------------------------------ Message: 18 Date: Tue, 20 Jan 2009 17:23:22 +0100 From: Jakub T <jakub.tlck@gmail.com> Subject: Strange nvidia GeForce 9800GT--harddrive conflict? To: freebsd-questions@freebsd.org Message-ID: <42b840be0901200823je4afa44hd7c68e4e828da815@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm trying to start X on FreeBSD-7.1-RELEASE (i386) with up-to-date ports tree with this graphics card: nvidia0: <GeForce 9800 GT> on vgapci0 vgapci0: child nvidia0 requested pci_enable_busmaster vgapci0: child nvidia0 requested pci_enable_io nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] When I try to start X, with or without xorg.conf generated either by Xorg or by nvidia-xconfig, with or without kernel nvidia module loaded, I get a lot of errors like this: (EE) end of block range 0xfb < begin 0xfffffffc Then, my hard drive detaches, like this (not copy-pasted text): ad7: FAILURE - device detached subdisk7: detached ... g_vfs_done(): ad7s1f [WRITE(offset=... length=...)]error = 6 ... vnode_pager_getpages: I/O read error panic: vinvalbuf: dirty bufs ... What is interesting is that I succee [Truncated by SpamCop]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?rt-3.8.2-24798-1232535250-230.190335-6-0>