> From: Alec Leamas [mailto:leamas.a...@gmail.com]
> Sent: Thursday, May 19, 2016 09:39
> To: devel@lists.fedoraproject.org
> Subject: Re: F25 System Wide Change: Use /etc/distro.repos.d as default
> reposdir
>
>
>
> On 19/05/16 15:16, John Florian wrote:
> >>
27;ve leveraged their yum repo config's
via a simple rpm install: PostgreSQL and Puppet. (Yes, these are wholly/partly
in Fedora, but sometimes you still must go upstream.)
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
> -Original Message-
> From: Scott Talbert [mailto:s...@techie.net]
> Sent: Tuesday, March 29, 2016 16:29
> To: Development discussions related to Fedora
> Subject: RE: ddclient orphaned
>
> On Tue, 29 Mar 2016, John Florian wrote:
>
> >> Somehow,
> From: Adam Williamson [mailto:adamw...@fedoraproject.org]
> Sent: Tuesday, March 29, 2016 19:30
> To: Development discussions related to Fedora
> Subject: Re: ddclient orphaned
>
> On Tue, 2016-03-29 at 20:10 +, John Florian wrote:
> > >
> > > -Or
ed it. Anyone who wants it can pick
> it up.
Is there anything particularly bad about it or is just a stray puppy that has
somehow "adopted" you? I only ask because I use/depend on it but am amenable
to using something else that's known to be better... and would need t
Is this[0] really the latest greatest documentation for doing this? Given that
it references FC5 it seems rather dated and I wouldn't expect something like
this to still be in Draft.
[0] https://fedoraproject.org/wiki/SELinux_Policy_Modules_Packaging_Draft
--
John Florian
--
devel ma
Ditto! That seems like a much simpler solution overall.
--
John Florian
> -Original Message-
> From: Petr Spacek [mailto:pspa...@redhat.com]
> Sent: Friday, December 11, 2015 03:48
> To: devel@lists.fedoraproject.org
> Subject: Re: Bodhi front page after login
>
>
t has happened through the use of some mirror probing.
Such a 3rd message should be carefully worded to indicate that the package has
started reaching *some* mirrors and that most should have it within another day.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
http://lis
sn't seem very usable to me. I didn't file a bug on BZ because
I wasn't sure where exactly one does that.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
t; Subject: [HEADS UP] dracut-live subpackage
>
> dracut now has a new subpackage "dracut-live" which is needed to boot live
> images with dmsquash.
>
> Please add this package to your dependencies.
>
Thanks for the advance notice. Where is this planned to land? W
rking on this.)
>
> Oh, and not to forget:
> https://fedoraproject.org/wiki/Packaging:Guidelines#Limited_usage_of_.2Fopt.2C_.2Fetc.2Fopt.2C_and_.2Fvar.2Fopt
>
> --
> Matthew Miller
>
> Fedora Project Leader
Thanks for that info. I've always referenced
http://www.pathname.com/fhs
On Fri, 2015-06-05 at 01:12 -0400, Nico Kadel-Garcia wrote:
> On Thu, Jun 4, 2015 at 2:21 PM, John Florian wrote:
> > I’ve been curious how Fedora plans to tackle inclusion of Puppet 4, but
> > haven’t heard even a peep on the subject. As described[1], they’ve moved to
&g
On Thu, 2015-06-04 at 20:17 -0700, Michael Stahnke wrote:
>
>
> On Thu, Jun 4, 2015 at 2:21 PM, Haïkel
> wrote:
> 2015-06-04 20:21 GMT+02:00 John Florian
> :
> > I’ve been curious how Fedora plans to tackle inclusion of
> Puppet 4, bu
On Thu, 2015-06-04 at 23:21 +0200, Haïkel wrote:
> 2015-06-04 20:21 GMT+02:00 John Florian :
> > I’ve been curious how Fedora plans to tackle inclusion of Puppet 4, but
> > haven’t heard even a peep on the subject. As described[1], they’ve moved to
> > an all-in-one p
cal,
but we use Fedora almost exclusively.)
[1] https://docs.puppetlabs.com/puppet/4.0/reference/release_notes.html
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1068867
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
27;ve seen yet.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
sort of failed was due to a bug I just couldn't see or due to a bad choice in
that chunk size I never learned -- it just never bothered me quite enough to
sort it all out.
I really like this prompt_command() idea; that's very clever. Thank you (and
AdamW) for sha
any luck convincing bash to
honor my desire for a very large HISTSIZE despite unsetting HISTFILESIZE but
I've not looked into that issue for several years. I'd love to dig up commands
I used several years ago even if I have to grep an auxiliary history file; I
don't mind dedicated
an lack of clothing,
memory card or camera?" will it be dead enough.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
20/F21?
>
> On 01/22/2015 03:17 PM, John Florian wrote:
> > If I read this page[1] correctly, python3-pyparted should be available
> > starting with F20, yet…
> >
> >
> > Did I miss something?
>
> Looks like apps doesn't quite handle subpackages
/python3-pyparted/overview/
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
place facter facts?
>
>
>
> Am 23.12.2014 um 20:03 schrieb Samuel Sieb:
> > On 12/23/2014 10:24 AM, John Florian wrote:
> >> Following the example set by other packages, I’ve traditionally used
> >> /usr/local/share/ruby/site_ruby/facter/MY_PACKAGE, but what if you have
&
to use and should be left
alone for site admins to use. The FPG didn't seem to say anything on this.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
will *definitely* have us kicking
> ourselves in 6 months. And shipping 1.7 by default will make lots of Django
> users/devs happy.
>
> Definitely bring it up to FESCo, but it's probably riskier to be shipping
> something that will become unsupported within the release lifetime
ers a lot to me since my spin is
relatively use-case agnostic; it's an generic Appliance OS and puppet makes
each node into something specific at run-time though always starting from a
common image.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproje
h foo-server + foo-client.
Whatever you do, please do so between Fedora releases so that those of us who
use things like puppet can have a simple condition on the OS release number.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Perfect! Thanks Christopher.
--
John Florian
-Original Message-
From: devel-boun...@lists.fedoraproject.org
[mailto:devel-boun...@lists.fedoraproject.org] On Behalf Of Christopher Meng
Sent: Wednesday, July 23, 2014 09:12
To: Development discussions related to Fedora
Subject: Re
resolve the issue via my
rpm directly. I’ve not been successful in finding any guidelines in how to
best approach that task. Do I package a bit of SEL policy or is there a way to
have my script run with the puppet_var_lib_t context?
--
John Florian
Then you should add a custom policy
olve the issue via my
rpm directly. I've not been successful in finding any guidelines in how to
best approach that task. Do I package a bit of SEL policy or is there a way to
have my script run with the puppet_var_lib_t context?
--
John Florian
--
devel mailing list
devel@lists.fedorapro
omething happen at the top?
It's still there as far as I can see.
http://mirrors.kernel.org/fedora/releases/20/Fedora/x86_64/os/.treeinfo
Sorry folks, there was a miscomm on our end. It was .treeinfo.signed he was
missing and that was excluded by our mirroring script.
--
John
e was "hidden" because I suspect many a
mirror exclude all hidden files for the reason I had done so, namely to avoid
pulling an upstream mirror's temporary files.)
Anyway, we checked a few upstream mirrors (e.g., kernel.org) and the file isn't
there. Did something happen at the
-
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Okay, count me in. Is there a BZ already in place for reporting issues or
should such reports
to Jakub Dorňák (#1035876) - I guess
> we could backport to f20 without any problems.
That would be extremely helpful here, especially given that f21 is still a
ways off.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
le -- as reversing the
Python 3 is really undesirable at this point -- is there any reason Fedora
couldn't have two mod_wsgi packages (one for Python2 and another for
Python3)?
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/lis
thias
> --
> Matthias Runge
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
I'd like to see 1.6 for F20. That would let me r
wedge so much capability and effort into a narrow
> installer-only use case? Bootable raid6 and raid4??
>
I actually like that idea of decoupling them. It would be good to see
more of the *nix tradition here, do ONE thing and do it very well. Of
course we'd need th
the
host I want/need LVM because in the physical world, LVM makes life way
more easier. Yeah, I can live with it in all cases, but then I'm just as
likely to do a complete reinstall of the VM as to resize the undersized
file system. However, that's only practical because puppet is doin
e home. (I
did learn accidentally with btrfs I can just ignore it and I've not lost
any space on /.)
So yes, simplicity is good, unless it makes everything else harder later.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
some tests. If he can make this work, that would
> > make our lives a lot easier. More to come, stay tuned...
> >
> >
>
> Ok, so it turns out that Python Eggs are a lot smarter than I gave
> them credit for. If you turn your attention to
> http://fedoraproj
sensible, yet it does lead the "jump when we say jump" syndrome. Still,
I'd rather deal with the upgrade conflict you mention than to be pinned to
an older Fedora release. It's always a fragile balancing act choosing
between what needs to be new and what cannot yet
ants to
maintain company-private packages based on django, this affords more
flexibility. I realize it may always mean more packaging work to keep
several python-djangoXYs in the distro, but it makes for a less rigid
coupling between the OS and what framework version you need to use.
--
John
much. Maybe this could be as
simple as the number of non-default CCs for a BZ. I know some bugs I've
been on have CCs added quite regularly. Surely that has to indicate the
interest, if not importance.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fed
s that aren't such moving targets.
I largely want to avoid a big mess of figuring out how to migrate the
deployed instance to new hosts as Fedora releases come out. (As a rule,
we never upgrade; just reinstall with much help from puppet. Think of it
as a fire drill.) Hopefully I
net/
>
> iEYEARECAAYFAlLeu4UACgkQeiVVYja6o6N22QCeJk4+xNa0tciSy4Iu//UaA8mi
> mNYAoIqoD9BCTI2lXX/LqKO0ikA0CYor
> =Lsln
> -END PGP SIGNATURE-
Thank you too Stephen! That indeed does look much more similar. Although
I don't see any Apache httpd config in the
builds into
/usr/share/openstack-dashboard. I need to keep stuff under
/usr/lib/pythonX.Y/site-packages so that the other, non-Django, parts
continue to work as expected. (I suppose I could just relocate the
Django-parts of the build, but sounds like it will break more things that
it will help.)
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
generic RPM spec sense. I'd rather not hard-code the Python version in
myapp.conf.
Any pointers would be greatly appreciated.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Only if you want to drop VESA support.
Please don't drop that. I have a large install base of SBCs using geode
and some on savage and s3virge IIRC. I need at least the VESA fallback,
although I suspect that may not suffice in some cases.
--
John Florian
--
devel mailing list
devel@lis
et the very blunt "head's up" and be explicit too? I have no idea when
py2 will truly go away, but I'm convinced it will eventually and I'd like
to create my works in the best possible fashion. Thus far I've relied on
the implicit py->py2 and explicit py3 invocations as that's the way I've
seen Fedora set examples, but I think this should really be more detailed
in the packaging guidelines.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
have to fix up
a bunch shebang lines and learn that I need to get going on my migration
pronto than the alternative of finding one day that python2 is just gone
where one is left with either a hurried port or downloading python2 from
external sources.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
do. After all "import this"
says:
Explicit is better than implicit.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
n?
I'd always choose the former, regardless of the case or how convenient it
was to me.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
l extra info conveyed via color)
that it's hard to grumble about much else. :-)
I may have avoided these largely because I knew it would take time to
learn the various names. But now I know I can "journalctl _ "
and have an instant refresher. Thanks for such a well-done tool.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
o test for remote
> ntp connectivity.
I think you want to work with:
chronyc tracking
Also, this might be useful too:
chronyc waitsync
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
s way if the specified server exists and responds correctly, and
> 'return false' if it doesn't. For now it is using ntpdate; I suppose we
> could switch it to ntpd, but it would make an awful lot more sense if
> chronyd could do this.
I'm on the chrony mailing list if the
> From: zbys...@in.waw.pl
> It only does an extra stat on the file do termine its kind, and then
> adds "_EXE=..." match. There shouldn't be any speed difference.
Hmmm... I cannot reproduce it now. It must have been something else.
Please disregard and my apologies
#x27;t see
that happen and feel no right in complaining without a BZ, so here we go
:-)
https://bugzilla.redhat.com/show_bug.cgi?id=985548 [RFE: improve
journalctl filtering by _COMM]
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
. But maybe it would be better to make
> 'journalctl /path/to/program' smarter, so that it would look at _COMM
when
> program is not an executable. This way things would work automagically.
That would be suitable too, if not more so. Also, for whatever reason,
I&#x
; The output is still authoritative, but you get more than just messages
> originating from the unit.
I just *knew* I was going to be corrected on that. Thanks for the
explanation though.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
g., python). I want to match on the name of the python
> > program, not python itself.
>
> journalctl _COMM= works for me on F19.
>
As it does for me, but somewhere it got clipped that what I was
asking/wishing for was a convenient -C option (like ps) to do just this,
> From: scl...@netwolves.com
> This seems like such a specious argument. Maybe it made sense when
> we were talking about disk drives
> that were megabytes in size, but now we have 500 gigabyte drives
> usually as a minimum.
You don't ever work with embedded systems, do y
x27;d
think
> > filtering on _COMM is quite routine -- it is for me at least.
>
> You can provide binary path (_EXE=) by ”journalctl /usr/sbin/sshd”.
Yes, but that's of little help with applications using interpreted
languages (e.g., python). I want to match on the name of
IT. I realize if all the fields were
thusly accessible it would result in option bloat quickly, but I'd think
filtering on _COMM is quite routine -- it is for me at least.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
keep
the
> useful ones and throw away the useless ones.
I used to do something like this with vim ":g/NOISE/d" until I could see
the detail I wanted when the alternations for grep would have been
tremendously long. With journalctl's built-in filtering capabilities I'm
#x27;m not fond of the truncation method either, but I do appreciate knowing
that I'm not seeing the whole line, nor do I much care for wrapped lines
with semi-structured output. So until my pager grows a throbbing
indicator per line to hint there's more I find it a reasonable approach.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
t I see nothing but benefit in not
having to add "| less" routinely to things that are UI in nature. These
auto-pagers get out of the way immediately if you need a pipeline, so
what's the harm? In fact, you can still "journalctl | less" or the l
t an in-place upgrade just
like that. (This is unbelievably useful if you have hundreds or more of
nodes running such images in an embedded hardware.) Yeah, I forced a
round peg into a very square hole, but it works beautifully. I'm both
embarrassed and proud! :-)
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
sed and tarballed again.
I'd like to see it behave more the way I expected it to when I naively
first started rolling my own packages. Specifically, it would be nice if
the %Source URI was processed intelligently to automatically retrieve the
content via HTTP, FTP, GIT, FILE or whatever (within reason) happens to be
specified there.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
tarballs
just to feed rpmbuild. It always seems such a huge waste of time,
especially for very large packages.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
mmy account to proceed past some mandatory setup is
irritating. I've raised this concern once before already. I don't mind
hitting a skip button -- I certainly don't want to make it hard for others
to set up their accounts manually if that's their cup o' tea.
--
John Flo
ra Project
URL : http://git.fedorahosted.org/git/livecd
Summary : Python modules for building system images
Description :
Python modules that can be used for building images for things
like live image or appliances.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ive spin with stateless Linux
features enabled, plus puppet (considering switching to ansible), plus a
little glue to make custom appliances where networked resources dictate
the various roles those appliances play ranging from kiosks to firewalls.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
las that Kevin proposed are the ideal replacement
for spins.
https://fedoraproject.org/wiki/Fedora_formulas
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
7;s the point of reviving it? Sometimes, if you don't get your
> $0.02 posted in time, it's best to just sit on it.
Agreed.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
> From: les
>Maybe I'm wrong, but given that I won't likely be around by the time
> these newer languages have become senior, I won't see my statement
> refuted.
You needn't wait long. Ada has been around for three some decades
already. ;-)
--
John Flor
that too. I sure hope we didn't add the efficient
method on top of the inefficient method, rather than replace it.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ld only be used if the DB size
exceeded some threshold.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Thanks Simone!
--
John Florian
From: Simone Caronni
To: Development discussions related to Fedora
Date: 03/28/2013 10:43
Subject:Re: Orphaned meanwhile package
Sent by:devel-boun...@lists.fedoraproject.org
Hello,
I'm replying here as the question was posed
cent Fedora
> releases, feel free to write me.
I would like to hear what you've worked out. We had it going back as late
as F15-16ish IIRC, but it got increasingly difficult and I lost interest,
settling for an RDP session to a Windows client.
--
John Florian
--
devel mai
going to yank the decided on release name, might as well
just
> call it \0.
>
> Bill
Ooh, then F20 could then be called "1 / \0" ... the inverse of null, or
the "everything" release. And switch to a rolling release at that point
too just to complete the paradigm.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
branch. Rawhide always uses the release
> name 'Rawhide'. Even though it's voted on a long way ahead of time, the
> new release name is only applied in the tree at branch time. Several
> people were using Rawhide considerably in advance of branching -
> including my
; touch /tmp/little-bobby-tables"
I joke of course ... sort of. ;-)
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
in a push (where X is probably small).
Long ago I used a perl script (IIRC) called 'mirror' that had just such a
safety feature and X was specifiable. I sure wish rsync had this.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
possible or preferable, but we should preserve traditional methods if
there's no or little harm in doing so.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
w safety net before removing the
old
> one)
>
> Sincerely,
>
> --
> Nicolas Mailhot
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
If this could be made to work as described, I'd be happy with it.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
before function. As an engineer, I see beauty in function
and capability, not glitter. If function doesn't have to be compromised,
yeah go to town with the appearance. As for those work clothes, it would
depend on the job. If I was to do business presentations, no I wouldn&#
e systems of all things, never having a single
> chance of seeing such things? They weren't merely hidden from me.
> They didn't even exist.
Well good for you, but why make it harder than it needs to be?
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ng their system as a
tool to do work, or if they're merely playing with them as a novelty. Not
that there's anything wrong such play, but please stop trying polish the
appearance at the expense of functionality for those who see them only as
tool.
--
John Florian
--
devel m
elog
Display change information for the package.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
rsonally could not care less about the defaults Fedora uses. I've
been overriding them for years. I'm just glad I was able to learn these
things before everything became hidden. I'm only concerned about the
future generations that are given a shiny black box with no way to see
w
find grub quite
arcane, I do like to tinker with low-level details that affect the
higher-level things. Such tinkering got me a decent career. Like it or
not, general purpose PC hardware needs a boot loader.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
much rather wait an
extra few seconds than spend all the time required to adjust configs, risk
borking the boot loader's config, rebooting, etc. just so that I can do
what I wanted to the first time 'round!
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
d thisis not only about the initial grub boot but also the
> > "main" boot process (and screen) that follows.
>
>
> I really do like the idea of a line which says:
>
> "Press to see what's going on right now"
>
> It creates a learning oppo
these are often rather vague. It's
very easy to forget the Fedora is merely packaging upstream and is not
always upstream.
It does seem that there's been a trend forming lately where the rpm's
changelog is covering only what's happened as far as the packaging itself
goes
search engine keywords. They integrate wonderfully into
pentadactyl, if you use that too.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
a domain
short of having to go out out of your way by booting into a non-default
run-level, removing firstboot, etc.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
n and
start itself as "our firstboot and every boot"). Presently I give users
the Fedora image and then direct them to a document that explains how to
install and start puppet which does the rest of the setup for them. It
works very smoothly this way, but only if there are very few
be installed would be a PITA. The whole idea of puppet is to avoid
having to such things because it can automate them.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
not all
need it.
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
nger server, on a single-user
workstation (in multi-user mode, of course). I believe it's getting the
data via NSS and in my case that means LDAP. That's not too esoteric
IMHO.
Again though, I'm not troubled by having to install it either; I'll just
add it to my puppet man
ue to always install finger
because I can't remember who 'd54321' is and finger really helps with
that. (Although, I'm also probably the only gray beard in the company
that uses this. :-)
--
John Florian
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
101 - 200 of 236 matches
Mail list logo
