Skip to main content

Upgrading to Fedora 16

Finally had some time to upgrade my Fedora 14 distribution to Fedora 16. I followed the YUM upgrade instructions on the Fedora website. Having never had good luck with odd Fedora releases, I will be skipping Fedora 17 for now and waiting for 18 instead. Overall, The Fedora 15 upgrade was smooth and the reboot of my dual-boot system was successful. However, the following Fedora 16 upgrade presented me with a blank GRUB screen after reboot even though I followed the instructions line by line. At the end, I had to create a Fedora 16 DVD, boot into rescue mode, re-run the GRUB setup commands again: 
chroot /mnt/sysimage

/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
/sbin/grub2-install BOOTDEVICE
After dealing with the usual sound problems, the system was up and running with the dual-boot GRUB setup still intact. At this point, a couple of changes have come to my attention. There is a new systemd component that handles system services. Runlevels concept is replaced by targets instead. Read more at systemd documentation and cheatsheet page. In addition, the chkconfig and service command outputs seem to have changed.
Labels:

Comments

Post a Comment

Popular posts from this blog

Securing Symfony2 REST services with FOSOAuthServerBundle

Overview In my previous article, I wrote about setting up a Symfony2 REST service using FOSRestBundle. However, this REST service was behind a firewall protected by a generic form_login provider. Not really ideal if you wish to open your REST API to other applications. So in this article, I will try to explain how to set up FOSOAuthServerBundle to protect your REST API methods using OAuth2. Before we start getting into the gritty details, it is a good idea to have a look at the official OAuth2 documentation . Let's begin... FOSOAuthServerBundle Installation You have to install v1.1.0 of FOSOAuthServerBundle if you are using Symfony 2.0.x. If not, see the docs . First, add the following entries to your deps file: [FOSOAuthServerBundle] git=git://github.com/FriendsOfSymfony/FOSOAuthServerBundle.git target=bundles/FOS/OAuthServerBundle version=origin/1.1.x [oauth2-php] git=git://github.com/FriendsOfSymfony/oauth2-php.git Run the vendors script to install these...
87 comments
Read more

Unexpected token "name" of value "if" ("end of statement block" expected) in "WebProfilerBundle:Collector:logger.html.twig"

Encountered this WebProfilerBundle error message when I ran the bin/vendors script to update my Symfony2 bundles. Make sure your deps file is up to date; you need to pay special attention to your version values. In this case, update your twig version to v1.2.0 as illustrated below: [twig] git=http://github.com/fabpot/Twig.git version=v1.2.0 Run the vendors script to update your bundle and the error message should disappear. You can get the most up to date deps file from the symfony-standard repository located at: https://github.com/symfony/symfony-standard/blob/master/deps
1 comment
Read more

Symfony2 SecurityBundle and FOSUserBundle integration: How does it work?

Overview A couple of days ago, I realized I needed to add some new functionality to the login process. Specifically, I needed to track all previous login attempts. Not knowing anything about the new Symfony2 SecurityBundle, I had to go through the underlying code to understand what was going on. In the process, I think got a basic idea about how the new SecurityBundle interacts with FOSUserBundle. Configuration I have a basic security configuration as illustrated below. app/config/security.yml security: encoders: Symfony\Component\Security\Core\User\User: plaintext role_hierarchy: ROLE_ADMIN: ROLE_USER ROLE_SUPER_ADMIN: ROLE_ADMIN providers: fos_userbundle: id: fos_user.user_manager firewalls: main: pattern: .* form_login: provider: fos_userbundle check_path: /user/login_check login_path: /user/login lo...
4 comments
Read more