On Mon, 21 Jan 2013 14:14:20 -0500 "Eddie G. O'Connor Jr."
wrote:
> On 01/21/2013 01:53 PM, Ranjan Maitra wrote:
> > On Mon, 21 Jan 2013 13:28:12 -0500 "Eddie G. O'Connor Jr."
> > wrote:
> >> I too was going to install F18...but I will wait until F19 or F20 before
> >> I move forwardI have w
On 01/21/2013 01:59 PM, Reindl Harald wrote:
Am 21.01.2013 19:53, schrieb Ranjan Maitra:
In my mind, the biggest issue with F18 is the installer which has been
commented on, and which puts things like disk partitioning under the
rug. Perhaps the goal is to mimic other popular (by ways of mob vo
On 01/21/2013 01:53 PM, Ranjan Maitra wrote:
On Mon, 21 Jan 2013 13:28:12 -0500 "Eddie G. O'Connor Jr."
wrote:
I too was going to install F18...but I will wait until F19 or F20 before
I move forwardI have way too much riding on this laptop working
properly...and since it's an "old" Gateway.
> semodule -r matahari
>
> Should remove matahari policy.
>
> >>>
> >>> Thanks, but I get the following (in F18):
> >>>
> >>> sudo semodule -r matahari libsemanage.semanage_direct_remove: Module
> >>> matahari was not found. semodule: Failed!
> >>>
> >> Ok so it is remov
Am 21.01.2013 19:53, schrieb Ranjan Maitra:
> In my mind, the biggest issue with F18 is the installer which has been
> commented on, and which puts things like disk partitioning under the
> rug. Perhaps the goal is to mimic other popular (by ways of mob vote)
> OS's, but some of us have never use
On Mon, 21 Jan 2013 13:28:12 -0500 "Eddie G. O'Connor Jr."
wrote:
> I too was going to install F18...but I will wait until F19 or F20 before
> I move forwardI have way too much riding on this laptop working
> properly...and since it's an "old" GatewayI'd rather not have to
> deal with v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/21/2013 12:30 PM, Ranjan Maitra wrote:
> On Mon, 21 Jan 2013 12:16:12 -0600 Daniel J Walsh
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 01/21/2013 12:14 PM, Ranjan Maitra wrote:
>>> On Mon, 21 Jan 2013 12:04:10 -0600 D
On Mon, 21 Jan 2013 12:16:12 -0600 Daniel J Walsh
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/21/2013 12:14 PM, Ranjan Maitra wrote:
> > On Mon, 21 Jan 2013 12:04:10 -0600 Daniel J Walsh
> > wrote:
> >
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
> >>
> >> On 01/
On 01/21/2013 01:04 PM, Daniel J Walsh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/21/2013 01:19 AM, James Freer wrote:
On Mon, Jan 21, 2013 at 12:28 AM, Ranjan Maitra
wrote:
Dear friends,
I recently upgraded from F17 to F18. I chose not to use fedup but rather
I used fedora-u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/21/2013 12:14 PM, Ranjan Maitra wrote:
> On Mon, 21 Jan 2013 12:04:10 -0600 Daniel J Walsh
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 01/21/2013 01:19 AM, James Freer wrote:
>>> On Mon, Jan 21, 2013 at 12:28 AM, Ranj
On Mon, 21 Jan 2013 12:04:10 -0600 Daniel J Walsh
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/21/2013 01:19 AM, James Freer wrote:
> > On Mon, Jan 21, 2013 at 12:28 AM, Ranjan Maitra
> > wrote:
> >> Dear friends,
> >>
> >> I recently upgraded from F17 to F18. I chose no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/21/2013 01:19 AM, James Freer wrote:
> On Mon, Jan 21, 2013 at 12:28 AM, Ranjan Maitra
> wrote:
>> Dear friends,
>>
>> I recently upgraded from F17 to F18. I chose not to use fedup but rather
>> I used fedora-upgrade, which is basically a wrap
On Mon, Jan 21, 2013 at 12:28 AM, Ranjan Maitra
wrote:
> Dear friends,
>
> I recently upgraded from F17 to F18. I chose not to use fedup but
> rather I used fedora-upgrade, which is basically a wraparound around
> yum upgrade (from the documentation). Everything went through
> reasonably smoothly
Dear friends,
I recently upgraded from F17 to F18. I chose not to use fedup but
rather I used fedora-upgrade, which is basically a wraparound around
yum upgrade (from the documentation). Everything went through
reasonably smoothly except for the following messages:
Font messages such as:
Updati
14 matches
Mail list logo