Posts by TheOgre

No Problem ;-)

Feel free to look me up when you're ready to give it another go.

In /etc/fstab, the three entries here show your Windows partitions:

/dev/hda1 /mnt/hda1 vfat noauto,users,exec,umask=000
/dev/hda5 /mnt/hda5 vfat noauto,users,exec,umask=000
/dev/hda6 /mnt/hda6 vfat noauto,users,exec,umask=000

If you want to access your Windows partition(s) under Linux, you have to mount the partitions to their mountpoint.

Let's examine the first line and break it down so you'll understand what it means:

/dev/hda1 is the first partition on the primary drive (/device/harddriveapartition1 is an easy way to remember it)

/mnt/hda1 is the mountpoint, or "local directory" where that partition gets "mounted" to the filesystem

vfat indicates the filesystem Linux will use to access the partition. FAT32 is accessed using the vfat module. (man mount for more detailed information.)

noauto tells the system not to automatically mount the partition during boot time.

users indicates that all users can mount this partition, not just root.

The rest you can safely ignore for now, as it's not pertinent for accessing your Windows partitions under Linux.

Now that we have a good idea on what all that means, let's put it together now...

To mount the first Windows partition (/dev/hda1) to it's mountpoint (/mnt/hda1) type this:

user@host$ mount /mnt/hda1

To see if it was successful, unless you received errors to let you know it didn't work, you can either type mount all by itself, which will list the mounted filesystems, or you can look in the directory to see what's there:

user@host$ ls /mnt/hda1

If everything worked …

-If FreeBSD is going to be the only O/S installed, the boot manager isn't needed.

-It's not a good idea to configure the system as a gateway unless that system is going to be used as a gateway/router. For a standard install, they should choose [N] when asked if they want to configure the system as a gateway.

The FreeBSD Handbook is the best place to find answers for installation questions, or for information on anything regarding the FreeBSD system configuration.

Yeah, giving up is the way to go. It's alot easier less pain.
Debian probably doesn't even work.
Check out Mandrake, SuSe or Fedora.
Yeah, best to give up instead of seeking help.

Nice. We're supposed to be assisting people, not browbeating them because something they were trying didn't work.

Some people will suggest, a noobie to start with Redhat,Mandrake or fedora......While in all reality, those people probably use linux sparingly. They might say it's easy to install,update,configure,upgrade,install pkgs...ect ,this a false myth. In reality the more advance the easier the installing,upgrading,updating...ect

I disagree. It's not a myth at all, but a reality. Those distributions were designed with "easy" in mind, regarding installing and upgrading packages. Show me a first-time Linux user who knows anything about compiling from source or patching a kernel. All they have to know is "rpm -i filename.rpm" and it works for them.

What you're saying is, "the harder it is to do, the easier for them it will be." That's like saying, "If you don't understand it, it will be a piece of cake." The average person trying out Linux is curious, like all of us who've been using Linux for years are. They want to experiment with something new and/or different to them, see if they like it, and maybe use it. Others just want to see what all the hype is about. Others yet are looking for a real alternative to something with a Microsoft brand name on the package, and they need to find out which distro will work the best for them.

I recommend Debian to people wanting to "check it out" simply because it's a very good distro. Knoppix, Gnoppix, Libranet, LindowsOS, and a slew of others are all based on Debian, so they're pretty much the same …

What services are running on your system? What O/S are you using?

Another thing to do is to disable the Windows Messaging service, which is used by spammers to send popup window ads using SMB:

Open Control Panel

Double-click on Administrator Tools

Double-click on Services

Locate "Messenger" in the list of services.

Double-click on "Messenger"

Click on "Stop"

After the service is stopped, disable it by choosing "Disabled" from the dropdown list next to "Startup Type:"

NOTE: Another thing to disable is the Remote Registry Service, unless you have a program that you know for sure uses it.

Bridge.dll is Ad/Mal/Spyware. To remove it, delete the following files:

C:\WINNT\SYSTEM\A.EXE
C:\WINNT\ryegrjof.exe
C:\WINNT\SYSTEM\SSUpdate.exe
C:\WINNT\SYSTEM\npnzdad.exe
C:\WINNT\Application Data\DownloadPlus.exe

