On Sat, 20 Nov 2010 22:08:25 -0500, Todd Zullinger wrote:
> Beartooth wrote:
[]
>> Also, what is a good way (if there is one, short of removing cobbler)
>> to get to the next item??
> It may be worth hitting 'i' at boot when it says something like "press
> 'i' for interactive boot" a
Beartooth wrote:
> The description in PackageKit (which I had to go through in unusual
> detail, because only the LiveCD had succeeded in installing F14)
> made it sound (to me) like a thing to try.
Fair enough, I suppose. Cobbler is really cool stuff, if you're
interested in automating the provi
On 11/20/2010 04:01 PM, Beartooth wrote:
> How do you know it completed? That upper case sure looked like an
> urgent warning to me
I don't remember, at this point, what the message was, but I've seen
them complain that something that ended with [OK] had failed. If it got
to the poin
On Sat, 20 Nov 2010 10:59:15 -0800, Joe Zeff wrote:
> On 11/20/2010 10:43 AM, Todd Zullinger wrote:
>> Are you even using cobbler? It is a provisioning tool, to automate the
>>setup of PXE booting for bare-metal and virt system installs. If not,
>> why do you have it installed and enabled?
On 11/20/2010 10:43 AM, Todd Zullinger wrote:
> It also sounds to me like cobbler is not your problem. If the system
> boot message show it starting and returning ok, then it's likely
> something after that which is halting your boot up.
Exactly. People tend to blame the last item listed, even t
Beartooth wrote:
>> Run
>> rpm -q --filesbypkg cobbler
>> to find where all the files are.
>
> Ye gods & little fishes!
Are you even using cobbler? It is a provisioning tool, to automate
the setup of PXE booting for bare-metal and virt system installs. If
not, why do you have it installed
On Fri, 19 Nov 2010 16:29:12 -0700, stan wrote:
> On Fri, 19 Nov 2010 22:10:59 + (UTC) Beartooth
> wrote:
[]
> What is to be done?
> How about, as root,
> chkconfig cobblerd off
OK; did that.
> The next time it boots, cobbler won't start, so the error won't occu
On Fri, 19 Nov 2010 22:10:59 + (UTC)
Beartooth wrote:
>
> On an oldish machine (Dell PowerEdge SC1420, *not being used
> as a server), boot messages look fairly unremarkable, till one saying
> "Starting cobbler daemon: SERVING!" -- which is called OK -- after
> which booting stops.
>
On an oldish machine (Dell PowerEdge SC1420, *not being used as a
server), boot messages look fairly unremarkable, till one saying
"Starting cobbler daemon: SERVING!" -- which is called OK -- after which
booting stops.
The machine can be ssh'd into, and I've done a yum update o
