set, so didn't get pie
with the initial gcc6 emerge and @world rebuild, but I was persuaded by
the discussion here to try it, second global rebuild, and so far it
works. So both because it's supposed to be safer and because I don't
want to do now a /third/ global rebuild, I stron
masked/forced for all
> packages in use.{mask,force}, then you would add a line like "-foo" to
> the use.{mask,force} file in /etc/portage/profile/.
Thanks. As I said I doubt I'm the only one who will find this useful.
=:^)
--
Duncan - List replies preferred. No HTML msgs.
&
w in a year (and
I'd argue something shorter, say 90 days, which just emphasizes how old
those bugs really are), where's the justification to bother migrating
them to the new workflow? They should have been acted upon well before
the new workflow came to be, and if people are bothering to
magine they could
similarly treat it to the way they do masked flags today. After all,
it's simply another method of masking, only in this case it's dynamic, by
the PM at solve time.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
makes the latter case relatively easy compared to some
distros. I did it with kde twice, when gentoo/kde wasn't supporting
builds without semantic-desktop. =:^)
And in this case it appears there's even someone already doing it and
making their work public via the lua overlay. =
William Hubbs posted on Sun, 02 Jul 2017 10:30:12 -0500 as excerpted:
> On Sun, Jul 02, 2017 at 03:55:54AM +0000, Duncan wrote:
>> William Hubbs posted on Sat, 01 Jul 2017 11:53:59 -0500 as excerpted:
>>
>> > See this article for why using liblua as a shared library
fter the upstream public vulnerability
and patch and/or unaffected release announcements, because that's what it
took to stabilize the patched version on some platform or other that was
holding up the glsa.
Automating stabilization and automated keyword dropping on timeouts seems
the only other pract
ng git/repository has been using git/
Second: s/Most of the developers/Most developers/
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
specification apply to
> the master branch only. The development branches can use relaxed rules.
Can/may... There may be other uses I won't mention but if you decide
it's worth changing at all, a search and evaluate usage may be worth it.
> Rewriting history (i.e. force pushes) of the master branch is forbidden.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
it commit ''preceding'' the
> bump.
> * When doing a minor change to a large number of packages, it is
> reasonable to do so in a single commit. However, when doing a major
> change (e.g. a version bump), it is better to split commits on package
> boundaries.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
usly is meaningless (they are redundant), and using the former
> has no advantages over using the classic #nn form in the
> summary or the body.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
retroactively is the OpenPGP
> signing. However, it has been an obligatory requirement enforced by the
> infrastructure since the git switch. Therefore, all the git history
> conforms to that.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
know it to be a practical impossibility, because were we to do so,
instead of freeing that time to work on what's now ~arch, we'd simply
lose most of the volunteers who have a major interest in stable.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
d have to ask
them if it's "painful" for them.
So it's certainly doable, maintainable over years and major changes, and
consumable, as gentoo/kde devs and their users have been and continues to
demonstrate. =:^) The /big/ question then is only whether that model's
act
Rich Freeman posted on Mon, 31 Jul 2017 20:55:05 -0400 as excerpted:
> On Mon, Jul 31, 2017 at 8:24 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>> Rich Freeman posted on Mon, 31 Jul 2017 11:11:24 -0400 as excerpted:
>>
>>> On Mon, Jul 31, 2017 at 10:52 AM, Alec Warn
w code, thus the "(apparently)" above, but
perhaps it's acting differently now due to the recent migration away from
eblits? What I know for sure is that the upgrade broke my system until I
manually copied the libm binary from the binpkg back into place.
--
Duncan - List replies prefer
untime-only dep of
kde-frameworks/solid, used for functionality I don't want/need anyway, so
I null-pkg it with an overlay version that has no deps and installs no
files.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
t might be worth a bit of extra care while fixing the one to
keep in mind the other so as not to further complicate fixing it, is all.
(I'll be working on my bug either late today/Friday or Saturday.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord
or ~arch)
keyword.
So the version bump is effectively mandatory due to security overrides in
any case, and that it was fixed by a temporary USE flag drop doesn't
change things at all. If that security-override isn't explicit in
current documentation, that'd be the bug, not the fa
er, reveal an angle I hadn't previously considered,
sometimes changing my mind entirely. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
M. J. Everitt posted on Sun, 13 Aug 2017 11:18:09 +0100 as excerpted:
> On 13/08/17 11:11, Michael Orlitzky wrote:
>> On 08/12/2017 10:52 PM, Duncan wrote:
>>> How so? Are you arguing that deciding to system-wide switch to/from
>>> pulseaudio, systemd, or gstrea
t;plus", if "in addition to" makes it too long...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
er and I wanted to be sure, likely unneeded these days) and smart-
live-rebuild of my (live) kde packages.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
Francisco Blas Izquierdo Riera (klondike) posted on Wed, 16 Aug 2017
12:09:57 +0200 as excerpted:
> s you may know the core of sys-kernel/hardened-sources have been the
> grsecuirty patches.
New typo: s/grsecuirty/grsecurity/
--
Duncan - List replies preferred. No HTML msgs.
"Ev
Duncan posted on Sun, 13 Aug 2017 02:52:58 + as excerpted:
> Michael Orlitzky posted on Sat, 12 Aug 2017 05:58:41 -0400 as excerpted:
>
>> On 08/12/2017 04:39 AM, Paweł Hajdan, Jr. wrote:
>>
>>> There are use-cases for --changed-use / --newuse other than changed
&
l r success saved_umask
> + local success saved_umask
> if [[ ${EVCS_UMASK} ]]; then
> saved_umask=$(umask)
> umask "${EVCS_UMASK}" || die "Bad options to umask:
> ${EVCS_UMASK}"
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
ge.
[Just my contribution to the shed color debate. =:^P ]
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
nd now unsupported versions in the tree when they're
guaranteed to be increasingly vulnerable to new attacks is simply
irresponsible, with no logical argument that can be made otherwise, thus
the removal.
Were it any other package, with any other primary purpose... but it's not.
-
but I'm just used to seeing it require the
** accept_keyword thing). So I'm just wondering what reason you
might have had to do it this way instead.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
act there. You also need to contact the proxy-maintainer
project to initiate that angle. There's further details and additional
resources on the linked page, above.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
URITY_HOLE (the ALL CAPS
helps distinguish it too, since most USE flags are lowercase) in the
name, say as ...
nrpe-command-args-SECURITY-HOLE
or just
nrpe-GAPING-SECURITY-HOLE
... seems to me the most effective. Anyone that would even *think* to
enable something like that without doing
xer if kmix isn't working
(I'm on live-git-kde after all) or is "working" but I'm not getting
the expected results or I simply want a different visual presentation.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
Kent Fredric posted on Tue, 29 Aug 2017 21:21:09 +1200 as excerpted:
> On Thu, 24 Aug 2017 03:06:13 + (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
>
>> nrpe-command-args-SECURITY-HOLE or just nrpe-GAPING-SECURITY-HOLE
>
> That's probably excessive, if you
at became of it. Perhaps gui-*
category names if that's actually moving forward, in ordered to maintain
a bit of consistency and for lack of a better idea?
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
d look today, due to
mobile, wearables, and possibly ultimately injectibles.
> IDK.
>
> I'm not committed to anything I've said here, just food for thought.
Same here. My biggest concern is simply avoiding, if possible, setting
up new categories now, only to have to redo
does, here (tho I already see a reply from someone else with the
opposite reaction, favoring desktop-* over ux-*).
---
[1] Dosbox game: Master of Orion, original, (c) 1993 updated copy.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
tive than some.
Meanwhile, it's certainly nice to see messages with more respect than may
sometimes be seen in this list. Thanks. But don't be afraid to post
your user's opinion just because it differs from someone else's opinion.
Your opinion is valuable too, even if
h "X Windows Systems"
> providing "X User Interfaces", despite the underlying protocols being
> different?
Warnock agree?
(Tho posting makes it no longer warnock.) Thanks for the warnock
reference[1], BTW. I knew of the problem but had no name for it, so you
broad
ble
to lean on CAs, it should hopefully at least resist the trivial stuff
like insecure wifi and ISP content-insertion games.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
ase is perfectly covered by https://xkcd.com/927/ :)
Well, I'd argue the case for "not 'perfectly'", because for better or for
worse, systemd has had rather more luck at cross-distro init-system
unification than that comic suggests. There's still special-cases
lags I actually want/need, so whatever
USE is pulling it in obviously isn't something I wanted or found I needed
due to required-deps or something, here.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
Andreas K. Huettel posted on Tue, 19 Sep 2017 14:53:20 +0200 as excerpted:
> Am Dienstag, 19. September 2017, 07:06:24 CEST schrieb Duncan:
>> Andreas K. Huettel posted on Mon, 18 Sep 2017 11:56:30 +0200 as
>> excerpted:
>> > It may not always be obvious where this is nee
package providing "service" that was for some reason a
dep, I'd strongly consider creating for myself an empty virtual to
provide it, just as I've done for a number of other packages that aren't
actually required to build or run the commands I /do/ want to run.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
Harald Weiner posted on Fri, 29 Sep 2017 04:47:35 +0200 as excerpted:
> Duncan posted on 09/29/17 2:08 AM as excerpted:
>
>> Or are we going to replace rm, and fdisk, and gdisk, and cfdisk, and
>> cgdisk, and who knows how many other binaries, with "safe"
>
ort the
scheme or not, what sort of detection they do if they support it, and how
they translate the passed parameters if necessary, and bugs in how they
do any of it become the bugs of that initsystem.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
ey've already crossed
with the gcc upgrade?
Either way, making the answer to that explicit should be useful, avoiding
either an unnecessary full rebuild, or avoiding the problems because the
news item wasn't clear and people already on gcc-6.4+ thought the
procedure didn't
Andreas K. Huettel posted on Tue, 10 Oct 2017 21:02:32 +0200 as excerpted:
> Am Dienstag, 10. Oktober 2017, 04:10:13 CEST schrieb Duncan:
>
>> One thing isn't clear here. Is this sequence necessary due to the
>> profile switch itself, because the /profile/ enables PIE
er the last arch
stabilizes gcc-6.4+, with the goal for the gcc stabilization being the
end of 2017, meaning 13.0 profile removal is planned for the end of 2018
if all archs meet their gcc-6.4+ stabilization goal."
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree
Duncan posted on Wed, 11 Oct 2017 03:31:55 + as excerpted:
> Andreas K. Huettel posted on Tue, 10 Oct 2017 21:02:32 +0200 as
> excerpted:
>
>> Switching the profile changes the settings for building gcc (it
>> switches a use-flag from forced-off to forced-on). A gcc-6 b
expensive or deal with it manually if the lower backtrack didn't
propose a satisfactory solution.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
tall is up and running, is
going to be easier.
So 7.5 months does seem reasonable, to me at least. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
Kent Fredric posted on Sun, 15 Oct 2017 06:36:34 +1300 as excerpted:
> On Thu, 12 Oct 2017 07:50:38 + (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
>
>> Wow. How'd you ever get a backlog of 400 packages in your depclean
>> list,
>> including critical o
ng to work,
with the intent being that it'll be done when I get back to it.
So the hash verification time really does matter, even if it's minutes
compared to hours of actual build time, because that's time I'm actively
waiting for it, vs. letting it do its thing in the ba
any good admin I try to follow the security news especially
where it touches machines I administer, so I'm following this thread with
particular interest.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
its value, when I needed to
bisect a package the first time.
So a variant without the repo OR package name would be my wish, here.
> 2. The overrides weren't suitable for packages checking out multiple
> repositories (LLVM, wine, glibc).
Valid point there!
--
Duncan - List replies p
p the last sentence to read a bit smoother
(I skipped formatting)...
While there is no hard restriction on the length of short-name,
limiting it to 20 characters is strongly recommended.
(s/for/on/, reversing order of the limit and strongly recommended.)
--
Duncan - List replies preferred. No HT
ting was to point out that it's
not as simple as just dropping stable, not really to provide an answer I
don't have), but can note that I believe there's two people now
volunteered for it, and of course people have to be aware of it before
they can realize their personal stake a
lly track separate lib locations once again.
So I'll probably keep my merged lib here, managing it much like I do my
merged bin and root/usr, but it'd be nice to know whether that's going to
remain an official layout or not, and if not, what the timeframe for
removing it is.
-
Mike Gilbert posted on Thu, 21 Dec 2017 09:10:09 -0500 as excerpted:
> On Thu, Dec 21, 2017 at 2:44 AM, Matthew Thode
> wrote:
>> On 17-12-21 08:34:31, Michał Górny wrote:
>>> W dniu czw, 21.12.2017 o godzinie 05∶29 +0000, użytkownik Duncan
>>> napisał:
>>&g
up running live-git, because each
release lists the bugs fixed and I can and do at least review their one-
line summaries every time I update. Between that and following the
patches as they're posted for review in portage-dev (so the release-time
bug list is primarily review), I'm ef
-
>
> Title: systemd sysv-utils blocker resolution
+1
The news item reads very clearly to me. =:^)
Thanks especially for explicitly including the list of symlinks and that
sysvinit otherwise provides those files, as well as the explicitly
suggested equery depends line for those who need it.
agreed, all that would remain to debate
would be whether 548 days (365*1.5 rounded up) is appropriate. The
precise config file path, name and format would be up to the implementer
and/or eselect news module maintainer.
* Other news readers could of course set and ship their own default
expiry, if desired.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
nless you simply want to be extra nice, because if nothing else they can
just grab a copy before the change and if they can't even do /that/ in a
month... . Beyond that and the old version can always be dug out of git
if necessary.)
Either way, thanks for the cleanup. =:^)
--
Duncan - Lis
packages supporting it) I have still depending on qt4, so a timetable as
to qt4 removal giving me some idea how long I have to find, install and
configure an alternative, and an idea where I'll be looking for it if I
don't get that conversion done by then, would be very useful.
--
Duncan -
il has made one of the hard calls they're elected to make,
for which tho I may be worried I can't fault them, and now we get to see
how it all plays out. But whether they, and gentoo as a whole, wins that
effective wager, or loses it, the bet has now been placed, so nothing to
do but wait and see the results. =:^/
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
s a prime example of
that. I honestly don't know which is worse, but the obvious ideal is a
sane upstream that doesn't veer to either extreme, or lacking that, at
least cooperates and provides support when a new at least /semi-/stable
release is needed as the old is just outdated and
ing and/or mounts to handle the non-identical stuff, so
simply toggling a symlink lets you switch machine layouts), or if the
machines have enough memory, setting up a single thumb drive to boot and
put everything in a tmpfs for the machine to run from, so you can use the
same thumb drive to b
iggered rebuild when gentoo/kde revbumps after dep-bumping to
reflect what upstream already did, won't be /that/ much different or
/that/ much more work. Only now I guess I'll be seeing it in --rX
revbumps, too.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
Michael Orlitzky posted on Mon, 22 Jan 2018 10:04:30 -0500 as excerpted:
> On 01/22/2018 05:10 AM, Duncan wrote:
>>>>
>>>> If the dependencies are to remain in the eclasses, then the eclasses
>>>> should get a new revision when those dependencies change
sync users can ignore,
or how they can get gpg signature verification as well if its possible.
(Sufficient to just link it if it's more involved than a single
paragraph, since this is primarily for rsync users.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program
nt was to ensure that Zynot couldn't take it private,
while Gentoo/DRobbins could, especially since at the time copyright was
assigned to Gentoo. Of course now we have the advantage of looking back
it it in history and can see how things turned out, but back then, it was
far less clea
more detail than I remembered or would write it again here.
(I had more written but deleted it as OT.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
perfectly addresses the question I
had about the original. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
using git or other methods are not affected, and
verification for them will be provided in the future.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
cases to test...
So bother sending the results in (you're ready for it already), or you
want them, but wait until you've adjusted the script to deal with it, or
don't bother, you're not going to try supporting anything that unusual
anyway?
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
WHAT YOU ARE DOING AND CAN
> HELP WITH TESTING.
What about "reverse" usrmerge as above? Flag on or not? Maybe I just
turn it on (obviously after updating my backups) to help test?
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
e hint at what might be needed.
("... Refreshing your backups before the upgrade and checking site-
specific solutions after the upgrade before reboot, is recommended.")
Because it's a system-critical package this becomes even more important.
(And FWIW, getting a longer heads-up
NSTALL_MASK, but
having it pointed at a tmpfs instead lets me examine what's actually
installed, if necessary.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
ime to get it,
prioritized high enough based on the severity of the problem to actually
do something about it.
So the problem remains...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
ing like this
(but might be too long, do those news item short title limits
still apply?):
Title: Portage rsync-verify feature not yet stable-keyworded
Perhaps omit the -keyworded if that's too long:
Title: Portage rsync-verify feature not yet stable
Feel free to revise further...
--
D
gation from others, as I'm not entirely sure I'm recalling that warning
post correctly. It might have been for other than github, or I might
have misunderstood, or maybe they've fixed that problem by now, or...
--
Duncan - List replies preferred. No HTML msgs.
"Every
ges
it's acceptable as-is.
Thanks. You put an awful lot of work into portage, and I'm sure I'm not
the only one who's thankful there's a steady hand at the portage wheel,
even if it doesn't always come thru. Your efforts certainly make the
gentoo experience a better o
do/ consider myself a
guest on this list, and arguably, posting to it has /always/ been a
privilege, not a right. And given the coming whitelisting, devs, thru
their elected council, have clearly expressed their desire to cut down
the outside noise from "guests", ensuring that any such
les I can't see, so I /can/ see them, as it is
about attempting to convince anyone of the correctness of my viewpoint as
I'm posting it. Sure I could be wrong, but if I am, please point it out
so I can see it too! =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
versions of the
> x11-proto/ packages to ease the transition.
I noticed that I didn't need many of the protos any longer here too, and
figured it was a recombining. Thanks for the confirmation. =:^)
And thanks for the roadmap to what's ahead re X. =:^)
--
Duncan - List replies
error for the generic *) catchall case. The error is then clearer if someone
typos EAPI=67 or the like.
+ 0|1|2|3|4|5|6) ;;
+ 7) die "${ECLASS}: EAPI=${EAPI} includes all functions from this
eclass" ;;
+ *) die "${ECLASS}: EAPI=${EAPI} Unknown" ;;
--
Duncan - Li
fficial tree.
Tho perhaps that can be reevaluated. But while there's more connectivity
now than over a decade ago when that policy was created, I expect there's
still those paying by the meg or gig for net access locally, that won't
enjoy having their sneakernet sync routine disrupted.
; 'forever'.
Test defensively. We're not just talking EAPI=8, etc, here. What
happens if someone typos EAPI=56 or some such? Positively support what
you recognize. If it's unrecognized, it should always fall thru to an
error saying it's unsupported. Much easier
Justin Lecher posted on Mon, 01 Feb 2016 12:08:32 +0100 as excerpted:
[Title/description only comment, body quote snipped]
What about eclass twos and eclass threes?
IOW, s/ones/once/
Meanwhile, thanks, you and everyone else working so hard on EAPI-6
upgrades. =:^)
--
Duncan - List replies
as it made a lot
more sense to me to have say applications or libraries at the product
level, and the cat/pkg at the component level, or even category as the
product and package as the component. But it was already too late to
change that when I became a gentooer in 2004, let alone now.
--
D
r developers and users
alike to simply settle on it as their standard, leaving support for other
alternatives to those who might feel the need to develop and document
them, and if they're not documented, well...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
fference when supporting that same specific use-case
is the primary and arguably only reason the considered alternative exists.
IOW, it's not about not liking upstream. It's about choosing a default
that supports our default use-case.
--
Duncan - List replies preferred. No HTML m
where the upstreams aren't rabid enemies.
My major remaining concern is, as I've already said, documentation. If
that can be resolved, the case is clear enough, and even if not, it's
simply a judgment call on which negative is less bad, lack of
documentation, or an upstream that&#x
s who have already made the non-systemd
choice, which both you and I, as gentooers first and systemd users
second, continue to strongly support _as_ a viable choice, or we'd
arguably not be very good gentooers after all. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"E
both the
stand-alone udev and eudev, as systemd is its own device-manager
provider. Thus, systemd users have the systemd-based network link
solution if they want it, via the systemd-integrated udev.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
lly -flag each individual flag I want to be hard off, not
squishy off, as that's all the flags I've not specifically set hard on.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
default for stand-alone udev-drop-in functionality, tho I'd definitely
rest a bit easier if the documentation were better and if it wasn't so
much a primarily one-man project.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
d normally refuse to do so due to files open for
writing. You might consider something like that as a fallback, if normal
mount-readonly fails. Of course it won't work if magic-srq functionality
isn't built into the kernel, but then you're no worse off than before,
and are far better off on kernels where it's supported, so it's certainly
worth considering. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
too, from time to time. I /hate/ it when that happens! =:^(
... Unless of course a sneaky insult was actually intended! ;^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
r the worse, as unfortunately, I've seen happen
too many times in my computer experience, Linux and otherwise. (No need
to enumerate details here.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
601 - 700 of 2048 matches
Mail list logo
