blackmath

Members
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About blackmath

  • Rank
    SCRiPT KiDDie

Profile Information

  • Interests
    Horseback riding, long walks on beaches, virgin daquiris, and your mom
  • Location
    Purgatory

Contact Methods

  • Website URL
    http://
  1. Stumbled upon this article earlier today: http://voipforenterprise.tmcnet.com/featur...ndows-linux.htm Is MS finally getting the hint that they can't smash Linux? I've always been of the opinion that Microsoft's best move (on their part) would be to start immersing themselves in the *nix world, instead of trying to fight it every step of the way. Now, whether this is a good or bad thing for the Linux community is yet to be seen. Personally, it makes me a little nervous, but it does pose the promise of making the transition from work (Win) to home (Linux) a little easier, especially if they get the MS Office and Open Office compatibility thing worked out, as the article claims they'll be working on. What's funny is Microsoft's and Novell's history, especially the release of Windows NT, when Novell was the big bad empire. Kind of a role reversal now, and a bit cyclic if nothing else. Your thoughts? EDIT: I hadn't noticed, but this topic had been brought up in the Links forum a few hours ago. Mods, feel free to remove this if it seems too redundant.
  2. kismet works fine for me, but I don't use it for much more than identifying networks and bit of other simple profiling. mplayer does suck tho. EDIT: sorry, I haven't tried kismet from the edgy repos... I was speaking from a purely Dapper standpoint, so I'm not sure if they're using the same build or not. I realized this after I re-read your post, livinded.
  3. Tried Edgy, didn't see any mind-blowing improvements as I had hoped (the new init replacement didn't shave much off my boot time, as I had tweaked Dapper's startup a bit), and couldn't get XGL/Beryl to work quite right. Back to Dapper, and quite happy.
  4. Dirk: You can hit Alt+F2 in Gnome to bring up a "Run" dialog, from which you can run commands. Alternatively, one could also add a launcher to their Gnome panel, with the amsn (or other) command. however, if an app doesn't show up in your Applications menu after installation, you can usually enter this in a terminal window: me@mycomputer:~$ killall gnome-panel That will restart the Gnome Panel process, and refresh it, so to speak. Usually does the trick.
  5. Ubuntu is sticking with a very strict policy about not including non-free software by default (not free as in free beer, but free as in... well, you all know this argument). It's simply a matter of uncommenting the universe and multiverse repositories in your sources.list file. I've never seen a DRM agreement during Gentoo install, and I've tried everything from 2005.0 through 2006.1. I'd like to give Slackware 11 a try, especially with one of the 2.6 kernels. Can someone point me to a good resource about Slackware package managers, or rather, how to teach my babied arse to manage software and dependencies without a package manager?
  6. http://www.distrowatch.com
  7. Ubuntu (and sometimes Fedora) is a great stepping stone to one of the "harder" distros, especially if you have a machine that Ubuntu likes (shortly after I got my laptop, Ubuntu was the only distro that got almost everything up and running immediately after install). You gain a confidence that "yes, linux really CAN work on my computer", and spend most of your time fixing the little things rather than pulling your hair out just trying to get X to work. Moving to something harder after that isn't so bad, because it becomes a learning experience rather than a "I need to get this running so I can log on to BinRev forums!!!!" type of deal. You can always fall back to an easier distro if things aren't working out, rather than falling back to Windoze. But yes, you'll find a great number of people here that have or are using complex distros like Gentoo and whatnot, and that you can find a lot of help from the friendly folk in these forums.
  8. Redhat 5(.5?). Never could get my modem working, and thus, couldn't find online help. The book I bought was crap as well, so I abandoned Linux for a while... Started using SuSE before Novell bought it, and it worked great, although no support for my wireless card at the time (ndiswrapper not available yet?), so I used wired ethernet to get on my network. Kind of annoying for a laptop. Started having to do a lot of work at home, requiring me to remove SuSE and reinstall Windows (proprietary software + small hard drive, couldn't feasibly dual boot). Got a new laptop in 2005 and it wasn't long before I wiped my HD and installed Slackware 10.1. Had some problems with my newer hardware and tried Ubuntu. Worked like a charm. A friend convinced me to try Gentoo, and I was on a Gentoo kick for several months (2005.1 release). Gave SuSE 10.1 a try, to see what this Compiz buzz was all about. After using apt and portage for a while, I couldn't stand RPMs and yum, and SuSE was more of a resource hog than Ubuntu was. Went back to Gentoo (2006.0 release), and hated the new installer and its numerous problems. Gave Ubuntu 6.06 a try, and that's where I've been since mid-June. Thinking about giving Gentoo another go to see if the 2006.1 installer works a little better, or perhaps waiting for Ubuntu 6.10.
  9. free world dialup assigns you a fwd number. Like 123456. Your SIP number, for all intents and purposes, would be 123456@fwd.pulver.com. This is so other SIP clients can call you by knowing what service you're using (fwd.pulver.com in this case, aka free world dialup), and your ID on that service (123456 in this example). It's not someting assigned to you by asterisk when setting up, it's an identifier you get from the service you use. HTH
  10. The beauty of Linux. Welcome aboard matey!
  11. No, Ubuntu creates a root account just like every other distro in the universe. I do not consider a seemingly disabled root account without a password "set up". You must take addtional steps outside of a normal install to get it "set up" and directly useable (i.e. log in ability, etc.). It tells you this in the Ubuntu docs. Sarcasm and semantics. Much <3, tehbizz. And yes, this is a step in the right direction.
  12. Yeah, by default Ubuntu does not "set up" a root account, only a user account from which you will work. You can issue commands as a superuser with sudo (as mentioned above). Once you're up and running, I suggest installing Clam AV (antivirus), and Firestarter (firewall). Just run Synaptic (System > Administration > Synaptic Package Manager), and do a search for those two packages.
  13. Ha! You actually helped me out! I had read a long time ago that LED support for ipw2200 was not there, and never bothered checking into it since then... I now have a working wifi LED on my lappy! The beauty of the binrev forums!
  14. Strange that the Ubuntu drive would mount during the Slackware install, but you should still see it in fdisk. fdisk will show all your partitions, mounted or not. I am under the impression you are working with a single, 120GB SATA drive, correct? The reason I ask is because if you're using two drives, fdisk will only see the partitions in the drive you specify when running fdisk (# fdisk /dev/hda OR # fdisk /dev/sda for SCSI/SATA drives). So, if by chance you are talking about two drives, say two SATA drives, you can only run fdisk on one at a time (# fdisk /dev/sda for the first one, and # fdisk /dev/sdb for the second).
  15. Hmmm... Strange. This really should get moved to the *NIX forum. Possibly (because I haven't tried Slackware since 10.1? earlier maybe?), Slackware installs grub now? What version of Slackware are you attempting to install? The Slackware installs that I remember ask you at a point if you want to install LILO to the MBR, to a floppy, etc. If you didn't choose the MBR, or possibly skipped that step at some point, then GRUB from the Ubuntu install will still be there. Which, if Ubuntu is no longer there, will error out. Either way, something is fuX0red. fdisk should recognize all partitions on your disk, whether or not there's Ubuntu on one of the paritions. That shouldn't matter. Ideally, you should be able to see any created partitions in fdisk. If none are listed, then none have been created (or were deleted somehow). Create a new parition, the full size of the disk (+120000 MB) and see if it will let you. If it does, then your whole disk is available to you. Delete the one you created, then proceed to create your Linux partitions, swap, root, home, etc. If fdisk tells you that you don't have 120 GB of total HD space, then something definitely is wrong. I'll keep your problem in mind, but I have to run out for some food and whatnot.