Results 1 to 10 of 24

Thread: The Linux 3.7 Kernel Is Going To Be A Beast

Threaded View

  1. #18
    Join Date
    Nov 2010

    Cool Way, way OT!! What has this to do with a new kernel release in fact!! NOTHING!!

    Quote Originally Posted by Viper_Scull View Post
    I must be one of those strange cases that have no problem whatsoever with Arch. Same installation for the last 3 years. A couple of situations where i had to fix some problems when major changes occurred (well explained and documented on the arch linux site or the forums)

    I've been using SystemD for more than 2 years now. Although it's true that at the beginning it was a bit of a pain in the ass, it's been in a rock solid state for more than a year and a half. And of course this is Arch, you are going to have to configure your system so if you make mistakes like with everything else it'll go wrong. You read (what you should have done before and not after), you fix them, you learn, you don't make them again, and then everything goes more smoothly than you'll ever find on Bugbuntu. And you just don't go back.
    One of the reasons I use ARCH and Gentoo is because it gives me a kick up the arse to delve into the depths of how a Linux Desktop system is configured. I personally find most Ubuntu-derived distros to be a bit boring. However I currently run about 7-8 distros (on bare metal) in a multi-boot configuration to compare how they do things. I like to remain distro agnostic!

    If you've been using systemd this long then perhaps you should be made aware it should be written "systemd" (correction I received some months ago from the ARCH systemd maintainer!!) - "SystemD" is not the correct name...

    BTW I've had my ARCH install switched over to systemd for about a year. So I've given it a fair go before feeling I could comment (either way) on the relative merits of Init-V vs. systemd (Upstart will die some day soon like Compiz). Some people seem to feel able to dimiss systemd without even testing it all... In fact I did try and offer some fixes to the BASH completion script for systemd about 9 months ago... However I just got the brush off by the guy who does the ARCH systemd packaging... Not very community spirited IMHO...

    Actually I read most of the ARCH and Gentoo Wiki pages in great detail (both are a bit lite on systemd detail IMHO). However my fstab get a bit complicated (as you can imagine!!) One little slip and a systemd-based system won't boot. That's just a fact - and is no fault of ARCH - it's simply how it's written. Perhaps there is simple switch so it doesn't just hang during boot - on a minor system configuration error (e.g. mountpoint for a non-critical FS partition does not exist). But not even dropping to a TTY console (like Init-V generally manages to do) - to do some quick repair work - is really unnecessary...

    Also I thought systemd would magically/on demand mount remote CIFS fmountpoints from my fstab file when I went to access them... However this is not how the lazy mounting works sadly... Personally I don't care so much about fast boot speeds (I boot of a Sammy 830 SSD after all). After boot KDE takes care of any speed gains I might have gained from systemd

    Last edited by bobwya; 10-07-2012 at 08:04 PM. Reason: rweregerger

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts