Hi,
You have two options:
(1) Log into freefall, and use all the doc stuff which is set up there.
or
(2) Set the docs stuff up yourself by following the setup steps at the
FreeBSD Documentation Project Primer page:
http://www.freebsd.org/doc/en/books/fdp-primer/ .
It's not too bad.
--
On Saturday, August 27, 2011 4:35:16 am Eric Masson wrote:
> Slawa Olhovchenkov writes:
>
> Hello,
>
> > Yes, from FreeBSD 6.x puc.ko don't work. Only in-kernel version work.
>
> Nope puc.ko module can't attach drivers compiled in kernel, but if both
> puc & uart are loaded as modules, they wor
On Mon, 29 Aug 2011, Vadim Goncharov wrote:
Hi Doug Barton!
On Sat, 27 Aug 2011 14:16:56 -0700; Doug Barton wrote:
May be for fist step: w/o devd, simle remove all posible from GENERIC and
include all removed
drivers in /boot/loader.conf?
You're better off using kld_list in rc.conf for
On Mon, Aug 29, 2011 at 05:55:33PM +0700, Vadim Goncharov wrote:
> > Not parallel ports -- plip interface
>
> Is someone somewhere boots over a known-to-be-long-broken slow interface?
Broken? And not removed from GENERIC 9.0?
> I doubt.
>
> >> The possible solution to this may be to have a MI
Hi Doug Barton!
On Sat, 27 Aug 2011 14:16:56 -0700; Doug Barton wrote:
>> May be for fist step: w/o devd, simle remove all posible from GENERIC
>> and include all removed
>> drivers in /boot/loader.conf?
>
> You're better off using kld_list in rc.conf for anything that does
Hi Slawa Olhovchenkov!
On Mon, 29 Aug 2011 14:40:50 +0400; Slawa Olhovchenkov wrote:
> Not parallel ports -- plip interface
Is someone somewhere boots over a known-to-be-long-broken slow interface?
I doubt.
>> The possible solution to this may be to have a MINIMAL kernel, also updated
>> by
On Mon, 29 Aug 2011, Vadim Goncharov wrote:
[snip]
> The possible solution to this may be to have a MINIMAL kernel, also updated
> by freebsd-update(8), but that will double requirements for space in /boot...
Axing .symbols from boot (and storing them elsewhere, say, /var/crash) would
actually
On Mon, Aug 29, 2011 at 05:32:34PM +0700, Vadim Goncharov wrote:
> So what could be really axed from there? Just agp, PCMCIA, parallel ports,
Not PCMCIA -- PCMCIA CF, PCMCIA falsh card etc.
Not parallel ports -- plip interface
> some of firewire drivers (not all - some needed for SCSI).
Not fir
On 8/28/2011 3:57 PM, Garrett Cooper wrote:
> I wish I had the docs stuff setup -- I would generate a draft for that
> if sgml functioned for me.
I'm assuming you're aware of the FDP, and merely lack the time to grind
through the process.
Meanwhile, there are plenty of people on freebsd-doc@ who
On Sat, Aug 27, 2011 at 4:47 PM, Doug Barton wrote:
> On 08/27/2011 14:39, Garrett Cooper wrote:
>> A certain set of quick guidelines (< 1 page should suffice) for
>> kld_list should be devised though.
>
> I look forward to reviewing your draft of that. :)
I wish I had the docs stuff setup --
On Sat, Aug 27, 2011 at 04:52:15PM -0700, Doug Barton wrote:
> On 08/27/2011 14:23, Slawa Olhovchenkov wrote:
> > GENERIC need not for me, GENERIC need for everyone: this is kernel on
> > installation image and kernel for first boot after install.
>
> We covered this a few weeks ago. The mechanis
On 08/27/2011 14:23, Slawa Olhovchenkov wrote:
> GENERIC need not for me, GENERIC need for everyone: this is kernel on
> installation image and kernel for first boot after install.
We covered this a few weeks ago. The mechanism used to load modules by
loader.conf is vrryyy sll
On 08/27/2011 14:39, Garrett Cooper wrote:
> A certain set of quick guidelines (< 1 page should suffice) for
> kld_list should be devised though.
I look forward to reviewing your draft of that. :)
--
Nothin' ever doesn't change, but nothin' changes much.
--
On Sat, Aug 27, 2011 at 02:37:34PM -0700, Garrett Cooper wrote:
> > If drivers moved from GENERIC to /boot/loader.conf it allow preserve
> > wide range of installation environment and give light way to reduce
> > count of loaded devices (by edit /boot/loader.conf).
>
> /boot/loader.conf is em
On Sat, Aug 27, 2011 at 2:16 PM, Doug Barton wrote:
> On 08/27/2011 14:04, Slawa Olhovchenkov wrote:
>> On Sat, Aug 27, 2011 at 01:32:07PM -0700, Doug Barton wrote:
>>
>>> On 08/27/2011 05:44, Slawa Olhovchenkov wrote:
On Sat, Aug 27, 2011 at 04:45:44AM -0700, Doug Barton wrote:
> On
On Sat, Aug 27, 2011 at 2:21 PM, Slawa Olhovchenkov wrote:
> On Sat, Aug 27, 2011 at 02:09:36PM -0700, Garrett Cooper wrote:
>
>> >> > What drivers in GENERIC don't need to boot from disk or network?
>> >> > sound only?
>> >>
>> >> man rc.conf, search for kld_list.
>> >
>> > Sorry for bad english.
On Sat, Aug 27, 2011 at 02:16:56PM -0700, Doug Barton wrote:
> >>> What drivers in GENERIC don't need to boot from disk or network?
> >>> sound only?
> >>
> >> man rc.conf, search for kld_list.
> >
> > Sorry for bad english.
> > What drivers (from current GENERIC) don't need for network or disk
>
On Sat, Aug 27, 2011 at 02:09:36PM -0700, Garrett Cooper wrote:
> >> > What drivers in GENERIC don't need to boot from disk or network?
> >> > sound only?
> >>
> >> man rc.conf, search for kld_list.
> >
> > Sorry for bad english.
> > What drivers (from current GENERIC) don't need for network or di
On 08/27/2011 14:04, Slawa Olhovchenkov wrote:
> On Sat, Aug 27, 2011 at 01:32:07PM -0700, Doug Barton wrote:
>
>> On 08/27/2011 05:44, Slawa Olhovchenkov wrote:
>>> On Sat, Aug 27, 2011 at 04:45:44AM -0700, Doug Barton wrote:
>>>
On 8/27/2011 3:53 AM, Slawa Olhovchenkov wrote:
> On Sat,
On Sat, Aug 27, 2011 at 2:04 PM, Slawa Olhovchenkov wrote:
> On Sat, Aug 27, 2011 at 01:32:07PM -0700, Doug Barton wrote:
>
>> On 08/27/2011 05:44, Slawa Olhovchenkov wrote:
>> > On Sat, Aug 27, 2011 at 04:45:44AM -0700, Doug Barton wrote:
>> >
>> >> On 8/27/2011 3:53 AM, Slawa Olhovchenkov wrote:
On Sat, Aug 27, 2011 at 01:32:07PM -0700, Doug Barton wrote:
> On 08/27/2011 05:44, Slawa Olhovchenkov wrote:
> > On Sat, Aug 27, 2011 at 04:45:44AM -0700, Doug Barton wrote:
> >
> >> On 8/27/2011 3:53 AM, Slawa Olhovchenkov wrote:
> >>> On Sat, Aug 27, 2011 at 10:35:16AM +0200, Eric Masson wrote
On 08/27/2011 05:44, Slawa Olhovchenkov wrote:
> On Sat, Aug 27, 2011 at 04:45:44AM -0700, Doug Barton wrote:
>
>> On 8/27/2011 3:53 AM, Slawa Olhovchenkov wrote:
>>> On Sat, Aug 27, 2011 at 10:35:16AM +0200, Eric Masson wrote:
>>>
Slawa Olhovchenkov writes:
Hello,
> Yes,
On Sat, Aug 27, 2011 at 04:45:44AM -0700, Doug Barton wrote:
> On 8/27/2011 3:53 AM, Slawa Olhovchenkov wrote:
> > On Sat, Aug 27, 2011 at 10:35:16AM +0200, Eric Masson wrote:
> >
> >> Slawa Olhovchenkov writes:
> >>
> >> Hello,
> >>
> >>> Yes, from FreeBSD 6.x puc.ko don't work. Only in-kernel
On 8/27/2011 3:53 AM, Slawa Olhovchenkov wrote:
> On Sat, Aug 27, 2011 at 10:35:16AM +0200, Eric Masson wrote:
>
>> Slawa Olhovchenkov writes:
>>
>> Hello,
>>
>>> Yes, from FreeBSD 6.x puc.ko don't work. Only in-kernel version work.
>>
>> Nope puc.ko module can't attach drivers compiled in kernel
On Sat, Aug 27, 2011 at 10:35:16AM +0200, Eric Masson wrote:
> Slawa Olhovchenkov writes:
>
> Hello,
>
> > Yes, from FreeBSD 6.x puc.ko don't work. Only in-kernel version work.
>
> Nope puc.ko module can't attach drivers compiled in kernel, but if both
> puc & uart are loaded as modules, they
Slawa Olhovchenkov writes:
Hello,
> Yes, from FreeBSD 6.x puc.ko don't work. Only in-kernel version work.
Nope puc.ko module can't attach drivers compiled in kernel, but if both
puc & uart are loaded as modules, they work fine :
emss@srvbsdfenssv:~> uname -mr
8.2-RELEASE-p2 amd64
emss@srvbsdfen
On Fri, Aug 26, 2011 at 05:34:26PM -0700, Doug Barton wrote:
> Sorry, I am not parsing this. Are you saying that the module is broken?
Yes, from FreeBSD 6.x puc.ko don't work. Only in-kernel version work.
>
> On 08/26/2011 14:22, John Baldwin wrote:
> > Author: jhb
> > Date: Fri Aug 26 21:22:34
Sorry, I am not parsing this. Are you saying that the module is broken?
Doug
On 08/26/2011 14:22, John Baldwin wrote:
> Author: jhb
> Date: Fri Aug 26 21:22:34 2011
> New Revision: 225201
> URL: http://svn.freebsd.org/changeset/base/225201
>
> Log:
> Enable the puc(4) driver on amd64 and i38
Author: jhb
Date: Fri Aug 26 21:22:34 2011
New Revision: 225201
URL: http://svn.freebsd.org/changeset/base/225201
Log:
Enable the puc(4) driver on amd64 and i386 in GENERIC. This allows
devices supported by puc(4) to work "out of the box" since puc.ko does
not work "out of the box".
Re
29 matches
Mail list logo
