top of page


Public·46 members

New Fedora Core 7 plan


The name of Fedora derives from the original "Fedora Linux", a volunteer project that provided extra software for the Red Hat Linux distribution, and from the characteristic fedora hat used in Red Hat's "Shadowman" logo. Warren Togami began Fedora Linux in 2002 as an undergraduate project at the University of Hawaii,[52] intended to provide a single repository for well-tested third-party software packages so that non-Red Hat software would be easier to find, develop, and use. The key difference between Fedora Linux and Red Hat Linux was that Fedora's repository development would be collaborative with the global volunteer community.[53] The original Fedora Linux was eventually absorbed into the Fedora Project, carrying with it this collaborative approach.[54] The Fedora Project is sponsored primarily by Red Hat with additional support and sponsors from other companies and organizations.[55]

To deploy a VM from such an image, you'll need to accept the image's terms the first time you use it, once per subscription. You'll also need to specify purchase plan parameters to deploy a VM from that image

To view an image's purchase plan information, run the az vm image show command with the URN of the image. If the plan property in the output isn't null, the image has terms you need to accept before programmatic deployment.

If you still have the original VM, or another VM created using the same marketplace image, you can get the plan name, publisher, and product information from it using az vm get-instance-view. This example gets a VM named myVM in the myResourceGroup resource group and then displays the purchase plan information.

Basic Droplets can now have Regular AMD CPUs. Additionally, you can now change between Premium AMD and Premium Intel CPUs when resizing Droplets. Learn more about resizing Droplets and how to choose a Droplet plan.

Our Basic Droplet plans now include Premium Intel and AMD Droplets, which have faster Intel and AMD CPUs and NVMe SSDs. Premium Intel plans are availabile in all regions, and Premium AMD plans are available in NYC3, SFO3, and FRA1.

We recently replaced Standard Droplet plans with Basic Droplet plans. Today, we have deprecated Standard Droplet plans from the API for new users. Existing customers will retain grandfathered access to these plans. See the API changelog for a full list of deprecated plans.

All users can now create Storage-Optimized Droplets in AMS3, FRA1, LON1, NYC1, and SFO3 using the control panel, API, or CLI. The slugs for the new plans are so-2vcpu-16gb, so-4vcpu-32gb, so-16vcpu-64gb, so-24vcpu-128gb, and so-32vcpu-256gb.

Changes to Droplet Bandwidth Billing announced. The new billing plan goes into effect June 1. Charges for June, if any, will appear on the July 1 bill. Customers can view usage and billing information on their billing page.

More Fedora Core 5 updates have made their way to the various repositories today. The FC5 update list for April 3, 2006 includes -- wpa_supplicant-0.4.8-7.fc5, binutils-, perl-Net-DNS-0.57-1, perl-DBD-Pg-1.47-0.1.FC5, perl-HTML-Parser-3.51-1.FC5, gnome-applets-2.14.0-1.fc5, pcmciautils-012-0.FC5.2,, k3b-0.12.14-0.FC5.2, mc-4.6.1a-12.FC5, selinux-policy-2.2.25-3.fc5, and policycoreutils-1.30.1-3.fc5. Some of these updates also have equivalent Fedora Core 4 packages.

Being released today are a great deal of official Fedora Core 5 updates. The partial list includes -- ncpfs-2.2.6-2, system-config-kickstart-2.6.6-4, scim-1.4.4-9.1.fc5, mlocate-0.14-0.fc5.1, spamassassin-3.1.1-1.fc5, gconf-editor-2.14.0-1.fc5, kernel-2.6.16-1.2080_FC5, cpio-2.6-16.FC5, libsetrans-0.1.20-1.fc5, selinux-policy-2.2.25-2.fc5, policycoreutils-1.30.1-2.fc5, libsemanage-1.6-1.fc5, libselinux-1.30-1.fc5, and checkpolicy-1.30-1.fc5. Fedora Core 4 also has a couple of package updates out today as well. One of the notable packages being updated today for Fedora Core 5 is the 2.6.16-1.2080_FC5 kernel. This is the first official kernel


Welcome to the group! You can connect with other members, ge...


Group Page: Groups_SingleGroup
bottom of page