Re: PHP Apache Assistance ~ like a moron
On Wednesday 24 July 2002 23:21, Steve Mazerski wrote: On Wednesday 24 July 2002 22:48, MET wrote: ee /usr/local/apache/conf/httpd.conf I then append the line:AddType application/x-httpd-php .php does Apache know about the PHP module? Somewhere in the httpd.conf there should be two sections (can't recall off-hand) where the modules-to-be-loaded are explictly mentioned. You may need to add PHP in both. hah, found an old httpd.conf knocking around. You will probably need something like this: IfDefine PHP4 AddModule mod_php4.c /IfDefine IfDefine PHP4 LoadModule php4_module /usr/lib/apache/libphp4.so /IfDefine S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: freebsd plugins?
On Thursday 25 July 2002 00:51, Ed Yu wrote: I tried search online but all I find is linux plugins. I made these work by installing linux-mozilla. But since there is no linux-galeon port and I'd rather run freebsd galeon, is there a way to make them work? This article: http://www.onlamp.com/pub/a/bsd/2001/12/13/Big_Scary_Daemons.html may or may not be helpful. S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: /cdrom for normal users?
On Thursday 18 July 2002 20:09, Daniel Bye wrote: On Thu, Jul 18, 2002 at 07:15:10AM -0700, Balaji, Pavan wrote: By default, cdrom is /dev/acd0c is only mountable by root in FreeBSD. You can make it mountable by normal users by changing the /etc/fstab entry to users,ro,noauto /dev/acd0c /cdrom cd9660 users,ro,noauto 0 0 Hmm, just edited my /etc/fstab to look like this, and I get a different message: cd9660: -o users: option not supported That's what I got when I borrowed the relevent line from my Linux /etc/fstab. Being a hopeless beginner I presumed this was a naive error on my part and discretely forgot to mention it. However, google brought me this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FLOPPY MOUNT Thanks, but been there, done that (see my original mail). So, what's up? At the moment things look like this? localuser@localhost uname -a FreeBSD localhost.local 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Sun Jul 14 17:14:44 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/KERNEL_1 i386 (I recompiled the kernel for ext2fs support) root# sysctl -a | fgrep vfs\.usermount vfs.usermount: 1 localuser@localhost ls -ld /cdrom drwxrwxr-x 2 root wheel 512 Jul 14 18:10 /cdrom localuser@localhost ls -l /dev/acd0c crw-rw 4 root operator 117, 0 Jul 14 18:15 /dev/acd0c localuser@localhost groups localuser wheel operator localuser@localhost cat /etc/fstab | fgrep cdrom /dev/acd0c /cdrom cd9660 ro,noauto,users 0 0 localuser@localhost mount /cdrom cd9660: -o users: option not supported localuser@localhost mount -t cd9660 /dev/acd0c ~/cdrom localuser@localhost ls ~/cdrom EULAREADME RedHat autorun GPL RPM-GPG-KEY TRANS.TBL (well, it was the first one I had to hand ;-) Any ideas? Just wondering... (I may of course be overlooking something). S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: /cdrom for normal users?
On Thursday 18 July 2002 23:20, Adam Weinberger wrote: there is no such parameter passable to mount called users. it needs to be removed. if you can mount it from the command line, you should make the fstab line agree with it, and i see no reason why it wouldn't then work. keep in mind that in your fstab, you are attempting to mount the CDROM onto /cdrom. on the command-line, you mounted it onto ~/cdrom. does localuser have permissions on /cdrom? what are those permissions right now? As posted in the prior mail: localuser@localhost ls -ld /cdrom drwxrwxr-x 2 root wheel 512 Jul 14 18:10 /cdrom localuser@localhost ls -l /dev/acd0c crw-rw 4 root operator 117, 0 Jul 14 18:15 /dev/acd0c localuser@localhost groups localuser wheel operator setting /etc/fstab with /dev/acd0c/cdrom cd9660 ro,noauto 0 0 produces: localuser@localhost mount /cdrom cd9660: /dev/acd0c: Operation not permitted Am I missing something, or is something missing me? ;-) S.Mazerski (07.18.2002 @ 1154 PST): Steve Mazerski said, in 2.1K: On Thursday 18 July 2002 20:09, Daniel Bye wrote: On Thu, Jul 18, 2002 at 07:15:10AM -0700, Balaji, Pavan wrote: By default, cdrom is /dev/acd0c is only mountable by root in FreeBSD. You can make it mountable by normal users by changing the /etc/fstab entry to users,ro,noauto /dev/acd0c /cdrom cd9660 users,ro,noauto 0 0 Hmm, just edited my /etc/fstab to look like this, and I get a different message: cd9660: -o users: option not supported That's what I got when I borrowed the relevent line from my Linux /etc/fstab. Being a hopeless beginner I presumed this was a naive error on my part and discretely forgot to mention it. However, google brought me this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FL OPPY MOUNT Thanks, but been there, done that (see my original mail). So, what's up? At the moment things look like this? localuser@localhost uname -a FreeBSD localhost.local 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Sun Jul 14 17:14:44 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/KERNEL_1 i386 (I recompiled the kernel for ext2fs support) root# sysctl -a | fgrep vfs\.usermount vfs.usermount: 1 localuser@localhost ls -ld /cdrom drwxrwxr-x 2 root wheel 512 Jul 14 18:10 /cdrom localuser@localhost ls -l /dev/acd0c crw-rw 4 root operator 117, 0 Jul 14 18:15 /dev/acd0c localuser@localhost groups localuser wheel operator localuser@localhost cat /etc/fstab | fgrep cdrom /dev/acd0c /cdrom cd9660 ro,noauto,users 0 0 localuser@localhost mount /cdrom cd9660: -o users: option not supported localuser@localhost mount -t cd9660 /dev/acd0c ~/cdrom localuser@localhost ls ~/cdrom EULAREADME RedHat autorun GPL RPM-GPG-KEY TRANS.TBL (well, it was the first one I had to hand ;-) Any ideas? Just wondering... (I may of course be overlooking something). S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message end of Re: /cdrom for normal users? from Steve Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: /cdrom for normal users?
On Friday 19 July 2002 00:15, Adam Weinberger wrote: user localhost doesn't have access to read from /dev/acd0c. -Adam user localhost is in group operator, and /dev/acd0c is readable by group operator: localuser@localhost ls -l /dev/acd0c crw-rw 4 root operator 117, 0 Jul 14 18:15 /dev/acd0c If I am missing something fundemental here, please say. Setting /dev/acd0c to a+rw didn't make any difference. vfs.usermount is set to 1, the CD-ROM works and I can mount it in a directory _owned_ by localuser. I can mount it on /cdrom if I chown it to localuser. S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
A: How big /var ? Or: too small for the xemacs package?
Me again.. Just had a call from the RTFM daemon: To answer my own questions... I moved /var to a larger partition (see http://www.freebsddiary.org/file-system-full.php for a HOW-TO) Questions: - I presume pkg_add puts temporary files in /var. Is this normal / sensible? pkg_add uses /var/tmp. (any reason why not /tmp?). The manpage says: ... The environment variables PKG_TMPDIR and TMPDIR, in that order, are taken to name temporary directories where pkg_add will attempt to create its staging area in. If these variables are not present or if the directo- ries named lack sufficient space, then pkg_add will use the first of /var/tmp, /tmp or /usr/tmp with sufficient space. ... - what would be a reasonable ball park figure for /var? On a desktop system a good couple of hundred MB? Even then it might be prudent to symlink /var/tmp to a larger partion when installing bloatware ;-) Or do this (again from the man page): ... -t template Use template as the input to mktemp(3) when creating a ``staging area''. By default, this is the string /var/tmp/instmp.XX, but it may be necessary to override it in the situation where space in your /var/tmp directory is limited. Be sure to leave some number of `X' characters for mktemp(3) to fill in with a unique ID. You can get a performance boost by setting the staging area template to reside on the same disk partition as target directo- ries for package file installation; often this is /usr. ... Enlightend S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
/cdrom for normal users?
Is it the done thing in FreeBSD for normal users to mount CD-ROMs in a local directory rather than /cdrom? As a normal user all I get is this: localuser mount /cdrom cd9660: /dev/acd0c: Operation not permitted despite changing the permissions on both the CD-ROM device and /cdrom to 660 and ensuring the local user is in the relevant groups I can mount CD-ROMs in a directory owned by the normal user. I ask because in Linux, /cdrom is generally useable as a mount point by all users. It's not a problem, just wondering. For reference: the relevant line in /etc/fstab: /dev/acd0c /cdrom cd9660 ro,noauto 0 0 vfs.usermount is set to 1, and yes, I have read this page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FLOPPYMOUNT S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Slow boot initialisation
Here's some further information: On Saturday 13 July 2002 23:01, Steve Mazerski wrote: (...) Every time the waiting symbols (i.e. the ASCII chars |/-\ ) appears, the system seems to be doing a series of seeks to each hard disks alternatively, but nothing else apart from keeping the waiting symbol turning. The sound is a sort of twang twock. By disconnecting all other drives I have determined that the sound is coming from the primary IDE drive ( WDC AC28400R ). With this drive disconnect I did a fresh install on a couple of ancient drives. FreeBSD booted from these without displaying the problem described, which leads me to believe the problem lies with Western Digital itself. Drive: Western Digital WDC AC28400R Board: Asus P5A-B , BIOS version 1005 Chipset: ALI15X3 BIOS settings for the drives are as autodetected, I am not an avid BIOS tweaker. I haven't found any references to this kind of problem through google etc. It's damned annoying, I was hoping to be worrying myself with more trivial problems like Flash Player for Mozilla by now ;-) Any ideas? S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Slow boot initialisation
I'm considering replacing Linux with FreeBSD and have just made a test installation on my desktop machine. This is an unspectacular KMD K6 with two IDE drives and no exotic hardware. The installation seems to have been successful. I installed 4.6-RELEASE on a free primary partition (ca. 1 GB) on the first (master) IDE drive. The partition is marked as bootable; the boot manager is LILO. FreeBSD boots, but with a significant delay between the initial BTX Loader messages and the actual boot process, during which there is some unusual-sounding hard disk activity. It goes something like this: BTX-Loader (some messages about drive numbering...) FreeBSD bootstrap loader, Revision 0.8 |/-\ ... Loading /boot/defaults/loader.conf |/-\ ... /kernel (...) |/-\ ... (FreeBSD boots with usual kernel messages at usual speeds) Every time the waiting symbols (i.e. the ASCII chars |/-\ ) appears, the system seems to be doing a series of seeks to each hard disks alternatively, but nothing else apart from keeping the waiting symbol turning. This continues for a painful amount of time, i.e. long enough to wonder whether the installation went wrong, or if the hard disks are slowly and irrevocably being munged (they are in fact OK), probably 20-30 seconds each time. I am not at all happy with this, and don't want to go any further until this behavior can be corrected. Anyone know what's causing it and / or what can be done? For the record: - the FreeBSD installation itself is OK, all hardware seems to be recognized - the IDE disks are attached to the motherboard's first onboard IDE controller (motherboard is an ASUS P5A-B); - a CD-ROM is connected as master to the second IDE controller; - under Linux there are no problems with this setup; - I installed 4.5-RELEASE on the same partition, exactly the same problem; - I have installed 4.5-RELEASE on two other systems (one with SCSI, one with SCSI and IDE harddisks, FreeBSD went on the SCSI disks) and have not had this problem). Any ideas? Yours S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
(minor) install partitioning bug?
Synopsis: FreeBSD interactive install tool unable to repartition a slice with a non-FreeBSD file system and system id. Description: I've just installed FreeBSD (4.6-RELEASE) on a Linux machine for the first time on that particular machine. My plan was to use a redundant primary partition on the first IDE harddisk for a test installation. The partition in question contained a fully functioning ext2fs file system. Using the interactive FDISK partition editor I changed the filesystem id from Linux (0x83) to FreeBSD (0xA5) and proceeded to the disklabel editor, where I attempted to create partitions in the rededicated slice. However any attempt was answered with the the message Unable to create the partition. Too big? even using the Auto defaults option. After trying various things (random panic option tweaking, expletive cursing etc.) I booted into Linux and used the Linux fdisk to set the partition / slice type to FreeBSD. (I left the filesystem as it was). On restarting the FreeBSD installation process, I was able to create partitions as expected and the slice was formatted correctly. Is this a bug or have I missed something? Yours S.Mazerski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
