On Mon, Mar 10, 2014 at 9:04 PM, Adrian Chadd <adr...@freebsd.org> wrote:
> Are you interested in just dumping all of the stuff you're discovering > into a blog, so it can be a journey? > > > -a > > On 10 March 2014 18:03, Joe Nosay <superbisq...@gmail.com> wrote: > > > > > > > > On Sat, Feb 8, 2014 at 5:26 AM, Joe Nosay <superbisq...@gmail.com> > wrote: > >> > >> I know that by reading the files in > >> webrtc_source/trunk/webrtc/modules/audio_device that a freebsd folder > needs > >> to be located there. The linux system shows control of the audio through > >> pulse and alsa . What should be located there are the files > referencing the > >> proper parts of system, phonon, gstreamer, esound, and others. If I > had a > >> nother computer with Linux on it, I would compare the references to the > >> files in trunk/build/webrtc/modules/audio_device/linux to what would be > the > >> equivalent on FreeBSD. The linux files would then be used as a > template to > >> create the freebsd ones. > >> What are the freebsd base system h files needed? Reference them at a new > >> folder. Which sound severs? Another reference. > >> > >> There is a command using find and grep to print out files which contain > an > >> exact phrase. I t is not " find /$PATH -exec grep -H -E -o "PATTERN" {} > \;" > >> > >> > >> > >> > >> > >> On Fri, Feb 7, 2014 at 8:41 PM, Joe Nosay <superbisq...@gmail.com> > wrote: > >>> > >>> > >>> > >>> > >>> On Fri, Feb 7, 2014 at 4:15 AM, CeDeROM <cede...@tlen.pl> wrote: > >>>> > >>>> Lets make wiki page on freebsd website and start a repository with the > >>>> code and make it happen :-) > >>>> > >>>> Please let me know if/how I can help :-) > >>>> > >>>> -- > >>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > >>> > >>> Okay, I need advice. I won't quit. Where and in what directory should I > >>> start. There is a build farm but it doesn't include FreeBSD. > >>> > >>> > >>> > >> > > > > > > What I have realized is that there needs to be an environment in which > > FreeBSD, Linux, and Google can share. > > My tutorial will be cleaned up. > > > > Here is what I have learned: > > 1. A Google FreeBSD environment can be created. > > 2. The filesystem must be ZFS. The architecture must be amd64/x86_64. The > > installations need to be CentOS and Debian on the FreeBSD Google > environment > > and the two Linux environments. > > 3. Emulation of the Linux systems will leave something to be desired. By > > comparing a build on a jailed Linux system to a bare metal Linux > install, > > we can see what needs to be done on FreeBSD. > > 4. The build environment allows the FreeBSD user to see how different > Linux > > distributions can be made to work together. E.g. What if the kernels > build > > faster in the Debian jail and the environments build faster in the CentOS > > jails? > > 5. Google and Linux developers will also have "native" environments while > > learning the layout and internals of FreeBSD. > > > > I had to realize that in order to deal with a Google project, one needs > to > > setup a Google environment. > > > > Okay, that is almost done. > > > > > Yes. That would be good. I need to setup blogger or what-have-you. Thanks for the idea. _______________________________________________ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"