Open the Registry Editor (Start | Run | "regedit")

Navigate to HKLM\Software\Microsoft\Windows\CurrentVersion\Run

See if one of those files in the above list is listed in that key, and if it is, delete JUST THAT LINE from the key.

When you reboot, you shouldn't see that error again.

I would *highly* recommend NOT using wu-ftpd, as it's an exploit magnet. I don't know too much about Macs, but being that Panther uses Darwin, which is based on FreeBSD, I'd suggest using ProFTPd instead. It's much more secure (about as secure as a non-secured ftpd can be, anyway) and is more or less the industry standard.

http://www.proftpd.org (Homepage)
http://fink.sourceforge.net/pdb/package.php/proftpd (Mac package maintainer)

Mac ProFTPd Configuration HOWTO:
http://www.projectomega.org/article.php?lg=en&php=tuts_howtos3&p=1

WC: No biggie. Thx for the rate, BTW.

bigpoppapumpg: Whats the status? Do you still need help locating the proper module, or is it working now?

I realize this post is old, but I just saw it and had to respond :)

Since Windows (any version) doesn't recognize Linux filesystems, you'll have to use either lilo or grub under Linux for a dual-boot system.

Also, before you edit/modify the boot.ini under Windows, remove it's READ-ONLY attribute before editing it.

Personally, I think you should be taking this up with Mr. Irving, since he was kind enough to post his e-mail address and offer to replace the unit for you, even though it's passed the 30-day limit. If you want to post your rants about it, get some free space on GeoCities and have at it. This forum is for questions and answers, not for badmouthing a company that sold you a a cheap part that happened to be defective.

That being said, there's the old addage, "You get what you pay for."

Windows DHCP servers start out with the lowest number in the pool - *nix boxes start off with the highest number in the pool.

In lilo, to make Windows the default boot operating system, simply make Linux the last entry in /etc/lilo.conf

Depending on which editor you use, you can either copy/paste the lines, or retype them manually.

Another key element is to RUN LILO WHEN DONE MAKING CHANGES TO LILO.CONF. If you forget to do this, none of the changes you made to lilo.conf will take effect. It might help if you add a line to the bottom of lilo.conf reminding yourself to run lilo after saving any changes:

root@host# echo Run lilo when after saving changes >> /etc/lilo.conf

Anyway, to answer your question, here's one way you can make the change:

At the bottom of /etc/lilo.conf, look for something similar to:

# Linux bootable partition config begins
  image = /boot/vmlinuz
    root = /dev/hda3
    label = Linux
    read-only
  # Linux bootable partition config ends
  # DOS bootable partition config begins
  other = /dev/hda1
    label = Windows
    table = /dev/hda
  # DOS bootable partition config ends

To make Windows the default booting operating system, simply move the Linux section to the end so it looks like this:

# DOS bootable partition config begins
  other = /dev/hda1
    label = Windows
    table = /dev/hda
  # DOS bootable partition config ends
  # Linux bootable partition config begins
  image = /boot/vmlinuz
    root = /dev/hda3
    label = Linux
    read-only
  # Linux bootable partition config ends

After you've done that, run lilo and check the stdout (standard output):

root@host# lilo
  Added Windows *
  Added Linux
  root@host#

