Slashdot is powered by your submissions, so send in your scoop

 


Forgot your password?
Close
typodupeerror
×
Linux Software

Stormix:Yet Another Distribution 148

Posted by CmdrTaco from the joining-the-fray dept.
IsleOfView wrote in with prove that there will never be a shortage of new distributions. This one is called stormix and its based on Debian, but has assorted advanced installation tools.
This discussion has been archived. No new comments can be posted.

Stormix:Yet Another Distribution More

Stormix:Yet Another Distribution

Comments Filter:

  • Redhat (Score:1)

    by Anonymous Coward
    Redhat has lots of icons and windows. Debian scares me. It just comes up with something like "root#" and sits there! I type stuff and it keeps saying "command not found". What a piece of junk...

  • The End is Near (Score:1)

    by Anonymous Coward
    If anything will be the downfall of Linux (aside from the outbursts from the fanatics), it will be the multitude of "distributions".

    Why? Quite simple: there is NO STANDARD. There is no way you can create a book on Linux that focuses on administration *from an admin's point of view* and say: "this is the way you do it...", etc... You can't do this when there are 40 million different distributions, each with it "own way of doing things".

    The typical Linux "distribution" is not even *complete*, from a network or sysadmin point of view. There are various utilities that are simply missing from the base system (what good is a Unix without dump/restore?), which you then have to go out of your way to find, when you *could* be doing other things.

    Perhaps if Linux developers would a) stop focusing on making Linux look (and run) like MS-Windows, b) concentrate on networking and server applications instead of desktop, c) make a consistent format that should be used as a *standard for all "distributions"* to provide a complete base system, then maybe Linux will stand a chance.

    But as it stands, it is chaos. It will not last at this rate. Once it starts hitting the server market, admins will see it for what it has become: a chaotic, confusing waste of their time. I personally do not have time to fix "broken" distriutions.

    Oh, and another thing: let's put the *essential system files* in /usr, /bin, /lib, /etc and so on. Put the "optional add-on packages" in /usr/local or /opt where they belong and don't interfere with system files.

    Linux's credibility has already suffered at the hands of the zealous fanatics, and now it's feeling the effects of its chaotic inconsistency of distributions.

  • Almost every small distro now has a GUI-install, but Red Hat and Debian have not. If we want to have "World Domination", we'd better shape up the installation process, and I find it very strange that Red Hat has not yet made a GUI-installer.

    I hate the cli-installation-style. I hate IRQs. I hate system administration. I want to code.
  • >Then make your own Super-Installer. Submit it to
    >the community.

    Perhaps, but I have to become a better programmer first. I could perhaps start after christmas.

    >Just because the installer sucks ass (CLI)
    >doesn't mean that you have to start a whole new
    >distro. That's just stupid.

    I agree, but Debian could use the installer from Stormix.
  • Posted by planders:

    I meant democracy in the ancient Athenian sense, where things are decided by the land-owning class of citizens. ;-) That would be the debian developers. I do understand that Joe User doesn't get to vote on Debian issues.

    I said 'democratic' as a counter-example to the benevolent tyranny of Red Hat or Slackware, where a corporation or extremely select group of individuals decides what goes into the distro.

    AFAIK, all it takes to be a Debian developer is the willingness to read the mailing lists and a well-signed PGP/GPG key. There's no 'code quota' that says you have to contribute a certain amount to be able to vote.

  • It's not that we/I "fear" new distros. It has nothing to do with that.

    Commercial vendors like to make money. That's what they're in it for. We, the community, like for the vendors to port to Linux. Why? So we get cool stuff. So Linux gets bigger and better. Everyone's happy.

    However, if there are fifty distributions, then they will inevitably wonder, "Wait, if we're going to support Linux, which distro do we port to?" Sure, you can compile it for Linux, put it in a tarball and be done with it - and leave the install specifics to the user.

    But what happens with support? "Oh, I see, you're using SuperDuper Linux?" Where is such and such installed? What version is your whatchamacallit binary? And so on...

    From my perspective, I think it would make commercial vendors feel a whole lot better about getting into Linux if they didn't feel like they were porting to a moving target.

    Personally, I could care less - use whatever you want or roll your own. I'm just thinking that commercial vendors will get scared off and end up not porting to Linux because "there are too many choices."

  • have you even done any research into what these guys are doing?

    its debian linux with a nice install and eventually a configuration program.

    all the changes are gpl, and the developers are active on debian-devel. while i don't exactly agree with their ideas (getting rid of text file configuration in favor of a binary database) their work can only help debian in the long run.

    fragmentation is bad, but this distribution is based closely on debian, which is as close to a standard as you can get.

    another distribution != fragmentation, or at least it doesn't have to.

    i'm certainly willing to at least give them the benefit of the doubt, and possibly to download it once it gets a little further along and give it a shot...

    -garrett
  • Strange. I've installed Debian many times on many machines, and only once had a problem (the mouse refused to work).

    Compare this to my Redhat experience -- I've tried five different versions on four different computers more times than I care to count, with only three sucessful installs. Every other time, the installer corrupted the filesystem while doing the install. (Oops, make that six versions on five computers -- LinuxPPC installed perfectly without a glitch.)

    My point?

    Installing OSes sucks ;-). Don't sweat it -- if the install doesn't take the first time, write to the maintainer(s) about it so they can fix it, then try again.

    -Billy
    (A very happy Debian user -- although I do want a better install, I believe that ease of use and upgrading is FAR more important, and Red Hat just does not handle that.)
  • I agree with you WRT deb vs. RPM, even though I'm told that rpmfinder is a nice program which can be pointed to central distributions -- Redhat just isn't designed for that, and Debian is.

    However, you asked "do people really find plain old fdisk THAT hard to use?"

    People Do.

    :)

    Or more specifically, Linux typically asks people to partition their hard drive before it tells them what for. In my ideal installation, you'd choose the apps you wanted before you ever saw the partitioning screen. That way the installer could straight out tell you "you need to clear at least X amount of space -- that's n% of your hard drive. Here's a suggested area."

    Until then, installs will require planning ahead, or dedicated systems. Planning ahead is wonderful, but it required knowledge, which is kind of a catch-22 for new Linux users (they're installing Linux so they can gain knowledge).

    -Billy
  • Of course registering makes you less anonymous -- if you _post_ with that ID consistently.

    I don't use people's emails or read their stupid (or clever) nicks; I don't even care. To me, they are what they write -- and an AC is someone who doesn't want to be associated with what they've written in the past.

    Fine for them, fine for me.

    -Billy
  • >It just comes up with something like "root#" and sits there!

    >>Also know as a command line interface. Learn to use it, and it shall become your friend. I suggest buying a good book on linux (or four good books), and reading them.

    I think Rob needs to add the ability to include little icons in our posts like the ones used to identify the main articles. That way we could add the "It's funny. Laugh" icon for the humor impaired.

  • "monstrously complex"? I don't find hitting "+" and "-" and occasionally being prompted for dependencies a difficult task. Oh, you can also hit "?" if you get confused.
  • This has kindof been touched upon in previous posts, but AFAIK not quite this way.

    "The Great Unwashed" that think they wanna try Linux, but don't know the first thing about using/installing it don't care weather or not the interface is GUI or CLUI. What they do care about are things like partitions, video drivers, IRQs etc. it is those things that you want to "shield" TGUs from [and have the ability for the power user to micromanage the install]

    All this gui does is show everything the textmode has in a "cute" closable window. My grandmother doesn't want to know what a partition is/ what mount points are.

    To reiterate, "normal" people don't give a rats arse if the install procedure is text based or gui based, they just don't want to have to understand things like video drivers, refresh rates, IRQs, etc.

    I think Stormix is missing the point of the GUI install

  • How many distros are there now?

    Lots [kernelnotes.org]

    We will never defeat Microsoft unless we all pull together and focus our energy!

    The Microsoft == the Borg analogy is used quit often, but many people fail to look at it thoroughly. The Borg are defeated by individuals, not by another collective. Individuals differ, compete and cooperate with each other. Neither pure competition, nor pure cooperation seem to be the best strategies, evolutionarywise.

  • Actually, Debian and Redhat are incredibly similar. They can even use each others' packages (via alien), and except for minor differences (like the way they arrange their rc.d script directories), they are practically interchangeable. What Debian has over RedHat, which is why I use it, is that it uses deb instead of RPM as its native package format. deb is much more powerful, having such features as:

    • Multiple levels of dependency (required, recommended, optional)
    • Both dependencies and providership, so that a program which needs, for example, vi can state that it requires, say, elvis, but only needs it for vi, and can use some other package that provides vi
    • Comes with ftp/http/etc. package repository capabilities out-of-the-box (yes, I know there's such things available for Redhat, but they're not as easy to find or learn, IMO); apt is *very* useful, since with a single commandline you can update your package lists and upgrade any packages which have changed (and it's all secure with md5 signatures on the secure Debian package repository servers); additionally, the beta/unstable distribution is always on the bleeding edge, and the current/stable distribution is constantly patched with any security fixes which are made available

    There are also many features of the distribution itself which make me prefer it, namely:

    • Being the FSF's distribution, is biased heavily towards totally-free software, though also provides plenty of non-free software for those who need Netscape et al
    • There is a huge network of volunteers creating packages for just about anything you can find, and for those things you can't find, you can, again, use alien to install an RPM version
    • The packages have to adhere to very strict standards for inclusion as official, and any official-sanctioned packages generally show up on the package servers; none of those silly RPMs which put things in /usr/local or whatever *cough*Q3Test*cough*
    • It's got such a cool name :)

    So basically, RedHat and Debian are basically the same OS, but Debian is a much better OS experience (strictly IMO). Of course, it could be argued that RedHat and Debian are different OSes than Slackware, and to that I'd somewhat agree, though they're still similar enough to have most things interchangeable (alien can also import/export "tarball" distributions such as what Slackware uses, and except for Slackware's antiquated /etc and /var layout - and this could have changed since 3.5, which is the last version I've used - they're still pretty much interchangeable).

    Now, I realize that you were just trolling/flaming/etc., but I don't see that as a reason that I can't at least try to give some friendly information, right? :)


    ---
    "'Is not a quine' is not a quine" is a quine.

  • arielb (Score:1)

    by arielb ( 5604 )
    So many distros and nobody wants to do anything meaningful such as knocking off that crazy /usr/ stuff in the directory system. Now that would be interesting and worth supporting.

  • Some anonymous coward said:

    I've TRIED to copy programs from Suse to Redhat. It doesn't work. They crash and burn for lack of proper DLL's. These are not the same OS!

    YM "Windows to Redhat". ;) (Linux doesn't have DLLs, and I copy stuff between SuSE and Redhat distributions of Linux regularly. Not little programs, either...I've successfully compiled uqwk (an offline Usenet newsreader) on a SuSE box, taken the binary to both Redhat AND Debian boxen, and the darn thing *works*. :)

    Now to run stuff that requires DLLs, you need a little utility called Wine [winehq.org]. I've never seen a huge use for it myself, though. :)

  • dpkg and rpm are for uberl33tz! Slackware's installpkg ownz!
    installpkg may not be very sexy, but it works. So what if you're missing packages? installpkg doesn't whine at you for it, you can just go and get them later! And in GUI tools, pkgtool makes glint and apt look like tinkertoys!

    I felt like I had to stick in something for Slackware.

    Armando Rojas

  • Hmmm... (Score:1)

    by BJH ( 11355 )

    Go to the web site and have a look at the screenshots.

    Could someone PLEASE tell me why in Ghod's name you would need miniaturize/maximize/close buttons on a fscking INSTALL window? Prettying it up is OK, but let's think while we're doing it, huh guys?
  • Actually, it is possible to mix binarys between distros, its just tricky. I, briefly created a Frankenstein Debian/Mandrake beast....attempting to combine the best aspects of each. It was, well, interesting to say the least, but most binary did run.
  • If you're going to install required packages from source, you ought to download the source packages, and compiling them produces a binary package which can then be installed.

    That beats having a lot of packages installed from source, with no idea of what individual files they have installed.

    Also, if you're into compiling lots of stuff, there is a host of tools to help you create debian packages, which you can use to generate binary packages from your source (*.tgz) files.

    Thusly debian will know what's installed. Also, I find your redhat comment confusing - In my experience of RH, (5.2 on my older computer), it does complain about missing packages, even if the binary file is there. I clearly remember having to use the --force option to rpm for certain things (for which I had installed hte dependant files myself)
  • Nope. Debian is NOT a product of the FSF, though there is a lot of good will between the two groups. The GNU in the name is a tribute to the old GNU OS which ended up being the majority of the OS the Linux Kernel was the heart of. Since that time, Linux has grown to the point where the GNU portion is fairly small compared to the rest(not counting programs compiled by gcc but written by other groups).
  • Casting aspersions without downloading and testing is a Bad Thing, but what the fuck. I'm bored.
    They're advertising a development environment 'without the need to learn a complex widget set'.
    If you're a developer, you learn complex widget sets. It's what you do. If you use Visual Basic you're not a programmer. You're a lego builder.

    Of course, just because you're not a programmer if you use this doesn't make it a bad thing; anyting that lets the average user build programmes can only be good for Linux. I'll happily download this new distro and stick it onto a laptop, after which I'll be able to offer some informed criticism. Of course, no-one'll listen. They never do. They're usually right.
  • You're a BSD person, no? One of the things I picked up from Darren Reed's talk at CALU was that in the BSD world, the whole distribution is considered the operating system. In the Linux world, it's just the kernel that is considered the OS. The distinction may be small, but it's important to grasp the concept. You can take a Linux kernel from Debian and compile and run it on a Slackware box. Have fun trying that on a BSD system ;-)
    The differences between the Linux distributions are mainly two-fold, a) the level of FHS compliancy and b) the VAR software included (packaging tools, useless GUI install programs, in some cases commercial software).
    That software still runs under the same OS - Linux. And in fact you can take that software and run it on any other distribution. From what I gathered from Darren Reed, even the exact same distribution of BSD you can't do that on between minor revisions! ('ps' was a case in point)
  • "Debian is a very free and democratic distribution. If your ideas are good, they will be included."

    What?! Only the Debian developers get to choose what gets included. It isn't a democracy. It's an enlightened benevolent oligarchy (one of the developers is enlightened, but he's not necessarily the one who's benevolent :-) )

    If there should ever be a truly democratic distribution, I'll run in terror the opposite direction. And anyone who thinks through the consequences will do the same.
  • This seems very interesting. It's sorta like forms for C..

    pretty slick idea.

  • Perhaps if Linux developers would a) stop
    focusing on making Linux look (and run) like
    MS-Windows, b) concentrate on networking and
    server applications instead of desktop, c)
    make a consistent format that should be used
    as a *standard for all "distributions"* to
    provide a complete base system, then maybe
    Linux will stand a chance.

    there. You have your chance. Why dont _YOU_ make up your own distribution that will suit _YOUR_ need and will have all the essential files in the right place at the right time, and will not look like windows ? I for one personally like the "windows look" because it will prevent me from teaching yet another interface to users who have problem remembering their own phone number.

    Sun Tzu must have been running Linux...
    - Hold out baits to entice the enemy. Feign disorder, and crush him. (Sun Tzu, The art of war)
  • yeah...you guys should read slashdot before you post arti- oh yeah...
    -Matt Jankowski

  • If you weren't aware, you can also use the menu-driven dselect as a front-end for apt-get. dselect does a good job of managing the dependencies between packages, so if you choose to install ncurses-bin, it will also automatically select ncurses-base if you don't have it on your system already.

    Debian may have a slightly more daunting initial install than Red Hat, but I vastly prefer dselect/apt to glint/rpm (even though glint does look nicer -- provided you are running X). I espescially like the fact that dselect gives you a current-to-the-minute list of packages on debian.org. With Red Hat, it always takes a bit of searching to find an rpm I'm looking for (or is there a way to point glint directly at a central rpm server that I don't know about?)

    I saw the Stormix page a few days ago (ooh ahh an on-topic post!) and while I'm always happy to see anything that will bring new users to Linux, this particular distro just leaves me a bit lukewarm. As many have said about the new OpenLinux, all those gee-whiz pretty install screens just increase the chances of things not working right on old/unusual hardware. And do people really find plain old fdisk THAT hard to use?

  • Hmm...following your logic:

    Microsoft is not better than BSD. Linux is.

    I'm glad to be finally able to end that debate once and for all. It has been turning people against each other for far too long. Here's one:

    Microsoft is not an operating system. Linux is.

    OK, that one actually made sense. How about:

    Microsoft is not pizza. Linux is.

    I like Linux pizza. The ingredients are all open source. Here is my grand finale:

    Microsoft is not good. Linux is.

    QED
  • We will never defeat Microsoft unless we all pull together and focus our energy!

    I thought we were just using Linux because we thought it was better. Get your priorities straight.
  • The kernel is Linux, but distribution are different. I have played with RedHat and Debian a lot I all I can conclude is that Debian is superior.

    1) Debian has more flexible installation thethods (direct ftp install over modem, anyone?)
    2) Debian does not detect any hardware during installation. Nebies might think this is a nightmare, but I have seen people who got stuck because redhat installer did not detect their hardware correctly.
    3) Overall quality of packages is way better on Debian.
    4) A way superior suite of package management tools. Dselect + apt-get + dpkg. You do not have to worry about dependencies at all. Whever you select a package, all dependencies and conflicts are solved automatically from dselect (of course you can alter those if you want). Also you do not need to download and install packages by hand. Just say "I want window maker", Dselect will download window maker and a bunch of packages that it depends on and install them. Another nifty feature, apt-get update;apt-get upgrade, will sync your system with the one on ftp server. In redhats case you have to visit erratas page once in a while and if there is something new download and install by hand.
    5) Finally, installation and configuration of "difficult" packages like sendmail and apache is rediculously easy, because dpgk asks you configuration questions during install.
  • s RedHat (the best, IMHO), Slackware, Debian, SuSE, Caldera, Mandrake, Power Linux (or something), McLinux,



    RedHat, SuSE, Debian... RedHat is the most broken of those three. 5.0 and 6.0 are broken beyond repair. SuSE can be thought of as the less broken version of RedHat, and Debian is on top of all of them (see my post in response to the very 1st comment) any ways.
  • D'oh!
    It's the kernel that makes the OS, not the set of packages and their configuration files around it.
    init is just an application, yeah?

    Next you'll be telling us Windows 95 OEM1 and OEM2 are separate OSs because of the filesystem support (FAT32), or something.

    Troll! :P

    ~Tim
    --
  • Well, I've just had a quick look at the screenshots.
    The first was the most off-putting, with "Storm linux. We make linux look good." (in caps) totally contradicting the grammar in "You must now create partitions for Storm to install on top of". Eeeurgh!

    FWIW I agree that there is no need for anyone to go round replicating the Windoze GUI under linux. It's fair enough that fvwm95 exists, of course, but I for one think it would help bring it home to the population as a whole that there are more ways to operate than Maximise, Minimise and Nuke.

    I didn't see that many installation methods - what was it, CD, NFS and something else? What about multi-CD-over-samba or NFS, for example?

    The installer does look cuter than debian's, even in text mode. But how do the run-time package-manglement tools look?

    ~P

    ~Tim
    --
  • Actually, they ARE the same operating system. Linux is the operating system.. The distros are just sets of packages and configuration crap.

  • This is news for nerds, stuff that matters. Linux is in the media all the time currently, and linux news certainly is news for nerds, stuff that matters... So WTF is up your big fat ass? Fine, leave!

    "Slashdot sucks. Slashdot readers are stupid. Slashdot is turning into a linux site." Geez! Shut your sorry whiny ass up!

    I'm sick of hearing about nothing but linux too, so for a while I just skipped all the linux stories... And guess what, it was ok. I didn't have a heart attack, or a stroke, or die of cancer. It's really ok! And I STILL got to read plenty of "News for nerds, stuff that matters"!

  • Hey, don't start slinging insults! That's ridiculous.

    You sure could change /etc with another, probably wouldn't be terribly easy, but you could do it.

    Try swapping the Linux kernel with another OS kernel...

  • I could say the same thing about you, you certainly aren't above slinging insults. You are also an Anonymous Coward. Your reply was also irrelevant, the reply before yours put me in my place. You on the other hand just insulted me with nothing to add to the topic at hand.

    It's been a bad day, I think I'll take your advice anyway and shut up.

  • And how old are you again?
  • Hey! Don't dis what you don't know!

    For the record, I know how to program in C, C++ and Visual Basic (in addition to a number of other varients - MFC, other BASICs, various assemblers, Java), so I know what that other guy says is damn near true.

    The thing that VB has going for it that no other language (with the exception of possibly Delphi, maybe JBuilder) is that of rapid application development. VB is probably the fastest way to bang out code for a prototype (or even a full application) for nearly anything (provided it is for Windows)!

    Would I use it for a console only application? No - though it can be done. Would I use it to write for a device driver? No - I personally don't think it could handle the processing needs (but hey, feel free to prove me wrong). However...

    I would use it for a nifty front end client for damn near anything. Nice games can be written in it. If I need even more power, I can call out to a DLL written in C++ for that extra boost (useful for intense calcs, or for those inner pixel rasterizing ops).

    Business likes VB - it is easy to learn, and can be used to develop applications quickly and painlessly. C/C++ can be a pain to create an app - in any environment (esp. a windowing environment, where it is useful to be able to see how your app looks before you compile and run it) - show me a beginner who can pick up C in a day and code a Windows app, and I will show you a bridge I have for sale.

    That is not to say that VB should be the only thing - and that C should go away. There are many things in C/C++ that I wish I had access to in VB (the mention of getting at the base objects to build your own objects is one). Speed issues are almost irrelevant, since in VB now, the code is converted to C, then ran through the Visual C compiler (though in a few instances, it is still better to code those intense portions in a Visual C DLL, or a COM object, and use them that way).

    I do have a gripe about beginning coders - because Visual Basic allows you to get habits that are bad (like not defining types at the start of the program, etc) - but this is more of a design issue (which many programmers who claim to be C/C++ programmers lack - I hate seeing code that isn't indented well nor commented properly).

    As far as your comment on the apps/utilities by M$ being written in VB? I would suspect that many may actually be written in part in VB. Probably more than you would suspect. If they are not - I can't see any reason why they couldn't be.

    Lastly - don't dismiss me as a M$ zealot - that I am not. In fact, I hate M$ and its business practices - and am currently playing around with Linux (and Legos! - Mindstorms, actually), and seeing what the best way to do development for it is (either Java or gcc/Allegro - I like doing game development, and would like to still support other platforms). I like VB - I just don't like the company that spawned it.
  • If we allow linux to change into anything it's truly not (commercial, for the public) then we are truly missing the mark here. Linux was made so desktop users could use a unix like operating system with big unix server functionality. Personally it sickens me to think of people playing games and "Surfing the web" with it.
  • Look, only a sheep would WANT a universal standard for a *nix OS. Any of the clued would realize exactly what kind of can of worms learning about a *nix is. EVERYBODY should know that there is fragmentation galore in the commercial unices and within an hour of research will be aware of the fragmentation in the Linux and *BSD areas. Deal with it.

    I use the Linuces and *BSDs to port my knowledge that I learned while working on NT and Mac networks. If you know how to run a file/web/FTP server on one OS, run it on another. The variety of OSs and distros helps and I welcome it. 'Course, I'm smart enough to read man pages. It doesn't throw me that useradd and adduser have different names. Jeez.

  • Don't fear the distros (Score:3)

    by Nafai7 ( 53671 ) on Tuesday July 20, 1999 @04:34AM (#1794426)
    I don't understand why so many people seem afraid of these extra distributions. Basically, there are several "primary" ones that about 90 to 95% of the Linux users will utilize. The rest are all secondary or custom distros either based off of those main ones or designed for a specific purpose. These "minor" distros will each suit a smaller group, but perform more specific/specialized functions. Don't use Microsoft as your standard for how OSs should be "marketed".

    Ultimatly all these choices may seem slightly painful, but the extra competition will just feed Linux evolution. We will all benefit in the long run.

  • You still have yet to point out all of the bad things about things like visual programming (Lego Building. I use Delphi, so I can access the widgets if necessary). Would it be easier to use the Legos, than have to remold them each time? (at least in delphi, you can get access to the original "mold", unlike vb...).
  • Err. ya. I had a similar experience with Essential Debian. I loaded it up, went through the rough install. I get to the command line, type ls, and nothing happens. command not found. i figure my path variable isn't setup. env. nothing happens. same error. at least cd /bin worked. IMO, if something as simple as ls and dir do not work right away, that is the sign of a really bad install. Redhat's install is really good, and i think more should follow it. You shouldn't have to fight an OS to get it working.
  • I've seen stories about all of those within the past few weeks. It's not like it's easy for them to go through tons of stories, back check them, AND move their stuff over to andover.net and keep you happy. Besides, it's not them digging up the articles, they just sort through what they can, and post what they do find. If you don't like it, don't be an AC, and start submitting stories.
  • The Borg are defeated by individuals, not by another collective. Individuals differ, compete and cooperate with each other.

    The borg are defeated by


    • Being the bad guys

    • Being stupidly set up with little planning having gone into it.


    Now, since we're living in the real world, we can ignore the first one.

    The second one we can't do anthing about, except to exploit it. Which is fairly easy and is being done.

    The other point is that the Federation are far scarier and drone-like than the borg...

    - Aidan

  • Actually, I accidentally replaced the Debian /etc directory with the /etc from a NetBSD install on a pmax DEC machine. Debian booted more-or-less successfully. I was even able to log in and repair the damage.

    I imagine it would be quite possible to replace the Debian /etc with a RedHat /etc, assuming you adjusted the appropriate pathnames and other minutae. Compare that to replacing the registry of a WinNT install with that of a Win95 install. No amount of tweaking will reconcile them. _They_ are different operating systems.

    -awc
  • You must have done something dramatically wrong. Debian's install is difficult to get going, but once the install process began, it was clear-sailing. It's been rock solid (despite some of the moronic things that I've done to the system) since then. I'm a believer.

    -awc
  • Yep. That was one reason that I was less than screwed. The key init scripts weren't overwritten. But lots of other parts were (including the passwd and shadowed passwd files).

    -awc
  • Although RedHat6.0 comes close, i havent yet
    seen the "Perfect Distribution for Me(tm)", so i welcome every attempt to make it better than the others - after all, thats what Linux is all about: To make it better than the Others (notice the capital "O" ;-)

    As long as the initial installation goes better than with debian, i'll give it a try.

    Free Software is about Freedom.

    The only thing i can see about the history of Unix is this: It has survived and is thriving.

    --
  • I do think he was joking. Its not as if you can do anything in RedHat without dropping down to the command line anyway! And the guy under me, I refuse to use a name such as X11R6 simply because of the excessive amounts of time spent between numbers and shift capitalized letters. If anything whats holding Linux back in the market is the lack of cool names. KDE, GNOME, X, FVWM, what is all that. We need cool names like NUKE, and RADIOACTIVELY COOL DESKTOP, and etc.
    (For mentally imparied, I was being sarcastic above. I shouldn't have to say it, but it seems some people don't get along with sarcasm too well.)
  • Since you mention Visual Basic I assume you count Windows programmers as REAL programmers. No learning widget sets is not what real programmers do, it is only what Unix programmers do. Windows does not use complex widget sets. There are a small number of controls and such, but beyond that, there is none of the stuff that comes with Unix environments.
  • Actually dropping HURD into a debian system will probably not work, becuase there is more Linux in Debian than just the kernel. The filesystem for one thing. In addition any linux distro wil always be like to other distros. Thus Debian Linux will always be closer to Redhat Linux than it is to HURD. HURD uses servers and a microkernel, and a much more updated design. The differnce between Debian and RedHat are only in installation, management and package tools. Remeber a lot of people consider Unix and operating system, and the different ones as flavors of Unix. Linux is a flavor of Unix. By their reasoning, the stucture is like this

    UNIX
    Linux HURD Solaris AIX IRIX
    Redhat Debian, etc.

  • I don't agree with comment you replied to but I don't understand how posting as AC reduces the value of comment. If I register as ABC with e-mail of abc@abcabc.com, does it make me less anonymous?.
  • I am somewhat new to Linux and all it's many wonders, so be gentle :)

    It said that Stormix was based on Debian. Now, would that mean that it's likely the same exploits could be used against a machine running Stormix as one using Debian (e.g. DOSEMU)?




  • I actually chose Debian for my home machine to play with/learn on because it was the distro I was able to find the least number of exploits for.


    Thanks again,
    Matt
  • Debian, RedHat, Slackware, etc. are all separate operating systems. They are all based on the Linux kernel. They are very close relatives in most ways, but they are not the same operating system. If you think they are, I welcome you to replace the /etc and /var directory from any one of them with any other. Other than the fact that they all use the same kernel and share many libraries, they are no more or less related to one another than they are to Solaris, Irix, NetBSD, FreeBSD, and SCO Unix.
  • You're getting all confused again. Not everybody who uses Linux, or wants to give Linux a try, has a pathological hatred of Microsoft and the Microsoft GUI.
  • You apparently are easily frightened. I also dislike Debian, but not because I am afraid of a command line. I'm just an old school Slackware fiend.

    Be careful not to shell down to the Command Prompt on your Windows machine. It will also frighten you. Probably in the same way one of my cats, who has lived indoors her entire life, is frightened when I put her out on the porch and introduce her to the idea of the entire world being open to her.
  • Debian is "like" Slackware except it's at least ten times as complicated to install. The packaging system may be comprehensive, but it's also monstrously complex.

    With a Slackware installation, you just do the install, and then where you want things customized, you use pkgtool to rip out the 'package' and build your stuff from source. That's what "hackers" do BTW.

    You never hear anybody doing any dogmatic sloganeering about Slackware. Because it's old (but the new 4.0 release uses the 2.2 kernel), established, and it works.

    I also like cool things like the loopback distribution called DOSLinux. [tux.org] You can stick such a beast almost anywhere you need the features of a Linux OS.

  • I am not involved with Debian in any way or form, but it seems like any time something gets big that it turns into a hierarchy. There will always be creative people 'on the fringe' of any big movement who want to have their say in ways that threaten a hierarchy, or even that just confuse a hierarchy or aren't considered important enough to pay attention to.

    All of this seems like the kind of reason to fork a distribution, rather than try to work through the layers of contributing the packages to Debian itself.

    The only people who should feel threatened are the people who need to feel threatened, if they even exist.
  • You aren't Microsoft, however, so your fantasies of what you would do if you were are irrelevant.
  • When did any of us start carrying on about virtue?

    Oh, you just did. Oh, oops, you're just talking about not-Virtue.

    My mistake.
  • You are partially right, and partially wrong. When the HURD is ready for the big-time, it will probably be a replacement kernel that people drop into the Debian system (you can almost certainly count on it.) The result will be an OS more closely releated to Debian as it exists now than Debian is to RedHat.

    If you think init is just an application, maybe you'd rather replace it with minesweeper?
  • The proper and respectful term to use is:
    The X Window System.

    People shorten that to X when they are being accurate.

    It is always wrong to refer to it as "XWindows" or "X Windows," which I have seen even supposedly clueful individuals and organizations do (in such places as full page ads in Linux Journal).
  • I consider myself a real programmer, and the only code I've written that is in wide use is some assembly language code I wrote to run on some NEC 4-bit embedded controllers (with 8K of program memory and about 512 bytes of data memory) that operate inside 5 or 6 different medical devices. Your aunt or uncle or even you might be 'experiencing' my software right now, as I know thousands of other people are.

    The first generation version of that assembly code was written using Microsoft Word for DOS as the editor, on a 286 'lunchbox' portable with an LCD display. That hardware was a step up from the 8086 machine I had previously used. (I didn't know any better at the time, believe it or not. No way would I EVER do mission critical code again on old junk hardware nobody else wanted.)

    No, there were no complex widget sets involved, and I didn't use anything easy like Basic or C.
  • Actually, if you're willing to spend about $400 you can buy Interix to install on your Windows NT system. Then you can run a real certified POSIX subsystem (not just the crippled POSIX subsystem Microsoft ships with NT). Once you have Interix happy and running on your NT box, you can use GCC to compile Unix, work in the C shell, and build and run (not just display) X Window apps. It isn't just a layer on top of Win32 like Cygnus.

    Going by the distinctions being made in this thread:

    Linux is UNIX.

    Windows NT/Interix is UNIX.

    etc. etc.

  • When I stated "drop in replacement" I meant at the source level, not that someone with a Debian GNU/Linux CD-ROM distribution could just download a HURD kernel and plug it in.

    I guess I assumed too much.
  • Maybe we should all lobby our congressmen to mandate that the DoD come out with a clean standardized version of Linux (painted green, of course) that we can ALL rally 'round. Then we can begin systematically eradicating all these other 'distributions.' (I'm kidding, of course.)

    It's all kinda-sorta POSIX, anyhow, isn't it?

Slashdot Top Deals

Whatever is not nailed down is mine. Whatever I can pry up is not nailed down. -- Collis P. Huntingdon, railroad tycoon

Close