On 06/30/2012 11:44 AM, JD cried with alarm:
> But that is strange!!
> As I reported, it is branded as fc16 from @updates.
> I had to delete these:
> # rpm -e subscription-manager-firstboot-1.0.3-1.fc16.i686
> subscription-manager-migration-1.0.3-1.fc16.i686 subscription-manager
> They all came from fc16 @updates.
The fact that it's in F17 doesn't preclude its also being in F16.
In any case, the important datum for you is that you shouldn't have it
On 06/30/2012 11:44 AM, Andre Robatino sayed:
> subscription-manager is in F17:
Yes, fair enough. But, as you quote,
> Description : The Subscription Manager package provides programs and
> : libraries to allow users to manage subscriptions and
> : yum repositories from the Red Hat entitlement platform.
On 06/30/2012 11:44 AM, JD howled:
> # yum -y update
> Loaded plugins: auto-update-debuginfo, downloadonly, etckeeper,
> langpacks, presto, priorities, product-id, refresh-packagekit,
> : subscription-manager
> Updating certificate-based repositories.
> Unable to read consumer identity
> This machine has not been registered and therefore has
> no access to security and other critical updates. Please
> register using subscription-manager.
> This is the first time I see the registration thing.
> Why is this being done?
> Why does anyone have to register their machine?
> I see no reason for this other than monitoring people's machines.
> This is totally unacceptable.
Uhm, what's that last plugin in the list of loaded plugins?
Has anyone managed get Postgrey working with postfix in F17?
I have huge problems.
un 30 10:22:04 oh1rdf postfix/smtpd: warning: connect to
127.0.0.1:10031: Connection refused Jun 30 10:22:04 oh1rdf
postfix/smtpd: warning: problem talking to server
127.0.0.1:10031: Connection refused Jun 30 10:22:05 oh1rdf
postfix/smtpd: warning: connect to 127.0.0.1:10031: Connection
refused Jun 30 10:22:05 oh1rdf postfix/smtpd: warning: problem
talking to server 127.0.0.1:10031: Connection refused Jun 30 10:22:05
oh1rdf postfix/smtpd: NOQUEUE: reject: RCPT from
sinikuusama.dnainternet.net[22.214.171.124]: 451 4.3.5 Jun 30 10:22:05
oh1rdf postfix/smtpd: disconnect from
I have had this working with old Mandriva, now I chaged into F17.
Earlier needed only line in /postfix/main.cf:
smtpd_recipient_restrictions = permit_sasl_authenticated,
permit_mynetworks, reject_unauth_destination, check_policy_service
But now it seems no worky.
So, any help....
I have disabled 3 extensions from TB.
However. after restarting TB, I was hoping
that now I would be provided with a Remove
button for each of these extentions. Only
the Enable button shows up.
So.... are thsese extensions built-in and
cannot be removed?
The extensions are:
Estonian ID Card
laajennus Voikon kaytoon
provider for google calendar
Warning: The syslog daemon is not running.
Warning: Suspicious file types found in /dev:
/dev/md/autorebuild.pid: ASCII text
yum whatprovides */autorebuild.pid
give no matches.
Google gives mdadm as possible culprit
mdadm is installed, no raid on that box.
"Jack of all, fubars"
A local FTTH ISP in Buenos Aires has showed some interest in becoming a
local mirror/repo for Fedora (currently, there is none in Argentina).
However, the person in charge tells me he doesn't have 1.2TB to spare. So I
did the math and found that F16 dir is 111G, F17 is 113G.
F16 updates /pub/fedora/linux/updates/16 is 58GB,and F17 UPDATES
/pub/fedora/linux/updates/17 is 38GB
The total tally is 320 GB to mirror F16, and F17... including updates....
So why does all the mirrors must carry obsolete versions from FC1 to F15 ?!
My guess is that this local ISP would be more than willing to mirror F16-17
(and then 18) but he says he can't commit 1.2 TB of data on his server to
host all the obsolete versions of Fedora.
That is, of course, unless the local RedHat branch can spare a 2TB drive...
But really, what is the rationale of mirroring ancient unsupported versions?
During times of Universal Deceit, telling the truth becomes a revolutionary
- George Orwell
On 06/30/2012 02:20 AM, various parties basically said:
> On 06/30/2012 07:54 AM, Mike Wright wrote:
>> Great tip. How do I get toabout:config ???
> Edit | Preferences | Advanced Tab | Config Editor...
FWIW, most of the things that one might want to do can be effected
with the Config Editor, but the only practical way that I know to drop
something such as a newline into that string involves using a text
editor to modify
where "<foo>.default" is replaced with the relative Path value of
Of course, screwing-up prefs.js is a very effective way to shoot
oneself in the foot, so create a back-up before modifying it.
I've got a remote test box which is set to dual boot Fedora 17 and
CentOS 6 using grub2 as the bootloader.
It's currently set to boot into Fedora "default=0" in grub.cfg
I want to change it to temporarly boot into CentOS. I've got the
following menu entries in grub.cfg
menuentry 'Fedora (3.4.3-1.fc17.i686.PAE)'
submenu 'Advanced options for Fedora Linux'
menuentry 'CentOS release 6.2 (Final)'
submenu 'Advanced options for CentOS release 6.2 (Final)'
menuentry 'CentOS (2.6.32-220.13.1.el6.i686)
menuentry 'CentOS (2.6.32-220.7.1.el6.i686)
What should I set default to to boot into CentOS. Should it be 1 if
the submenu entries don't count or 2 if they do count.
Plaform: Fedora 17 x64
Evolution loses its data and launches the Setup Assistant.
Upon reboot everything is OK.
I don't like Windows because of its poor performances but
I am getting tired of Linux utilities bugs. Too much is
too much. I wish Fedora secondary programs were developed
with the same care Red Hat programmers designed their rock