Hi,
I found service(8) to be inconsistent that it listed files with `service
-e`, but plain services with `service -l`
My patch makes the default just list *service names*, and specifying -F
will show the full path to the file.
Patch:
http://www.shatow.net/freebsd/patch-service.txt
Regards,
Br
TB --- 2012-05-12 21:50:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-05-12 21:50:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Thu, May 10, 2012 at 12:39:00PM +0200, Peter Holm wrote:
> On Thu, May 10, 2012 at 12:21:18PM +0200, Mateusz Guzik wrote:
> > On Tue, May 08, 2012 at 09:45:14PM +0200, Peter Holm wrote:
> > > On Mon, May 07, 2012 at 10:11:53PM +0200, Mateusz Guzik wrote:
> > > > On Mon, May 07, 2012 at 12:28:41P
On 5/12/2012 4:39 PM, Konstantin Belousov wrote:
>
> My own preference is to implement second choice and put the driver
> into dev/drm2.
Is there a way to have an OPTION in the config file build one driver,
and without the OPTION to build the other, but use the same name? If so,
that might be t
With r235375, all required VM support for new Intel GPU driver was
committed into HEAD. There are still some things to improve and
change, but now the all.14.9.patch does not touch anything outside agp
or drm. This allows to start the process of importing the new Intel
GPU driver into HEAD.
I am
_
The bsdconfig(8) utility
URL: http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdconfig/
URL: http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1.svg
URL:
http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1i.svg
Contact: Devin Teske
Contact: Ron McDowell
TB --- 2012-05-12 15:30:01 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-05-12 15:30:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-05-12 15:30:01 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-05-12 15:30:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-05-12 15:30:01 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-05-12 15:30:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On 5/12/2012 6:25 AM, Vance Siemens wrote:
Can you share a brief overview of what's wrong with it? I guess I'm
not as knowledgeable as I thought. The story was quite enticing to me.
Very few of the historical facts are actually correct.
___
freebsd-cu
On Sat, May 12, 2012 at 4:40 PM, hopto wrote:
> on first problem:
> #ifconfig ral0 inet 192.168.0.1 netmask 0xfff0 ssid freebsdap channel 11
> mediaopt hostap
> ifconfig: SIOCS80211: Invalid argument
>
> on second problem:
> If the set is not as klinet otobrazhayutsya available networks at all
on first problem:
#ifconfig ral0 inet 192.168.0.1 netmask 0xfff0 ssid freebsdap channel 11
mediaopt hostap
ifconfig: SIOCS80211: Invalid argument
on second problem:
If the set is not as klinet otobrazhayutsya available networks at all.
Ate configured as an access point to the kind of okay (wla
TB --- 2012-05-12 12:46:15 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-05-12 12:46:15 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
Can you share a brief overview of what's wrong with it? I guess I'm
not as knowledgeable as I thought. The story was quite enticing to me.
On Thu, May 3, 2012 at 7:13 AM, Dag-Erling Smørgrav wrote:
> Vincent Hoffman writes:
>> Vance Siemens writes:
>> > http://www.trollaxor.com/2012/05/freebsd-
On Sat, May 12, 2012 at 8:44 AM, hopto wrote:
> does not work DWA-525 is not as an access point, not as a client
>
> May 12 01:57:23 bit-box kernel: ral0: mem
> 0xfe51-0xfe51 irq 16 at device 0.0 on pci6
> May 12 01:58:52 bit-box kernel: ral0: unable to receive rt2860fw firmware
> image
does not work DWA-525 is not as an access point, not as a client
May 12 01:57:23 bit-box kernel: ral0: mem
0xfe51-0xfe51 irq 16 at device 0.0 on pci6
May 12 01:58:52 bit-box kernel: ral0: unable to receive rt2860fw firmware
image
May 12 01:58:52 bit-box kernel: ral0: could not load 8051 m
16 matches
Mail list logo