(In …

I always suggest to read the manpage(s) because that's where the core documentation is located. Granted, you can search Google.com to find answers, but what happens when you can't get online to use Google? Suppose you're trying to find out how to set your IP address so you can get online. Knowing where to find the information is one of the key things in both Linux and UNIX, and surprisingly, when you get in the habit of reading the manpage(s) for something, you tend to retain the information you've learned from it better and longer than if you just copy/paste something found on the Net.

I also mention the proper manpage(s) for the specific item in question as a reference for further information, along with other sources, if available (like info, apropos, etc.) If anyone is seriously wanting to learn *nix as a trade and not just a hobby, knowing where to find the information to a particular system is crucial.

I may not be the most knowledgable person when it comes to Linux and/or UNIX, but I've been using Linux for the past 8 years (Slackware & Debian) and UNIX (Solaris, HP-UX, and FreeBSD) for about 6, so I know the easy way to find answers to something in a hurry, mainly because I RTFMP :)

Well, you just answered that one yourself. He didn't say he was using a onboard nic.

No, he said his mobo had an onboard mac:

my nforce2 mobo uses the embeded nvidia mac, but im not sure which one this is.

I was clarifying for him in case it was a typo.

I will admit, you through me off saying Realtek.

That's why I prefixed the comment with Example: as I always do when giving an example.

As root, try this:

XFree86 -configure

It's not perfect, but it will probe your system's hardware to see which configuration variables should be set. This will give you a good starting point with XF86Config. You can test the configuration file it generates by following the instructions it gives you after it completes.

As always, read the manpages. In this case, man XF86Config

The same can be said about any programming/scripting language. I was referring to when Perl code is good. Personally, I've never made it further than "Hello World" with Perl, but everyone I know who does know Perl (among others) say that it's their language of choice, when given the option. According to one collegue, "Why write 5000 lines of C code when I can write 200 lines of Perl code to do the same thing?"

Frankly, Verisign and the RIAA should be piped into /dev/null - right along with the MPAA IMHO.

You can either get a 1 year subscription for $15 (I think), or you can get a lifetime membership for $99. Either way, you have access to every image he's created for the last few years, plus the "pickle jar" plus videos, wide & dual screen versions. It's highly worth it for the bucks, if you're into wallpapers.

I have a few modules I downloaded with tons of network devices in them, but i have no idea which one to specify. my nforce2 mobo uses the embeded nvidia mac, but im not sure which one this is. anyone have any idea how i can install this network module?

Each module is for a specific NIC. If you donwloaded more than one module trying to figure out which one to use, first figure out what NIC you have and search google for the corresponding module. If all else fails, use modprobe until you find the right module. (modprobe is how you install a module. You can also you insmod if you know which module to load.)

man modprobe
man insmod

You shouldn't have to worry about parameters until you have the right module loaded, and even then you shouldn't need any extra parameters unless recommended by the manufacturer.

nVidia doesn't make NICs. Did you mean the motherboard has an onboard video adapter?

(Hint) If your mobo has an onboard nic, turn it off in the BIOS.

Why would he want to do that, when he's trying to use it?

This is a BIG no-no:

ServerName dns1.manitobamotorsports.com

That's the same thing as saying your machine is the primary DNS server for the domain manitobamotorsports.com

ServerName is the address of your webserver.

Example:

ServerName [url]www.manitobamotorsports.com[/url]

...just FYI...

You can use this nifty lil util I've been using for the past few years now - PowerMenu. Unzip and run the .exe (there's only 3 files in the .zip, and 1 is an .html README page. The other file is a .DLL)

No installation, no fuss, no mess :)

Works on any program in all versions of Windows. Also adds the ability to change the transparency (sp?) of a window, and to make it "always on top."

http://www.geekis-kahn.net/files/Win32/PowerMenu_1_5_0.zip

MD5: fc4d96434c03567e481a30809ebf33fb *PowerMenu_1_5_0.zip

(After you run the .exe, just right-click on the titlebar of a window and choose "Minimize to tray.")

... I'm convinced that that company is not run by humans, but by Perl scripts. ...

If it were run by Perl scripts, there wouldn't be a problem :)

Samba 3.x is designed to replicate Active Directory, as well as work as a PDC with Windows 2000 and XP. Previous versions (2.x) emulated a WINNT 4.0 Server that worked well as a PDC for WINNT 4.0 and Windows 95/98, but didn't cut the mustard with 2000/XP. If you're not going to use Samba as a PDC for your network, staying with 2.x should be fine (I still use 2.2.8 ...)

Regarding VMWare, you probably won't see much of a difference upgrading to 3.x unless you're testing the Active Directory changes, which I'm guessing you won't be doing, at least for now.

username map = /etc/samba/smbusers
....
username = owner
valid users = owner
admin users = owner

[homes]
comment = Home Directories
valid users = %S
read only = No
create mask = 0664
directory mask = 0775
browseable = No

[root directory]
comment = root
path = /
read only = No

[home]
comment = home
path = /home
read only = No

