Facebook killed the radio star. And by radio star, I mean the premise of distributed forums around the internet. And that got got by Instagram/SnapChat. And that got got by TikTok. Where the fuck is the internet we once knew?
0 Members and 1 Guest are viewing this topic.
[17:32:45] * xar sets mode: -oooooooooo algorithm ban chris cipher newby stdio TehUser tnarongi|away vursed warz[17:32:54] * xar sets mode: +o newby[17:32:58] <xar> new rule[17:33:02] <xar> me and newby rule all
Quote from: CrAz3D on June 30, 2008, 10:38:22 amI'd bet that you're currently bloated like a water ballon on a hot summer's day.That analogy doesn't even make sense. Why would a water balloon be especially bloated on a hot summer's day? For your sake, I hope there wasn't too much logic testing on your LSAT.
I'd bet that you're currently bloated like a water ballon on a hot summer's day.
I'd personally do as Joe suggests
You might be right about that, Joe.
Who gives a damn? I fuck sheep all the time.
And yes, male both ends. There are a couple lesbians that need a two-ended dildo...My router just refuses to wear a strap-on.
www.slackware.com.I'm getting my three install disks as we speak.
Like all things in life, pumping is just a primitive, degenerate form of bending.
Hey, I don't tell you how to tell me what to do, so don't tell me how to do what you tell me to do! ... Bender knows when to use finesse.
Warning: mysql_pconnect(): Too many connections in /var/www/slackware/php_includes/database.inc on line 20could not connect to database
I have a programming folder, and I have nothing of value there
Our species really annoys me.
What's all this sticky white shit on the thread?*Notes iago didn't post*Ewwwwww
It's really not that big of a deal to me. I'm content with Slackware 10.2, and I'm not in a rush to update.
Is this your external hard drive?I still need to set up my RAID in Linux. I'm sure there's a workaround without the 2.6 kernel, but all of the pages I found explaining the linux installation of the RAID controller I have require the 2.6 kernel.
I noticed that they said there were "more options" with the 2.6 kernel. Does this mean you can install it in place of 2.4 without all the hassle of setting it up after the slackware install?
There's a Slackware kernel designed for RAID. It worked perfeclty. It's a 2.4 kernel, obviously. It's called "raid" I think.
First, by "more options", they mean that you can use 2.6.17.something (which is in the /extras folder) or 2.6.18 (which is in the /testing folder). Second, you could always install the 2.6 kernel at the start. I forget how, though..
Nothing is intuitive. RTFM.
Quote from: iago on October 03, 2006, 04:11:51 pmNothing is intuitive. RTFM. It should be...
I was wondering if they added an intuitive way to accomplish the recommendation in your second sentence.
4.6 The CONFIGURE option:The setup's CONFIGURE option does the basic configuration your systemneeds, such as creating links for your mouse and modem, setting yourtimezone, and more.The CONFIGURE option will first ensure that you've installed a usableLinux kernel on your hard drive. The installation program should suggestinstalling the same kernel from the CD-ROM that you used for theinstallation process, and you should go ahead and do this. There is ageneric kernel (kernel-ide) that comes with the A series that is actuallythe same as the bare.i kernel, but the best kernel to install to your harddrive is the one that you used to do the installation. If you used abootdisk rather than booting the CD-ROM, you should install the kernelfrom your bootdisk by selecting the "bootdisk" option on the kernelinstallation menu. The menu will prompt you to reinsert your installationbootdisk and hit enter, and then setup will copy the kernel from thebootdisk to your hard drive.If you don't want to use the recommended kernel, you can pick any kernelfrom the menu of kernels available on the CD-ROM, but if you install thewrong kernel the machine likely won't boot -- it's really a much betterplan to install the same kernel you installed the system with. Since youused it to successfully install Slackware, you know it will work on theinstalled system as well.NOTE: If you install a kernel on your system that doesn't boot correctly,you can still boot your system with the CD-ROM. To do this, you need toenter some information on the boot prompt. For example, if your rootpartition is on /dev/hda1, you'd enter this to boot your system: bare.i root=/dev/hda1 noinitrd roThe "noinitrd" option tells the kernel not to load the installer imageinto RAM, and the "ro" option makes the root partition initially load asread-only so Linux can safely check the filesystem.You can also start the system with an installation bootdisk, but thesyntax is slightly different: mount root=/dev/hda1 roOnce you've installed a kernel, you'll be asked if you want to make abootdisk for your new system. This is a very good idea, so insert aformatted floppy disk and use the "Create" option to create a bootdisk foryour system.
Not when it's considered 'testing' (ie, beta)
Quote from: iago on October 03, 2006, 06:37:17 pmNot when it's considered 'testing' (ie, beta)Installing a kernel that is considered somewhat standard in the Linux community should be installed in an obscurely difficult fashion? Cool, Newby. That's sitll more difficult than it could be, though! I'll give it a try sometime...
Well, I don't think a beta/testing version should be easy to install, if you want it you should know what you're doing. So shuttup
Quote from: iago on October 03, 2006, 10:40:51 pmWell, I don't think a beta/testing version should be easy to install, if you want it you should know what you're doing. So shuttup It may be considered beta testing, but have you ever had any problems that you were able to directly attribute to the 2.6 kernel? I've ran into so many issues that had solutions only implementable with the 2.6 kernel that I don't think it's very sensible to make it difficult to install it.
It's not difficult, you install it the same way you install anything: find the package, and run "installpkg" on it. It's just not easy.
It's not easy, but it's not difficult, huh?
If it's that easy, why don't they just make it an option during the install sequence?!
Also, I was unable to get the installpkg to work with the 2.6 kernel when you recommended it. I had to use a custom kernel.
Yes, it's like doing an average Su-Do-Ku, to take a completely random example. They aren't easy, nor are they hard.
You install it the same way you install other weird packages. It's completely normal for the distro.
Then it probably wouldn't have worked if you'd installed it during the normall installation, either. All the installer does is run "installpkg" on everything you tell it to.
I'm talking about the install sequence. I see no reason for it to not be an option.
It's a kernel, though! It should be implemented into the install sequence.
Then they should fix it.
Quote from: Sidoh on October 04, 2006, 12:19:48 pmI'm talking about the install sequence. I see no reason for it to not be an option. Because it's considered beta/'testing', which means it won't always work. Quote from: Sidoh on October 04, 2006, 12:19:48 pmIt's a kernel, though! It should be implemented into the install sequence.Because it's considered beta/'testing', which means it won't always work. Quote from: Sidoh on October 04, 2006, 12:19:48 pmThen they should fix it. Why do you think it's beta?
But when you compiled it, it's configured differently than the way Slackware configured it. That's probably why.
But yeah, you're suggesting that they make this beta version, which didn't work on your laptop, should be easier to install? Make it easier for people to potentially render their installation unusable? Phoey!
In the linux world, there's unstable, stable, and release. A finished version is always marked "release", and a working beta is "stable".