drm.ko/radeon build stops with specialreg.h
FreeBSD SNAPSHOT-9 from people.freebsd.org/~nwhitehorn not ppc64. In the directories of /usr/src/sys/modules/drm/ and of /usr/src/sys/modules/drm/radeon the build breaks with specialeg.h not found. Using find -f /|grep specialreg.h only leaves me with /usr/src/sys/(x86-variant)/include/speialreg.h. At the same time, make complains of object directory not being changed. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Unable to compile drm.ko on powerpc
http://slexy.org/view/s2NSVy7aTU The build also fails looking for machine/specialreg.h. This file is only found on i386/amd64 processors. Drm.ko is needed by agp.ko. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
How do I change the default graphics card on a Powermac G4 Quicksilver?
The last email I sent stated that the drm kernel module could not be built because specialreg.h is an i386 only function. I am also aware that the agp module needs drm to run. Why did I ask for help? The PowerMac G4 Quicksilver has an agp graphics slot. I also know that OpenFirmware is related to OpenBoot. If the default graphics slot can be switched with OpenBoot, then why not with Open Firmware. The item I do not have is the diagnostic tool. If the drm module cannot be built for the machine in question, then what is the proper forth command for choosing a PCI slot over the agp one without frying the logic board. In the event that my request seems to be spam: 1) Whoever has the same machine can install the PowerPC snapshot 9.0 from Nathan Whitehorn's site. The proper howto is at the FreeBSD forums. 2) Try building the module from the 9.0 sources. The card is a radeon 200. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Unable to compile drm.ko on powerpc
My graphics port is agp and not pci. It's a Quicksilver 2002 with a 4x agp slot. Now, how do I make it work? That's the problem I've been recently asking about. Forgive me for bringing the next part here. The PowerPC snapshot 9 for the 32bit ppc needs updating. The ports tarball is behind. On 1/12/11, Nathan Whitehorn wrote: > On 01/12/11 02:39, Super Bisquit wrote: >> http://slexy.org/view/s2NSVy7aTU >> >> The build also fails looking for machine/specialreg.h. This file is only >> found on i386/amd64 processors. Drm.ko is needed by agp.ko. > > DRM is not required by AGP, rather the reverse, and DRM does not > presently work on powerpc. The AGP kernel module also doesn't provide > any useful features unless you are using DRM. You don't need either for > graphics on powerpc machines. > -Nathan > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Unable to compile drm.ko on powerpc
I see this > Identifier "Card0" > Driver "ati" > VendorName "ATI Technologies Inc" > BoardName "Rage 128 PR/PRO AGP 4x TMDS" > BusID "PCI:0:16:0" > > From the October 2008 ppc mailing list. Am I going to need to configure X with AGP 4X in the board name section? The Quicksilver will have a reinstallation with 9.0 snapshot with ports grabbed by csup or portsnap. I'll post the results and crashes on the proper mailing list. On this mailing list, I'd still like to know the open firmware commands for switching default graphic slots. On Thu, Jan 13, 2011 at 11:17 AM, Nathan Whitehorn wrote: > AGP is derived from PCI, so AGP devices show up on the PCI bus. All the AGP > kernel module does is provide hooks to manipulate some advanced features of > the bus, mostly for the benefit of drm. > -Nathan > > > On 01/12/11 19:24, Super Bisquit wrote: > >> My graphics port is agp and not pci. It's a Quicksilver 2002 with a >> 4x agp slot. >> Now, how do I make it work? That's the problem I've been recently asking >> about. >> Forgive me for bringing the next part here. >> The PowerPC snapshot 9 for the 32bit ppc needs updating. The ports >> tarball is behind. >> >> >> On 1/12/11, Nathan Whitehorn wrote: >> >>> On 01/12/11 02:39, Super Bisquit wrote: >>> >>>> http://slexy.org/view/s2NSVy7aTU >>>> >>>> The build also fails looking for machine/specialreg.h. This file is only >>>> found on i386/amd64 processors. Drm.ko is needed by agp.ko. >>>> >>> DRM is not required by AGP, rather the reverse, and DRM does not >>> presently work on powerpc. The AGP kernel module also doesn't provide >>> any useful features unless you are using DRM. You don't need either for >>> graphics on powerpc machines. >>> -Nathan >>> ___ >>> freebsd-hackers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to " >>> freebsd-hackers-unsubscr...@freebsd.org" >>> >>> ___ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org >> " >> > > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: New Boot-Loader
And what if I need to boot into single user mode?
On Mon, Mar 28, 2011 at 12:48 AM, Devin Teske wrote:
> Hi fellow hackers,
>
> I'm designing an open-sourced replacement boot-loader for FreeBSD. I feel
> that the existing options in the boot-loader menu today can be whittled down
> significantly with a stateful menu system rather than a single-action item
> menu system.
>
> In designing the new menu, I'd like to get your opinions. From old:
>
>FreeBSD 8.1-RELEASE: twitpic.com/4e485w
>
> to new:
>
>Replacement Boot-Loader: twitpic.com/4e46ol
>
> NOTE: The final release will have a single-user mode option.
>
> The new menu allows for more flexibility as selecting options 2 ("Boot
> Verbose") or 3 ("ACPI Support") independently toggles the status, updates
> the menu item, and redisplays the menu -- ever-waiting until the user
> ultimately presses ENTER, "1", or escapes to the prompt and types "boot".
> Thus, one could potentially launch single-user mode with verbosity on and
> ACPI disabled (if one so desired).
>
> In addition, I really tried to capture the essence of the new logo (spent
> months off-and-on using different conversion programs with different
> inputs). In the end, I found text-image.com produced the best result. I
> used the official freebsd.org/logo.html Standard Logo (black and white),
> cropped (to 122x123) and converted to jpeg with white background. I used an
> "Image Width" of 45 in their "Convert into ASCII" program available here:
> text-image.com/convert/ascii.html
>
> I would be distributing this as an installable package (perhaps in the
> ports tree if it gains popularity).
> --
> Cheers,
> Devin Teske
>
>
> -> LEGAL DISCLAIMER <-
> This message contains confidential and proprietary information
> of the sender, and is intended only for the person(s) to whom it
> is addressed. Any use, distribution, copying or disclosure by any
> other person is strictly prohibited. If you have received this
> message in error, please notify the e-mail sender immediately,
> and delete the original message without making a copy.
>
> -> FUN STUFF <-
> -BEGIN GEEK CODE BLOCK-
> Version 3.12
> GAT/CS/B/CC/E/IT/MC/M/MU/P/S/TW d+(++) s: a- C+++@$ UB$ P@$ L$
> E-
> W+++ N? o? K? w@ O M++$ V- PS+>++ PE@ Y+ PGP-> t(+) 5? X(+) R(-) tv+ b+>++
> DI+
> D+(++) G++ e> h r+++ z+++
> --END GEEK CODE BLOCK--
> http://www.geekcode.com/
>
> -> END TRANSMISSION <-
>
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: multi-boot bootstrap?
Now, how are you going to multiboot OpenBSD and NetBSD on a PowerPC machine
from the same hard disk. From what I know, one or the other can only be as
the first entry and it then has to be set from the forth prompt.
So, you will need two disks to boot , saya: OpenBSD, NetBSD, FreeBSD, Linux,
and MacOSX or a combination of these.
On PPC boxes with OpenFirmware 3.x, you actually need to set the active
partition if you want to boot Linux and/or freebsd from the forth prompt if
both are on the same disk.
You would need to reprogram the OpenBoot prompt on the UltraSPARC boxes.
No one on the FreeBSD hacker list does any forth programming. If such was
true, I would have had a few questions answered long ago.
On Mon, Mar 28, 2011 at 2:04 PM, wrote:
> The discussion of a new bootloader reminded me of the
> following problem:
>
> What we need more than a new bootloader is a new bootstrap.
> With MBR, NetBSD's boot selector MBR works reasonably well.
> (About as well as can be expected given the limited space available.)
> You get a menu of partitions ("slices" in FreeBSD-speak)
> and can enter a number to select which one you want to boot.
> If you don't enter anything it times out and boots the default.
> You can boot a different disk by pressing F1, F2, F3 ...
>
> example:
>Fn: diskn
>1: NBSD4.0
>2: NB5.0.1
>3: FBSD7.1
>4: FBSD8.2
>
> The menu labels are limited to 7 chars due to the limited space
> available in the MBR.
>
> But, disks larger than 2 GiB need to be GPT rather than MBR.
> I haven't found a bootstrap with similar functionality for GPT.
>
> GPT allows a larger bootstrap than MBR. So the bootstrap can
> be nicer. Firmware disk numbering is completely insane on some
> machines. So spare the poor user from having to guess which
> disk is which number today. Go through all the disks and look
> for bootable partitions. Extract the GPT partition labels for
> these partitions. Present a menu of choices.
>
> example:
>Enter the menu number for the partition you wish to boot.
>The default will automatically boot in 5 seconds.
>
>1: FreeBSD 7.1
>2: FreeBSD 8.2 (default)
>3: NetBSD 4.0
>4: NetBSD 5.0.1
>5: OpenBSD
>6: Plan 9
>7: reboot back to firmware
>
>Boot:
>
> As with the boot loader, this needs to work on all machines,
> and all terminals (without having termcap/terminfo), so just plain
> ASCII text, no graphics.
>
>
>
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
Go through the mailing lists. You can only boot 64bit on 64bit and 32bit on 32bit for FreeBSD. Debian needs to boot a 64bit kernel for 64bit machines. I made the reply because that is similar to the BTX bootloader. Let Baptiste get a powerpc machine and try using that bootloader, it won't work. It won't work on sparc (64/ultra), and it won't work on arm. On Mon, Mar 28, 2011 at 3:01 PM, Garrett Cooper wrote: > On Mon, Mar 28, 2011 at 11:22 AM, Super Bisquit > wrote: > > The ppc 32bit series does not boot directly into the boot loader prompt. > You > > have to: > > A) Hold logo+opt+o+f and then > >1) setenv boot-device hd# > >2) mac-boot > >3) Wait for the boot sequence to allow you to make interaction > >4) Hit the space bar and then type boot -s > > B) > > 1) Hold down the option key. > > 2) Wait, and choose the icon of harddisk. > > 3) Follow 3 and 4 above > > C) If you have more than one installation, set the current device you > want > > to be active from the OF prompt and then: > >1) Follow 3 and 4 from A above. > > > > Unless he is going to write that script in forth, you can count out both > > PowerPC(32 and 64) and UltraSPARC boxes. > > > > If you can get the BTX loader to work on the architectures I just > mentioned, > > let me know, because the rest of us can't. > > Huh? This seems way outside of what I was referring to. >The powerpc64 architecture does support 32-bit on 64-bit (biarch) > support. Whether or not it's supported in FreeBSD I don't remember. > Thanks, > -Garrett > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: multi-boot bootstrap?
On Mon, Mar 28, 2011 at 4:59 PM, wrote: > Now, how are you going to multiboot OpenBSD and NetBSD on a PowerPC >> > machine > >> from the same hard disk. >> > > I didn't say anything about a requirement for booting multiple OSes from the same disk. I said: Go through all the disks and look >> for bootable partitions. Extract the GPT partition labels for >> these partitions. Present a menu of choices. >> > Not that easy. > There can be multiple disks. (Assuming the hardware supports that.) > Openfirmware isn't BIOS. > I haven't worked with PowerPC machines and it has been a very long time > since I worked with Sparc. OpenFirmware is based on OpenBoot and both require forth programming. I had to reference Gentoo documentation because none of the hackers knew or knows how to change devices. By the way, SILO is the only Bootloader I know of that can multiboot on a sparc box. Linux emulation for sparc doesn't exist on freebsd, you'll be working on that yourself. > I'm more familiar with Alpha, which would take > some hacking to boot more than one OS per disk, but some rocket scientist > decided to drop FreeBSD support for Alpha, so I suspect that no one here > cares about Alpha. FreeBSD alpha needs to follow debian alpha: become a self sustaining project. > > > From what I know, one or the other can only be as >> the first entry and it then has to be set from the forth prompt. >> So, you will need two disks to boot , saya: OpenBSD, NetBSD, FreeBSD, >> > Linux, > >> and MacOSX or a combination of these. >> >> On PPC boxes with OpenFirmware 3.x, you actually need to set the >> > active > >> partition if you want to boot Linux and/or freebsd from the forth >> > prompt if > >> both are on the same disk. >> > > Can these PPC boxes boot from GPT disks? "active partition" sounds MBRish. > Perhaps they can use the "protective MBR" trick? Sorry, doesn't work like that. Linux does yaboot. FreeBSD does the bootloader Whitehorn wrote for it. OpenBSD either takes up the whole disk or you need to do a lot of hacking. NetBSD requires exact command lines to boot. Active partition on a ppc machine means that which you will boot from after the kernel is loaded. It boots from an hfs partition on which the bootloader has been dd'ed to. If you have more than one installation, you need need to set which ufs partiton is the active one by specifying on the command line. > > > > > > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > You're setup will be as such for a ppc machine: 1) Your bootloader on an hfs partition has to be the very first entry on each disk which is attached. 2) It will need to load Whitehorn's bootloader by using forth commands from the console. 3) Whitehorn's bootloader will need to be set from your bootloader to choose which ufs2 partition will load- in the event someone has more than one install. 4) Whitehorn's bootloader will need to be paused to allow module loading, single boot or an alternative kernel from the selected install. 5) This will need to be done for every boot. There are no slices on a ppc machine. There are partitions only. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
I'm just going to clarify a statement I made earlier on this thread in order to remove some possible misconceptions. One can only boot 32bit PPC on a 32bit PPC machines and have it work properly. The same applies for 64bit ppc machines. On Tue, Mar 29, 2011 at 8:11 AM, Julien Laffaye wrote: > On Tue, Mar 29, 2011 at 5:15 AM, Tim Kientzle > wrote: > > II. Package signing. > > That would be really nice. > >>> > >>> Right know we only planned to sign the repo database, so we can trust > >>> the sah256 of the packages stored in the database. Then if the package > >>> has the same sha256 as the one in the repo database it is considered > >>> trusted. > >>> If we want a per-package signing, we would have a tarball in a tarball. > >> > >> I really expected this to have been mentioned already, but this approach > (tarball in a tarball) is taken by Debian packages, and I don't remember > hearing of any issues related to it. I don't think it's worth discounting > from the start without giving some considerationg, but I will defer to the > people actually doing the work. > > > > If you use libarchive-style streaming, it's even > > pretty straightforward to read and extract such > > things without having to create a bunch of > > temporary files. > > > > You just need to be careful about compression. > > Agreed, if we dont want to verify the signature, we can extract the > tarball in the tarball efficiently. > > But to verify the signature, we have to read the tarball in the > tarball twice: the first time to compute the digest and verify the > signature, the second time to do the real extraction. > So I guess that the tarball containing the real package archive and > the signature should be uncompressed. The real package archive would > be compressed, though. > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: kernel dumps on powerpc/pmap questions
Why don't you ask Whitehorn or other members of the FreeBSD PowerPC team this question. Very few of the hackers deal with anything outside of standard i386 and AMD64 platforms. nwhiteh...@freebsd.org chmeeed...@gmail.com Justin Hibbits On 4/3/11, Andreas Tobler wrote: > Hello all, > > to investigate a system lockup I need to implement kerneldumps on > powerpc. Well, exactly on PowerMacs. The booke should already support > this feature. > > Right now I'm at the point where I can dump something, means the > mechanism to be able to get a (core) dump for example via 'call doadump' > in db works. I can restore the dump via savecore. > > I took the approach from booke and implemented the necessary functions > for PowerMacs. But here I'm offline. > > I do not understand what I want to dump, means which part of the memory. > Once I know what to dump, where do I find the information, which addresses? > > How can I get a picture of the memory organization form powermacs? > Is there a pointer available about pmap in the kernel to find out a bit > more on this topic? > > What is really needed to be able to run kgdb on a core file to be able > to find where the kernel crashed? > > I know the questions are a bit vague, but I need an entry point. > > I appreciate any pointer to implement this feature. > > Tia, > Andreas > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: kernel dumps on powerpc/pmap questions
Apologies; but, he can get more help from one of the two of you before he can get any from the FreeBSD hacker mailing list. On 4/3/11, Super Bisquit wrote: > Why don't you ask Whitehorn or other members of the FreeBSD PowerPC > team this question. Very few of the hackers deal with anything outside > of standard i386 and AMD64 platforms. > > nwhiteh...@freebsd.org > chmeeed...@gmail.com Justin Hibbits > > > > On 4/3/11, Andreas Tobler wrote: >> Hello all, >> >> to investigate a system lockup I need to implement kerneldumps on >> powerpc. Well, exactly on PowerMacs. The booke should already support >> this feature. >> >> Right now I'm at the point where I can dump something, means the >> mechanism to be able to get a (core) dump for example via 'call doadump' >> in db works. I can restore the dump via savecore. >> >> I took the approach from booke and implemented the necessary functions >> for PowerMacs. But here I'm offline. >> >> I do not understand what I want to dump, means which part of the memory. >> Once I know what to dump, where do I find the information, which >> addresses? >> >> How can I get a picture of the memory organization form powermacs? >> Is there a pointer available about pmap in the kernel to find out a bit >> more on this topic? >> >> What is really needed to be able to run kgdb on a core file to be able >> to find where the kernel crashed? >> >> I know the questions are a bit vague, but I need an entry point. >> >> I appreciate any pointer to implement this feature. >> >> Tia, >> Andreas >> ___ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to >> "freebsd-hackers-unsubscr...@freebsd.org" >> > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Bugzilla file reported. gnome developers want freebsd help
https://bugzilla.gnome.org/show_bug.cgi?id=648430 It doesn't seem that there was any before this willing to submit a bug report about networking. The gnome developers are willing to work with the freebsd project. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Bugzilla file reported. gnome developers want freebsd help
Let the individual know that the gnome developers are willing to work with him. For gnome desktop devel, here's the link and project: http://www.google-melange.com/gsoc/project/google/gsoc2011/kulakovad/4001 On 4/29/11, Andrey V. Elsukov wrote: > On 29.04.2011 23:30, Super Bisquit wrote: >> https://bugzilla.gnome.org/show_bug.cgi?id=648430 >> >> It doesn't seem that there was any before this willing to submit a bug >> report about networking. >> >> The gnome developers are willing to work with the freebsd project. > > Also there is approved GSoC Project "FreeBSD port of Network Manager", > so i think things may be changed soon. > > -- > WBR, Andrey V. Elsukov > > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: CUDA porting effort?
I'd be willing to try building it on the Power(PC) platform. On Wed, Feb 15, 2012 at 4:45 PM, Eric McCorkle wrote: > Given that NVidia is releasing the CUDA platform source on a limited > basis, is anyone actively working to port it to FreeBSD? The reason I > ask is that to get access to the source, you have to submit a request > explaining what you intend to use it for. It might be a good idea to > get ahold of the source on behalf of FreeBSD, so that interested people > could work on porting it. I could devote a small amount of time to such > an effort; I'm wondering if there's interest from anyone else. > > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD has serious problems with focus, longevity, and lifecycle
The individual maintainers of each architecture have the right to make a "PRE-RELEASE" of the system at any time. Come to think of it, anyone who can has that right- that is to make a pre-release. On 2/18/12, Mark Linimon wrote: > On Thu, Jan 26, 2012 at 09:45:47PM +1000, Da Rock wrote: >> 1. Incidentally, what exactly does constitute a major release? > > That point in time where we guarantee that we break a certain degree > of backwards compatibility. (Well, that's the key component. Feature- > additions ride on top of that.) > >> 2. Is there a reason to update the numbers so quickly? > > Yes, so that we don't have to keep supporting backwards compatibility > for as long a period (see 1) -- it's a significant burden to maintain. > It's necessary to do these as we rework things like network layers for > higher performance, rework wireless to work with modern devices, and > other high-demand items. > >> 3. Could a higher bar be set to reach a major release than simply >> temporal objectives? > > Yes. We did that with 5.x, and blew it big-time. The goal of "rewrite > the entire system to support SMP in a scalable, reliable fashion" was > simply too aggressive. It led to ~5 years between major releases, and by > that time the system had changed very dramatically (SMP, suspend/resume, > IIRC GEOM, and too many other things to list). It was a huge jump and > the learning curve for upgrading was way too large. We lost userbase. > > Also, keeping 5 years between major releases led to very high developer > frustration. Why work on something when it will take 4+ years to even > see the light of day? > > This is why we moved to the time-based releases. 18 months was seen as > a compromise between all the various demands. Even so, we are almost > exactly at 24 months in practice; see the graphs I updated last month as > a result of all the recent discussion: > > http://people.freebsd.org/~linimon/schedule/ > > My own view is that 5 years between major releases is not going to happen, > due to how painful the 5.x experience was for all concerned. But as I'm > not a src committer, I'm not one of the people who will be picking the > interval for our major-branch timeline. I just try to graph it as it > goes by. > > mcl > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Kernel memory usage
CPU architecture and model have a lot to do with performance. You will also get different results if you used qemu in place of VirtualBox. Qemu allows you to choose different emulated architectures, CPUs, and machine bases. What's the downside? You have to use the command line. Install qemu and run a series of virtual machines. Embedded devices also include Power(PC), ARMv?, Coldfire, et al; you're only dealing with i386 and/or the 64 bit extension (AMD64). CISC- which does not contain any hardware modification to be a RISC replacement- runs fewer instructions than RISC due to the limited number of registers. Take this into consideration every time a program runs. Everything else also matters on real and emulated systems: Is it ide, scsi, sdd, flashdevice for the hard drive? What type of RAM? Dedicated or shared disk? On 3/11/12, Da Rock <9phack...@herveybayaustralia.com.au> wrote: > I may be required to move this to embedded, but I am only looking for > generalisation. > > Recently a thread came up on questions regarding memory usage, and a > post was made regarding wired memory being nearly all kernel- something > I was ready to dispute, but then I thought I'd better make sure. > > So I tested a few theories first off: > > 1. Comparing memory usage across machines > > I checked servers and desktops as well as vm's for memory usage, and I > found some interesting results. On a firewall with no apps installed > only 35M wired is used, on a desktop up to 700M~ can be used. Even as a > dedicated server with a few services used it remains around 35M. > > Surely this means that the wired memory used is not just kernel? But I > held off my assumptions as it was still plausible that the structures > used by the kernel could balloon that far, too. > > 2. Stripped down, lean mean, kernel machine > > I then (using a vm I was building a kernel for anyway) stripped down a > kernel in a VBox VM using le drivers for network to see what could be > achieved. This is my kernel conf: > > include GENERIC > ident VPN > options IPSEC > options IPSEC_DEBUG > options IPSEC_NAT_T > device crypto > device enc > > # minimise kernel > nooptions UFS_GJOURNAL > nooptions MD_ROOT > nooptions NFSCL > nooptions NFSD > nooptions NFSLOCKD > nooptions NFS_ROOT > nooptions MSDOSFS > nooptions CD9660 > nooptions PROCFS > nooptions PSEUDOFS > nodevice fdc > nodevice mvs > nodevice siis > nodevice ahc > nodevice ahd > nodevice esp > nodevice hptiop > nodevice isp > nodevice mpt > nodevice mps > nodevice sym > nodevice trm > nodevice adv > nodevice adw > nodevice aic > nodevice bt > nodevice ses > nodevice amr > nodevice arcmsr > nodevice ciss > nodevice dpt > nodevice hptmv > nodevice hptrr > nodevice irr > nodevice ips > nodevice mly > nodevice twa > nodevice aac > nodevice aacp > nodevice ida > nodevice mfi > nodevice mlx > nodevice twe > nodevice tws > nodevice splash > nodevice cbb > nodevice pccard > nodevice cardbus > nodevice uart > nodevice ppc > nodevice ppbus > nodevice lpt > nodevice plip > nodevice ppi > nodevice puc > nodevice bxe > nodevice de > nodevice em > nodevice igb > nodevice ixgbe > nodevice ti > nodevice txp > nodevice vx > nodevice miibus > nodevice ae > nodevice age > nodevice alc > nodevice ale > nodevice bce > nodevice bfe > nodevice bge > nodevice dc > nodevice et > nodevice fxp > nodevice jme > nodevice lge > nodevice msk > nodevice nfe > nodevice nge > nodevice pcn > nodevice re > nodevice rl > nodevice sf > nodevice sge > nodevice sis > nodevice sk > nodevice ste > nodevice stge > nodevice tl > nodevice tx > nodevice vge > nodevice vr > nodevice wb > nodevice xl > nodevice cs > nodevice ed > nodevice ex > nodevice ep > nodevice fe > nodevice sn > nodevice xe > nodevice wlan > nooptions IEEE80211_DEBUG > nooptions IEEE80211_AMPDU_AGE > nooptions IEEE80211_SUPPORT_MESH > nodevice wlan_wep > nodevice wlan_ccmp > nodevice wlan_tkip > nodevice wlan_amrr > nodevice an > nodevice ath > nodevice ath_pci > nodevice ath_hal > nooptions AH_SUPPORT_AR5416 > nodevice ath_rate_sample > nodevice ipw > nodevice iwi > nodevice iwn > nodevice malo > nodevice mwl > nodevice ral > nodevice wi > nodevice wpi > nodevice md > nooption USB_DEBUG > nodevice uhci > nodevice ohci > nodevice ehci > nodevice xhci > nodevice usb > nodevice uhid > nodevice ukbd > nodevice ulpt > nodevice umass > nodevice ums > nodevice urio > nodevice u3g > nodevice uark > nodevice ubsa > nodevice uftdi > nodevice uipaq > nodevice uplcom > nodevice uslcom > nodevice uvisor > nodevice uvscom > nodevice aue > nodevice axe > nodevice cdce > nodevice cue > nodevice kue > nodevice rue > nodevice udav > nodevice rum > nodevice run > nodevice uath > nodevice upgt > nodevice ural > nodevice urtw > nodevice zyd > #nodevice firewire > nodevice fwe > nodevice fwip > #nodevice dcons > #nodevice dcons_rom > nodevice sound > nodevice snd_es137x > nodevice snd_hda > nodevice snd_ich > nodevice snd_uaudio > nodevice snd_via8233 > > World was also rebuilt as recommended by t
Re: will 9.2 be called 'diehard'? or maybe Naktomi?
"Energizer Bunny" is more threatening. On 3/13/12, Julian Elischer wrote: > > > http://modcult.org/read/2008/2/20/nakatomi-socrates-bsd-9-2 > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Exporting environment from Linux to FreeBSD
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=89377+0+archive/2008/freebsd-java/20080203.freebsd-java is the template given for me to follow. I have Debian running on an iMac G4 and FreeBSD running on a QuickSilver G4. 1. The assumption is that the script is ran on the iMac. Considering that SSH between both machines is set up, is the exporting: a) From the iMac to the QuickSilver. b) The inverse of the above. And c) Is it ran from the same terminal used for the SSH login d) Or from another terminal connected on the target to the SSHed login? If the exporting is done such as stated in d above, then how do I set that up properly? Also, does the shell type in the original environment need to match the shell of the target environment or is it an irrelevant point? I'm using the standard ssh user@ for logins. If the method to use is NFS with a and b being replaced with the NFS variables- being both server and client, then which similar method is the correct one? Is the script setup in /usr/share/java, /usr/lib/java, or both? Thanks. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD installers and future direction
Please don't turn this into an architecture dependent mess. PCBSD is i386 & AMD64 only. On Sat, May 25, 2013 at 9:01 PM, Dirk Engling wrote: > On 26.05.13 01:07, Nathan Whitehorn wrote: > > > I'm not aware of any movement there (on either side of the table). I'd > > personally be very suspicious of an all-sh(1) future -- by far the > > cleanest parts of bsdinstall are in C -- and this is especially true for > > interacting with geom. That said, since I've lost nearly all of my free > > time and ability to work on bsdinstall, I won't get in the way of anyone > > else working on things > > As discussed at BSDCan, I'd be willing to participate in the development > and at least implement setting up zpools/zfs and geli/gbde providers. I > have done similar things in sh in my ezjail tools and think I can glue > the rest together. > > Scanning through the pc-sysinstall code, I find nothing too fancy there > regarding either interaction with zfs nor geom tools. I do not think it > is necessary as a back end just for these features. > > Nathan, is there any design rationale available for the scripts, e.g. on > why you chose sh versus C and were you provided with some kind of wish > list/requirements in the first place? Any particular mail thread to scan > through beforehand? > > Regards, > > erdgeist > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD installers and future direction
May I- and others- see the hyperlink to the project, please? On Sat, May 25, 2013 at 11:45 PM, Teske, Devin wrote: > > On May 25, 2013, at 7:51 PM, Super Bisquit wrote: > > > Please don't turn this into an architecture dependent mess. PCBSD is > i386 & > > AMD64 only. > > > > There's a GSoC project (of which I'm potential mentor) to fix that. > > However, you are entirely right… we can't in all seriousness even think > about using pc-sysinstall until it is solid on all architectures as > bsdinstall already is. > > GSoC project is: "Making pc-sysinstall FreeBSD ready by porting it to > multiple architectures" > -- > Devin > > > > > > > On Sat, May 25, 2013 at 9:01 PM, Dirk Engling > wrote: > > > >> On 26.05.13 01:07, Nathan Whitehorn wrote: > >> > >>> I'm not aware of any movement there (on either side of the table). I'd > >>> personally be very suspicious of an all-sh(1) future -- by far the > >>> cleanest parts of bsdinstall are in C -- and this is especially true > for > >>> interacting with geom. That said, since I've lost nearly all of my free > >>> time and ability to work on bsdinstall, I won't get in the way of > anyone > >>> else working on things > >> > >> As discussed at BSDCan, I'd be willing to participate in the development > >> and at least implement setting up zpools/zfs and geli/gbde providers. I > >> have done similar things in sh in my ezjail tools and think I can glue > >> the rest together. > >> > >> Scanning through the pc-sysinstall code, I find nothing too fancy there > >> regarding either interaction with zfs nor geom tools. I do not think it > >> is necessary as a back end just for these features. > >> > >> Nathan, is there any design rationale available for the scripts, e.g. on > >> why you chose sh versus C and were you provided with some kind of wish > >> list/requirements in the first place? Any particular mail thread to scan > >> through beforehand? > >> > >> Regards, > >> > >> erdgeist > >> ___ > >> freebsd-hackers@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >> To unsubscribe, send any mail to " > freebsd-hackers-unsubscr...@freebsd.org" > >> > > ___ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to " > freebsd-hackers-unsubscr...@freebsd.org" > > _ > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete the > message and all copies; (ii) do not disclose, distribute or use the message > in any manner; and (iii) notify the sender immediately. In addition, please > be aware that any message addressed to our domain is subject to archiving > and review by persons other than the intended recipient. Thank you. > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD installers and future direction
In the case of firmware loaded systems, all of them aren't going to work with a single boot loader. On Tue, May 28, 2013 at 1:15 PM, Teske, Devin wrote: > > On May 28, 2013, at 8:54 AM, Alfred Perlstein wrote: > > On 5/28/13 7:49 AM, Nathan Whitehorn wrote: > On 05/27/13 23:36, Alfred Perlstein wrote: > On 5/27/13 6:53 PM, Nathan Whitehorn wrote: > On 05/27/13 20:40, Alfred Perlstein wrote: > On 5/27/13 2:23 PM, Bruce Cran wrote: > On 27/05/2013 21:28, Alfred Perlstein wrote: > On 5/27/13 11:40 AM, Bruce Cran wrote: > Yes. > Is this a joke? > > It probably /was/ too short a reply. Personally I think there should be a > single UI and scripting interface across all platforms. We should try and > get pc-sysinstall running on all of them first in case there's some problem > that means it can't be done, in which case we'd need to use a different > backend. > > > There are just going to be certain platforms that make it EASY to do cool > things. We should embrace that! That's why there are different platforms! > > Some are great for low power, others are great for graphics, cpu power, > gpu, networking etc. > > If we always go for the lowest common denominator then we are crippling > all the platforms for no one's benefit. Even if something CAN be done, if > it is very difficult, or just never happening, then we can't limit > everyone's experience based on the more difficult and/or resource strapped > platforms. > > It's just not good business. > > Yes, and all of this cuts both ways: pc-sysinstall has no wireless setup > support, for instance. Right now we support what we support because it is > the most feature-complete thing we have, not just on tier-2 platforms but > also on x86. > > To bring this discussion back to the ground, the fact is that we lack an > installer that has both internal support for ZFS and a UI. One of the > reasons for this is that making a good expressive UI for ZFS is a > non-trivial undertaking given its enormous flexibility. The bsdinstall > partition editor has been written to be extensible for this, and several > people have started writing code to do it, but no one ended up having time > to finish. Probably a reasonable thing to do is to start with supporting > only a minimal set of features. If anyone felt like actually writing this > code, I'm sure it would be appreciated by all and be more productive than > email exchanges. > -Nathan > > I'm sure if there was a list of reasonable things, such as wireless then > pc-sysinstall could be augmented. This is the first I've heard of that. > All the other complaints have been based on portability. > > Is that all that is required now, wireless? > > There are more, as well. A partial list of missing features on both sides > is here: https://wiki.freebsd.org/PCBSDInstallMerge. Other major ones are > IPv6 (maybe this has changed?) and no jail setup feature. Most of the > existing disk partitioning code in pc-sysinstall, which is the only thing > in a FreeBSD installer that is at all complicated, is also *extremely* > fragile and needs in all likelihood to be entirely replaced. The merge > effort stalled because of this kind of issue -- doing a "merge" rapidly > became rewriting both from scratch. > -Nathan > > Ah this is so cool. I'll bring it up with the PCBSD folks today. > > Thank you Nathan. > > > I had my own look at the pc-sysinstall and bsdinstall code and came to the > same conclusions, plus some. > > One of the biggest obstacles I see is actually a high-level issue that > I've self-identified through extensive work on bsdconfig (which is both a > back-end and a front-end). > > This is the issue of debugging and namespaces. > > I've sat down and made lists of other issues… but when I review, I find > these issues to be secondary to the above-stated larger issues. > > Concretely, I'm saying thus: > > + bsdinstall lacks debugging (debugging is different than logging; from > what I could see BSDINSTALL_LOG -- although utilized by both the sh(1) side > and the C side -- is only populated during an installation). The ability to > have the type of debugging that is in bsdconfig would greatly diminish the > amount of time developing important new features. > > + pc-sysinstall lacks debugging (similar situation… producing a log for > some action is not the same as being able to have debug statements for the > purpose of enhancement the program or troubleshooting an enhancement) > > + bsdinstall separates the backend functionality and the front-end > functionality into two separate namespaces (and in the case of C binaries, > a third namespace) > > + pc-sysinstall separates one backend into more than one namespace > > === > > To get an idea of the type of debugging I'm talking about, install > sysutils/bsdconfig from the ports tree or install it from a HEAD checkout > of base (it's in usr.sbin) and execute: > > bsdconfig -d > # produce debugging statements on stdout collated in realtime with the > dialog screens > > or > > bsdconf
Increasing the kernel hertz rate in 10.0, RELEASE, and CURRENT
At 2500 Hz, the tick rate increases by 1 Hz per cycle. There was mention of a patch that would allow the rate to be as high as 40k without this effect. --I'll post the link as soon as I find the mailing list thread-- Will this patch work with the current available releases? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Kern.hz= +1 hertz at anything 2500 and above.
http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051789.html This is the thread that I was referring to earlier. Since the patch is for 2009, what are the chances it would work with 10.x or 9.x? On PowerPC machines with a low MHz rate- or any machine with a CPU rate of 800 MHz or less- increasing the kern.hz improves performance and cuts down on latency. I am building audio applications and suites that are used in different projects. A G3 based machine should be able to run a kernel with kern.hz=5000 with no problem. Unfortunately, this cannot be done. @PowerPC: some of you may find that performance does increase at a higher kern.hz rate. @Hackers & Current: What's the chance that the default rate limit can be raised to 5k? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Kern.hz= +1 hertz at anything 2500 and above.
When I started with FreeBSD on a G3 B&W, I noticed that the performance improved with a higher kern.hz rating. Unless the future holds an emu20k2, there will be RAM used from the motherboard. 1. I will need a real-time or a faster kernel- hence the high rate wanted- because the devices to be built will be used in an active environment: art, music, audio control. 2. Any system with limited memory and a low CPU hertz rate benefits from the higher kern.hz setting. 3. Why not? If it works for PowerPC, SPARC64, AMD64, and i386 then it may work for other architectures. 4. Some applications may be ran from within a jail. On Wed, Jul 24, 2013 at 8:16 PM, Adrian Chadd wrote: > Well, why is it reducing latency? That's the thing you should investigate. > > Is it because processes aren't getting enough time? or too much time? > Or the audio device isn't getting enough time to run? etc. > > > > -adrian > > On 24 July 2013 15:35, Super Bisquit wrote: > > > http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051789.html > > > > This is the thread that I was referring to earlier. Since the patch is > for > > 2009, what are the chances it would work with 10.x or 9.x? > > > > On PowerPC machines with a low MHz rate- or any machine with a CPU rate > of > > 800 MHz or less- increasing the kern.hz improves performance and cuts > down > > on latency. I am building audio applications and suites that are used in > > different projects. A G3 based machine should be able to run a kernel > with > > kern.hz=5000 with no problem. Unfortunately, this cannot be done. > > > > @PowerPC: some of you may find that performance does increase at a higher > > kern.hz rate. > > > > @Hackers & Current: What's the chance that the default rate limit can be > > raised to 5k? > > ___ > > freebsd-...@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > > To unsubscribe, send any mail to "freebsd-ppc-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Kern.hz= +1 hertz at anything 2500 and above.
I haven't done much messing with scheduling. It is set at the default ULE for this machine. On Thu, Jul 25, 2013 at 12:11 PM, Adrian Chadd wrote: > On 25 July 2013 02:51, Wojciech Puchar > wrote: > >> improved with a higher kern.hz rating. Unless the future holds an > emu20k2, > >> there will be RAM used from the motherboard. > >> 1. I will need a real-time or a faster kernel- hence the high rate > wanted- > >> because the devices to be built will be used in an active environment: > >> art, > >> music, audio control. > >> 2. Any system with limited memory and a low CPU hertz rate benefits from > >> the higher kern.hz setting. > > > rather opposite. more kern.hz=more interrupts. > > Right. > > More hz == more interrupts and less ability for a CPU-bound process to > chew all the CPU. > > So is it a scheduling issue, where you have multiple CPU bound > userland processes that aren't being fair and consuming all the CPU? > Is it that your device driver(s) aren't interrupting correctly, > relying on the hz tick to make up the slack, etc. > > Is it a busted halt loop, which is being papered over with hz ticks? > > Have you tried -10 on that kit, with the more aggressive clock/timer > code that won't interrupt unless it needs to? Has that changed things? > > > > -adrian > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: I am frustrated
Calm down for a minute. There are people who work with embedded systems on the different mailing lists. Think about things first. You were given some suggestions in that thread. The problem is convincing the embedded market and not those who maintain FreeBSD. You need the hardware along with the software to do your project. What systems and architectures will be your focus? The other projects started with someone who took time and tried. If you start on what you want while allowing others to be able to join in, you may get more help. Adrian mentioned the MIPS kernel to you in that thread. The raspberry Pi /ARM port could use some help. Even the PPC and standard ports could use that help; but, you need to test what you build. Amit, the project takes a lot of people who work constantly on making the system stable. Making an ultimatum will not have the effect that you so desire. Have you asked if anyone is willing to teach you more about the kernel internals? Have you looked at all of the code? Take a breath and start over. On Sat, Aug 3, 2013 at 6:14 AM, Amit Rawat wrote: > Hi, > > I am Amit Rawat. Here is the link to my two proposal which I submitted in > two consecutive year > 1. > > https://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/amitrawat10/1#c8001 > > 2. > > https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/amitrawat10/12001 > > But I didn't get selected. I posted the mail in freebsd hackers as per the > instruction > > http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042411.html > > and what I propose is based on the fact given by the people of freebsd. I > spent one year on working in freebsd. I remain most of the time in the irc > channel #freebsd-soc and #bsdmisp. I maintain the blog > > https://amit10rawat.wordpress.com/ > > as per suggested by the google. I follow all the mailing list. > > Now I don't know why I didn't get selected and How many times I need to > apply to get selected. Now I am confused what to do to get selected to > freebsd.. It is total waste of time and energy and every time they give > lame excuses to me. I tried hard to attach to this community but it is > really disappointing and frustrating. When I see the result I found that > some of them never came to IRC or even tried to post anything on freebsd > mailing list. I am questioning the selection procedure of freebsd. I have > no faith in it. > > I have few questions > > 1. FreeBSD FUSE* *has been allotted two slots before and third this time. > One project with three slot. > > > 2. Port GlusterFS to FreeBSD how it can be completed since it depends on > FUSE as written by the project submitter. But FUSE is still not ported. > > 3. What is the relation b/w capsicum and FreeBSD ? and Why capsicum project > are put in freebsd slots ? > > The management of project is disaster. If my project is not so worth people > should have said it before. I would have applied to some other community > which care about the people who want to join the community. > > Regards, > > Amit Rawat > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: ps_strings
http://forums.freebsd.org/showthread.php?p=228128 http://www.dolphinburger.com/cgi-bin/bsdi-man?proto=1.1&query=ps_strings&msection=5&apropos=0 On Sat, Aug 17, 2013 at 2:00 PM, Carlos Jacobo Puga Medina < cjpug...@gmail.com> wrote: > Hi people, > > Despite I made a request not long ago[1], I'm looking for documentation to > create the ps_strings structure man page because isn't covered in other man > page such e.g. execve(2). So, I'm interested to know for what it's > currently used. > > Any input will be appreciated. > > --CJPM > > > [1] http://lists.freebsd.org/pipermail/freebsd-doc/2013-July/022422.html. > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
mpx on laptop produces pointer but does not show usb mouse
Says right there. http://alec.mooo.com/mpx.html Followed the instructions in the link. Second part will have more info. Thanks much and apologies. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