First off, I HIGHY RECOMMEND NOT SHARING OUT THE ENTIRE ROOT PARTITION! This is VERY BAD! If you want to share the filesystem to get used to the layout, share it as READ ONLY.

Also, the following three lines are safe to comment out - they might be causing grief:

username = owner
	valid users = owner
	admin users = owner

Also, if you don't have a usermap (username map = /etc/samba/smbusers) it's safe to comment that line out.

It also appears you're sharing out the /home directory as well as each user's $HOME directory. If it's just you who'll be accessing the files, I would just keep the [Homes] section and create a [Public] section and use that as a file dump. That way, any files you want to share, you can copy/move from/to the public filedump and leave the rest of the filesystem intact.

Here's one of my smb.conf files to give you an example:

[indent]
# Samba config file for Mars.geekis-kahn.net
# FreeBSD 4.9-RELEASE
# …

For whatever my 2 cents is worth, I've been a Microsoft OEM System Builder since 1996, and I've lost track of how many systems I've built over the years (my Microsoft Certified System Builder cert is from 1998, for Win98 & WinNT 4.0 :P)

I would highly recommend using an AMD processor (CPU) over an Intel Pentium, mainly for price, and also because the Athlons have improved greatly over the past few years (all my new systems are built with an AMD processors, including the rack servers.)

I certainly agree with Tek about NewEgg.com. I've had my reseller account with them for about two years now, and they're top-notch. I don't even bother looking anyplace else for parts.

My advice is to use name-brand parts when possible. It might cost a little extra, but it's worth it if you ever have to get an RMA for a week-old video card. I built my sister a machine a few weeks ago, and the entire box cost $515.84 in parts, complete with a 15" LCD monitor (512 MB DDRAM, nVidia Ti 4200 64MB video card, Western Digital 80GB hdd, Intel EtherExpressPro 10/100 NIC, etc.)

If you're looking for reviews on hardware, check out Tom's Hardware: http://www.tomshardware.com

I have a Lifetime Digital Blasphemy membership :)

From Microsoft's HALO site (http://www.microsoft.com/games/PC/halo.aspx#sysreqs):

System Requirements

* Microsoft Windows 98SE/Me/XP/2000
* PC with 733 MHz equivalent or higher processor
* 128 MB of system RAM
* 1.2 GB available hard disk space
* 8x speed or faster CD-ROM drive
* 32 MB T&L capable video card required
* Sound card, speakers or headphones required for audio
* Microsoft Mouse or compatible pointing device
* 56.6 Kbps or better modem or LAN for online play; broadband to run a server

From the README.txt included in the Dedicated Server installation (yes, I actually installed the Dedicated Server just to get the system requirements..)

Halo Dedicated Server requires a personal computer with the following minimum requirements:

Multimedia personal computer with a 733 MHz or higher processor.
Windows 98 SE, Windows Me, Windows 2000 Service Pack 1, or Windows XP.
128 Megabytes (MB) of RAM.
200 MB of available hard disk space.
Keyboard and Microsoft Mouse or compatible pointing device.
Broadband internet connection.

It also depends on what ports they have open, if they allow only HTTP and POP3 outbound connections, etc. Have you tried connecting to the net via dial-up an tried connecting that way? (You bypass their infrastructure, and if you can connect via dial-up, you know it's their firewall that's blocking the ports.)

Can you post the contents of your smb.conf file so I can have a look-see to see where the problem might be?

OK, here's one for you MS gurus: I have a client who recently had a local "expert" remove a bunch of "infected" files from a WinXP Home box. Problem is, I have no way of knowing which files were removed, compared to the actual infected files (I don't have access to the machine, since it's in Maine and I'm in NJ...) The problem shows it's ugly head when she opens IE and tries to login to a secure server - no go.

I had her do "Help | About" to see which version of IE she had, and it turns out there is NO encryption listed, and NO VERSION in the About box.

What I need to know is, should I walk her through reinstalling IE, followed by a Windows Update, or is it worth bothering with? Should I have her do a reformat/reinstall of the O/S? I tried to walk her through using Windows Update, but her browser can't even access the update site.

Any ideas?

