On Mon, 22 Dec 2014 17:43:39 -0800, Adam Williamson
> Once again I noticed a new nightly test event was 'needed' while
> testing relval changes! So the new testing nightly is 20141222.
I've tested the x86_64 network install image on real hardware for the
Server. It did work.
We use a 1998 vintage DHCP server that's been heavily modified. As a
consequence, I have to specify enough networking specifications so that
a network installer can see the, um, network as Fedora 21 and later
doesn't want to send the hardware id as the defaul any longer. There's
some discussion of this in this closed BZ
In the past, I've been able to switch to one of the text consoles once
the first panel is up, provide enough DHCP config to satisfy my vintage
server, and then return. It appears that this most recent
nightly-to-be-tested tries to reach back home and refresh the repos
before / during the display of that first panel. And it crashes
horribly at that point (usual panel with a Report this bug button). I'll
find some way to get the network up in the crashed system and submit a
problem next week, but didn't want to leave this unremarked until then.
I can specify enough information as kernel parameters to avoid this, but
that also raised an interesting question: on a new piece of hardware, if
one has to specify networking on the kernel parameter line, how does one
know what the name of the (or at least a) network device is?
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 a fact that isn't written in Ruby? I'm also aware of /etc/facter/facts.d but I suspect that's considered inappropriate for a package to use and should be left alone for site admins to use. The FPG didn't seem to say anything on this.
Tom @ ncst.edu - hey perfect, thks for the repo solution - but in all
our conversion confusion lost your email with the repo address and can't
see it in archives - can you pls resend
*>Gerald B. Cox* gbcox at bzb.us
/>Sun Dec 21 01:51:29 UTC 2014/
>I don't know anyone who even bothers with installing Chromium.
*>M. Edward (Ed) Borasky*
>znmeb at znmeb.net <mailto:devel%40lists.fedoraproject.org?Subject=Re:%20Re%3A%20chromium&In-Reply-To=%3CCAHkRx6Fa4RhLhXAMK_z31eOnkjzq-Yh_LdBKGnTU%3D9uvQW7JVA%40mail.gmail.com%3E>
>/Sun Dec 21 03:18:44 UTC 2014/
>*Chromium* has never been popular and hopefully
a) where I teach the edu uses the crappy MS Outlook Live (or whatever
they call it) - pretty unusable in Firefox, but can use it better in
Chromium (and I don't allow any MS on our machines to access it with IE
even in a VM)
b) personally I actually like the dev tools in Chromium
A great thing about Linux is we get mix and match choices of apps - so
yes there should be a way for others to use in F21.
*>Stephen John Smoogen* smooge at gmail.com
/>Sat Dec 20 19:18:46 UTC 2014/
> I realize you are angry and upset
Do not make false assumptions or portrayals - We have used Linux in my
companies for a very long time - we just need certain things to use
F21, and switch from Debian Testing. But the crap installer
partitioner did cost us a lot of man-hrs (and why we offered to help ).
*>Oleg Osipov* legolegs at yandex.ru
/>Sun Dec 21 18:03:16 UTC 2014/
> Russian fedora has three repos: re Russian Fedora
thks for suggestions but we prefer to stick to repos based on
*>Antonio Trande* anto.trande at gmail.com
/>Sat Dec 20 16:41:48 UTC 2014/
> What has to do the browser with a wireless driver problem?
*>Reindl Harald* h.reindl at thelounge.net
> which implies a completly unrelated problem
> you stripped that error message and should write a bugreport
re goofy wireless / Firefox bug - who knows. agree, but posted before
filing bug report because it might just be one of those 1 in million
outliers that's not worth bug filing - we've FEDup to 21 and haven't
seen it since.
Cobbler ships a tftp server written in python that integrates with (and
requires) cobbler. Cobbler requires a tftp server, and it would be nice
to be able to install either the cobbler-tftpd or tftp-server package to
satisfy that dependency. Could I have cobbler-tftp provide tftp-server,
or would that cause too many problems? What if both were to provide
"server(tftp)" or some such?
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
I started a yum upgrade process. When it reached 342/784 (@avahi) over half
an hour ago, the screen writing from the process simply halted. Ps on another
tty shows Yum is still running. Disk space and RAM are ample. Top shows
virtually no CPU in use. Nothing seems amis in the tail of /var/log/yum.log.
How does one find out why nothing is happening?
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/