missing AMQ usage in dummynet/ipfw man page for 12-alpha3
hi, I see the AMQ function is there but there is no usage info. And find this review marked accepted: Dummynet AQM usage documentation for ipfw man page ： https://reviews.freebsd.org/D12507 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
old top and new -current: missing arcstat sysctl
Hi, top reports missing sysctl kstat.zfs.misc.arcstats.other_size for 12.0-alpha3 with a top from an old-ish -current. Is/will this be handled via a compat-11 sysctl (my kernel is without compat-xx), or did this slip through? Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: beadm vs bectl
On 2018-08-27 14:50, Pete Wright wrote: > hi there - i have a zfs based system where /boot is on its own pool. > beadm seems happy enough with this setup but bectl errors out like so: > > $ sudo bectl list > / and /boot not on same device, quitting > $ > > $ beadm list > BE Active Mountpoint Space Created > default NR / 47.6G 2018-03-02 20:30 > snapshot_02262018 - - 1.5G 2018-03-03 14:38 > badresume_05122018 - - 4.4G 2018-05-12 19:45 > 11_2_beta - - 2.6G 2018-05-13 18:26 > resume_works - - 12.6G 2018-06-01 16:45 > $ > > reading the manpage for bectl it doesn't mention this being an issue. > so i guess i have two questions: > 1) is it a bad thing(tm) to have /boot on its own pool? > 2) assuming that having /boot on its own pool, why does bectl not work > with this configuration? > > thanks! > -pete > Your /boot being on a separate pool can never work, since you can't take a consistent snapshot of / and have it include your kernel (which is under /boot/kernel which is a separate pool) Do you know why you have 2 separate pools? If it was for GELI support, FreeBSD 12.0 will not require two separate pools anymore, and there will be migration instructions shortly. -- Allan Jude signature.asc Description: OpenPGP digital signature
beadm vs bectl
hi there - i have a zfs based system where /boot is on its own pool. beadm seems happy enough with this setup but bectl errors out like so: $ sudo bectl list / and /boot not on same device, quitting $ $ beadm list BE Active Mountpoint Space Created default NR / 47.6G 2018-03-02 20:30 snapshot_02262018 - - 1.5G 2018-03-03 14:38 badresume_05122018 - - 4.4G 2018-05-12 19:45 11_2_beta - - 2.6G 2018-05-13 18:26 resume_works - - 12.6G 2018-06-01 16:45 $ reading the manpage for bectl it doesn't mention this being an issue. so i guess i have two questions: 1) is it a bad thing(tm) to have /boot on its own pool? 2) assuming that having /boot on its own pool, why does bectl not work with this configuration? thanks! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm / drm2 removal in 12
Thanks for the drm-next efforts. I could not, and would not be using FreeBSD without it. Joe Maloney On Mon, Aug 27, 2018 at 5:58 AM Thomas Mueller wrote: > Excerpt from Oliver Pinter: > > > Let's do some more step backwards, and see how the graphics driver > > developments works from the corporation side. > > They not bother about any of the BSDs, they focus only to Windows and > > Linux. If you want to use a recent (haha recent, something after 2014) > you > > are forced to use new drivers from linux. > > The fore/advantage on the Linux side are the zillions of corporately paid > > kernel developers. > > They can just focus on a new hw supports, on freebsd side, there are no > > corporately paid drm driver developer. Sadly. > > In linux word their internal KPI (try a Google for a "stable API > nonsense" > > words) moves so fastly, that porting of these drivers gets non trivial > > without a dedicated paid team. > > > If you want to change on this situation, try to learn for you could help > or > > send directed donations to freebsd foundation. ;) > > Linux and FreeBSD are not the only open-source OSes. > > There is also (Net, Open, DragonFly)BSD, Haiku, OpenIndiana and others. > > Maybe better would be for the hardware manufacturers to release more > general specifications that could be adapted to any OS, by the NetBSD > developers, Haiku developers, etc. Certainly not to ignore Linux. > > Tom > > ___ > freebsd-sta...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm / drm2 removal in 12
blubee blubeeme wrote: On Sat, Aug 25, 2018 at 10:04 AM Mark Linimon wrote: On Sat, Aug 25, 2018 at 07:07:24AM +0800, blubee blubeeme wrote: Are these guys insane and please avoid the nonsense about you're doing this in your spare time. Let us know how whatever OS you wind up using instead works for you. I suggest you look for one that will put up with your constant harangues. There are very few people on the mailing lists as nasty and rude as yourself. It is tiresome, demotivating, and childish. Please go elsewhere. mcl Your opinion has been noted but this issue isn't about me. It's about the Graphics devs coding themselves into a corner and looking for an easy button so they can continue to feel good about their toy. There's a reason the changes they tried to force down the FreeBSD source tree was reverted; It does not meet any standards of quality. I have no inside knowledge other than my ability to think clearly and it's obvious that The FreeBSD team wanted to hint at them that their code doesn't pass the sniff test. Instead of being whiny brats improve your code and have it work without breaking compatibility with what has been working for quite a long time. Here's the play by play; You guys push this mess contaminating the FreeBSD source tree, some long standing user tries to update their machines and it blows up; 1) Most will just leave 2) Some will complain 2a) You guys will say; Read UPDATING. bleh bleh blen They'll get aggravated, thereby aggravating people who came to this platform for Stability. Users who actually use FreeBSD to get things done do not time to trawl these mailing lists, they have real world problems to solve with real world constraints. There are OS with kqueue and all those things it's called Linux; You can go there and play w/ that stuff to your hearts content. If you want your code to get merged, make sure it follows the guidelines and not break the systems for people who are already using the platform. Now, I understand hearing harsh criticism about your work might hurt your feelings and all but here's the antidote; work harder, improve your code, try again when your code quality improves. You guys cannot expect people to accept these kludges in their systems that they run everyday. It's an open source project, you can't get mad because your code isn't accepted, it's your jobs and engineers to do better not expect users to jump through hoops to accommodate your subpar attempts at coding. This isn't about me, it's about the quality of code that you guys are trying to submit. Not much to disagree with what you say here.. because that's why I no longer work on using FreeBSD instead having created my own fork which is something I can call stable, that can be patched for security issues and something that is usable across my environment. The one thing who you should be aware of and what I do disagree with you over is who you are speaking to ML is a long standing 'old hat' of FreeBSD and someone I respect and I know would not be putting 'kludges' and substandard code into the trees... Direct your anger elsewhere, whilst still making valid points. Regards, Michelle -- Michelle Sullivan http://www.mhix.org/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm / drm2 removal in 12
Excerpt from Oliver Pinter: > Let's do some more step backwards, and see how the graphics driver > developments works from the corporation side. > They not bother about any of the BSDs, they focus only to Windows and > Linux. If you want to use a recent (haha recent, something after 2014) you > are forced to use new drivers from linux. > The fore/advantage on the Linux side are the zillions of corporately paid > kernel developers. > They can just focus on a new hw supports, on freebsd side, there are no > corporately paid drm driver developer. Sadly. > In linux word their internal KPI (try a Google for a "stable API nonsense" > words) moves so fastly, that porting of these drivers gets non trivial > without a dedicated paid team. > If you want to change on this situation, try to learn for you could help or > send directed donations to freebsd foundation. ;) Linux and FreeBSD are not the only open-source OSes. There is also (Net, Open, DragonFly)BSD, Haiku, OpenIndiana and others. Maybe better would be for the hardware manufacturers to release more general specifications that could be adapted to any OS, by the NetBSD developers, Haiku developers, etc. Certainly not to ignore Linux. Tom ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
