Thursday, May 26, 2011
Plistic GNU/Linux Journal
I decided that I'd be better off writing programs than creating a Linux Distro From Scratch. So... I installed Fedora 15. Now all I have to do is think of a program to write... It's not as easy as it sounds. Anyway, just thought I'd post that Plistic GNU/Linux - in it's short life - is being discontinued.
Tuesday, May 24, 2011
Plistic GNU/Linux Journal
Well, I started over yet again! It wasn't due to problems, it was more or less due to a wild-hair I had to itch. I decided to try to install GNU/Hurd. After I repartitioned my hard-drive I found out that SATA isn't supported by GNU Mach / Hurd. So, I couldn't install it because my computer uses SATA. So, I'm back at ground-zero with building the LFS-system.
Well, I'm just starting chapter 6 again. I'm in the middle of waiting for Glibc to compile. This time around I didn't install any X Window System on the host system. I'm only using a terminal window anyway, so why bother installing the GUI stuff? I just installed the necessities for building LFS.
Well, I'm just starting chapter 6 again. I'm in the middle of waiting for Glibc to compile. This time around I didn't install any X Window System on the host system. I'm only using a terminal window anyway, so why bother installing the GUI stuff? I just installed the necessities for building LFS.
Sunday, May 22, 2011
Plistic GNU/Linux Journal
I'm currently running the torture tests for GCC. I hope it finishes soon so I can continue building the LFS-system. My plan is to build an LFS-system. Then from the LFS-system build another LFS-system that is the same. After that, I'll be building another LFS-based-system, but the new system will use upstart instead of sysvinit. Once I figure out what programs I want to be in my core distribution, then I'll try to build RPM into the tool-chain and see if my theory of using RPM in the tool-chain to install all the programs works.
The reason why I'm building an LFS-system twice is so that the host system to build LFS is a homemade system. That way every single program on the computer will be built with programs that I compiled myself. It might seem unnecessary, but this is my project and that's how I want to do it.
The reason why I'm building an LFS-system twice is so that the host system to build LFS is a homemade system. That way every single program on the computer will be built with programs that I compiled myself. It might seem unnecessary, but this is my project and that's how I want to do it.
Saturday, May 21, 2011
Plistic GNU/Linux Journal
As promised. I bought some Rum! Time for some "drunkin' computing" as I work on Plistic GNU/Linux again. I'm in the middle of the Linux From Scratch book (somewhere in chapter 6). When there are long compiles I will be writing in this journal. Stay tuned!
A side note: I started over in building LFS. I had some issues using Fedora. Maybe I didn't do something right in the process, but just to be safe I installed Debian 6.0.1a as my working environment. I know that Debian doesn't use SELinux, which could be trouble-some - possibly. Anyway, I'll keep you posted!
I just noticed. I'm starting to feel the Rum working! This is good news! I'm a little buzzed. I almost forgot how this feels. It is good.
I think when I get to building gcc I'm going to play a round of Starcraft II. I don't play it much; even though it was the excuse for replacing Linux with Windows on this machine. I think I'll do a one-on-one match instead of the campaign. I'll let you know how I do. Hmmm... do I be Terain, Protoss, or Zerg? I like the Protoss flying units, I like the Zerg for their Playboy-style reproductive-ness, and, well, the Terain are like people on Earth, so maybe I should be Zerg. I suck at the game no matter which race I choose, so it shouldn't really matter. Also, this computer is shit. So, that's part of my excuse for sucking so bad.
Okay, now I'm good an drunk. And... Guess what? I'm also at the GCC compile time. Time for dunkin' Starcraft II! In the next paragraph, I'll tell you how I did... I definitely am drunk. I just walked around a bit (and wobbled while I walked) so i know for sure that the Rum has done it's job! Well, my Starcraft II program is around 88% complete with it's update. And GCC is building as we speak (It's estimated build time is about 44 SBU's, which amount to -- A LONG ASS TIME!!!). So, as soon as Starcraft II is done updating, I'll be on my way to battling an unsuspecting foe.
Well, I didn't even find the enemy base by the time they killed me. That is totally sucky. And... it had nothing to do with my slow PC... My computer didn't experience any slowdowns (which is surprising). However, we were both Zerg, and he killed me by creating a small army of Mutalisks. All I had was a bunch of Zerglings and a couple of Hydralisks. I couldn't even find his base before I was destroyed! Drunk or not, I would have done the same. As I stated earlier... I suck at this game!
GCC is still compiling. I think I'm gonna go pee, then we'll see what I do next.
I just puked in the toilet. Time to stop drinking I think. I just poured myself a glass of straight Coca-Cola. The room was spinning for awhile, then I felt sick, so I vomited, now I feel a little bit better. I figure, I better sober-up before I go to sleep or I will be regretting it in the morning. Oh, and good news! GCC is done compiling, so it's time to continue on with building an LFS-system. BTW, I finished almost a half-a-bottlle of Rum. It's only 70-proof. I remember I used to be able to hold half-a-bottle of 151-proof Rum in the past (without puking). Must be because I'm out of practice. That's not a bad thing. I'm not much for drinking these days.
Well, it's the morning after now... I don't think I'll do that again. I'm not much for feeling sick and puking. Surprisingly, I don't have a hang-over. I feel fine now. I think for the rest of my Rum, I'll limit myself to one drink a night and only on the weekend. That bottle should last me the rest of the summer.
Next time I do a "drunkin' computing" night I think I'll do a "caffeinated beverage computing" thing instead. Drinking made me feel sleepy. That's an effect I don't remember happening before. As I said, it's been years since I drank more than one beer in a night. I don't usually buy any type of alcoholic beverage, and I think I'm going to keep it that way. "Drunkin' computing" is something I did about seven years ago. Maybe my body has changed so it rejects alcohol, I don't know. But, last night wasn't as fun as I remember it. Oh well. Live and learn I guess.
A side note: I started over in building LFS. I had some issues using Fedora. Maybe I didn't do something right in the process, but just to be safe I installed Debian 6.0.1a as my working environment. I know that Debian doesn't use SELinux, which could be trouble-some - possibly. Anyway, I'll keep you posted!
I just noticed. I'm starting to feel the Rum working! This is good news! I'm a little buzzed. I almost forgot how this feels. It is good.
I think when I get to building gcc I'm going to play a round of Starcraft II. I don't play it much; even though it was the excuse for replacing Linux with Windows on this machine. I think I'll do a one-on-one match instead of the campaign. I'll let you know how I do. Hmmm... do I be Terain, Protoss, or Zerg? I like the Protoss flying units, I like the Zerg for their Playboy-style reproductive-ness, and, well, the Terain are like people on Earth, so maybe I should be Zerg. I suck at the game no matter which race I choose, so it shouldn't really matter. Also, this computer is shit. So, that's part of my excuse for sucking so bad.
Okay, now I'm good an drunk. And... Guess what? I'm also at the GCC compile time. Time for dunkin' Starcraft II! In the next paragraph, I'll tell you how I did... I definitely am drunk. I just walked around a bit (and wobbled while I walked) so i know for sure that the Rum has done it's job! Well, my Starcraft II program is around 88% complete with it's update. And GCC is building as we speak (It's estimated build time is about 44 SBU's, which amount to -- A LONG ASS TIME!!!). So, as soon as Starcraft II is done updating, I'll be on my way to battling an unsuspecting foe.
Well, I didn't even find the enemy base by the time they killed me. That is totally sucky. And... it had nothing to do with my slow PC... My computer didn't experience any slowdowns (which is surprising). However, we were both Zerg, and he killed me by creating a small army of Mutalisks. All I had was a bunch of Zerglings and a couple of Hydralisks. I couldn't even find his base before I was destroyed! Drunk or not, I would have done the same. As I stated earlier... I suck at this game!
GCC is still compiling. I think I'm gonna go pee, then we'll see what I do next.
I just puked in the toilet. Time to stop drinking I think. I just poured myself a glass of straight Coca-Cola. The room was spinning for awhile, then I felt sick, so I vomited, now I feel a little bit better. I figure, I better sober-up before I go to sleep or I will be regretting it in the morning. Oh, and good news! GCC is done compiling, so it's time to continue on with building an LFS-system. BTW, I finished almost a half-a-bottlle of Rum. It's only 70-proof. I remember I used to be able to hold half-a-bottle of 151-proof Rum in the past (without puking). Must be because I'm out of practice. That's not a bad thing. I'm not much for drinking these days.
Well, it's the morning after now... I don't think I'll do that again. I'm not much for feeling sick and puking. Surprisingly, I don't have a hang-over. I feel fine now. I think for the rest of my Rum, I'll limit myself to one drink a night and only on the weekend. That bottle should last me the rest of the summer.
Next time I do a "drunkin' computing" night I think I'll do a "caffeinated beverage computing" thing instead. Drinking made me feel sleepy. That's an effect I don't remember happening before. As I said, it's been years since I drank more than one beer in a night. I don't usually buy any type of alcoholic beverage, and I think I'm going to keep it that way. "Drunkin' computing" is something I did about seven years ago. Maybe my body has changed so it rejects alcohol, I don't know. But, last night wasn't as fun as I remember it. Oh well. Live and learn I guess.
Saturday, May 14, 2011
Plistic GNU/Linux Journal
I haven't done "drunkin' computing" for years... As a matter of fact, I haven't gotten drunk in years. I barely drink at all these days.
I was thinking... I used to do "drunkin' programming" once in awhile. It's a fun experience! If you've never programmed while drunk, you're missing out. I think I'm going to try "drunkin' computing" sometime in the near future.
When I'm going to start a new crazy idea such as building a "Linux Distro" I better have a good explanation for doing such a crazy thing. I mean, let's face it, there are literally tons of distributions to choose from. So, why create a new one? My excused could be "I was drunk one night and just started messing around." That would be a good excuse if you ask me.
Anyway, just thought I'd throw the idea of "drunkin' computing" out there.
As a side thought, "I wonder how much software drinking has produced."
Well, I don't have any liquor on hand, so I'm going to have to do this sober for awhile. Maybe next weekend I'll get some booze. We'll have to wait and see. Anyway, onto the next part... Building the LFS System. I thought I'd have my journal up so I can comment on the progress as I go through the motions.
As I read the LFS book, I keep in the front of my mind that I'm going to be using RPM... I just got to the section about chrooting into the LFS environment which contains only the tool-chain. It occurred to me that RPM is just another tool. Perhaps what needs to be done is to build RPM into the tool-chain. Then use the RPM tool from the chrooted environment to install every package. This means that I'd need to prep an RPM Package for every program that is to be installed. I wonder what order the packages need to be installed in. Do I install RPM first and then use the newly installed RPM instead of the one in the tool-chain? Or do I install them all using the tool-chain RPM? I'm sure all of these questions will answer themselves once I get to doing it.
Back to Building the LFS System. I haven't even done anything (except read) yet.
I thought I'd take a short recess from LFS. Some of this stuff it tedious. Right now, I'm manually creating config files using the "cat" command in a terminal window. It's mindless copy what the book says kinda-work. But, it must be done to get an LFS system going. I can't wait until I get to the part where I can experiment with things. I'm going to save my experimenting for LFS-Round-Two though. I figure it would be best to get a working system before trying to change things. So, when I build my second LFS it will be called LFSRPM because I'm going to try to build the basic LFS system using RPM's instead of "make install" scripts.
I'm finally compiling Glibc. The first big program in my new LFS system. I thought while larger programs compile I should post journal entries because all I have to do is wait for them to finish. Might as well take this time for some out-loud thoughts...
Okay. When I build a Busy Box live USB Linux System I ran into a problem of chrooting into the live system. The problem was that I had to recreate my /dev directory. I think I stumbled onto the solution to that. In LFS I had to issue a "mount --bind" command on the /dev directory. This made a duplicate of the directory in question. So, the solution (I think) will be to issue a "mount --bind /dev /plistic/dev" before chrooting into the /plistic directory. I'm not sure exactly if this was the problem or not... I haven't booted my Plistic USB in about a year; I'm just basing this analysis off of faint memories. However, the "mount --bind" command is new to me. See, I learned something already!
I'm running the test-suite for Glibc now. I noticed that SELinux denied some of the tests. The test program (after a long long wait) came back with an error, and I didn't even have to look at the log. SELinux is the problem. I hope that switching it to permissive mode will work. Oh! It just finished. It must not have had to compile as many tests this time around! Time to verify the log file... No errors! Huh, I was expecting at least a couple. Oh well, as long as it works.
I was thinking... I used to do "drunkin' programming" once in awhile. It's a fun experience! If you've never programmed while drunk, you're missing out. I think I'm going to try "drunkin' computing" sometime in the near future.
When I'm going to start a new crazy idea such as building a "Linux Distro" I better have a good explanation for doing such a crazy thing. I mean, let's face it, there are literally tons of distributions to choose from. So, why create a new one? My excused could be "I was drunk one night and just started messing around." That would be a good excuse if you ask me.
Anyway, just thought I'd throw the idea of "drunkin' computing" out there.
As a side thought, "I wonder how much software drinking has produced."
Well, I don't have any liquor on hand, so I'm going to have to do this sober for awhile. Maybe next weekend I'll get some booze. We'll have to wait and see. Anyway, onto the next part... Building the LFS System. I thought I'd have my journal up so I can comment on the progress as I go through the motions.
As I read the LFS book, I keep in the front of my mind that I'm going to be using RPM... I just got to the section about chrooting into the LFS environment which contains only the tool-chain. It occurred to me that RPM is just another tool. Perhaps what needs to be done is to build RPM into the tool-chain. Then use the RPM tool from the chrooted environment to install every package. This means that I'd need to prep an RPM Package for every program that is to be installed. I wonder what order the packages need to be installed in. Do I install RPM first and then use the newly installed RPM instead of the one in the tool-chain? Or do I install them all using the tool-chain RPM? I'm sure all of these questions will answer themselves once I get to doing it.
Back to Building the LFS System. I haven't even done anything (except read) yet.
I thought I'd take a short recess from LFS. Some of this stuff it tedious. Right now, I'm manually creating config files using the "cat" command in a terminal window. It's mindless copy what the book says kinda-work. But, it must be done to get an LFS system going. I can't wait until I get to the part where I can experiment with things. I'm going to save my experimenting for LFS-Round-Two though. I figure it would be best to get a working system before trying to change things. So, when I build my second LFS it will be called LFSRPM because I'm going to try to build the basic LFS system using RPM's instead of "make install" scripts.
I'm finally compiling Glibc. The first big program in my new LFS system. I thought while larger programs compile I should post journal entries because all I have to do is wait for them to finish. Might as well take this time for some out-loud thoughts...
Okay. When I build a Busy Box live USB Linux System I ran into a problem of chrooting into the live system. The problem was that I had to recreate my /dev directory. I think I stumbled onto the solution to that. In LFS I had to issue a "mount --bind" command on the /dev directory. This made a duplicate of the directory in question. So, the solution (I think) will be to issue a "mount --bind /dev /plistic/dev" before chrooting into the /plistic directory. I'm not sure exactly if this was the problem or not... I haven't booted my Plistic USB in about a year; I'm just basing this analysis off of faint memories. However, the "mount --bind" command is new to me. See, I learned something already!
I'm running the test-suite for Glibc now. I noticed that SELinux denied some of the tests. The test program (after a long long wait) came back with an error, and I didn't even have to look at the log. SELinux is the problem. I hope that switching it to permissive mode will work. Oh! It just finished. It must not have had to compile as many tests this time around! Time to verify the log file... No errors! Huh, I was expecting at least a couple. Oh well, as long as it works.
Friday, May 13, 2011
Plistic GNU/Linux Journal
Well, I built a crappy computer that has a big hard-drive (1.5TB). The video on it sucks (it can’t do much), so I figure I can use it for building a GNU/Linux distribution. I toyed with the idea about a year ago and I actually made a live system on a USB-drive. All you could do was login and browse around the directory structure, but it was a start. I used Busy Box for the basis of the system.
I want to build a better system that I can actually call a distribution. The reason behind all of this is that I am not satisfied with any of the “Linux Distros” out there. Non of them do everything “right”. They all have strengths and weaknesses. The biggest weakness that I find with distributions that I like is that they install all sorts of programs on the system. So, when I install a distro, the first thing I do is spend an hour hunting down packages to remove. It’s time-consuming and annoying.
I know that building a distribution is a big job. It took me a long time just to figure out how to make a simplistic Busy Box based system to boot and operate properly. However, if I can figure out how to do this, I think it will be well worth it. This distribution isn’t going to be much and it probably will never see the Internet for download, but it’s a hobby-project that I can feel good about. There is much to learn and that is one of the reasons for this. I also think that some distributions make too many releases. I think that a release once every year or two is adequate.
To start out, I’m building an LFS (Linux From Scratch) system. This way I’ll get a quick refresher on what goes into a basic system. Next, I’ll be trying to add RPM support (I like RPM). Once that is in place, then I’m going to figure out how to create a live system on a USB-drive using the LFS-based system. Then, I’ll be creating install scripts to install the live system to the hard-drive.
There will be a lot of work just to do that. But, I have more plans... I want to use a yum repository system and setup an add-on repository for installing the X Window System and other free packages. I also want this distribution to remain GNU-compliant, so that means nonfree packages are not allowed.
The repository structure will be something like this:
My development machine partitions configuration:
I just finished building the LFS tool-chain. Now time to decide on the bare-minimum packages to install on the base-system. Here's the package list (stripped from the LFS-6.8 book).
plistic-core:
I'm not sure how this will work. The big question with RPM is how do I add RPM packages to the system if they are already installed on the system? Do I just install the RPM and overwrite the existing files so the RPM-DB is updated? Anyway, that's a ways away, so I shouldn't fret over it quite yet. I have a lot to learn!
I want to build a better system that I can actually call a distribution. The reason behind all of this is that I am not satisfied with any of the “Linux Distros” out there. Non of them do everything “right”. They all have strengths and weaknesses. The biggest weakness that I find with distributions that I like is that they install all sorts of programs on the system. So, when I install a distro, the first thing I do is spend an hour hunting down packages to remove. It’s time-consuming and annoying.
I know that building a distribution is a big job. It took me a long time just to figure out how to make a simplistic Busy Box based system to boot and operate properly. However, if I can figure out how to do this, I think it will be well worth it. This distribution isn’t going to be much and it probably will never see the Internet for download, but it’s a hobby-project that I can feel good about. There is much to learn and that is one of the reasons for this. I also think that some distributions make too many releases. I think that a release once every year or two is adequate.
To start out, I’m building an LFS (Linux From Scratch) system. This way I’ll get a quick refresher on what goes into a basic system. Next, I’ll be trying to add RPM support (I like RPM). Once that is in place, then I’m going to figure out how to create a live system on a USB-drive using the LFS-based system. Then, I’ll be creating install scripts to install the live system to the hard-drive.
There will be a lot of work just to do that. But, I have more plans... I want to use a yum repository system and setup an add-on repository for installing the X Window System and other free packages. I also want this distribution to remain GNU-compliant, so that means nonfree packages are not allowed.
The repository structure will be something like this:
plistic-core/dev: The core system, development.
plistic-free/dev: Free packages, development.
plistic-lsb/dev: Linux Standard Base packages, development.
plistic-corex/dev: X Window core packages, development.
plistic-freex/dev: Free X Window related packages, development.
plistic-core/<release number>: The core system, release.
plistic-free/<release number:> Free packages, release.
plistic-lsb/<release number>: Linux Standard Base packages, release.
plistic-corex/<release number>: X Window core packages, release.
plistic-freex/<release number>: Free X Window related packages, release.
My development machine partitions configuration:
sda1 - /boot - 500MB
sda2 - /usr/src - 12000MB
sda3 - / (Fedora 14) - 4000MB
sda4 - extended - *
sda5 - /lfs - 4000MB
sda6 - swap - 2000MB
I just finished building the LFS tool-chain. Now time to decide on the bare-minimum packages to install on the base-system. Here's the package list (stripped from the LFS-6.8 book).
plistic-core:
- Bash (LSB Core)
- Binutils (LSB Core)
- Bzip2
- Coreutils (LSB Core)
- E2fsprogs
- File (LSB Core)
- Findutils (LSB Core)
- Glibc
- Grep (LSB Core)
- GRUB
- Gzip (LSB Core)
- Iana-etc
- Inetutils
- IProute2
- Kbd
- Less
- Linux Kernel (Minus headers)
- Module-Init-Tools
- Nano
- Ncurses (LSB Core)
- Procps (LSB Core)
- Psmisc (LSB Core)
- Readline
- RPM (When I get to package management)
- Shadow (LSB Core)
- Sysklogd
- Sysvinit (Will be replaced by upstart)
- Tar (LSB Core)
- Udev
- Util-linux (LSB Core)
- yum (When I get another computer to host a yum repository)
- Zlib (LSB Core)
- Autoconf
- Automake
- Bison
- DejaGNU
- Expect
- Flex
- Gettext
- GDBM
- GMP
- Groff
- Libtool
- Linux Kernel Headers
- Man-pages
- MPC
- MPFR
- Make
- Patch
- Pkg-config
- Tcl
- Texinfo
- Vim
- XZ Utils
- At (LSB Core)
- Alsa Libraries (LSB Multimedia)
- ATK (LSB Desktop)
- Batch (LSB Core)
- Bc (LSB Core)
- Cairo (LSB Desktop)
- Cpio (LSB Core)
- CUPS (LSB Printing)
- Desktop-file-utils (LSB Desktop)
- Diffutils (LSB Core)
- Ed (LSB Core)
- Fcrontab (LSB Core)
- Freetype (LSB Desktop)
- Fontconfig (LSB Desktop)
- Gawk (LSB Core)
- Gcc (LSB C++)
- Glib2 (LSB Desktop)
- GTK+2 (LSB Desktop)
- Icon-naming-utils (LSB Desktop)
- Install_initd (LSB Core)
- Java (LSB Multimedia)
- Libjpeg (LSB Desktop)
- Libpng (LSB Desktop)
- Libxml2 (LSB Desktop)
- Lsb_release (LSB Core)
- M4 (LSB Core)
- Man-DB (LSB Core)
- MesaLib (LSB Desktop)
- NSPR (LSB Multimedia)
- NSS (LSB Multimedia)
- OpenSSL (LSB Multimedia)
- PAM (LSB Core)
- Pango (LSB Desktop)
- Perl (LSB Runtime Languages)
- Python (LSB Runtime Languages)
- Qt3 (LSB Desktop)
- Qt4 (LSB Desktop)
- Remove_initd (LSB Core)
- Sed (LSB Core)
- Sendmail (LSB Core)
- Test (LSB Core)
- Xdg-utils (LSB Multimedia)
- Xorg (LSB Desktop)
I'm not sure how this will work. The big question with RPM is how do I add RPM packages to the system if they are already installed on the system? Do I just install the RPM and overwrite the existing files so the RPM-DB is updated? Anyway, that's a ways away, so I shouldn't fret over it quite yet. I have a lot to learn!
Monday, May 9, 2011
Fedora is Good
Well, I hopped onto the #fedora channel at freenode.net. They were very helpful!
The problem with my networking was my iptables configuation. To make a long story short; all I had to do was run system-config-firewall and enable SSH. And... Make sure that the services where running.
I am now 100% Fedora! Everything works, it is Good.
The problem with my networking was my iptables configuation. To make a long story short; all I had to do was run system-config-firewall and enable SSH. And... Make sure that the services where running.
I am now 100% Fedora! Everything works, it is Good.
Fedora is good, but I have some Troubles
I want to run Fedora. Since Fedora 14, I got the "only" thing that was holding me back working... The proprietary Catalyst video driver. I thought, hey now that my video works, I'm all set. Well, not true.
I found that I cannot get a simple home network working. If it's not one trouble, it's another. I finally decided to stick it through instead of distro-hopping. It must be something with SELinux. I know that SELinux has been a pain in my ass in the past.
I've never asked for help with this topic before. So, I think I'm going to jump on the IRC and see if anyone has a solution. Here's my problem... I can "ping" my Fedora-box, but I can't connect to it through ssh. If I can figure this out, I will have to say that Fedora is my favorite distro. I think it's very polished and done right.
One final hurdle (networking) is left to solve... Wish me luck!
I found that I cannot get a simple home network working. If it's not one trouble, it's another. I finally decided to stick it through instead of distro-hopping. It must be something with SELinux. I know that SELinux has been a pain in my ass in the past.
I've never asked for help with this topic before. So, I think I'm going to jump on the IRC and see if anyone has a solution. Here's my problem... I can "ping" my Fedora-box, but I can't connect to it through ssh. If I can figure this out, I will have to say that Fedora is my favorite distro. I think it's very polished and done right.
One final hurdle (networking) is left to solve... Wish me luck!
Subscribe to:
Comments (Atom)