Quote:
But given I'm not a 'Slacker' (but maybe one day), I'm leaving while the going's still good! ;) |
Quote:
|
I've already grabbed the *.iso.
I'll report back tomorrow.:) |
It is a slack baby ... good to no !
:p |
I was unable to get Cucumber to install in a VM under VirtualBox. I had the 64-bit *.iso, so I created a 64-bit "Other Linux" VM with about a 20GB virtual HDD (dynamically allocated).
I fired up the *.iso and got as far as partitioning the drive with cfdisk. Formatting was not a discrete step in the default installation routine. I got an error that swap could not be mounted. I deleted the VM and tried again. This time, after creating the partitions, I formatted / with mkfs, then formatted the swap with mkswap. I got the same error. You can see a screenshot of the "select partition" dialog here: http://pineviewfarm.net/weblog/wp-co...partitions.jpg You can see a screenshot of the error message here: http://pineviewfarm.net/weblog/wp-co...ber2_error.jpg I'm pretty much booked tomorrow and the next day, so I won't have a chance to try this on another computer for a few days. |
I installed cucumber linux (64 bit) on an unused partition of my main hardrive.
Had some trouble getting the install disk working. Don't remember the error, but it kept looking for some i386 stuff. It finally booted, though. Did a full install, returned to my main partition, reworked grub and reboot into cucumber. Had only a few minutes to play with it, but it seemed to work okay in a console. Could not get X to come up. Major problem: startx is missing. It's new so I expect a few problems, but I think I will still like Slackware better. |
Is this a Slackware derivative?
From the FAQ: Quote:
|
Hello Everyone,
I'm Scott (A.K.A. Z5T1), the creator and BDFL of Cucumber Linux. Thank you all for taking the time to check out and discuss Cucumber Linux. I see you have some questions and I'm going to do my best to answer some of them. Quote:
Now I could have easily just forked Slackware; however, I decided to build a new distribution from scratch, figuring that would provide a much more complete learning experience. I actually initially set out to create a disto based off of Linux from Scratch, not Slackware. There were some thing I thought Linux from Scratch did well, but there were some things I thought Slackware did better. Ultimately, I largely combined the two distributions together, drawing heavily from both distros but also doing certain things my own way. I actually used very few SlackBuild scripts; I wrote most of the buildscripts myself, and if you look at the way they build the packages you'll see they're closer to the Linux from Scratch/Beyond Linux from Scratch buildscripts than SlackBuild scripts. After I spent over a year working on Cucumber Linux, I figured I may as well make it publicly available in case anyone else happened to find the project interesting. Quote:
Quote:
Also, Slackware's lifecycle is a little vague about security and can be deceiving. For example, Slackware 13.37 is still supported; however, it uses a kernel that hasn't been patched since upstream support ended for the Linux 2.6 kernel many years ago. Turns out this kernel is vulnerable to both dirty cow and stack clash, and probably several more vulnerabilities. With Slackware, if you don't dig deep enough, you can easily end up thinking your system is secure when it really is not. With Cucumber Linux, I have a much more clearly defined lifecycle and I make sure that if a version of Cucumber Linux is supported, it is really completely supported and up to date on all security patches, period. - Scott |
Thanks for taking time to respond here Scott. I suspect we'd see eye to eye on quite a few subjects based on what you've written above. Best of luck with your project.
|
Agreed! Good luck Scott and keep Cucumber going!
|
Thanks for the explanation. It's always good to have alternatives in case something ever happened to Slackware.
|
Quote:
|
Quote:
|
Quote:
CVE-2016-1248 arbitrary code execution in Vim via a specially crafted text file. CVE-2016-9273 and several vulnerabilities in libtiff that were fixed in libtiff 4.0.8 (Slackware is still on 4.0.7). CVE-2017-3636, CVE-2017-3641 and CVE-2017-3653 all in MariaDB that allow unauthorized access of information and unauthorized inserts, deletes and updates. CVE-2016-0634 arbitrary shell command execution as any user in Bash via a specially crafted hostname. CVE-2017-10663 in the Linux kernel allows for arbitrary code execution in the kernel space when mounting a maliciously crafted F2FS filesystem. CVE-2017-12424 a buffer overflow vulnerability in shadow that could result in a crash and other unspecified impacts, possible privilege escalation. And I could go on, but I think you get the point :). I tried contacting the Slackware security team about some of these, but never got a response. All of these vulnerabilities have been patched in Cucumber Linux. Also, there are some vulnerabilities that have now been patched in Slackware, but went unpatched for several weeks after the upstream patches were released. In these cases, Cucumber Linux was patched within a day or two. |
Quote:
Also, as I mentioned in my previous post, I did try submitting some of the patches to the Slackware security team, but I never got a reply from them and the patches ultimately went unapplied. After this happened a couple of times, I gave up on submitting them. |
All times are GMT -5. The time now is 11:22 AM. |