Re: DragonFly testing
Jeremy C. Reed wrote: Yes, I thought about it too. However, the packages.7 manpage is part of the pkgsrc bootstrap, so adding a link would either have to be done directly by the pkgsrc people or we'd have to add it to nrelease/Makefile (which I'll do on the weekend if no one objects). NetBSD does link to pkgsrc.7 to packages.7 since October.\ I forgot to mention that is for the base NetBSD operating system and not for bootstrap (pkgsrc/pkgtools/pkgmanpages/). Jeremy, any chance to modify the pkgsrc bootstrap so that it: 1) Installs packages.7 in mdoc format. At the moment we only get a packages.0 in /usr/pkg/man/cat7 instead of packages.7 in /usr/pkg/man/man7. 2) Provides a link for pkgsrc.7. I think that should be enough since packages.7 points to pkgsrc.txt already so I think the only thing we really need is the link. Sascha -- http://yoyodyne.ath.cx
Re: DragonFly testing
> > > Yes, I thought about it too. However, the packages.7 manpage is part of > > > the pkgsrc bootstrap, so adding a link would either have to be done > > > directly by the pkgsrc people or we'd have to add it to > > > nrelease/Makefile (which I'll do on the weekend if no one objects). > > NetBSD does link to pkgsrc.7 to packages.7 since October.\ I forgot to mention that is for the base NetBSD operating system and not for bootstrap (pkgsrc/pkgtools/pkgmanpages/). Jeremy C. Reed
Re: DragonFly testing
On Fri, 23 Feb 2007, Trevor Kendall wrote: > > Yes, I thought about it too. However, the packages.7 manpage is part of > > the pkgsrc bootstrap, so adding a link would either have to be done > > directly by the pkgsrc people or we'd have to add it to > > nrelease/Makefile (which I'll do on the weekend if no one objects). NetBSD does link to pkgsrc.7 to packages.7 since October.\ > packages(7) doesn't explain how to install pkgsrc for building from > source which is what I think is needed here. Thats sounds like a good idea. > Following is an mdoc version of section 2 of pkgsrc/doc/pkgsrc.txt, > almost word for word, including awkward language: > http://franchan.ath.cx:4848/~tj/DragonFly/patches/pkgsrc.7 > Licenses may need to be adjusted. Definitely if almost word for word then license is wrong. (Please tell me the awkward language and I may commit fixes.) > It might be a good idea to include sections 4 and 5 (of pkgsrc.txt) in > pkgsrc(7) as well. I don't know if it is worth keeping this documentation in sync. Maybe just have DragonFly install pkgsrc.txt and have the pkgsrc.7 be a link to packages.7 that gives path to documentation (pkgsrc.txt) in the SEE ALSO. Maybe even install just /usr/pkg/doc/pkgsrc.txt ? Jeremy C. Reed
Re: DragonFly testing
Yes, I thought about it too. However, the packages.7 manpage is part of the pkgsrc bootstrap, so adding a link would either have to be done directly by the pkgsrc people or we'd have to add it to nrelease/Makefile (which I'll do on the weekend if no one objects). packages(7) doesn't explain how to install pkgsrc for building from source which is what I think is needed here. Following is an mdoc version of section 2 of pkgsrc/doc/pkgsrc.txt, almost word for word, including awkward language: http://franchan.ath.cx:4848/~tj/DragonFly/patches/pkgsrc.7 Licenses may need to be adjusted. It might be a good idea to include sections 4 and 5 (of pkgsrc.txt) in pkgsrc(7) as well. - Trevor What does an airport in Hong Kong have to do with this? I think Adsense has gone bonkers.
Re: DragonFly testing
Justin C. Sherrill wrote: On Thu, February 22, 2007 2:25 am, Sascha Wildner wrote: Ben Jolitz wrote: I found the how to a little non specific. I do think that a getpkgsrc script would help set things up. There were no man pages (maybe install fubar'ed?) on pkgsrc, so unlike man ports, I could not get a man pkgsrc. Try 'man packages'. Why doesn't 'man pkgsrc' work? Rather, is there any reason other than nobody's set it up that way? It would make absolute sense. Yes, I thought about it too. However, the packages.7 manpage is part of the pkgsrc bootstrap, so adding a link would either have to be done directly by the pkgsrc people or we'd have to add it to nrelease/Makefile (which I'll do on the weekend if no one objects). Sascha -- http://yoyodyne.ath.cx
Re: DragonFly testing
On Thu, February 22, 2007 2:25 am, Sascha Wildner wrote: > Ben Jolitz wrote: >> I found the how to a little non specific. I do think that a getpkgsrc >> script would help set things up. There were no man pages (maybe install >> fubar'ed?) on pkgsrc, so unlike man ports, I could not get a man pkgsrc. > > Try 'man packages'. Why doesn't 'man pkgsrc' work? Rather, is there any reason other than nobody's set it up that way? It would make absolute sense.
Re: DragonFly testing
On Thu, 22 Feb 2007 13:34:28 +0100 Joerg Sonnenberger <[EMAIL PROTECTED]> wrote: > On Thu, Feb 22, 2007 at 02:43:18AM +0100, Gergo Szakal wrote: > > (I admit that mplayer in pkgsrc tree is quite outdated.) > > Actuallly, no. It is the latest release version. Complain to the devs > for not creating releases more often. > True, I stand corrected. I looked at the "wip" one first. -- Gergo Szakal <[EMAIL PROTECTED]> University Of Szeged, HU Faculty Of General Medicine /* Please do not CC me with replies, thank you. */
Re: DragonFly testing
On Thu, Feb 22, 2007 at 02:43:18AM +0100, Gergo Szakal wrote: > (I admit that mplayer in pkgsrc tree is quite outdated.) Actuallly, no. It is the latest release version. Complain to the devs for not creating releases more often. Joerg
Re: DragonFly testing
On Wed, 21 Feb 2007 20:14:11 -0600 (CST) "Jeremy C. Reed" <[EMAIL PROTECTED]> wrote: > The pkgsrc infrastructure is BSD licensed. The individual patches for > various software are generally just the same license as the software they > patch. > Then my guess was right. ;-) > pkgsrc does not prompt for build options like FreeBSD Ports. That's fine. I was a FreeBSD newbie and on a low-end machine I was installing Apache from ports (because ports and packages conflict there, and the prebuilt packages are...) I typed make install clean and left. After like 4 hours I returned and pulled my hair out seeing it was waiting for options. > For mplayer, you may want to send-pr it or turn in a bug report so it gets > updated in pkgsrc. Or a polite note to the MAINTAINER. I usually hit (and did that a few time already) the pkgsrc mailing lists when I have such problems. I don't care about mplayer since my desktop is Windows XP, and prefer VLC anyway. ;-) -- Gergo Szakal <[EMAIL PROTECTED]> University Of Szeged, HU Faculty Of General Medicine /* Please do not CC me with replies, thank you. */
Re: DragonFly testing
Ben Jolitz wrote: Petr Janda wrote: For your sound you need to load sound.ko + snd_ess.ko Best if you add snd_ess_load="YES" to /boot/loader.conf and in /dev you need to run sh MAKEDEV snd0 I think thats what has to be done. Petr I was under the impression that sound.ko was loaded by association, as kldstat said. I had not done a ./MAKEDEV snd0, but I suspect it will not work, since Dells are notorious for having standard equipment in non-standard locations. Will research some more on forcing discovery of Crystal WDM. -- Ben See if you put it /boot/loader.conf and run sh MAKEDEV snd0. Then post us your dmesg output. Petr
Re: DragonFly testing
Ben Jolitz wrote: I found the how to a little non specific. I do think that a getpkgsrc script would help set things up. There were no man pages (maybe install fubar'ed?) on pkgsrc, so unlike man ports, I could not get a man pkgsrc. Try 'man packages'. Sascha -- http://yoyodyne.ath.cx
Re: DragonFly testing
On Wed, 21 Feb 2007 19:47:04 -0800 Ben Jolitz <[EMAIL PROTECTED]> wrote: > I found the how to a little non specific. I do think that a getpkgsrc > script would help set things up. There were no man pages (maybe install > fubar'ed?) on pkgsrc, so unlike man ports, I could not get a man pkgsrc. Try man packages -- C:>WIN | Directable Mirror Arrays The computer obeys and wins.| A better way to focus the sun You lose and Bill collects. |licences available see |http://www.sohara.org/
Re: DragonFly testing
Regarding other parts of the log: as a freebsd-user, you should have had some basic idea on getting the pkgsrc tree and unpacking it (although I don't know what permits DF developers to include it on the CD, maybe licence? Or a /usr/sbin/getpkgsrc script would probably do as well.) I found the how to a little non specific. I do think that a getpkgsrc script would help set things up. There were no man pages (maybe install fubar'ed?) on pkgsrc, so unlike man ports, I could not get a man pkgsrc. It is much like the ports tree, expect the (very stupid) interactive setting of build options (this was one of the reasons I dropped freebsd). I have always considered the pkgsrc way of life quite straightforward, especially because I have FreeBSD and OpenBSD experience. Could you describe your pkgsrc problems more? (I admit that mplayer in pkgsrc tree is quite outdated.) I guess the problems lay in miscommunication, lack of documentation, and being 'new' to pkgsrc. I've only messed with ports and raw sources for most of my tenure with BSD.
Re: DragonFly testing
On Thu, 22 Feb 2007, Gergo Szakal wrote: > Regarding other parts of the log: as a freebsd-user, you should have had > some basic idea on getting the pkgsrc tree and unpacking it (although I > don't know what permits DF developers to include it on the CD, maybe > licence? The pkgsrc infrastructure is BSD licensed. The individual patches for various software are generally just the same license as the software they patch. > Or a /usr/sbin/getpkgsrc script would probably do as well.) It > is much like the ports tree, expect the (very stupid) interactive > setting of build options (this was one of the reasons I dropped > freebsd). pkgsrc does not prompt for build options like FreeBSD Ports. (But pkgsrc does have build options that can be customized. It is a lot more consistent that FreeBSD ports which are hit and miss on how to configure stuff.) > I have always considered the pkgsrc way of life quite > straightforward, especially because I have FreeBSD and OpenBSD > experience. Could you describe your pkgsrc problems more? > (I admit that mplayer in pkgsrc tree is quite outdated.) For mplayer, you may want to send-pr it or turn in a bug report so it gets updated in pkgsrc. Or a polite note to the MAINTAINER. Jeremy C. Reed
Re: DragonFly testing
On Thu, 22 Feb 2007 11:46:07 +1100 Petr Janda <[EMAIL PROTECTED]> wrote: > For your sound you need to load sound.ko + snd_ess.ko > > Best if you add snd_ess_load="YES" to /boot/loader.conf > > and in /dev you need to run sh MAKEDEV snd0 > Load snd_ess.ko only. It loads sound.ko as dependency. MAKEDEV was not necessary for me, however I had snd_ich. Regarding other parts of the log: as a freebsd-user, you should have had some basic idea on getting the pkgsrc tree and unpacking it (although I don't know what permits DF developers to include it on the CD, maybe licence? Or a /usr/sbin/getpkgsrc script would probably do as well.) It is much like the ports tree, expect the (very stupid) interactive setting of build options (this was one of the reasons I dropped freebsd). I have always considered the pkgsrc way of life quite straightforward, especially because I have FreeBSD and OpenBSD experience. Could you describe your pkgsrc problems more? (I admit that mplayer in pkgsrc tree is quite outdated.) -- Gergo Szakal <[EMAIL PROTECTED]> University Of Szeged, HU Faculty Of General Medicine /* Please do not CC me with replies, thank you. */
Re: DragonFly testing
Petr Janda wrote: For your sound you need to load sound.ko + snd_ess.ko Best if you add snd_ess_load="YES" to /boot/loader.conf and in /dev you need to run sh MAKEDEV snd0 I think thats what has to be done. Petr I was under the impression that sound.ko was loaded by association, as kldstat said. I had not done a ./MAKEDEV snd0, but I suspect it will not work, since Dells are notorious for having standard equipment in non-standard locations. Will research some more on forcing discovery of Crystal WDM. -- Ben
Re: DragonFly testing
Ben Jolitz wrote: Hi. I'd like to introduce myself. I am Ben Jolitz, technologist and student. Recently, I tried to run DragonFly on an old Dell Latitude CPi. I detailed my tries with DF. Perhaps after reading this log you might have some suggestions. The log is at: http://ben.telemuse.net/27 One of my biggest questions is how would I get audio running? Snd_ess loaded, and spat out one line of DMA information, but never initialized the device... Thanks, Ben Jolitz For your sound you need to load sound.ko + snd_ess.ko Best if you add snd_ess_load="YES" to /boot/loader.conf and in /dev you need to run sh MAKEDEV snd0 I think thats what has to be done. Petr
DragonFly testing
Hi. I'd like to introduce myself. I am Ben Jolitz, technologist and student. Recently, I tried to run DragonFly on an old Dell Latitude CPi. I detailed my tries with DF. Perhaps after reading this log you might have some suggestions. The log is at: http://ben.telemuse.net/27 One of my biggest questions is how would I get audio running? Snd_ess loaded, and spat out one line of DMA information, but never initialized the device... Thanks, Ben Jolitz
