bfc

Members
  • Content count

    26
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bfc

  • Rank
    SCRiPT KiDDie
  1. Yea, i clearly like parts of Sawfish, but it seems to be in experimental mode, and the Lisp doesn't grab me as something I want to hack on. I think i'd rather use assembly.
  2. I'd rather something didn't look like Windoze. I just use Gnome with Sawfish on my older box, and Gnome wth Metacity on a newer one. But the annoying things with the newer one: i can't find a way for window positions to be remember next time I restart an App, or next time I boot and a session is restored. And I can use a hotkey to cycle forward from the last workspace to the first workspace. Both of which I can do with the old Sawfish/Gnome box. The only other thing I've tried is Openbox with Gnome, but I didn't put enough time in to customize it properly. I guess I don't know any better about the Gnome speed, though it does feel slower. I rejected KDE long ago because IT looked too windows-like. Frankly, i was just fine on CDE. So does Equinox have workspaces? Can you make it remember favorite window positions?
  3. Ah yes, any VMS command can be given by the shortest disambiguating abbreviation, forgot about that nicety. On *nix I just make an alias if it seems like it's gonna be a consistent typo on my part. Didn't know you could have much control of spawning after the fact. I do remember extensive "batch" facilities. And I'd have to say they're probably friendlier than *at* or *cron*. Re: the verbosity, I mean the output tends to have extra cruft to try to make it friendly. Whereas on *nix you don't have to worry about stripping away extra stuff when piping tools together. If you also have an interest in Ada or Pascal, I suppose you could do a lot worse than VMS. (Or Fortran for that matter.)
  4. You can run VMS on an Alpha, and i'm sure they're around on EBay for pretty cheap -- probably preloaded with VMS so you don't have to worry about loading OpenVMS (haha) or whatever they're calling it these days. There are certainly still hardcore VMS fans, and it might even make sense for a cluster where it was supposedly the best, but yuck, i'll take Linux. Or BSD, or Solaris, or.... I've lived with VMS, and it's a lot easier to say: cmd >& output & # csh ..than.. spawn/nowait/output=output/notify /blah /blah /blah Plus on a Unix system you can change your mind and suspend, background, foreground, etc, anything you want. Plus even slightly older Unices have CDE, which has workspaces. What did VMS have? (I don't even remember.) Not to mention pipes, etc -- whereas on VMS the default is verbosity, so you usually have to add another switch to every command to cut it down to the minimum before hooking tools together. To mention something positive about VMS, it was easy as a user to explore using the help system, there was very fine-grained permissions, the file system had intrinsic support for various types and was probably more stable than Unix for years. But if I was to pick a hobby system to mess around with, I think I'd go more retro (and basic). There's plenty on Linux to play with anyway, so why bother?
  5. If you want to get it done w/o actual learning, you might try a different approach. Go back and make sure you followed the kernel build instructions correctly. Since I cycle through all the mistakes myself, here's a couple: forgetting to run make oldconfig with your old.config if upgrading forgetting to run mkinitrd afterwards You might also forget to do a make modules and/or make modules_install depending on the distro. If the distro has good instructions, then definitely follow them. Try to simply duplicate the existing config before moving onto customization. It's real easy to add what you want and get carried away with turning off a bunch of things you don't want and get carried away. Make sure you can simply rebuild and use the modules and new kernel before you move onto customizations. Using VMWare to debug a new kernel sounds cool, though!
  6. Old post i know, but in case you never figured this out, i was just down a similiar trail. Do you have ip_forward turned on? Don't you also need a FORWARD rule for replies comining back from dns/http? Don't you also want TCP for http? Do you have a default gateway of the host for the guest? In my case, i didn't use any POSTROUTING, and all of the above could be BS, but perhaps some things to think about. I want to feed traffic for a particular port through to the guest, and I also seemed to see some oddities with VM interfaces not seeing everything, but eth0 WAS, so there might be some subtleties there I just don't follow. I was using bridged networking though -- which I could find a good writeup on when you'd want to use what, though. I understand what NAT does, but picking the practical choice between NAT and BRIDGED seems confusing.
  7. I did this study myself because my Linux box was hooked directly to the Big Bad Net for a while before I got a router. Twas very educational, and perhaps headache inducing at times. A little googling (or the sites people have already given you) will show some boilerplate rules that should be on most every firewall. For example, many local nets may use 192.168.0 as their subnet, so if you see traffic coming from the outside *claiming* to be from that subnet, you drop it. You pick default policies (Accept, Reject, Drop..) for your main chains, like INPUT, OUTPUT, and FORWARD, then you make exceptions to suit your taste. Then you can move on to dealing with fragments, if you like, or filtering by MAC address, and so on. Kernel rebuilds may be required for more advanced stuff. The nice part is that I can now safely forward anything i want from the router, and watch the attack attempts from the outside, or let particular IP's in to particular ports. And the possibilities of logging from iptables does WAY better than the pathetic router log. Some day I'll play with some forwarding and/or masquarading to a VM running Apache. I also understand there's friendly GUI frontends to iptables, but I haven't played with them.
  8. You really can't get more memory? I just got more mem for an 810 board (866MHz P3) -- it only maxes out at 512MB anyway, but that's a big improvement from the 256 i was running with. It's been enough to start playing with VMWare. Memory usually counts for a lot more than CPU -- my rebuilds of the kernel may take quite a while, but other than that it's just the sheer amount of crap I like to get running at the same time that will really make it sluggish.
  9. Haven't tried Ubuntu yet, so this will be more generic Linux thoughts.. I use gaim for IM, it talks AIM/Yahoo/XMPP and even ICQ and MSN, though i only use AIM and Yahoo regularly. I think Trillion looks a bit slicker, but there's really only so much an IM client has to do, unless you're swapping files using it. I encourage even Windoze users to use Gaim to save themselves from the malware that AOL distributes by default. And i think Trillion and gaim share the same plugin engines anyway. That's why when Yahoo changes the protocol to shake off 3rd party clients, both of these clients get back on at the same time. See http://gaim.sourceforge.net. I've used xchat some for IRC because it's generally just there, haven't tried anything else since the olden days with a total CLI client. I use VLC to play Windoze crap, otherwise xmms or plaympeg or whatever. VLC will play pretty much everything, i guess just like mplayer, and i can't argue which one's better. But either will play DVD's, as will Totem, which i think is old hat. I use cdrecord for creating CD's -- it might not be that friendly, but once you make it work once, you can potentially do things faster than cranking through a GUI. With the security stuff ... if you don't have a service listening, then it can't be attacked. And if you don't set your router to let services through, then they also can't be attacked. I just switched to the Belkin G recently, and found that while the GUI was a bit clumsier than Netgear, it did most of the same stuff. You have to use "Virtual Servers" to let specific port traffic through. Reset your default admin password, turn on encryption if you care to, turn on MAC filtering if you care to, etc. If you have time on your hands, run 'setup' on your Linux box, select 'services', and see which ones are turned on, and hit F1 (i think it is) to see the description. There may be many you can shutoff. Although there may be something friendlier than 'setup' on Ubuntu. Turn off services that you know you're not using to save memory and lesson security issues. If you have even MORE time on your hands, you can hand craft the iptables rules, but that's certainly a headache-inducing chore. Once you do it, you can let some more ports through your router just to watch the attacks on the Linux box. The Belkin doesn't seem to log for crap. Sorry SO long winded!
  10. It's really not much fun to talk about packet layouts with human beings. And believe it or not, the RFCs are more readable than most books, and a better reference in most cases. I couldn't begin to spill out the TCP state diagram, and that might actually be described better in some book (like one of the Stevens books), but I've certainly had to crawl through hex counting the bytes, and for that, the RFCs are the best!
  11. I just mount vfat drives (the old 8X3 file names supported by earlier DOS) onto Linux, say under /dos. Same thing with NTFS drives, but they only became read-writable relative recently, say in the last few years. They say the ntfs support is "safe" in that it won't make a mistake but it's not guaranteed to work every time, and if it can't, it won't even make the write. Does that make sense? So you'll get the file and/or blocks written correctly if success is claimed. In practice, I never had a problem with it, but I didn't use the NTFS drive as an ongoing dumping ground as I've frequently used my FAT drive. If you're twisted enough to run Linux under Windows instead of the other way around, I couldn't imagine if this would be a useful way to work or not.
  12. i thought 'sam' was for HPUX, and 'smit' was for AIX. See if 'smit' runs -- and i think that gives you all the sysadminny stuff. AIX frowns on doing things the old fashioned way (editting configs), but at least you can easily expose the commands that are running from what i remember. Otherwise i think AIX should just be another SVR4, not my favorite, but definitely better than HPUX.
  13. I think you need your own DNS if you have users on the inside that need to access machines by internal IP's on your own subnet. You may also have DMZ machines that should be accessed by another interface and IP.
  14. This is a good opportunity to see if i understand this correctly. VMWare Server allows you to create vmx files (VMWare images) of running "real" versions, right? But even with the mere VMWare player, i can get a session going (potentially bootstrapped from QEMU), change some things, and my current state will be saved when I exit... so I could take those session files (vmdk,vmx, whatever the memory file is), back them up, and essentially I've made my own reusable snapshots anyway, right? Just not sure which direction I wanted to go -- and whether the Server was worth the trouble over the Player. I'm not planning anything complex, prob. just try some distros out, potentially run an old Win version underneath very occasionally, and that sort of thing. And I have only 512Mg to work with.
  15. OK, that link http://www.sysresccd.org is still live, i just looked. I think they include everything you need if you want to recover some space from your NT installation. If you've run the defragger once through I expect that's fine. Given your nervousness, you shouldn't touch anything until you back it all up if you care about your existing bits. Then download the iso from the above link, write yourself out a rescue CD, and reboot to the CD. Select the gparted, select the disk to edit, select a partition to edit from the disk (if there's more than one), and then bring the size WAY down. I also remember, vaguagely, you have to COMMIT the changes somehow before it will do anything (it's been a couple of years now). Then you'll be ready for a normal Linux install.