Making arch-based distro

Hello.
I started to make Arch-based distro. I have fully installed Arch + Openbox.
I have a couple of questions:
- How can I make an ISO from installed system I have?
- I haven't installed drivers for my graphics because if I respin it into a new system, users with nvidia graphics, for e.g. will involve with problems then. How can I avoid that, i mean, is there a script that will recognize graphics and download drivers for it?
That's all for now. Arch with Openbox and some setup rox.

Dobrosslove wrote:
Hello.
I started to make Arch-based distro. I have fully installed Arch + Openbox.
I have a couple of questions:
- How can I make an ISO from installed system I have?
- I haven't installed drivers for my graphics because if I respin it into a new system, users with nvidia graphics, for e.g. will involve with problems then. How can I avoid that, i mean, is there a script that will recognize graphics and download drivers for it?
That's all for now. Arch with Openbox and some setup rox.
You can check out Archbang GiT. Alternativly, you can even join ArchBang Dev-team. Choice is yours, would be happy to help.

Similar Messages

  • List of arch based distros

    Can someone give me a list of arch based distros? thanks

    http://en.wikipedia.org/wiki/Arch_Linux … vironments
    Here's a list of Arch-related distros. There are probably more floating around somewhere.

  • Arch based distro - same repository?

    hey,
    i got a question.
    let's say i'm making a new ,archlinux based distro. must i use own repositorys then or can i just use archs repositories? i won't really make a new distro (no time for that) but i always asked myself this question.
    pure curiosity.

    Ιf it's rolling, I guess there is no problem, but you need to make it clear (on the distro site for example) that the most of work done is thanks to the Archlinux devs, if you are gonna use the official repos.
    Chakra-project for example is Arch+KDEmod, thus it currently* uses the official repos.
    *they are gonna make their distro, afaik, non-rolling.

  • Arch based distro for mame cabinet

    hi all folk,
    I'm a retro gaming aficionado!!
    I made a cabinet on my own and installed mame and some other emulators on.
    the system is a win xp "modded" to boot directly to the frontend instead of explorer.
    but I would like to have an open source system.
    I think that archlinux could be the right distro to build a mame machine.
    anyone of you would to joinor help with this project?

    I found this in arch wiki:
    Arch Linux uses AIF aka 'Arch Linux Installation Framework' to perform installations.
    This tool - written in bash - consists of some libraries to perform various functions (installing packages, setting up disks etc) and some so called procedures which use these libraries to provide an easy means to do an installation or to smaller related tasks ('partial procedures'). These procedures are shipped by default:
    interactive: An interactive installation procedure, which asks you some questions, guides you through an installation and helps you configuring the target system by automatically changing some settings for you depending on what you did earlier (eg network settings)
    The installed system will initially have only a customisable set of "base" packages installed with whatever utilities and drivers you need to get online.
    Then once you've successfully booted the installed system, you'll run a full system upgrade and install any other packages you want. (aliased as /arch/setup)
    automatic: An automated, deploy-tool-alike procedure designed for low-to zero interactivity.
    uses profiles for configuration of the target system.
    See /usr/share/aif/examples/ for example profile files. The examples implement quite generic scenarios but you're free to change them how you like to install extra packages, do configuration tweaks, etc.
    base: basic, little-interactivity installation with some common defaults.
    This procedure is used by the others to inherit from, it is NOT meant to be used directly by end users
    partial-configure-network: exposes the network configuration step from the interactive procedure, to help you setup the network in the live environment
    partial-disks: Process disk subsystem or do a rollback
    partial-keymap: change your keymap/console font settings. (aliased as km)
    The benefit of procedures such as partial-keymap and partial-configure-network over direct usage of tools such as loadkeys or ifconfig is that when running the interactive procedure, you will get asked if you want to apply your settings to the config files of the target system.
    If you want to go further, you can also:
    write your own procedures from scratch or by overriding certain parts of other procedures
    write your own libraries, to provide new, reusable functionality
    create your own configs for the procedures that support them (eg automatic)
    For more information, consult the readme of AIF.
    is there any how to for this?
    anyone has experienced this kind of tool

  • Lowarch 0.1.1 (Savitri) - i486 Arch based Distro - Released

    I needed to make a new release now, since the current repo address has changed, so the old install cd and floppies don't work for ftp install anymore (without changing the url, of course).
    But there are of course package upgrades and bug fixes as well. And now all the install floppies are finished. There's also the ongoing process of deleting unimportant packages and adding new useful ones.
    Quite a few people have joined and done some very useful testing. I'm always happy to hear about problems and other experiences with different systems (old and new). So give it a try if you have some free disk space, time and think it's fun.

    cr7 wrote:when I need to customize my rc.conf, I have to set the keymap as "i386/qwerty/it.map.gz", instead of "it_IT" as in Arch Linux.
    Shouldn't it be just 'it', not it_IT? I thought it_IT is for locale. I use 'no' (Norwegian) without problems.
    cr7 wrote:If I want to recompile the entire system for i586, with updated packages, how can I do? :?:
    I'm running lowarch on a Pentium M, and I can't say I have noticed any difference in speed between Arch and Lowarch on it. I doubt you will see any difference at all with the system compiled for i586 instead of i486.
    But if you think it's fun to try out things, here's how:
    Download http://www.lowarch.org/abs.tar.bz2 which is the current abs tree. (I don't have access to cvs server or similar, so I can't set up normal abs access.
    Change the /etc/makepkg.conf
    Extract the abs.tar.gz (it'll be called abs-clean because my abs tree has all the source files, so I have a script copying all the files except source files to abs-clean)
    in the abs-clean directory use makeworld to build all the packages.
    (On the 166Mhz It will last, oh, about, let's see /me is calculating ....ahh about an eternity...) If you'll use a i686 machine for the compiling, you should install lowarch on it, and use the uname hack (search for it, I don't have the link in my head, if you don't find it, tell me).
    Then use gensync to create a custom repo of the files.

  • Arch-based distro

    Ok, hopefully this is the right place to pose such a question but anyway...here we go...
    I have a few months before I ship out to college (computer science major) and I am going to spend my last bit of free time creating a Linux distribution. I had thought about just doing a LFS project but, I really like how arch works and If some thing's not broke, why try and fix it? Can someone point me in the direction I need to go to build an arch-derivative? I am willing to take the time and make something for the community but I need to know where to start..if anyone can just give me somewhere to start and some info I'd greatly appreciate it.

    tomk wrote:
    pcninja wrote:I want to make it a bit more user friendly like having a simpler install method.
    I'm curious here - apart from the installer, what else about Arch needs to be "simpler", in your opinion?
    Arch is simple in one way but I mean like make something extremely customizable and something you can have control over without being as advanced as arch. For more intermediate users. It took me a lot of reading and learning before I could get through a full arch install and then how to use arch. By simple I mean easier to use.
    And nice to see someone else in Ireland, I live in waterford

  • Arch-based medical distro

    I started a simple project to build an arch-based distro for medical professionals
    The base install is ready and my own-developed simple medical apps are in development to be included...
    I was searching for more apps to include (medical image viewer, electronic medical records) and I found a lot of options, and have no idea what to include and where to start.. I never used any of them, (still a medical student), and I was wondering anyone could help in bringing birth to this distro?
    Suggesting apps, or maybe helping in building and packaging apps not available in the official repo or the AUR? or even only testing?
    Any interest?!

    hadiyazdi wrote:I started this to learn more about archiso and then after having my custom arch image ready, I had this idea in mind... I guess I was a little over enthusiastic
    No worries - far better to be occasionally over enthusiastic, then never enthusiastic enough.  There simply may be more productive ways to channel that enthusiasm: more productive both for you, your would-be users, and the rest of the arch community.
    First, let me highlight the real problem with spin-off distros.  You certainly could put together an installation iso with all the right stuff for a medical professional to put an arch-based system on their computer and start using it.  But are you going to commit to maintaining it and doing all the hard work that really comes with maintaining a distrobution?  If not, the best case scenario is that your distro would be a passing fad, and you'd get (probably less than) your 15 minutes of micro-fame.  The more realistic scenario is that your distro would be just a fart in the wind - and as a result, so too would be your enthusiasm for contributing in other ways.
    In contrast to all this, there are very productive ways to channel any such enthusiasm.  A majority (if not all) of the great things about archlinux have come from one person scratching their own personal itch, then sharing the products with the community.  This way they are giving back to the community - but it is not purely selfless: they are appreciated by the community.  How small would be your target audience for the new distro?  You'd tell a few collegues, and maybe one or two of them would share it with a few of theirs ... pretty small.  But if you see software that could be useful to medical professionals that is lacking in archlinux and instead you make/improve AUR packages, or even set up an unofficial repo with the precompiled binaries, then any medical professional who searches the AUR can find your products.
    Further benefits of this approach are that now your contribution will likely last much longer.  There will be more users to benefit from it, and more to appreciate your contribution.  And when you inevitably get too busy to maintain a few of the AUR packages, or the repo, there will be a much larger pool of potential volunteers to take over - thus preserving the 'legacy' of your contribution.
    I suppose this all lends itself well to a parable of sowing seeds on different types of ground.  Suffice it to say that being a successful farmer may have more in common with being a successful archer than one would first suspect.
    And in contrast to my initial answer of "No", I would be happy to help you get PKGBUILDs working for all the tools you would like to make available in the AUR or in a custom repo.  I also suspect many others here would be much more welcoming to this as well.

  • [arch-based] TP-Link TL-WN822N losses

    Hi. I need your help adjusting something wrong with my Arch-based distro and USB WiFi adapter: the last one is a TP-Link TL-WN822N.
    The issue is this one: it often happens that automatically network disconnects from the home's WiFi network, not only when the computer is locked, but even if I'm surfing the internet or just using it.
    Maybe this will help someone understanding something more specifically:
    $ lsusb | grep TL-WN822N
    Bus 001 Device 005: ID 0cf3:7015 Atheros Communications, Inc. TP-Link TL-WN821N v3 / TL-WN822N v2 802.11n [Atheros AR7010+AR9287]
    If you need some other tests, I obviously will do it.
    Last edited by streambinder (2014-10-29 14:12:18)

    Sorry, we can't help with "arch-based" distros as we have no idea what changes they have made.
    https://wiki.archlinux.org/index.php/Fo … pport_ONLY

  • Arch influenced distros?

    What are the Arch influenced distros? Not distros necessarily based directly in some way upon Arch Linux, but influenced by Arch Linux?
    For example, Alpine Linux uses the Arch build system. Does anybody know of other distros that are "inspired" by Arch in a similar fashion?
    Frugalware comes to mind, because it uses pacman. But it seems that pacman-g2 is a fork of an early beta-release of what is now pacman 3.x. Is this enough to meet the standard of "Arch influenced" distro?
    If folks can make a good case in this thread for a distro being influenced by Arch, I'll add it to the appropriate section on the Arch-based Distros wikipage.
    Thanks everyone.
    Last edited by lseubert (2009-06-23 11:08:37)

    PJ wrote:
    I was woundering if there should be a category for custom repositories? I mean that is IMHO somthing more in the spirit of Arch Linux since Arch is a meta-distribution. If that's the case I think ArchVDR might be a good candidate to be included in that kind of category.
    ArchVDR
    http://sourceforge.net/apps/trac/archvdr/
    Actually, I think custom repositories deserve an entire wikipage of their own. (Guess I have another wikipage to work on now ;-)
    That said, what is the difference between a custom repository and an Arch-based distro? For most Linux distros, this is pretty easy to figure out. But as you rightly point out, Arch is more of a meta-distribution. You install a very small core set of packages, and then build your own distro on top of them. Thus, 'extra' and 'community' are, technically, custom repositories and only 'core' is the "One, True Arch Linux" - to get pedantic about it.
    But seriously, what distinguishes an Arch distro from a custom repository? Where do extra, testing, and community belong in the grand scheme of things? What about kde-mod and Chakra? What about something like 'http://repo.archlinux.fr/', which is the repository for yaourt, among other things?
    Also, on the Arch-based Distros wikipage, I listed larch and archiso-live as meta-distros, because they are used to build a custom install .iso or .img file. But given your point that Arch itself is really a meta-distro, should I use some other word to describe larch and archiso-live?
    PJ wrote:Not really sure about this but after reading a bit more it seems to be a more integrated qt desktop environment on top of arch linux:
    eth-os
    http://eth-os.org/
    http://code.google.com/p/eth-os/
    To me, this seems to be a custom repository, but it is somewhat hard to tell. They haven't actually released anything yet, so there isn't anything to evaluate right now. I'll keep an eye on it though, and write it up upon release of something official.

  • Differences between Arch linux and RHEL-based Distros?

    Hi there!
    So, I am officially trying to make the permanent switch from Windows to Linux. I've used Linux in the past, from Ubuntu, to Fedora, to Mint, and I've always liked Arch the most. Nothing beats the feeling of an OS you had a hand in setting up.
    I'm wondering though, what are the differences in Arch vs distros like Red Hat, Fedora, and CentOS? I recently picked up a book called, "The Linux Bible" which provides a course-like approach to learning the intricacies of Linux. I'm wondering if it would be easily possible to adapt the lessons from that to Arch, or to use Fedora or another RHEL-based distro like it suggests.
    Thanks

    The biggest issue I find is with SE Linux. I don't know if this is default in RHEL itself but Fedora uses it. If I understood it properly, though, I doubt it would be such an issue!
    EDIT: I think it would be best to learn one distro first, using documentation for that distro. So if you want to use the book, install something that matches the book as closely as possible. If you want to use Arch, use the wiki as your primary documentation. I say this because there is a big difference between figuring out the ways in which two distros differ when you understand the GNU/Linux basics and (I imagine) trying to do so when you are still learning those basics. I don't just mean ls, grep etc. - other systems use those - but the stuff which is common to any GNU/Linux distro. Obviously this applies even more if you also are learning stuff like ls, grep, cd etc. (which might be true if you're moving from Windows rather than, say, OS X or one of the BSDs).
    Last edited by cfr (2013-10-31 23:30:15)

  • Btrfs Arch-based rescue images

    From linux-btrfs mailing list today :
    http://comments.gmane.org/gmane.comp.fi … btrfs/3150
    Hello everyone,
    As Linus discovered, the new btrfs disk format in 2.6.31-git can be
    problematic if your FS gets forward rolled to the new format and you end
    up bisecting back to the old code.
    It would also be nice to have a way to run btrfsck on a root filesystem
    and do other assorted tasks.  So, I'm making live boot usb images for
    both x86 and x86-64.
    They should have enough to get your filesystems mounted and they also
    include git, gcc, make and enough to compile the kernel.  These are
    based on the Arch 2.6.30 distro with just the btrfs newformat code
    added.
    I've got the 32 bit image uploaded, and I'll queue up 64 bit overnight.
    If anyone is feeling brave, just dd the image onto a usb stick and
    rescue boot away.
    They work on both of my test boxes, but a little extra testing would be
    nice.
    Edit :
    Additional link http://btrfs.wiki.kernel.org/index.php/Rescue_me
    Last edited by Nezmer (2009-06-16 21:01:33)

    sekenre wrote:
    I've just found this: https://bbs.archlinux.org/viewtopic.php?id=18424
    An arch based bootdisk that's only 30MB? I've got a way to go!
    It says "Many utils are supplied by busybox" so I'd call it loosely based on Arch.

  • Bodhi Linux Arch-based build, need dev(s) and supporting team members

    Hello forum,
         First, apologies if I have posted this topic in the wrong thread. I am writing to inquire as to whether or not there are any other Arch users and/or developers that would be interested in assisting Jeff Hoogland with his new distro, Bodhi Linux, and working on an Arch-based build. Bodhi Linux is a Ubuntu-based distribution that uses Enlightenment as the desktop environment and is focused on promoting the light weight, beauty, and speed of Enlightenment while remaining minimalist. Jeff has plans to release a Fedora-based version of Bodhi in the future, as well as an Arch-based build, but he would need some help, specifically with the OS disc itself. He can work on the Enlightenment side of things. Is there anyone interested in working on such a project? If you haven't heard of Bodhi Linux already, please visit http://bodhilinux.com/

    Greg_S. wrote:ANOKNUSA, you think it's wasted energy? "Throw-away distro" is it?
    Sorry if this seems unduly harsh.  I wasn't trying to troll, but merely reiterating what others here have said.  The Bodhi Linux developers are certainly within their right to direct their efforts in any way they wish.  However, they have two serious conceptual flaws they need to consider and overcome:
    1)  Are the devs planning on releasing both x86 and AMD64 versions of Bodhi?  Even if not, this still means that once the project gets going, they'll need to build the entire E17 compilation three times a week; if so, they'll need to do so six times a week.  This is very tedious and time-consuming for a group of people working in their spare time, with no financial backing or chance for compensation.  Naturally, it leaves very little time to maintain the rest of the repos, discuss/research/pursue further development, track bug reports, etc.  The latter is worth noting, since
    2)  The devs will need to keep track of bugs and development roadmaps for three different distros, each with their own kernel patches, boot/init protocols, etc.  They'll need to build separate packages and "tune" separate repos for each spin, provide a forum(s) able to handle questions regarding each spin, with devs and moderators specializing in each spin.
    This is an awful lot of work to simply "showcase E17 and give it the 'love' it deserves."  The Enlightenment devs are the ones providing the weekly snapshots on SVN; the Bodhi devs just package them.  If promotion of Enlightenment DR17 is the ultimate goal, it could be better accomplished by establishing and promoting a PPA for Ubuntu, a PKGBUILD or PUR for Arch, and a (name of unofficial repo here) for Fedora.  This would make an up-to-date version of E17 readily available, and require only promotion and packaging on the part of the maintainers.  Bug reports could be sent directly to the Enlightenment folks with no need for an intermediary, as well as to the appropriate distro, rather than sending them to Bodhi which must then check to see if the problem is one extant in the base distro concerned before applying efforts to fix the problem.  Just think: you get a bug report and begin to reseach it, only to find out it's a problem you inherited from Ubuntu which in turn inherited it From Debian [unstable].  Where does that leave you?  If you do manage to fix the problem, then the only decent thing to do would be to share whatever patch/code changes you made with the folks upstream anyway.
    I ain't trying to be a killjoy here, and I'm definitely not trying to discourage the commitment and spirit of contribution the Bodhi folks obviously have; just the opposite.  Besides, it does look like you found at least one Archer willing to help you guys, so whatever ends up happening, I wish you all good luck with it.

  • Lunar linux and sourced based distros in general

    Whilst looking for versions of linux that I haven't tried as of yet, I stumbled across Lunar.
    Distrowatch:
    Lunar is a source based Linux distribution with a unique package management system which builds each software package, or module, for the machine it is being installed on. Though it can take a while to do a complete Lunar installation it's worth it as it tends to be quite fast, once installed! In the beginning Lunar was a fork of Sorcerer GNU Linux (SGL). The fork occurred in late January to early February of 2002 and was originally made up of a small group of people who wanted to collaboratively develop and extend the Sorcerer technology. The original name for the project was Lunar-Penguin but the group decided to re-christen it Lunar Linux while the Lunar-Penguin name has become a sort of umbrella which the team could use if they decide to collaboratively develop something besides Lunar Linux.
    Has anyone tried this flavour yet? Might give it a whirl on a VM (compile times on a VM might be a deal breaker though!). Something which strikes me as odd is the fact the forums are closed.. link. I cant find any information as to why this is the case.
    Does the community think that sourced based distributions are better than pre-compiled versions? There dont seem to be that many sourced based about, but of those that are they seem to tout speed as a big plus.
    Gentoo "Extreme performance, configurability and a top-notch user and developer community are all hallmarks of the Gentoo experience".
    Lunar "locally compiling an optimized system tailored toward the users specific needs. This should result in a lean and optimized operating system for example both tout speed as being one of their major plus points".
    Is the linux world lazy, and just like the ease of .deb .rpm pacman etc? Because if sourced based is better, then surely there would be more sourced based distros about? So this leads me to think that either potential sourced based bonuses dont outweigh the time it takes to compile, or the linux world is just plain lazy (hardware issues aside as a reason not to used sourced based).

    ryuslash wrote:
    I've tried it a couple of times, but I've never gotten it to work, always with installing something some dependency couldn't be met because it couldn't be found on the server. Too bad too because I really thought it could be interesting...
    Oh well, now I've found arch
    Same experience here.
    I won't call Lunar a bad distro. It has some appeal for a small niche-within-a-niche. However, because of the small size of the project and community, the quality suffers.
    I've tried it in the past on the most generic hardware I had at the time and there were always installation issues which turned out to be showstoppers for me.
    There are so many distros, yet in my view, there are so few high-quality distros.
    Debian (big), Slackware (small), Arch (small), Fedora (big), and Centos (small) are all good, solid distros.
    I find once I venture outside of these solid systems, lack of quality and annoying bugs manifest themselves. And even though a project may look intriguing for its innovation or fresh approach, unexpected behavior is to be expected.
    YMMV

  • New FaunOS Live Arch-Based DVD/USB Distro Now Available

    Hello fellow archers,
    We have just released the latest version of FaunOS. Since this version of FaunOS is the answer to the most important question in the universe, we have named it "fortytwo."
    FaunOS-fortytwo contains many improvements over previous releases and more packages (575 total). Improvements, in no particular order, include:
    - Improved wireless support, both wlassistant and knetworkmanager are now included.
    - Improved automatic X configuration with 3D acceleration.
    - Better boot splash support. We have moved to fbsplash which seems to work pretty consistently and has lead to a faster boot time.
    - A new boot option for quickly booting into a console-based system with no X windows.
    - A new boot option for machines that hang when booting from DVDs using piix modules.
    - Ability to save FaunOS session back to a multi-session DVD-+R or DVD-+RW.
    - Permanent Arch Linux Installer using archin.
    - Permanent FaunOS Installer for creating additional FaunOS USB drives from within FaunOS and for performing a "frugal" install to hard drive. Frugal install (not to be confused with Frugal Linux) installs the compressed FaunOS files to a hard drive permanently leading to an "unbreakable desktop" meaning the end user can totally ruin everything at runtime. To revert back to the starting point all the user has to do is reboot the machine and everything goes back to normal since all changes happen in ram, unless the FaunOS session is saved at boot time.
    - FaunOS is probably the only live distro that can perform two kinds of installations.
    - New added packages include: wlassitant, madwifi, firmware packages for ipw2100 and ipw2200, ndiswrapper, lynx for text-based web browsing, and kmobiletools accessing phone books and other information on mobile phones.
    - All packages have been upgraded to the latest from the Arch repos as of today, 8/27/2007.
    - And, most importantly, a new logo.
    We have also decided to stay away from the evil 2.6.22 kernel which seems to have created more bugs and headaches than introducing new features, no flame war intended. The latest 2.6.21-faunos kernel is based on the stock arch kernel with the addition of the fbsplash patch from genpatches.
    There are those people that may think FaunOS is bloated, but we like to think that it is a muscular and strong live Linux distribution, thanks to Arch. Of course keeping with Arch's KISS principal, we have tried to make FaunOS simple and easy enough for anyone to use.
    You can get the latest version at:
    http://www.faunos.com/downloads/faunos-fortytwo
    A new wiki has been created at http://wiki.faunos.com. Feel free to contribute and change the wiki as you wish.
    Our support and discussion forums can still be found at http://forum.faunos.com
    We can definitely use some mirrors for our downloads. We will also be creating a torrent shortly and can use some seeders. Please let us know either here or in the FaunOS forums if you can help in any way.
    We'll see ya at the FaunOS forums!
    So long and thanks for all the fish,
    Raymano

    We have simply used larch but with some additions and changes:
    - FaunOS uses a slightly modified version of larch with the added ability to build a live system from a preinstalled partition on the harddrive.
    - Added fbsplash capabilities to the initial initrd images and kernel.
    - Applications on FaunOS are preconfigured and integrated to work out of the box.
    - Some kernel specific modules/packages have been compiled for the FaunOS kernel, e.g. ndiswrapper.
    - All services are pre-configured to execute out of the box.
    - All available codecs are included.
    - 3D desktop using beryl is preconfigured to run on intel based graphics cards and some ATI cards with a click of a button.
    - Network management is simplified with use of knetworkmanager and wlassistant.
    - Storage are is included on the FaunOS device to share files with other platforms.
    - R/W access Windows parititions by clicking on an icon in KDE.
    - Common grub booting on USB and DVD. With multiple boot options for graphical and non-graphical system.
    - FaunOS's own mkxorgconf utility was added (using hwd) for better automatic configuration of graphics cards. This includes setting up AIGLX.
    - Easily performs frugal install of the live FaunOS system to hard drive, including saved overlays. This was not part of the original larch scripts.
    - Use of sudo to allow the user to perform certain system wide configuration tasks.
    - Integrated flash java and mplayer plugins for Firefox.
    - Ability to put a computer running FaunOS into sleep (suspend-to-ram), remove the FaunOS media, boot and work on other computers with the FaunOS device, return to the original computer, insert the FaunOS device, turn on the computer and continue working where you left off. This in not possible with latest Arch Linux because of the kernel.
    - And we believe, most importantly, you can hand a FaunOS DVD to a user with no knowledge of Linux and say go try this out.
    Last edited by raymano (2007-10-09 17:38:40)

  • Is it possible to use Arch like a source-based distro?

    I installed Gentoo on a spare box recently, and rather liked the idea of a source-based distribution. It's nice to think that the natively compiled code is optimized for my processor, even though even many Gentooists admit that the practical performance gains are minimal. However, Gentoo is less KISS-oriented and less bleeding edge than Arch, and I love Arch too much to switch anyway. I was wondering if one could recompile an entire Arch system using processor-specific optimizations like Gentoo, and maybe even have some equivalent of Gentoo USE flags? I can't manually recompile every package, and then do it again every time there's an upgrade - that would be too tedious. So, is there some automated method - to essentially use Arch like a source-based distribution? Can ABS help, or maybe a community-contributed tool? And finally, for a source-based and yet Arch-like distribution, what do you guys think of CRUX? Given that their documentation and community is much smaller than ours, is it very bothersome to install and maintain a desktop system using CRUX?

    Xyne wrote:
    Rebuild everything from source:
    bauerbill --build-all -S $(pacman -Qq)
    Build all available upgrade from source, including dependencies:
    bauerbill --build-all -Syu
    Install new package by building from source, including dependencies:
    bauerbill --build-all -S <pkgname>
    Bauerbill also provides an "AutoPatch" option that enables you automatically apply patches to PKGBUILDs and install files when building from source so you only have to edit a PKGBUILD once.
    *edit*
    Of course, you could simply enable "BuildAll" in the configuration file and skip the flag.
    @Xyne
    So bauerbill will build all the deps for packages from source too [dependency resolution] and build from source packages from groups [ex. xorg, gnome, kde, xfce4, etc]?? I'm having a hell of a time with pacbuilder as it's not as functional as I had hoped, so I am thinking of using bauerbill, if it does what I need or is actually functional as pacbuilder but more functional [deps, patching, etc] then i'll use it exclusively! Thanks for any help.
    Last edited by Chaniyth (2010-08-19 02:49:14)

Maybe you are looking for