Date: Fri, 23 Dec 2011 18:31:39 +0100 From: Roland Smith <rsmith@xs4all.nl> To: Da Rock <freebsd-questions@herveybayaustralia.com.au> Cc: freebsd-questions@freebsd.org Subject: Re: PolicyKit confusion Message-ID: <20111223173139.GA7648@slackbox.erewhon.net> In-Reply-To: <4EF49DDB.2060609@herveybayaustralia.com.au> References: <4EF4010B.5040704@herveybayaustralia.com.au> <20111223142252.GC660@slackbox.erewhon.net> <4EF49DDB.2060609@herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 24, 2011 at 01:27:23AM +1000, Da Rock wrote: > couldn't give a shit about network drives. One scenario is network goes= =20 > down and I get a screenful of error messages- it annoys the shit out of= =20 > me, let alone scaring illiterate users. If the network goes down, network drives won't work. Your users will be sad/scared/frustrated with or without error messages, I'm guessing. > > I don't think enough people care to make it really work under FreeBSD. = I've > > certainly never missed it. > They don't care too much under linux either.... So many years, yet not a= =20 > single user doc anywhere on any of the f***ing monsters! Goddamn linux=20 > devs- ever heard of KISS?! How about a user doc for something so bloody= =20 > confusing it takes a brain surgeon to figure it out? That's exactly why I've avoided using this stuff. :-) > Ahh, one more thing of note here: polkit-gnome-authorization would not=20 > work under any circumstances (run as root or otherwise) to change=20 > policies! WTF! > > You might take a look at devd(8) as a FreeBSD alternative, but I'm not = sure if > > it notices new da devices popping up. > > > Oh, believe me I'd happily jump on it rather than deal with this mess.=20 > But I can't find anything that will interact happily with the apps,=20 > mount network shares of all kinds, and be exceedingly user friendly=20 > (take note lin-devs: user-friendly !=3D sys_admin-hell at least it=20 > _doesn't have to_). Another way to go about it is to install e.g. ubuntu on a virtual machine a= nd peek under the hood how it works there. But as you say it's probably tied i= nto udev pretty tightly.=20 > How forgiving is devd to a user pulling the plug to early? I did look=20 > into it a bit, but it appeared nearly as difficult as deciphering the=20 > above scenario- that said, having come through the other side of that=20 > I'm not so sure my judgment was very accurate :) So now I might check=20 > that fork out and see... Devd just gets some notifications and acts on them. There is a problem with mounted usb devices, but that is one of architecture, I guess. Devd only ge= ts notified _after_ a device has been pulled. There is no way you can prevent data loss in all cases like that. On windows you're supposed to "prepare to eject" a USB device before pulling it out as well. The only "cure" is to mo= unt a device syncronously, and disable _all_ write caching for those devices. If you try that you'll find that doing so has significant performance impact a= nd not in a good way (disks are sloooow).=20 =20 > God! What a mess... this belongs in the X-files: the truth _is_ out=20 > there. But you might lose your head and many years of life just finding= =20 > the fragments! FreeBSD is on my personal desktop and laptop, but that seems to be the exception rather than the rule. Maybe you should write your experiences up = and submit it to the freebsd-doc mailing list for inclusion in the official doc= s? And talking about mailing lists, maybe you should try your luck on the freebsd-gnome list? [http://lists.freebsd.org/mailman/listinfo/freebsd-gnome]=20 Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --0F1p//8PRICkK4MW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk70uvsACgkQEnfvsMMhpyXZ9ACglwzAf8nLNykdfj4Wu6oPJHGk XjoAn1O5GWRvM+ONlKMRyAY91E01efNV =PeCp -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111223173139.GA7648>