Re: Quick Install Question
Gerard Seibert wrote: On 10/11/2005 5:29:42 PM, Gerard Replied: Actually, there are three computers. One is running FreeBSD 5.4 and the other two have WinXP Pro installed. I networked all three together. The WinXP systems are using the NTFS format. Samba can read and write to both of the WinXP machines without any problems. I really do not know if this is germane to a dual boot system however. It probably is not since WinXP would not actually be running when FreeBSD was in this type of configuration. Fat32 is really a poor file system when compared to NTFS. It is too bad that he is unable to get a second machine and use FreeBSD on it instead of dual booting. Unfortunately, NTFS is not documented by Microsoft so non-Microsoft drivers cannot write to that file system reliably. See http://www.linux-ntfs.org/ -- they've put a lot of work into discovering how to use NTFS. So 'out-of-the-box', FreeBSD OS can mount and read from NTFS partitions, but not write. Samba allows computers to exchange files, but uses each computer's local OS to access a filesystem. There are GUI tools that use the linux-ntfs utility 'ntfsresize' to resize an NTFS partition, so you can add a FreeBSD partition even if you have a pre-built NTFS install. I keep a copy of 'SystemRescueCD' around for just that purpose, since it has those tools already. Some of the WinXP recovery' disks will wipe out your entire drive when you 'recover', so as most people will recommend, install Windows first(!) because it's install utilities are very presumptuous and you can easily waste all your previous effort on a different OS. I have read that there is a way to use the WinXP NTFS driver from within Linux (and probably FreeBSD) to provide NTFS write support, but I have not tried that yet. In any case, Welcome Daniel! Good luck with your install. If you are installing on a machine whose BIOS is a few years old, you may find the 1024-cylinder limitation: the BIOS will not boot from a partition whose start is beyond that limit. If it's a new machine, then you probably don't need to worry about it. If you do, create a small NTFS partition for WinXP, then the FreeBSD partition, then a larger NTFS partition if you need it (it will appear as drive 'd:'). I always keep a reasonably sized FAT32 partition so I can transfer files between the two OS's (that's the only 'common' read/write FS). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Running sendmail w/o FQDN
I am also having problems with sendmail configuration on my machine. I
suppose it's all related to the fact that I don't have a fully qualified
domain name (FQDN), but I have not been able to find a simple method to
allow sendmail to operate as the local message manager without having
a FQDN -- and not complain about it. I've skimmed the 180k
'/usr/share/sendmail/cf/README' and 'man sendmail' and a few .cf files.
There must be a simple way to have a development' machine that's on a
private LAN which has internet access and DNS via a router, but is not
allocated an FQDN. When I wasn't running 'inetd' everything was fine,
but I'd like those services (ftp, Samba's swat, etc.) to be available to
the other LAN machines.
I also get the 'sendmail sleeping' message when the machine is booting
because it can't find its FQDN.
Can anyone help?
Thanks,
Doug
I get this in my message log every 10 minutes:
{Date} {hostname} inetd[PID]: netbios-ns/udp: bind: Address already in use
{Date} {hostname} inetd[PID]: ssh/tcp: bind: Address already in use
{Date} {hostname} inetd[PID]: ssh/tcp: bind: Address already in use
Networking and Services part of my /etc/rc.conf:
ifconfig_rl0=DHCP # Handled by my ADSL router/modem
hostname=beastie
sendmail_enable=NO
inetd_enable=YES
nfs_client_enable=YES
nfs_server_enable=YES
ntpdate_enable=YES
ntpdate_flags=-b tk1.ihug.co.nz
router_enable=NO
rpc_lockd_enable=YES
rpc_statd_enable=YES
rpcbind_enable=YES
sshd_enable=YES
usbd_enable=YES
dictd_enable=YES
mysql_enable=YES
mysql_dbdir=/bsd5/var/db/mysql
samba_enable=YES
apache_enable=YES
gdm_enable=YES
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installation
Gayn Winters wrote: I use Linux, but for a project I am doing it involves the BSD port system so now I want to experience it for myself. As I said I have Linux and Windows with GRUB. If I try and install FreeBSD will it detect I already have grub, a swap drive? Will it also give me an option to partition it? I strongly recommend reading about installations, slices, and (BSD) partitions in the FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html. I concur with Gayn, read all about it first! FreeBSD uses the term slice for DOS-style disk partitions and partition for the subdivisions within a given slice. You don't want to confuse that while creating file new systems! NTFSresize is a great Linux utility for altering Windows partitions. I've had WinXP on one disk, and FreeBSD 5.4 on another for ~6 mo. Recently upgraded to FreeBSD 6.0 on a spare 40G disk slice (I now have 40G: FBSD 5.4, 100G: NTFS non-boot, 40G FBSD 6.0, 20G spare on a 200G disk), but I couldn't boot FBSD6! It turns out the reason was that old BIOS boot limit (found that out from GRUB). Since only the root filesystem needs to be below the limit, I pointed my FBSD 5.4 swap to use FBSD 6's swap space, then moved FBSD 6's root into FBSD 5.4's old swap space (which is below that limit). Works great. If you are putting another OS on the same disk, you may have the same challenge. Good luck. Feel free to contact me directly if you'd like more details about the process. Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
