From: "Scott Berry" <sberry@northlc.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Running a personal domain
Date: Sat, 30 Jun 2007 18:17:13 -0500 [thread overview]
Message-ID: <002901c7bb6c$cfe3e6b0$c701a8c0@yellobow> (raw)
In-Reply-To: <BAY141-DAV48A85C5070063A19DD9268F0F0@phx.gbl>
Well to run yum you have the following syntax:
yum install package
yum remove package
yum update package
Now in Fedora we have what they call:
what provides
this tells you what a package depends on:
So for an example the statement might look like this:
yum whatprovides perl
or the name of the package.
Do you need to know how to install rpm's?
Scott
----- Original Message -----
From: "Zachary Kline" <Z_kline@hotmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, June 30, 2007 5:57 PM
Subject: Re: Running a personal domain
> Hiya,
> Well, I'm mostly wondering about how Yum works, and a lot of that basic
> kind of package management stuff. The problem is that the server I have
> access to is probably customized in some way, so I need to figure out how
> it
> does things. I'm afraid of breaking it and needing to call in the tech
> support folks to fix it.
> To quote them, they say that only advanced users need to access the
> machine
> via SSH.
> Thanks,
> Zack.
>
> ----- Original Message -----
> From: "Scott Berry" <sberry@northlc.com>
> To: "Speakup is a screen review system for Linux."
> <speakup@braille.uwo.ca>
> Sent: Saturday, June 30, 2007 3:52 PM
> Subject: Re: Running a personal domain
>
>
>> What exactly do you want to know I am using Fedora here which is based on
>> the Redhat scheme of things.
>>
>> ----- Original Message -----
>> From: "Zachary Kline" <Z_kline@hotmail.com>
>> To: "Speakup is a screen review system for Linux."
>> <speakup@braille.uwo.ca>
>> Sent: Saturday, June 30, 2007 4:40 PM
>> Subject: Running a personal domain
>>
>>
>>> Hiya,
>>> I recently bought the domain name blindlinux.com from a registrar and
>>> set it's DNS and such using the control panel they provide. I'm also
>>> allowed a virtual private server for my site and such, which I can
>>> access
>>> via SSH. I guess I have a desire to learn how all that works
>>> internally.
>>> I'm not gonna run a massive site off it or anything, but maybe host some
>>> files and just a personal page.
>>> I was wondering if anybody here is familiar with Cent OS. I'm not,
>>> though
>>> have heard it's based on Red Hat Enterprise Linux. I'm not familiar
>>> with
>>> Red Hat in general.
>>> Any tips from anybody?
>>> Thanks muchly,
>>> Zack.
>>> PS: I wish I could host it myself, but I'd need to talk to my ISP about
>>> getting a static IP, and anyway it isn't my connection.
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>>
>>>
>>> --
>>> No virus found in this incoming message.
>>> Checked by AVG Free Edition.
>>> Version: 7.5.476 / Virus Database: 269.9.14/880 - Release Date:
>>> 6/29/2007
>>> 2:15 PM
>>>
>>>
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.9.14/880 - Release Date: 6/29/2007
> 2:15 PM
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Scott Berry
` Zachary Kline
` Scott Berry [this message]
` Zachary Kline
` Butch Bussen
` Scott Berry
` Gaijin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002901c7bb6c$cfe3e6b0$c701a8c0@yellobow' \
--to=sberry@northlc.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).