| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| wiki:user:exaga [2016/12/17 19:44 (UTC)] – updated exaga | wiki:user:exaga [2017/12/26 19:27 (UTC)] – exaga |
|---|
| ====== Exaga ====== | ====== Exaga ====== |
| | |
| | * Creator and maintainer of the 'Slackware ARM on a Raspberry Pi' - [[http://sarpi.co.uk|SARPi Project ]]. |
| | * Passionate //Slacker// since 2004. |
| | |
| === About me === | === About me === |
| |
| === Slackware Linux === | === Slackware Linux === |
| |
| My first venture into Linux was in December 2004 on the suggestion of a friend, [[http://aal.fatdog.nl/|Aal]]. He strongly advised that I should try Slackware. Little did I know at that time that this was to be my baptism of fire! I spent the first week with Slackware by breaking my system, many times, and asking Aal to "fix it". Until the point came when he said, "WTF!?!?! Slackware is the most stable Linux system you will __EVER__ work on. How can you keep screwing it up??? The next time you break it, you'll be fixing it yourself!" After that, I got real and instead of employing the //trial and error// methods of educating myself (which had served me so well in the past), I decidedly took to the Internet and began to learn the right way. Or, at least, not the wrong way. Slackware (and Linux in general) was a whole new and very different, but exciting, ball game for me personally and up until this very day I have enjoyed every minute of it! Well, mostly every minute. lol :-D | My first venture into Linux was early in December 2004 on the suggestion of a friend, [[http://aal.fatdog.nl/|Aal]]. He strongly advised that I should try Slackware. Little did I know at that time that this was to be my baptism of fire! I spent the first week with Slackware by breaking my system, many times, and asking Aal to "fix it". Until the point came when he said, "WTF!?!?! Slackware is the most stable Linux system you will __EVER__ work on. How can you keep screwing it up??? The next time you break it, you'll be fixing it yourself!" After that, I got real and instead of employing the //trial and error// methods of educating myself (which had served me so well in the past), I decidedly took to the Internet and began to learn the right way. Or, at least, not the wrong way. Slackware (and Linux in general) was a whole new and very different, but exciting, ball game for me personally and up until this very day I have enjoyed every minute of it! Well, mostly every minute. lol :-D |
| |
| I have tried many other Linux distributions but their appeal has not lasted with me. I think Slackware's, "KISS" philosophy, of what an operating system should offer and consist of, is the thing that's endeared me to it. More so than any others. | I have tried many other Linux distributions but their appeal has not lasted with me. I think Slackware's, "KISS" philosophy, of what an operating system should offer and consist of and how it should run, is the thing that's endeared me to it. More so than any of the others. Slackware just makes sense to me. |
| |
| === FatDog.NL === | === Slackware ARM on a Raspberry Pi - The SARPi Project === |
| |
| Over the years I've been involved in too many projects to recall. The most prevalent of which is [[http://www.fatdog.nl|FatDog]], owned by Aal. Since 2007 [[http://www.fatdog.nl|FatDog]] has been a virtual //playground// by which we have expressed ourselves and the work we love to do in many and various ways. You might think that "FatDog" is a funny and peculiar name. Well there's a reason for it. A brief conversation which took place on IRC between two crazy guys, sometime during 2005, will explain everything... | It was a few months before the first Raspberry Pi was released when Aal and me discussed the device. We both agreed that neither of us would be interested in playing with it if Slackware was not an available operating system to install and run. Of course, we were both aware of [[http://arm.slackware.com|Slackware ARM]] and the work [[http://www.slackware.com/~mozes/|Mozes]] was involved with. After much searching on the Internet the prospects looked very grim indeed. There were a few places where Slackware on a Raspberry Pi was mentioned but no concrete information on development or signs that any plans had been formulated to bring this wonderful OS to the RPi platform. So, we decided we were going to do it ourselves. (NB: we hadn't got much of a clue that it would be so much work and effort, in our ignorance at that time. lol) However, I'm glad to say that during the approx. 6 month wait for delivery of our Raspberry Pis, quite a few people had been quietly and successfully working away at bringing Slackware ARM to the device. We then decided to shelf our plans (as no time or effort had been wasted on them anyway) and instead we downloaded and installed various images that had become available. For a few days we tested and played with these pre-built Slackware ARM images but I have to say, personally, I wasn't getting that 'Slackware factor' of enjoyment and rewarding experience that I so much loved. It took me a few seconds to realise why, once I'd given it some thought. These Slackware ARM images I was installing weren't installed from scratch or configured by me. They were somebody else's idea of what my Slackware system should contain and how it should be configured. THAT right there was the point at which I realised there needed to be more involved than just downloading a disk image, writing it to a SD card, and booting it in a Raspberry Pi. That's when Aal and me started to discuss and plan what we needed to do. Aal, being more technically minded and vastly more experienced in using Slackware than me, started firing off what was required and procedures and the order of things and 10 billion other things that seriously blew my mind because most of he said was wayyyyy over my head and level of understanding. However, there was light at the end of this tunnel (vision) and this particular light was as big and as bright as the Sun itself!!! |
| > Aal: I need to walk the dog and don't really feel like it. | |
| |
| >> Exaga: why not? | Independent of each other, we both came across [[http://www.daves-collective.co.uk/raspi/index.shtml|Dave's Collective - Slackware ARM on the Raspberry Pi]] website. All credit and kudos goes to **Dave Spencer** who had brilliantly created his own set of Slackware scripts which enabled users to create their own Slackware ARM installers and packages. Having realised that this was __EXACTLY__ what we were trying to achieve, we downloaded the scripts which Dave had made available through his website and used these to create test packages and installers. Because Aal and me both had jobs and worked 5 days a week there wasn't a lot of time to spend on this project at that time. It took approx. 3-4 weeks, with much editing/hacking/modifying of Dave's scripts, to get to a stage where we were happy with the results. In order to keep the disk images to a minimum size, Aal suggested that only the /boot partition should be present, which made sense. As a consequence, which I fully supported and encouraged, users installing Slackware ARM would subsequently be forced to create their own /swap and root partitions, which I believe is part of the 'Slackware experience' - the same as it is when installing Slackware x86_64. This way users were able to set the parameters of their system during SETUP (i.e. installation) and configure it according to their own needs. This familiar method to install Slackware (ARM) was preferable to using pre-built images where the learning-curve and experience gained from it was omitted by design. |
| | |
| > Aal: it's raining :-( | |
| | |
| >> Exaga: well, you could wear the dog on your head... | |
| >> Exaga: that way you'd be taking it for a walk AND stay dry | |
| | |
| > Aal: NO! | |
| | |
| >> Exaga: why not? | |
| | |
| > Aal: because it's a fat dog! lol | |
| | |
| >> Exaga: HAHAHAHAHAHAHAHAHAHAHAH! | |
| | |
| > Aal: :-D | |
| After that, and with the long-overdue dream of having a domain/network on which to develop and broadcast our hobbyist activities, [[http://www.fatdog.nl|"FatDog"]] was born. | |
| | |
| === FatDog Minecraft [FDMC] === | |
| | |
| One of the few games I have enjoyed playing is Minecraft. Early in 2012 we created [[http://minecraft.fatdog.eu/|FatDog Minecraft]] which is a survival multiplayer (open-pvp) server that's available for public use. It still runs to this day so if you want to login and try it out, please feel free. :-) \\ | |
| Server: **minecraft.fatdog.eu** \\ | |
| Port: **25565** | |
| | |
| === Slackware ARM on a Raspberry Pi - The SARPi project === | |
| | |
| It was a few months before the first Raspberry Pi was released when Aal and me discussed the device. We both agreed that neither of us would be interested in playing with it if Slackware was not an available operating system to install and run. Of course, we were both aware of [[http://arm.slackware.com|Slackware ARM]] and the work [[http://www.slackware.com/~mozes/|Mozes]] was involved with. After much searching on the Internet the prospects looked very grim indeed. There were a few places where Slackware on a Raspberry Pi was mentioned but no concrete information on development or signs that any plans had been formulated to bring this wonderful OS to the RPi platform. So, we decided we were going to do it ourselves. (NB: we hadn't got much of a clue that it would be so much work and effort, in our ignorance at that time. lol) However, I'm glad to say that during the approx. 6 month wait for delivery of our Raspberry Pis, quite a few people had been quietly and successfully working away at bringing Slackware ARM to the device. We then decided to shelf our plans (as no time or effort had been wasted on them anyway) and instead we downloaded and installed various images that had become available. For a few days we tested and played with these pre-built Slackware ARM images but I have to say, personally, I wasn't getting that 'Slackware factor' of enjoyment and rewarding experience that I so much loved. It took me about 3 seconds to realise why, once I'd given it some thought. These Slackware ARM images I was installing weren't installed from scratch or configured by me. They were somebody else's idea of what my Slackware system should contain and how it should be configured. THAT right there was the point at which I realised there needed to be more involved than just downloading a disk image, writing it to a SD card, and booting it in a Raspberry Pi. That's when Aal and me started to discuss and plan what we needed to do. Aal, being more technically minded and vastly more experienced in using Slackware than me, started firing off what was required and procedures and the order of things and 10 billion other things that seriously blew my mind because most of he said was wayyyyy over my head and level of understanding. However, there was light at the end of this tunnel (vision) and this particular light was as big and as bright as the Sun itself!!! | |
| | |
| Independent of each other, we both came across [[http://www.daves-collective.co.uk/raspi/index.shtml|Dave's Collective - Slackware ARM on the Raspberry Pi]] website. All credit and kudos goes to **Dave Spencer** who had brilliantly created his own set of Slackware scripts which enabled users to create their own Slackware ARM installers and packages. Having realised that this was __EXACTLY__ what we were looking to do, and trying to achieve, we downloaded the scripts which Dave had made available through his website and used these to create test packages and installers. Because Aal and me both had jobs and worked 5 days a week there wasn't a lot of time to spend on this project at that time. It took approx. 3-4 weeks, with much editing/hacking/modifying of Dave's scripts, to get to a stage where we were happy with the results. In order to keep the disk images to a minimum size, Aal suggested that only the /boot partition should be present, which made sense. As a consequence, which I fully supported and encouraged, users installing Slackware ARM would subsequently be forced to create their own /swap and root partitions, which I believe is part of the 'Slackware experience' - the same as it is when installing Slackware x86_64. This way users were able to set the parameters of their system during SETUP (i.e. installation) and configure it according to their own needs. This familiar method to install Slackware (ARM) was preferable to using pre-built images where the learning-curve and experience gained from it was omitted by design. | |
| |
| Once the finer details (i.e. what should be included in the kernel, etc.) were decided upon I then realised that a walk-through "How To install Slackware ARM on a Raspberry Pi" type tutorial/guide would be ultimately beneficial for those who have never gone through the process, and also for those who have. So, I personally undertook the task of creating the [[http://rpi.fatdog.eu|SARPi Project website]] in order to fulfil this idea. During the months and years which followed there have been quite a number of people involved in helping and assisting with various problems that popped up due to various changes in hardware and updates in code. Far too many people to mention but much gratitude, heartfelt thanks, and great respect, goes out to all those who have helped, directly or otherwise, towards making the SARPi Project become a small success. 8-) | Once the finer details (i.e. what should be included in the kernel, etc.) were decided upon I then realised that a walk-through "How To install Slackware ARM on a Raspberry Pi" type tutorial/guide would be ultimately beneficial for those who have never gone through the process, and also for those who have. So, I personally undertook the task of creating the [[http://rpi.fatdog.eu|SARPi Project website]] in order to fulfil this idea. During the months and years which followed there have been quite a number of people involved in helping and assisting with various problems that popped up due to various changes in hardware and updates in code. Far too many people to mention but much gratitude, heartfelt thanks, and great respect, goes out to all those who have helped, directly or otherwise, towards making the SARPi Project become a small success. 8-) |
| |
| Over time, after the releases of the RPi2 and RPi3, came the [[http://rpi2.fatdog.eu|SARPi2 Project website]] and [[http://rpi3.fatdog.eu|SARPi3 Project website]] respectively. Then, in quite an astute observation from [[http://www.slackware.com/~mozes/|Mozes]], it was suggested that to cut down on time, effort, and maintenance, that the three separate SARPi Project websites should be combined into "one site to rule them all". This was realised with the inception of the current [[http://sarpi.fatdog.eu|SARPi Project website]] with the other three website URLs redirecting to it. | Over time, after the releases of the RPi2 and RPi3, came the [[http://rpi2.fatdog.eu|SARPi2 Project website]] and [[http://rpi3.fatdog.eu|SARPi3 Project website]] respectively. Then, [[http://www.slackware.com/~mozes/|Mozes]] suggested that to cut down on time, effort, and maintenance, the three separate SARPi Project websites should be combined into "one site to rule them all". Great idea! This was realised with the inception of the current [[http://sarpi.co.uk|SARPi.co.uk Project website]] with the other website URLs redirecting to it. |
| | |
| | |
| === FatDog Online Forum === | |
| |
| The FatDog Online Forum has been running for many years which I have always tried to manage and maintain as time permits. It's there for users to read, make posts, and communicate. The forum mainly covers the [[http://sarpi.fatdog.eu|SARPi Project]] and [[http://minecraft.fatdog.eu/|FatDog Minecraft]]. You need to register and create an account before you can make new posts or reply to existing ones. The SARPi Project sub-forum doesn't attempt, or intend, to replace better established institutions for Slackware (ARM) support, such as the [[http://docs.slackware.com|Slackware Documentation Project ]] or [[http://www.linuxquestions.org/questions/slackware-arm-108/|Linux Questions Slackware ARM forum]], but it's more of an informal gathering of social users. We never try to take ourselves too seriously on FatDog. 8-) | === Slackware for the future === |
| |
| === FatDog on Freenode IRC === | I'm very interested in seeing Slackware ARM64 (Aarch64 port) become a reality. It's a seriously massive undertaking but I think, if enough of the right people put their heads and efforts together, anything is possible. |
| |
| If you feel like chatting on IRC you can find me in the #fatdog channel on [[http://webchat.freenode.net|irc.freenode.net]]. Although, I'm often busy with other things so you might not always find me active there. | I'll be running Slackware/Slackware ARM until Pat and Stuart stop releasing it. Then I'll cry! ;-p |
| |
