You are not logged in.
Pages: 1
I hereby challenge the two of you (and especially Fourdrinier) to a three month Bedrock Linux marathon.
No need for a challenge. I will be running Bedrock Linux on my netbook for far longer than a year, as I plan to help with development and client(distro) compatibility. Each person handles and uses Linux in a different way. It may be masochistic in nature, but I enjoyed using Gentoo for 2 years, and I am looking forward to working with Bedrock extensively. This kind of Linux work is very fun to me. I would NEVER use this for my desktop computer. In fact, because I game extensively and work with Electronic music production, I use Windows 7. Quite the contrast eh?
Heh, I do love digging through the kernel config menu...
Bedrock's initial installation can seem a bit stressful, but even with the more complex step of configuring the kernel for compilation, you can import the list of options and modules in the kernel of the Live distro you are using as a host. Even in alpha, the installation instructions for Bedrock are detailed enough, and that should improve extensively. Several of us are preparing to create automated scripts and menu's to cover the installation part. Once you build the kernel, configure the filesystem, and patch and install busybox and capchroot, you can install your software through other distros. If you like compiling, use emerge. If you like a rolling release, use pacman. If you like easy setup and stability, use apt-get. If you want to mix and match, use them all. The setup stage for installing a new client(distro) is relatively simple, and once that is done, the rest is handled with very few commands. Honestly, the most intimidating part should be the kernel configuration step. Beyond that, enjoy the several br* scripts that do all the work for you.
Future plans include a bcm command which automatically installs and configures a new client(distro).
Again, this is an alpha release, so polish is not a priority.
...that you are incompetent enough to fail miserably enough at building a package from source and adding distro-related patches?
Of the 10 or so distro's I have abused and twisted over the years, I have, in spite of distro patches, distro specific code, and even code that should be distro independent, run into many source packages that would not compile, even after digging into the code and fixing some of it myself. For goodness sake, my recent Gentoo install fought against a source compile, even after I reverted back to source that was almost 3 years old. After manually fixing several compile error's in the code, I would have had to hand-edit the .asm that was used. Instead, I was stuck with the older Gentoo source emerge of this package, and I was NOT about to waste my time and the valuable resources of my netbook integrating the Ubuntu, Fedora, or Debian filestructure and init(specifically Ubuntu's terrible init setup) scripts just to run a single application. If other distros stuck to a standardized /etc/ file structure, this wouldn't be an issue, but it is.
Some level of laziness plays an important role here. This is the same concept as to why Gentoo is so popular instead of LFS. Both are source compiled and manually configured, but Gentoo handles package stability and versioning to prevent conflicts and circular dependencies so you don't have to.
It's important to note that installation of Bedrock is similar to that of LFS. The main point is to provide the most minimal base possible and let other distro's packages fill in the gaps without interfering with the base system, or each other. This allows CLEAN interaction between distros, which will NOT happen if a separate distro's package is integrated into the one you are currently running. Library and /etc/ conflicts alone can produce migraines that could kill.
The real issue arises from the extreme number of patches applied to any one distro. In the name of compatibility, most distros will patch software until it works. This makes any foreign software an unholy nightmare to install. If you are lucky enough to find a distro specific patch, then you have to cross your fingers and hope it compiles. Too often, you're simply told to use the version that currently exists in the repo's.
Edit: Removed a piece of sarcasm.
This(CrunchBang) distro looks like an optimal solution for installing Bedrock. It's a lightweight and speedy Debian distro, which also implies relative stability. It should have the full GNU toolkit, and it has full APT support, so tool updates would be possible. A lightweight Live environment with a full package repo is somewhat rare.
Edit: To clarify, it would serve as a Live host to install Bedrock to disk as a standalone distro, and would also serve well to repair Bedrock in the event that something drastic happens. It's function is not unlike Gentoo's current "installation" disk.
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.