You are not logged in.
How long did it take you to create Crunchbang Linux? How many hours? Did you use something like Linux from Scratch?
This is a typical newbie question but I would appreciate it if you would answer it.
**************
[Moved from "Elementary School]
Last edited by damo (2015-10-28 10:47:02)
Offline
Well, a couple of points -
- This is BunsenLabs, so you would have to contact @corenominal to find out what he did to produce Crunchbang.
- The basic isos are from those supplied by Debian; live build was configured; several people have made artwork, themes, scripts, configurations, packages, repos; lots of time talking behind the scenes and checking things.
The process was started last February, approximately, and we are still tweaking! Thousands of manhours probably.
(And it is not a usual "noob" question!")
Last edited by damo (2015-10-28 10:56:34)
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
Of course I meant Bunsen Labs. And not an usual noob question? Maybe I am an expert now, lol. Thank you for your answer.
Last edited by CooKiECruNChEr43 (2015-10-28 11:06:59)
Offline
To add to what damo said, the ISOs were created using Debian live-build...
http://live.debian.net/
http://live.debian.net/manual/4.x/html/ … al.en.html
https://packages.debian.org/jessie/misc/live-build
Each ISO has to be built on a system that uses the architecture you want to create, so I had to add a partition to my disk and install Debian 64 bit in addition to the 32 bit partition I normally use.
On my laptop, each build takes between 1 and 2 hours, depending on if I'm using cached packages or not (see the manual). I was pretty lucky in figuring out the sometimes confusing manual well enough to create a working ISO, but I had to build several ISOs before we came up with one suitable for general testing, and several more for each release we've done. Heck, just to correctly implement the BunsenLabs-branded installer took half a dozen tries (there's almost no documentation for that).
I can't speak for nobody's work in setting up the web presence and creating the repository packages and torrents, or johnraff and damo's in transferring and improving on all the #! scripts, or Sector11, Ututo and everyone else's who has contributed, but between themes and builds I've spent dozens and dozens of hours on it.
I don't care what you do at home. Would you care to explain?
Offline
The process was started last February, approximately, and we are still tweaking! Thousands of manhours probably.
Hours for which I, for one, am very grateful and thankful!
The servant lifted off a kind of ottoman a long peacock-blue drapery, rather of the nature of a domino, on the front of which was emblazoned a large golden sun, and which was splashed here and there with flaming stars and crescents. “You’re to be dressed as Thursday, sir,” said the valet somewhat affably.
Offline
damo wrote:The process was started last February, approximately, and we are still tweaking! Thousands of manhours probably.
Hours for which I, for one, am very grateful and thankful!
![]()
+1 and waiting for the donate button on the main site.
Last edited by KrunchTime (2015-10-28 22:28:11)
Offline
If you're talking build time, I think the person you'd want to hear from is nobody; he's the one who actually builds the live images. From what I hear, once you've set the proper hooks, the build process itself is just a matter of processor time.
Actual development, on the other hand, requires multiple massively parallel processors (neural nets, i.e. human minds) spending countless hours on the various details. IMHO, johnraff did a great deal of the heavy lifting with his "Wally" project at the CrunchBang forums.
Be excellent to each other, and...party on, dudes!
BunsenLabs Forum Rules
Tending and defending the Flame since 2009
Offline
If you're talking build time, I think the person you'd want to hear from is nobody; he's the one who actually builds the live images. From what I hear, once you've set the proper hooks, the build process itself is just a matter of processor time.
Is the build time is that long, because the live-build scripts are building every package from source?
Offline
If you're talking build time, I think the person you'd want to hear from is nobody; he's the one who actually builds the live images. From what I hear, once you've set the proper hooks, the build process itself is just a matter of processor time.
I do the builds, nobody creates the torrents from my ISOs and the Bunsen debs from the GitHub sources. Early on, I gave nobody all the live-build configs I had been using and a walk-through and he came back with "Well, I've built something."
"What we got back didn't live long, fortunately."
live-build is not all that well documented, and the Debian installer even less so. It's been a lot of trial and error, and very, very, very time consuming.
/vuvuzela
I don't care what you do at home. Would you care to explain?
Offline
@hhh: Didn't realize the builds were yours; you do great work! FWIW, I was just going off what the baconator had told me about the live build process.
@ostrolek: My only experience with the live build process is a minimal Debian installation, and that took about 20 minutes on a triple-core AMD machine; take from that what thou wilt.
Last edited by pvsage (2015-10-29 15:01:42)
Be excellent to each other, and...party on, dudes!
BunsenLabs Forum Rules
Tending and defending the Flame since 2009
Offline
Build time is dependent on processor speed, how many packages are being installed and whether they have already been cached or not, meaning the first build will be the longest. live-build doesn't build packages from source but it does have to download all the debs at least once...
http://live.debian.net/manual/4.x/html/ … n.html#321
If you've ever done a netinstall or a dist-upgrade, you know how long it takes to, for example, install or upgrade Xorg. live-build is in effect doing an install or an upgrade of the entire system every time you do a build.
I don't care what you do at home. Would you care to explain?
Offline
How much time it takes to build one system with packages from Debian? More than 1 1/2 hour? Does the live-build create a live iso? Do you add the custom bunsenlabs apps after or before?
Yes, I install through netinstall, just the basics + xorg, then boot into the system and install the rest.
Offline
This part I can answer:
Does the live-build create a live iso?
Yes; "It does exactly what it says on the tin."
For the rest, you'll have to ask Hasselhoff, assuming you can get back on his good side.
Be excellent to each other, and...party on, dudes!
BunsenLabs Forum Rules
Tending and defending the Flame since 2009
Offline
Read post #4, read the manual, read the man pages, run the provided tutorials, etc...
I don't care what you do at home. Would you care to explain?
Offline
This part I can answer:
ostrolek wrote:Does the live-build create a live iso?
Yes; "It does exactly what it says on the tin."
What I meant was, does it make a live iso together with the bunsenlabs apps.
Offline
You have eyes but you don't see...
http://live.debian.net/manual/4.x/html/ … n.html#448
/hand holding
I don't care what you do at home. Would you care to explain?
Offline
You have eyes but you don't see...
http://live.debian.net/manual/4.x/html/ … n.html#448/hand holding
I don't need any hand holding. You say it takes so much time to create the live iso, that's why the question. Its not that hard to understand the live-manual, but I never tried to build a live iso that way.
Offline
It basically creates a chroot environment, downloads all the debs, including those for BunsenLabs I wold presume and install them into the chroot with some caveats (initrd changes are blocked from triggering, for example.) It will also install the live packages needed to buiild a live iso assuming you configured it to do so. Once it is done with the build process, it goes into mksquashfs to build up the iso. It will then do some cleanup.
This is a rough idea of how it goes, and yes even on a good machine it can take quite some time.
But aside from that is how much hhh has to keep track of in order to make sure that all the little details end up in the live build. I have enough trouble keeping track of my own changes, let alone those of an entire community wanting this detail or that.
Last edited by tknomanzr (2015-10-29 17:56:56)
Offline
Fortunately, I'm not alone in that department, but even then things get lost in the shuffle.
I don't care what you do at home. Would you care to explain?
Offline
It basically creates a chroot environment, downloads all the debs, including those for BunsenLabs I wold presume and install them into the chroot with some caveats (initrd changes are blocked from triggering, for example.) It will also install the live packages needed to buiild a live iso assuming you configured it to do so. Once it is done with the build process, it goes into mksquashfs to build up the iso. It will then do some cleanup.
This is a rough idea of how it goes, and yes even on a good machine it can take quite some time.
Thank you for the write-up.
That's what it does. I read the whole manual, before I asked whether(why) it takes so long. If hhh didn't mention it, I wouldn't even have thought about it. I've just been reading every file in live-build scripts. It is a headache to build a live iso this way. You are not really sure of the result, until you try it out.
Offline