Slashdot Mirror


User: bugg

bugg's activity in the archive.

Stories
0
Comments
853
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 853

  1. Re:im glad... on Why is BSD Not As Popular As Linux? · · Score: 1

    "with such a lack of knoweldge"

    Apparently, judging by the lack of capitalization. Real gurus follow the syntax of the English language.

  2. Re:A Standard UI on "What is Linux Missing?" · · Score: 1

    twm has been around for 20 years? Wow.
    Kinda hard to belive considering that X has been
    around for only 10. What windowing system
    did twm exist for before X, and why'd they bother
    porting it? :D

  3. Re:Horray. I hate sysinstall on FreeBSD 3.4 released · · Score: 1

    My 3.2 installations went great with IDE disks.
    While it could have been friendlier, it certainly isn't "buggy" per-se. More likely a case of operator error, which isn't anything to be ashamed about because it may not have been too clear.

  4. Re:Negative on that 4.0 thing, its sooner than you on FreeBSD 3.4 released · · Score: 1

    No, "setup" has not hit 4.0-CURRENT and from the looks of it it never will.
    There has been _lots_ of talking about it on the mailinglists, freebsd-current iirc, with a thread similar to: sysinstall: is it at the end of its line?

    You probably won't see setup until 5.0
    Go search the mailing lists for more, too much to cover here.

  5. Re:Super Cool. on FreeBSD 3.4 released · · Score: 1

    With what sort of confidence? "I could fathom a guess"

  6. Re:Super Cool. on FreeBSD 3.4 released · · Score: 1

    I would fathom a guess that a freebsd smp box performs just as well as a linux smp box in the real world.. unless someone can prove me wrong.

    SMP has been making leaps and bounds.

  7. Re:Super Cool. on FreeBSD 3.4 released · · Score: 1

    I've never done the RH6.0 or RH6.1 installs,
    but i've done debian 2.0 and redhat 5.1 installs.

    I'd say that the FreeBSD install is _DEAD_ simple.
    It is as straightforward as you'd possibly want..
    You won't see X-based graphics until 4.0 sometime, so you will have to settle for the console, curses (well, dialog) screen.
    You tell it if you want a minimal, basic, X-user, developer, etc. install, whatever other packages you want, it runs XF86Setup for you, you tell it whether you want KDE or Windowmaker or what have you, you tell it whatever, its dead simple..

    Installation of software is a sinch, nothing is easier than pkg_add -r packagename or cd /usr/ports/category/packagename && make install.

    Stuff doesn't break much :D
    http://www.freebsd.org/
    Read, it'll talk a lot more than I will :D

  8. Negative on that 4.0 thing, its sooner than you th on FreeBSD 3.4 released · · Score: 2

    ink.
    "Those will come with the 4.0 release, later next year."

    Not really "late" next year.. Q1 or Q2, depending.

    Sysinstall is finally being replaced with something a little more modular. Expect to see X-based installs, just like Caldera and RedHat, as an option for users who don't care about the OS but are instead writing a magazine review ;)

    The second biggest change with sysinstall is that if one of the packages is interactive and prompts the user for a question about their mail relays or something else, when the progress meter on the first tty stops, the dialog will come up (For the weenies you don't realize you have to do Alt-F2, i watch _entire_ installs on that screen. Progress bars are for weenies)

    Enough of that. I'm going to give sysinstall source a whirl.. dcs and jkh have been fighting over who does what next ;)

  9. Re:ISO files are "permission denied" on Intel using FreeBSD · · Score: 1

    Want to know why that is?
    3.4-RELEASE just came out today.
    There are some _last minute issues_ with a couple of the minor packages on the cd.. hence, it was set so that you couldn't download them. Wait a few days for it to settle while they fix it up.

  10. Re:Linux or FreeBSD on Intel using FreeBSD · · Score: 1

    Thats because of very bad coding on the part of the authors. Using kernel headers in cases like that is very un-bright.
    Dagrab works great, as well as others in ports..

    PROTEST NON-PORTABLE CODE ;)

  11. Re:Linux or FreeBSD on Intel using FreeBSD · · Score: 2

    What software can you run on linux but not freebsd?
    I bet you you can't name 5 programs very fast, unless you have been training for this.
    Between the compatiblity and just being able to compile it natively, I don't think that is an issue.
    I'm using linux-netscape, linux-realplayer, and even a _linux X server_ (XFCom_Rage128)
    VMWare works now too.
    As for device compatiblity, that is more of a rumor that is becoming less and less true every day. What kind of support for USB does Linux have?
    (snippet from LINT, the list of kernel options)
    # General USB code (mandatory for USB)
    controller usb0
    #
    # Generic USB device driver
    device ugen0
    # Human Interface Device (anything with buttons and dials)
    device uhid0
    # USB keyboard
    device ukbd0
    # USB printer
    device ulpt0
    # USB Iomega Zip 100 Drive
    controller umass0
    # USB mouse
    device ums0

    That's a good amount of support.. and most of it has been there for awhile.
    Even MCA is supported in -CURRENT now, and I don't know anyone who uses MCA equipment still. (Well, I lie, I know one)

  12. Re:wow on Intel using FreeBSD · · Score: 1

    I believe that their customized version is
    getting a license from McKusick for softupdates (http://www.mckusick.com/ follow link) for commerical use. If you want softupdates for home usage, go right ahead it is free.
    McKusick works for BSDi so Softupdates is not
    very free.. but free for home users nonetheless.
    I highly doubt that they changed anything else.
    ...Softupdates is free for personal use
    and i recommend you all add options "SOFTUPDATES" to your kernel and tunefs -n now!

    Softupdates takes the place of a journaling
    filesystem and has the same benefits: two solutions to the same problem.


    /dev/ad0s2f on /usr (ufs, local, soft-updates, writes: sync 53 async 836, reads: sync 2197 async 283)
    (I know you like it)
    And if you are wondering about the ad instead of wd, i'm using the new ATA driver on -CURRENT just
    added a couple days back.

  13. Re:Go Nikola Tesla! on Gigabyte Modems over Electric Lines · · Score: 1

    It'll be a cold day in hell when Tesla dream comes true with all of those inbred southerners whining about how their child is retarted because they live under high voltage power lines and they use cell phones when the real obvious answer is that of FAS.

  14. Crazy people, exercise on JWZ on Dealing with Wrist Pain · · Score: 1

    Jamie didn't cover this enough.
    When you do your weightlifting (as you all should be doing) add in some wrist curls at the end of your exercises (do it at the beginning and you will injure yourself doing other chest or arm exercises) and you'll feel great. Always. I haven't had wrist pain since I started this ~8 months ago.

  15. Re:Excuse my ignorance, but... on Daemonnews reviews Applixware · · Score: 1

    Lame troll, but it should be pointed out
    that it was NetBSD people who started the development of the compatibility layer.

  16. Re:VMware on VMWare/Quake 3/Unreal Tournament on FreeBSD · · Score: 1

    I've used it, its nice.
    Slow on my box, but i think that at leas 99% of that is at the fault of my box and VMWare eating resources :D

    Now we just need vmnet

  17. Re:what? on Stevie Wonder to Implant Eye Chip? · · Score: 1

    The vast majority of people who consider themselves blind have SOME sort of vision. Usually its just the ability to see blobs of color, sometimes its more or less. I don't recall too well what caused his blindness, but if it was because he was a preemie, then it is probably was eye damage (because his brain was most likely fully developed in the senses) which blinded him. It wouldn't surprise me that he could see some things, like a lightbulb or the sun.

  18. Re:Fine, but isn't GPL! on Debian FreeBSD Distro? · · Score: 1

    Developers care about the license?
    I don't, as well as most of the other developers I know.
    In *BSD camp we just care about good code. Thats it.

  19. Re:Oxygen? on Extrasolar Planet's Light Observed · · Score: 1

    Yeah, at either pole days are a year long.
    6 months of light, 6 months of darkness.
    At the equator, days go by the fastest.

    Who knows? This guy could be a scientist working in Antartica.

  20. Re:cool on Mediator Appointed in Microsoft Case · · Score: 1

    isn't that a fairly obscure carvey reference?
    Everyone thinks your crazy.

    That, and shes a... choppin' broccillli!

  21. Re:The Debian Project! on Candidates for 1999 GNU Free Software Award · · Score: 1


    B) Debian is cool. So what if it doesn't have the latest kernel? It's arguably the most stable and
    well-designed of the Linux distributions; certainly the most "BSD-ish".

    "Take what you can use and let the rest go by." (Ken Kesey)

    "Hand in hand, we copy foreigners' merits and compensate our shortcomings." (Fong Sai Yuk) There
    are flashier contributions from individuals and groups, but personally when I think Linux I think
    "Debian", on both technical and philosophical grounds.
    Um, Debian is NOT the most BSD-ish.

    Debian is much more SysV'ish.

    Slackware, OTOH....

  22. Re:I want my BSOD! on SGI announces Linux Kernel Crash Dumps (LKCD) · · Score: 1

    Look into the KDE screensaver.

    the BSOD is alive and well on my FreeBSD desktop.

  23. Re:Now if... on FreeBSD driver database now covers *BSD · · Score: 1

    Did you actually read the first clause?
    Specifically the part about "redistributions must retain the above copyright notice"

    sheesh.

  24. Re:True Story on Which BSD? · · Score: 1



    What card? $30? thats a rip.
    I bought 3 Intel Etherexpress PRO/10+s for $21. Thats $7 a pop.

    If you tell me what card, i'll tell you how to set it up.

  25. Re:The BSD Family on Which BSD? · · Score: 1

    Stuff like cpuinfo shouldn't be in /proc.
    Ask any local UNIX guru what he thinks about all of linux's stuff in /proc, he'll yell and scream at you saying that its dumb.

    Plainly put, /proc isn't for stuff like cpuinfo. /dev would be a better place (cat /dev/cpustat)

    Its non-standard and unprofessional.