(I have no idea which virus was supposed to be on the system, or if that was even the case at all. Some local wannabe tech who's taking self-study Windows 101 courses did the job for free while working at Burger King...)

Sygate beats the pants off McAfee, Symantec, ZoneAlarm, Tiny, and a slew of others.

If you're on high-speed (broadband) Internet, you can expect a lot of portscans, probes, and other "scans." Most of these are harmless, unless your ports are hanging wide open.

There *should* be an option of some sort to limit the notifications you receive about portscans & such. Sometimes they're referred to as "silent" alerts, wherein they only show up in the logfiles, as opposed to popping up some sort of alert box.

If you don't have access to nmap, or don't know anyone who has it/knows how to use it/knows what it is, feel free to ask one of the *nix gurus for assistance.

...and don't bother with Gibson and his drivel...

OK, got HTTP (Apache) working on port 5906 and mail (qmail) running normally on 25. I'm routing external requests for 5906 to internal port 80 (via my FreeBSD firewall/router), and it's been working fine for over 2 weeks now. I've also added SquirrelMail, which makes checking e-mail on the road a snap. I've had FTP running normally on port 21 for over 2 years now, and I'm hoping the additional bandwidth isn't going to draw any attention to OptOnline anytime soon...

Or, for less than $9/year you can register/renew with GoDaddy.com or one of their affiliates (like me) for even less...

I cringe when I hear that people are still paying $35/yr for a domain purchase/renewal/transfer!

For Apache, in httpd.conf, look for this line:

AddEncoding x-gzip gz tgz

It's usually on by default, but if it isn't, you can add/uncomment it within <IfModule mod_mime.c> so it reads like this:

<IfModule mod_mime.c>
AddEncoding x-compress Z
AddEncoding x-gzip gz tgz

If you don't have that module loaded (mod_mime.c) then it won't do you any good, so check the Modules section to ensire it's being loaded.

Don't forget about gnoppix, which is basically Knoppix with a Gnome wm, as opposed to KDE.

http://www.gnoppix.org

There's also LindowsCD, which is the same thing as Knoppix & Gnoppix - a Linux distro that runs from the CD (Live CD), in this case, Lindows.

http://www.lindows.com

If you store the config file for X (XF86Config) in root's $HOME, then only root will be able to read that config, and if you try to launch X as a different user, that user will be reading the other (bad) XF86Config file.

To fix this, locate the other XF86Config file (usually /usr/X11R6/lib/X11/XF86Config) and rename it to XF86Config.old :

root@host# cd /usr/X11R6/lib/X11
root@host# cp XF86Config XF86Config.old

Then copy root's XF86Config to the same location and make it world readable:

root@host# cp ~/XF86Config /usr/X11R6/lib/X11/
 root@host# chmod +r /usr/X11R6/lib/X11/XF86Config

Also, ~/.xinitrc is the file that determine which window manager you will use when starting X. On Slackware, if you use xwmconfig, it will give you a text menu to choose your window manager. In FreeBSD, you have to manually create the file and edit it for your preferred wm.

Example:

user@host$ cd
 user@host$ echo startkde > .xinitrc

What NIC does the mobo have? Once you find that out, you'll be able to find out which module for the NIC you need.
Example:
NIC = Realtek 8139
Module needed: rtl8139.o

To install the module after you've located/identified it, you use either modprobe or insmod

...an encrypted shell account? I've never seen or heard of one of those, and I've been on IRC for a VERY long time. Could you explain to me what that is? I know what a bouncer is (like bnc), but I've never heard of an encrypted shell account. Or do you mean using SSH to connect to a UNIX shell account?

Nice job on the tutorial, btw :)

do:

ps wax | grep swat

and see if swat is running. Some distros install swat with samba, others don't. You also have to edit /etc/services to enable swat, or add the entry if it doesn't exist. Read the manpage for swat and it will show you an example of this, or refer to Dani's tutorial (I think she has it in there...)

If swat isn't running, then port 901 won't be listening, which will give you the error you received.

If you would read my last post and paste the output you're getting so we can see it, it'd be a lot easier to see what you're doing and why it isn't working...

qmail would be a LOT easier to configure. I had mine up and running in about 20 minutes.

when i get to the samba directoy in the terminal and i type ./configure gives me no such file or directory...
i get stuck on that part
THE rom file that BOX suggested should i download the client or the server???

Copy the output (when you type ./configure) and paste it here. Then type pwd and paste the output here so we can see what directory you're in.

Obviously, you need to be in the correct directory or you won't be able to complete the install. If you do ls and only see one thing, it's usually the directory created when you unpacked the tarball. You need to change to that directory, do ls, and if you see configure*, you're in the right spot. Just follow the instructions that were posted before and you should have no problem.

If you want to share directories from this machine to Windows clients, you'll need the server. If you download the full tarball from www.samba.org you'll have the full installation (client and server.)

Is there:cheesy: such a think as a fedora box............. lol

I don't know, but I know such a thinG as a Fedora box exists :)

chmod 777 /path/to/samba/share
provided you want everyone to have read+write access

man chmod for more info about assigning attributes to a directory/file

simple howto on installing samba

tar -zxvf samba.foo (foo being the version)
cd samba.foo
./configure
su -
password
make
make install
cd /etc/samba
edit the samba config file with your favorite text editor.

You only need to be su for "make install", and it's better not to use the trailing hyphen when doing "su" so you remain in the same directory.

Example:

me@host$ pwd
/usr/src/samba/samba-3.0.1
me@host$ ./configure
...scrolling list of checks...
...scrolling list of checks...
...scrolling list of checks...

me@host$ make
...compiler runs...
...compiler runs...
...compiler runs...

me@host$ su
Password:

root@host# pwd
/usr/src/samba/samba-3.0.1
root@host# make install

You might also want to run updatedb after the install finishes, so you know where everything is located. The Samba configuration file is smb.conf (usually /etc/samba/smb.conf), but usually it gets installed as smb.conf.example or smb.conf.dist (depending on which platform you're on.)

When you use the hyphen with "su" all the environmental variables are loaded and applied to root's environment, like $SHELL, $PATH, $DISPLAY, and so on, and you are transferred to root's $HOME (usually /root )

By not using the trailing hyphen, you remain in the same directory, keep the same $SHELL (if root's $SHELL is different) and get what you want - root access. It's always recommended to install sudo, so you wouldn't have to go through all this to begin with. (me@host$ sudo …

once u installed it , u can connect to your windows box using this command
smbclient -L \\COMPUTER -I 198.168.x.x <---- windows ip
by this u will be able to see the shared folders in the win box.

Or you can use smbmount (or mount -t smbfs) //path/to/shared/dierctory /local/mountpoint {any options here}

Notice that FORWARD slashes are used under *nix. Backslashes are used for an entirely different thing.

If you have entries in your /etc/hosts file, or a working local DNS server, you can use the machine name instead of IP for mounting remote directories.

Reference:
man smbmount
man mount
man smbclient

Linux doesn't use a "Recycle Bin" when deleting files, including files that are stored in a shared directory using Samba. If you delete files in a shared directory on a *nix machine, they're gone, just as if you typed rm -rf in a shell.

While the later version of 2.x and the newest version (3.01) add an option in smb.conf to include a "Recycle Bin" in the directory, I haven't yet got it to work on either Linux or FreeBSD. (Hey, it's not perfect yet, but they're working on it:)

My suggestion would be to COPY them back to your XP box, then once you're sure you have everything, wipe 'em from the *nix box. This is also good practice, in the event you have a sudden power loss and both boxes shut down (or something along those lines, like the power supply blowing chunks or the motherboard cracking in half) you'll have two copies of the files. Then you can safely remove the unwanted copies.

This is also how the majority of new worms spread - by self-mailing themselves to people in your address book, but by masking WHO they came from, again, using an address from your address book. I've received e-mail from friends and associates claiming that i've sent them infected messages, when in fact it came from someone else. Check the header of the message to see the full path (route) it took to reach you, and it might give you an indication of where it originated.

Don't forget that there are other window managers available, like BlackBox, Window Maker, and a ton of others that aren't as "heavy" as Gnome or KDE. Both KDE and Gnome are great for various reasons, but they are by no means the end-all be-all of window managers.