Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
On Saturday 30 May 2009 14:50:31 Prokofyev Vladislav wrote:
Bind9 started in chroot:
root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10
/usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s
bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23
/usr/sbin/named -t /var/named -u bind
Configuration of logging channels from named.conf:
logging
{
channel xfer
{
file /var/named/var/log/xfer.log versions 3 size
10m;
The named running chrooted has no clue about /var/named. You can either use
ducttape:
cd /var/named/var sudo ln -s .. named
or just strip /var/named from your config file, hence use /var/log/xfer.log.
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
Prokofyev Vladislav wrote: Hello, I have setup FreeBSD recently, can somebody help me with one interesting thing - Bind9 slave DNS server, everything is works great, but I got a problem with extended logging of xfer, etc. Bind9 started in chroot: root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23 /usr/sbin/named -t /var/named -u bind [snip] Changing permissions and putting log-files in different places (with changing paths in named.conf of course) has no effect. I see that problem is pretty silly but searching info about this doesn't say something special - I still got file not found in /var/messages. Maybe Iam don't understand where files must be placed, so, thanks in advance for everybody who can explain how it works :) Don't know if this will help, but took a quick look at my box here at home and have the following in my rc.conf - but I don't have logging turned on with this machine. Note the last line. So the logs should be in /var/named/var/log named_enable=YES named_program=/usr/sbin/named named_chrootdir=/var/named -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
named_enable=YES named_program=/usr/sbin/named named_chrootdir=/var/named -Mike After adding these options on my system, named didn't start at boot. Manully attempt to start it via '/etc/rc.d/named start' brought to the following error: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/sbin/named Anyway, thank you for time you've spent to write an answer. Hope this thread will help somebody who is stuck with the same problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
On Saturday 30 May 2009 17:01:17 Prokofyev Vladislav wrote: The named running chrooted has no clue about /var/named. You can either use ducttape: cd /var/named/var sudo ln -s .. named or just strip /var/named from your config file, hence use /var/log/xfer.log. -- Mel This helped, thank you a lot. So, if I think in a right way, /usr/sbin/named with -t start option don't effect on any symlinks etc. Erm, yes or ... no. I suggest you read up on chroot. The short answer is that relative symlinks within the chroot environment work while absolute ones should take into the account the new filesystem root. I didn't pay attention to this cause named(8) says: -t directory Chroot to directory after processing the command line arguments, but before reading the configuration file. and have a look at what /etc/namedb really is: # ls -l /etc/namedb lrwxr-xr-x 1 root wheel 21 May 21 06:24 /etc/namedb - /var/named/etc/namedb And this demonstrates chroot a bit: # cp /rescue/ls /var/named/ # chroot /var/named /ls -l /etc/namedb total 1 drwxr-xr-x 2 53 0512 Feb 28 05:57 dynamic drwxr-xr-x 2 0 0512 May 15 13:42 master -rw-r--r-- 1 0 0 11714 May 15 14:40 named.conf -rw-r--r-- 1 0 0 2956 May 15 13:42 named.root -rw--- 1 53 0 97 Apr 18 10:29 rndc.key drwxr-xr-x 2 53 0512 May 30 11:21 slave Warning: This option should be used in conjunction with the -u option, as chrooting a process running as root doesn't enhance security on most systems; the way chroot(2) is defined allows a process with root privileges to escape a chroot jail. And I thought that all actions for proper work are made by named :) They are, you just need reference the right path, the one without /var/named, or use relative paths where the working directory is /etc/namedb. So one would get to /var/log using: file ../../var/log/xfer; -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Well it is possible - but what information it can give me? Could you explain - just to know if this 2 hours is acceptable for this. Check DELL website for more info - but generally tests the harwrare componnents.. Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Tuesday 27 January 2009 10:32:57 Mel wrote: Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. If by lots you mean 2 minutes for a reboot, I'd be inclined to agree. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Wednesday 28 January 2009 11:24:50 Kirk Strauser wrote: On Tuesday 27 January 2009 10:32:57 Mel wrote: Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. If by lots you mean 2 minutes for a reboot, I'd be inclined to agree. Right, you really want to do buildworld on a production machine that experiences random reboots. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Jan 28, 2009, at 3:45 PM, Mel wrote: On Wednesday 28 January 2009 11:24:50 Kirk Strauser wrote: On Tuesday 27 January 2009 10:32:57 Mel wrote: Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. If by lots you mean 2 minutes for a reboot, I'd be inclined to agree. Right, you really want to do buildworld on a production machine that experiences random reboots. That would make the situation worse how? The worst case is that it fails during installkernel, leaving him to boot from kernel.old. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Wednesday 28 January 2009 13:24:59 Kirk Strauser wrote: On Jan 28, 2009, at 3:45 PM, Mel wrote: On Wednesday 28 January 2009 11:24:50 Kirk Strauser wrote: On Tuesday 27 January 2009 10:32:57 Mel wrote: Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. If by lots you mean 2 minutes for a reboot, I'd be inclined to agree. Right, you really want to do buildworld on a production machine that experiences random reboots. That would make the situation worse how? The worst case is that it fails during installkernel, leaving him to boot from kernel.old. The worst case is 1 to N random reboots during buildworld (been there, done that), leaving the filesystem inconsistent, needing an fsck -y, unless you trust background_fsck, then finding out it's the hardware, not the OS. It's easy to find out if the OS panics, by enabling crash dumps. Then you can still decide whether an upgrade might fix it and you may even get a clue as to which hardware or kernel subsystem is affected, if the kernel dumps. I've had a machine where I never got buildworld to finish, tried 4 or 5 times hoping to get lucky this time... Reapplying thermal paste to the CPU heatsink made everything work. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
- Original Message From: Proskurin Kirill proskurin...@fxclub.org To: freebsd-questions freebsd-questions@freebsd.org Sent: Tuesday, January 27, 2009 12:07:25 PM Subject: FreeBSD 7.0 reboots on Dell 2950 Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? -- Best regards, Proskurin Kirill I think you should upgrade to FreeBSD 7.1-RELEASE at least, if not -STABLE. Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Abdullah Ibn Hamad Al-Marri wrote: - Original Message From: Proskurin Kirill proskurin...@fxclub.org To: freebsd-questions freebsd-questions@freebsd.org Sent: Tuesday, January 27, 2009 12:07:25 PM Subject: FreeBSD 7.0 reboots on Dell 2950 Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? I think you should upgrade to FreeBSD 7.1-RELEASE at least, if not -STABLE. Well - why I must do this? It is was a some problems with 7.0? I don`t want to do this just to do this. Well - if nothing helps may be. -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Check the fan on the CPU. Probably it's dead or malfunctioning. Also check the heat sink underneath the fan. It could be dirty and blocking the airflow. Regards, Mikhail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
- Original Message From: Proskurin Kirill proskurin...@fxclub.org To: Abdullah Ibn Hamad Al-Marri wearab...@yahoo.ca; FreeBSD Questions Mailing List freebsd-questions@freebsd.org Sent: Tuesday, January 27, 2009 12:45:46 PM Subject: Re: FreeBSD 7.0 reboots on Dell 2950 Abdullah Ibn Hamad Al-Marri wrote: - Original Message From: Proskurin Kirill To: freebsd-questions Sent: Tuesday, January 27, 2009 12:07:25 PM Subject: FreeBSD 7.0 reboots on Dell 2950 Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? I think you should upgrade to FreeBSD 7.1-RELEASE at least, if not -STABLE. Well - why I must do this? It is was a some problems with 7.0? I don`t want to do this just to do this. Well - if nothing helps may be. -- Best regards, Proskurin Kirill Because there are many bugs were in 7.0 and got fixed in 7.1, and maybe you are affected by one of them. Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Mikhail Goriachev wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) Check the fan on the CPU. Probably it's dead or malfunctioning. Also check the heat sink underneath the fan. It could be dirty and blocking the airflow. No - fan is work good. It is not a heat problem. -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Hi, Try updating to lastest version: BIOS RAID Controller BIOS RAID Controller Firmware Peter Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Peter wrote: Hi, Try updating to lastest version: BIOS RAID Controller BIOS RAID Controller Firmware Do you think it can be a problem? It is possible to test it some how? This host is really far away from me. -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Michael Toth wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Hi, Are you by any chance running 'megarc' to check your raid controller ? Hm Port: megarc-1.51 Path: /usr/ports/sysutils/megarc Info: LSI Logic's MegaRAID controlling software Maint: gerrit.be...@gmx.de B-deps: R-deps: WWW:http://www.lsilogic.com/products/megaraid/ Do you think it can work with Dell controller? -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Proskurin Kirill wrote: Michael Toth wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Hi, Are you by any chance running 'megarc' to check your raid controller ? Hm Port: megarc-1.51 Path: /usr/ports/sysutils/megarc Info: LSI Logic's MegaRAID controlling software Maint: gerrit.be...@gmx.de B-deps: R-deps: WWW:http://www.lsilogic.com/products/megaraid/ Do you think it can work with Dell controller? I know it works w/ the Dell controllers, I have also had issues with it where it randomly made my machines (all Power Edge 2950 running 7.x) core dump ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Michael Toth wrote: Proskurin Kirill wrote: Michael Toth wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Hi, Are you by any chance running 'megarc' to check your raid controller ? Hm Port: megarc-1.51 Path: /usr/ports/sysutils/megarc Info: LSI Logic's MegaRAID controlling software Maint: gerrit.be...@gmx.de B-deps: R-deps: WWW:http://www.lsilogic.com/products/megaraid/ Do you think it can work with Dell controller? I know it works w/ the Dell controllers, I have also had issues with it where it randomly made my machines (all Power Edge 2950 running 7.x) core dump mail# cd /usr/ports/sysutils/megarc mail# make install clean === megarc-1.51 is marked as broken: Running megarc seems to cause memory corruption. *** Error code 1 Stop in /usr/ports/sysutils/megarc. mail# Hm. Do I really need it? :-) -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
On Tuesday 27 January 2009 01:02:00 Abdullah Ibn Hamad Al-Marri wrote: Because there are many bugs were in 7.0 and got fixed in 7.1, and maybe you are affected by one of them. Even though 7.1 has bugfixes, this kind of guesswork causes a lot of downtime for OP without any certainty that things will be any better. At the very least, we should find out if the OS is at fault at all. For Proskurin: Find out if the machine reboots, because of a kernel panic and if so try to get a kernel crash dump [1]. If it does not panic, you're 90% sure it's a hardware issue. The remaining 10% is left for the case where FreeBSD does not configure hardware correctly through ACPI, causing hardware to operate badly. [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Proskurin Kirill wrote: Peter wrote: Hi, Try updating to lastest version: BIOS RAID Controller BIOS RAID Controller Firmware Do you think it can be a problem? It is possible to test it some how? This host is really far away from me. Last 3 months I had issues will DELL 1650 and DELL R200. In both cases BIOS update fixed it. 1) DELL 1650 - FreeBSD did not want to installl, after BIOS udpate all went well 2) DELL R200 with SATA - no problems 2) DELL R200 with SAS, installed well, extremely scary message about HDD, after BIOS update, RAID controller BIOS udpate and RAID controller firmware udpate all went well BTW when the R200 scared me , I got a DELL diagniostic CD with FreeDOS and it did full system test. If you can get KVM over IP, have someone to put in the CD and 2 hours downtime is acceptable, it is good idea to run that CD on your machine. Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Peter пишет: Proskurin Kirill wrote: Peter wrote: Hi, Try updating to lastest version: BIOS RAID Controller BIOS RAID Controller Firmware Do you think it can be a problem? It is possible to test it some how? This host is really far away from me. Last 3 months I had issues will DELL 1650 and DELL R200. In both cases BIOS update fixed it. 1) DELL 1650 - FreeBSD did not want to installl, after BIOS udpate all went well 2) DELL R200 with SATA - no problems 2) DELL R200 with SAS, installed well, extremely scary message about HDD, after BIOS update, RAID controller BIOS udpate and RAID controller firmware udpate all went well BTW when the R200 scared me , I got a DELL diagniostic CD with FreeDOS and it did full system test. If you can get KVM over IP, have someone to put in the CD and 2 hours downtime is acceptable, it is good idea to run that CD on your machine. Well it is possible - but what information it can give me? Could you explain - just to know if this 2 hours is acceptable for this. -- Best regards, Proskurin Kirill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
Proskurin Kirill wrote: Michael Toth wrote: Proskurin Kirill wrote: Michael Toth wrote: Proskurin Kirill wrote: Hello all. What we have: Dell 2950 with FreeBSD-7.0-p9 on it. It work as mail server(Exim+Dovecot and so on). All latest version from ports. After start a production use - it is start to reboot 3-4 times a day with no reason. We think what it is a hardware problem. We swap RAM - not helps. We swap chassis - not helps. I rebiuld all ports - not helps. (well i notice what it start to be more stable - 1 reboot in 1-2 days) In attach screens of error what i have to catch. Can someone say - what it can be or how to find what may cause this? Hi, Are you by any chance running 'megarc' to check your raid controller ? Hm Port: megarc-1.51 Path: /usr/ports/sysutils/megarc Info: LSI Logic's MegaRAID controlling software Maint: gerrit.be...@gmx.de B-deps: R-deps: WWW:http://www.lsilogic.com/products/megaraid/ Do you think it can work with Dell controller? I know it works w/ the Dell controllers, I have also had issues with it where it randomly made my machines (all Power Edge 2950 running 7.x) core dump mail# cd /usr/ports/sysutils/megarc mail# make install clean === megarc-1.51 is marked as broken: Running megarc seems to cause memory corruption. *** Error code 1 Stop in /usr/ports/sysutils/megarc. mail# Hm. Do I really need it? :-) No, you do not really need it, it would just allow you to get information from the raid controller (and as I said before this port caused me issues and core dump'd my machines) I was more trying to get at IF you were running this that if may have been the cause of your issues. As someone else has already mentioned you really need to find out if there is a kernel panic or not and going from there. -- -- [ Queldor ] (Warning: This message may cause you to understand something) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 reboots on Dell 2950
mail# cd /usr/ports/sysutils/megarc mail# make install clean === megarc-1.51 is marked as broken: Running megarc seems to cause memory corruption. We have a PR open on that - ports/130326: http://groups.google.com/group/lucky.freebsd.ports.bugs/browse_thread/thread/14c7c3b8261e8be7/f8cd79bbd9404609?lnk=raotpli=1 ~BAS *** Error code 1 Stop in /usr/ports/sysutils/megarc. mail# Hm. Do I really need it? :-) IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 Installation error
This is a listing of my hardware, I probably should have listed it in my earlier post. Hardware: Motherboard: A7N8X-E Deluxe socket A (462) Chipset: Northbridge: NVIDIA nforce2 spp ultra400 Southbrdige nvidia nforce2 MCP-T memory ddr 184pin (maximum of 3x184) I have kingston kvr400x64c3ak 512mb pc3200 (two pieces) ram installed.. on board audio: mcp-t southbridge + realtec alc50 6channel audio codec networking: Marvell 88e8001 gigibit, mcp-t southbridge controller mac + realtec 8201BL phy 1394: mcp-t southbridge ieee 1394a controller + realtec 8801BL phy internal connectors: usb2 connectors, games/midi, 2 ide, 20pin atx power, 2 sata, 2 1394, 5 pci, 1 asus propriety wi-fi slot and a couple others. Hard drive is a Western Digital WD2000jb ide caviar 200GB optical drive: asus drw-1604p (jumper cap is on cable select at the moment. However there are five rows of pins, three are cable select, master and secondary, no idea what the other two are) Graphics card is an asus A9600 series AGP ati From what I remember seeing fly by on the screen last night the majority of the motherboard parts were detected including the rear panel connectors which I did not list (if you want me to list those, let me know). Hope this helps. Thanks Tom --- On Tue, 13/1/09, T D ttd...@yahoo.com.au wrote: From: T D ttd...@yahoo.com.au Subject: FreeBSD 7.0 Installation error To: freebsd-questions@freebsd.org Received: Tuesday, 13 January, 2009, 11:04 PM Hi people, Hi people, I am Tom and I have been attempting to install FreeBSD 7.0 from a dvd. I put the dvd in the drive and boot, the boot screen appears with the options default, acpi disabled, safe mode, etc, I then select default. The hardware probing/detecting scrolls by and then comes to a halt with the following line: GEOM_LABLE: Lable for provider acd0 is is09660/FreeBSD 7. I have also on other boot attempts tried acpi disabled, safe mode with the same outcome. Have selected single user on another attempt and sysinstall program boots, after going through setting up the hard drive and paritions durring the install of the os the following error occurs numerous times: Write failure on transfer! (write 0 bytes of 1425408 bytes) 100% Just wondering if this has occured to any one else and how they got around it. Look forward to replys, thanks Tom Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 Installation error
Hopefully I am posting to the correct list...Or should I be posting to freebsd-stable? --- On Wed, 14/1/09, T D ttd...@yahoo.com.au wrote: From: T D ttd...@yahoo.com.au Subject: Re: FreeBSD 7.0 Installation error To: freebsd-questions@freebsd.org Received: Wednesday, 14 January, 2009, 6:58 AM This is a listing of my hardware, I probably should have listed it in my earlier post. Hardware: Motherboard: A7N8X-E Deluxe socket A (462) Chipset: Northbridge: NVIDIA nforce2 spp ultra400 Southbrdige nvidia nforce2 MCP-T memory ddr 184pin (maximum of 3x184) I have kingston kvr400x64c3ak 512mb pc3200 (two pieces) ram installed... on board audio: mcp-t southbridge + realtec alc50 6channel audio codec networking: Marvell 88e8001 gigibit, mcp-t southbridge controller mac + realtec 8201BL phy 1394: mcp-t southbridge ieee 1394a controller + realtec 8801BL phy internal connectors: usb2 connectors, games/midi, 2 ide, 20pin atx power, 2 sata, 2 1394, 5 pci, 1 asus propriety wi-fi slot and a couple others. Hard drive is a Western Digital WD2000jb ide caviar 200GB optical drive: asus drw-1604p (jumper cap is on cable select at the moment. However there are five rows of pins, three are cable select, master and secondary, no idea what the other two are) Graphics card is an asus A9600 series AGP ati From what I remember seeing fly by on the screen last night the majority of the motherboard parts were detected including the rear panel connectors which I did not list (if you want me to list those, let me know). Hope this helps. Thanks Tom --- On Tue, 13/1/09, T D ttd...@yahoo.com.au wrote: From: T D ttd...@yahoo.com.au Subject: FreeBSD 7.0 Installation error To: freebsd-questions@freebsd.org Received: Tuesday, 13 January, 2009, 11:04 PM Hi people, Hi people, I am Tom and I have been attempting to install FreeBSD 7.0 from a dvd. I put the dvd in the drive and boot, the boot screen appears with the options default, acpi disabled, safe mode, etc, I then select default. The hardware probing/detecting scrolls by and then comes to a halt with the following line: GEOM_LABLE: Lable for provider acd0 is is09660/FreeBSD 7. I have also on other boot attempts tried acpi disabled, safe mode with the same outcome. Have selected single user on another attempt and sysinstall program boots, after going through setting up the hard drive and paritions durring the install of the os the following error occurs numerous times: Write failure on transfer! (write 0 bytes of 1425408 bytes) 100% Just wondering if this has occured to any one else and how they got around it. Look forward to replys, thanks Tom Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Stay connected to the people that matter most with a smarter inbox. Take a look http://au.docs.yahoo.com/mail/smarterinbox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
On Fri, Jan 09, 2009 at 08:46:54PM -0500, Garance A Drosihn wrote: At 2:09 PM -0800 1/4/09, David Christensen wrote: I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? Why do that? Just create your own root account, put what you want for a shell on that account and use it. Use vipw. Copy the root line and then change the _second_ one to be your own root id- say, Rgad - and make a loging in directory for it. Change the directory part of the pw entry to be that and the the shell to be what you want. Then change the password to be what you want or use some pwvault utility or whatever. Just make sure you specify the second root account (Rgad) when doing so or it will change the real root's password. jerry What I do is add the following lines to /root/.login : if ($?prompt) then if ( -x /usr/local/bin/bash ) then # echo Switching to bash setenv SHELL /usr/local/bin/bash exec /usr/local/bin/bash -login endif endif I've been doing this for at least 10 years. I haven't had any problems with it, but Your Mileage Might Vary. -- Garance Alistair Drosehn= g...@gilead.netel.rpi.edu Senior Systems Programmer or g...@freebsd.org Rensselaer Polytechnic Instituteor dro...@rpi.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
David Christensen dpchr...@holgerdanske.com writes: freebsd-questions: I'm building a fresh Amanda server using FreeBSD 7.0-RELEASE-i386: http://portsmon.freebsd.org/portoverview.py?category=miscportname=amand a-server Most of my software background is GNU/Linux. I would prefer using the Bash shell, but the default FreeBSD shell for root appears to be the C shell: p3450# echo $SHELL /bin/csh I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? Assuming you build the shell statically linked, and put it in the root partition, you're unlikely to have any trouble. However: - that is what the toor user is for - in my own opinion, anyone who cares what shell root runs is probably spending too much time running as root -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
At 2:09 PM -0800 1/4/09, David Christensen wrote: I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? What I do is add the following lines to /root/.login : if ($?prompt) then if ( -x /usr/local/bin/bash ) then # echo Switching to bash setenv SHELL /usr/local/bin/bash exec /usr/local/bin/bash -login endif endif I've been doing this for at least 10 years. I haven't had any problems with it, but Your Mileage Might Vary. -- Garance Alistair Drosehn= g...@gilead.netel.rpi.edu Senior Systems Programmer or g...@freebsd.org Rensselaer Polytechnic Instituteor dro...@rpi.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-Stable Crashed with Cacti
On Tue, Jan 6, 2009 at 3:30 AM, Kalpin Erlangga Silaen kal...@muliahost.com wrote: Dear All, we face problem with running cacti on FreeBSD 7.0-Stable. From top command output: - snip - We realized that all cacti process just eat my cpu and memory (STATE: pfault) and my server should be reboot. Is there any way how to fix it? Thank you Kalpin Erlangga Silaen Cacti runs the poller script using php. It looks like the poller script is taking too long to finish, and it ends up having several instances running at the same time. I'd recommend that you look into the 'Spine' poller (formally known as Cactid). It's a threading C program, which is _MUCH_ faster than php will ever be. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-Stable Crashed with Cacti
On Tue, Jan 6, 2009 at 3:30 AM, Kalpin Erlangga Silaen kal...@muliahost.com wrote: Dear All, we face problem with running cacti on FreeBSD 7.0-Stable. From top command output: - snip - We realized that all cacti process just eat my cpu and memory (STATE: pfault) and my server should be reboot. Is there any way how to fix it? Thank you Kalpin Erlangga Silaen Cacti runs the poller script using php. It looks like the poller script is taking too long to finish, and it ends up having several instances running at the same time. I'd recommend that you look into the 'Spine' poller (formally known as Cactid). It's a threading C program, which is _MUCH_ faster than php will ever be. ___ Thank you for reply. I've change to spine poller. I'll try to update if we face same problem. thank's Kalpin Erlangga Silaen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
On Sun, Jan 04, 2009 at 02:09:03PM -0800, David Christensen wrote: freebsd-questions: I'm building a fresh Amanda server using FreeBSD 7.0-RELEASE-i386: http://portsmon.freebsd.org/portoverview.py?category=miscportname=amand a-server Most of my software background is GNU/Linux. I would prefer using the Bash shell, but the default FreeBSD shell for root appears to be the C shell: p3450# echo $SHELL /bin/csh I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? I change my root shell to pdksh. It's statically linked and I copy it from /usr/local/bin to /bin. In single user mode you're prompted for a shell (/bin/sh is the default) so I usually use that. I've never had any problems (famous last words ;) Just have to remember to copy the executable to the root filesystem if your shell gets upgraded. What you don't want to do is overwrite /bin/sh with /bin/bash or anything like that. The boot up scripts depend on /bin/sh and although bash is meant to be Bourne compatible, I wouldn't trust it myself to bring up the system without problems. TIA, David Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
Does anybody know if it's okay to change the root shell? A topic of debate, but yes it is okay to change the root shell, but there are some things to know... Some people fret about the idea that shells like bash are not on the root partition and are usually dynamically linked to libraries which reside on /usr and are therefore not available in single-user mode. (One could install a static version of bash to avoid this.) Additionally, FreeBSD prompts the user for the path to the desired shell when going into single-user mode. Shells like sh and tcsh, while dynamically linked, their libs reside on the root partition. If that isn't enough, statically linked shells exist in /rescue and therefore should always be available. Furthermore, the installation CD can be booted from and can provide an emergency repair shell. So yes, there is no technical reason you cannot change the root shell. Just be aware that a default bash install will not be available in single-user mode. But... best security practices dictate that you should not be using the root shell. If you're using the root shell often enough to find the default shell inconvenient, you should consider using something like sudo and a regular user account instead. You can use the builtin 'su' command with the '-m' flag to preserve the environment of the current user, while elevating your privileges. The shell used will be the login shell of the user issuing the 'su' command. Only members of the group 'wheel' may issue the 'su' command. -Modulok- On 1/4/09, David Christensen dpchr...@holgerdanske.com wrote: freebsd-questions: I'm building a fresh Amanda server using FreeBSD 7.0-RELEASE-i386: http://portsmon.freebsd.org/portoverview.py?category=miscportname=amand a-server Most of my software background is GNU/Linux. I would prefer using the Bash shell, but the default FreeBSD shell for root appears to be the C shell: p3450# echo $SHELL /bin/csh I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? TIA, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-i386 will changing root shell break anything?
On Sun, Jan 4, 2009 at 5:09 PM, David Christensen dpchr...@holgerdanske.com wrote: freebsd-questions: I'm building a fresh Amanda server using FreeBSD 7.0-RELEASE-i386: http://portsmon.freebsd.org/portoverview.py?category=miscportname=amand a-serverhttp://portsmon.freebsd.org/portoverview.py?category=miscportname=amanda-server Most of my software background is GNU/Linux. I would prefer using the Bash shell, but the default FreeBSD shell for root appears to be the C shell: p3450# echo $SHELL /bin/csh I have changed the root shell to Bash on another machine I use as a CVS server and haven't noticed any issues yet, but I've been wondering if I'm setting myself up for problems by doing so. Does anybody know if it's okay to change the root shell on FreeBSD 7.0-RELEASE-i386? TIA, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org well you will lock yourself out of the system if you uninstall bash or bash breaks. I would enable toor just in case ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0 problems
On Thursday 04 December 2008 03:06:34 Da Rock wrote: I have just installed FreeBSD 7.0 on a laptop I just cleaned up. It used to run Fedora linux (I have a tv card which used to work on it, but now I can't get the drivers to work again), and it got very cluttered and started getting issues. The hardware is fine though- it just returned from servicing under warranty and nearly every component was replaced. Ergo I can't fault the hardware in any way. I tried FreeBSD 7.0 before, but it wasn't working properly for me and I didn't have the time then to get all the reports to make a PR. Now, I decided to sort this out- finally! The issues I'm having are similar to before, but not quite the same (keeping in mind that I didn't take much time with it before). They are: The wifi driver complains of timeout errors. (Intel iwi 2200bg - last time I tried had a ralink wifi) Xorg has DRI errors - fills /var and tries to kill the whole system (I'm probably exaggerating, but it felt like it at least) dhclient loses the IP constantly. So: How do I present these issues for review? What information is needed? Anything I've missed? This is the first time I've had to do this (which I think is pretty good- goes to show how well the OS is built), so I'm a little green in this regard. For starters: * dmesg * pciconf -lv * if you have omni-positional antennas on the AP or not * if the dri problems go away when dri is disabled and no other symptoms show up * /var/log/Xorg.0.log without the abundance of dri errors * ls /var/db/pkg/ |grep 'xf86-video-*' * Why you installed 7.0 and not 7.1-BETA2 -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 problems
On Thursday 04 December 2008 19:51:59 Da Rock wrote: snip provided info Why would I install a beta when I'm mainly interested in stable releases? That's why I asked. You're not in a position to troubleshoot this problem, since the usual suspects (wrong driver, signs of significant acpi problems) don't apply and you'd have to really be willing to compile custom kernels, set tunables and apply patches to get to the bottom of this. The drm devices aren't created, and the reason for that is unclear. Nothing in dmesg shows a failure. The iwi problem could be signal strength, driver related or the fact that 7.0 uses SCHED_4BSD instead of the proven better working SCHED_ULE. And when reporting bugs in the PR system, the first thing developers will ask you is if you reproduce it on 7.1-BETA or a snapshot. Loads of fixes have gone into the upcoming 7.1. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
2008/12/2 Pieter Donche [EMAIL PROTECTED] On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? I never googled it before, but 2 sec gave me http://www.freebsd.org/releases/7.0R/hardware.html#PROC-AMD64 So use the amd64 ;) 368 vs 372 is that the 64 bit is compiled for 64 bit, and uses a little more space. what is 368 vs 372 ?? The size difference you talked about (368 vs 0.372) / Ebbe 2008/12/2 Pieter Donche [EMAIL PROTECTED] If motherboad is Supermicro X7SBE XEON 3000 with 2 Quad core processors Intel Harpertown E 5405 2.0Ghz 12M cache 1333FSB and 4 x 4Gb memory, what distribution of FreeBSD 7.0 applies: i386 or ia64 ? Why are the ISO's so different in size between i386 and ia64 (i386: disc1,2,3: 534, 728, 368Gb; ia64: 449Gb, 0,372 Gb, 0,372 Gb) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. 368 vs 372 is that the 64 bit is compiled for 64 bit, and uses a little more space. / Ebbe 2008/12/2 Pieter Donche [EMAIL PROTECTED] If motherboad is Supermicro X7SBE XEON 3000 with 2 Quad core processors Intel Harpertown E 5405 2.0Ghz 12M cache 1333FSB and 4 x 4Gb memory, what distribution of FreeBSD 7.0 applies: i386 or ia64 ? Why are the ISO's so different in size between i386 and ia64 (i386: disc1,2,3: 534, 728, 368Gb; ia64: 449Gb, 0,372 Gb, 0,372 Gb) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
On Tue, 2 Dec 2008, Ebbe Hjorth wrote: 2008/12/2 Pieter Donche [EMAIL PROTECTED] On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. I never googled it before, but 2 sec gave me http://www.freebsd.org/releases/7.0R/hardware.html#PROC-AMD64 So use the amd64 ;) Is the amd64 distribution mature enough, as compared to the i386? Aren't there any problems to be expected to arrive, months after initial install and way in the production usage ?? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
So use the amd64 ;) Is the amd64 distribution mature enough, as compared to the i386? yes Aren't there any problems to be expected to arrive, months after initial install and way in the production usage ?? no. the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
On Tue, 2 Dec 2008, Wojciech Puchar wrote: the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. what kind of drivers would be missing for the amd64 distribution ??? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
If motherboad is Supermicro X7SBE XEON 3000 with 2 Quad core processors Intel Harpertown E 5405 2.0Ghz 12M cache 1333FSB and 4 x 4Gb memory, what distribution of FreeBSD 7.0 applies: i386 or ia64 ? Why are the ISO's so different in size between i386 and ia64 (i386: disc1,2,3: 534, 728, 368Gb; ia64: 449Gb, 0,372 Gb, 0,372 Gb) ia64 is itanium. you need amd64. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 7.0: which distribution
the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. what kind of drivers would be missing for the amd64 distribution ??? Nvidia!!! Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.12/1824 - Release Date: 2-12-2008 9:31 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nvidia (Re: FreeBSD 7.0: which distribution)
Johan Hendriks wrote: the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. what kind of drivers would be missing for the amd64 distribution ??? Nvidia!!! I am one ot these folks, using 32-bit FreeBSD on my desktop, just because of Nvidia drivers. Wanted to ask, maybe somebody here knows, is there any hope to expect 64 bit Nvidia drivers in some reasonable future? What is the problem with Nvidia? Why they do not provide 64 bit drivers? Regards, O.K. -- Testi oma Interneti kiirust / Test Your Internet speed: http://speedtest.zzz.ee/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nvidia (Re: FreeBSD 7.0: which distribution)
=?windows-1250?Q?Ott_K=F6stner?= writes: I am one ot these folks, using 32-bit FreeBSD on my desktop, just because of Nvidia drivers. Wanted to ask, maybe somebody here knows, is there any hope to expect 64 bit Nvidia drivers in some reasonable future? What is the problem with Nvidia? Why they do not provide 64 bit drivers? For the same reason they don't provide up-to-date i386 drivers. This is a recurring thread; please search the mailing list archives. (Hint: try Zander nvidia as a search term.) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia (Re: FreeBSD 7.0: which distribution)
Nvidia drivers. Wanted to ask, maybe somebody here knows, is there any hope to expect 64 bit Nvidia drivers in some reasonable future? What is the problem with Nvidia? Why they do not provide 64 bit drivers? because there are not enough pressure from clients? (by not buying them) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? 368 vs 372 is that the 64 bit is compiled for 64 bit, and uses a little more space. what is 368 vs 372 ?? / Ebbe 2008/12/2 Pieter Donche [EMAIL PROTECTED] If motherboad is Supermicro X7SBE XEON 3000 with 2 Quad core processors Intel Harpertown E 5405 2.0Ghz 12M cache 1333FSB and 4 x 4Gb memory, what distribution of FreeBSD 7.0 applies: i386 or ia64 ? Why are the ISO's so different in size between i386 and ia64 (i386: disc1,2,3: 534, 728, 368Gb; ia64: 449Gb, 0,372 Gb, 0,372 Gb) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Nvidia (Re: FreeBSD 7.0: which distribution)
Nvidia drivers. Wanted to ask, maybe somebody here knows, is there any hope to expect 64 bit Nvidia drivers in some reasonable future? What is the problem with Nvidia? Why they do not provide 64 bit drivers? because there are not enough pressure from clients? (by not buying them) They missing some things in the kernel of FreeBSD so it has nothing to do with nvidia not willing it is FreeBSD who lacks support in the kernel for a 64bit NVIDIA driver. But like said before there are numoures threads about this. Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.12/1824 - Release Date: 2-12-2008 9:31 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
On Tue, Dec 2, 2008 at 4:59 PM, Johan Hendriks [EMAIL PROTECTED] wrote: the only reason that people use FreeBSD/i386 on 64-bit processors is that some binary-only drivers are only availaboe for i386. what kind of drivers would be missing for the amd64 distribution ??? Nvidia!!! No Nvidia on that particular motherboard so the OP is on the safe side. @OP: I have just installed FBSD amd 64 2 weeks ago to benefit of +4 GB of RAM and until now i didn't have any kind of problem in compiling and running applications. My box is a web/mail/vpn/router/samba (yes i know there shouldn't be that many services on the box, but tell my boss that) and all the apps are working like a charm. v Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.12/1824 - Release Date: 2-12-2008 9:31 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
My box is a web/mail/vpn/router/samba (yes i know there shouldn't be that many services on the box, but tell my boss that) and all the apps are working like a charm. his money his problem. overspending on hardware it's quite common, instead of paying more employees with the same money. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0: which distribution
Pieter Donche wrote: On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? No -- ia64 is the Itanium chip. Use amd64 for Xeons -- it covers all recent multi-core Intel chips as well as the AMD 64bit processors. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD 7.0: which distribution
Pieter Donche wrote: On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? No -- ia64 is the Itanium chip. Use amd64 for Xeons -- it covers all recent multi-core Intel chips as well as the AMD 64bit processors. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD 7.0: which distribution
Pieter Donche wrote: On Tue, 2 Dec 2008, Ebbe Hjorth wrote: Hi, All new XEON cpus are 64-bit spo use the 64 bit freebsd version. So this would point to ia64 distribution? But clicking op www.freebsd.com/where.html - Hardware notes/View tells for ia64: Currently supported processors are Itanium and Itanium2 There nothing about Intel XEON ?? No -- ia64 is the Itanium chip. Use amd64 for Xeons -- it covers all recent multi-core Intel chips as well as the AMD 64bit processors. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD 7.0 fdisk issue during installation
Thank you both for the very detailed description. It's nice to get my suspicion about boot sequencing confirmed :-) When I installed the system yesterday (I think I'll try a re-install today based on your input) I observed however that all the slices I made appeared to be bootable. As originally mentioned I managed to get the system to boot when I only had 4 slices which resulted in the system only wanting to boot through the FreeBSD Boot Manager. The Boot menu listed 4 menu items, each called FreeBSD. If I only used the MBR to boot however, then the machine would fail with Invalid Partition Table during startup. I'm quite confident that I had only specified a single slice (/) as being bootable through fdisk in sysinstall but apparently all 4 of them were made bootable anyway. I took a picture of my fdisk screen which can be found at http://demo.ois-inc.com/freebsd_fdisk.jpg From the picture it appears (to me anyway) that only the first slice should be bootable as indicated by the A flag? Not sure what to make of this observation as you both indicate that I wouldn't have had these problems if I only had made 1 slice bootable. Does sysinstall make all slices bootable automatically? Appreciate any input you may have to this observation. /Jona On Fri, Nov 21, 2008 at 11:58 PM, Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Nov 21, 2008 at 10:41:07PM +0100, Jonatan Evald Buus wrote: Hi Jerry, Thank you for the swift and very thorough response. If I understand you correctly, then I should only create 1 slice of the entire disk (seeing as FreeBSD will be the only OS) using fdisk and then partition the slice using bsdlabels from sysinstall? Yes. Or you don't have to use sysinstall. You can do it manually. But, using sysinstall makes it easy. You don't absolutely have to slice or bsdlabel it. You can either just newfs the device /dev/da0 or you can create a slice and just newfs that /dev/da0s1. Then you get that 'dangerously dedicated' disk which FreeBSD can use, but nothing else can including some non-FreeBSD boot managers. Some people do that to save a couple thousand bytes of space, but on a multi-gigabyte drive, who cares about a couple thousand bytes. Previously I was aiming for 5 slices, each of which had a single partition as described below. Yup. That won't work. From your explanation I take it that slices are what Windows refers to as Primary Partitions? If that's the case then I understand the behaviour I experienced. Yes. There is that conflict of terminology. But, FreeBSD has called it slices from the beginning. Is it possible to make a slice non-bootable? Yes. Just don't put in an MBR and don't mark it bootable in the fdisk stage. And would there be any benefits (less fragmentation, faster access time etc.) in using slices rather than partitions to layout the harddrive or should slices only be used to represent a physical harddrive? There is no advantage in making a slice non-bootable, except you might be able to save a few bytes of storage - storage that is not normally used anyway. There is no advantage in speed or access time and fragmentation is only a MS worry. It is not an issue in superior UNIX filesystems - at least in FreeBSD's. I don't understand the last line of that paragraph. Pretty much everything is virtual in disk drive addressing nowdays. It doesn't matter which level you refer to. The slice and its limit to 4 is a feature of standard BIOS basically. All the other things, partitions, extended partitions, etc are ways of getting around the limits.The only real reason nowdays to have more than one slice on a drive in FreeBSD is if you want to put more than one bootable system on the drive. For example, the machine I am typing on has MS-XP and FreeBSD, plus a Dell diagnostic slice - so three slices are used. I could squish those slices down and add one more, say for Linux or a different version of FreeBSD if I wanted, but I don't. Generally, when I make a machine intended only for FreeBSD, I put all the disk in one bootable slice. Then I partition that slice to suit me. My pattern is usually: a / (root) b swap (125% of memory size) c defines the slice - not a real partition d /tmp (used as scratch space by many utilities) e /usr f /var (size depends on logging and databases which live here) g /home(user home directories, plus I put some of the things that can grow unexpectedly such as /var/mail, /var/spool /usr/ports, /usr/local here and make symlinks to them) Some people make just one big partition for root plus some for swap. I like the control I have over things my way a little better and I can get by with backing up and restoring more manageable chunks my way. If the machine is to be a dual boot as this one is, I carve it up in to slices - one
Re: FreeBSD 7.0 fdisk issue during installation
On Fri, Nov 21, 2008 at 08:03:58PM +0100, Jonatan Evald Buus wrote: Greetings, I tried to install FreeBSD 7.0 on an old server earlier today and ran in to a number of issues related to slicing and labeling the disk using fdisk. The drive in the machine is a 40GB Seagate Barracude (ST34001A) installed as a Secondary Master on the IDE bus using LBA. The BIOS reports that the drive has 16 sectors pr block, but little else. When accessing fdisk during install, fdisk complains that the disk geometry is invalid and sets it to the default geometry for 40GB: Cylinders: 4865 Heads: 255 Sectors: 63 I've tried with the following configuration based on what was reported by the BIOS: Cylinders: 19150 Heads: 255 Sectors: 16 Looking in the manual: http://www.seagate.com/support/disc/manuals/ata/cuda7200pm.pdf, Seagate is specifying the following logical characteristic: Cylinders: 16383 Read / Write heads: 16 Sectors pr track: 63 Which of these settings should be the correct one for the fdisk geometry? Let the system set it and just go with what it does. Geometry is virtual nowdays. Except in some unusual situations (on IDE) Cylinders, heads and sectors most often do not mean what they used to. The system drivers have it all figured out. The important thing for you is the total number of blocks/sectors. If that doesn't work, you will have to do some diagnosis, but in about 10 out of 9 times, accepting how FreeBSD sets it is correct and works. Additionally I encountered problems during installation if splitting the disk into more than 4 slices. This would cause the following error to be thrown during prior to the install files being copied (when sysinstall was executing the newfs commands): You cannot have more than 4 slices. The system limits you to 4 slices, identified by numbers 1..4 Once you divide in to slices, each can be further divided in to up to 8 partitions, although it is really 7 because partition 'c' has special meaning and is not really available to be a real partition. Partitions are identified with alpha letters a..h - with 'c' being used to identify the whole slice. You use fdisk to create the slices (and write the MBR and set the bootable flag). Then you use bsdlabel (formerly called disklabel) to create the partitions within a slice (plus write the slice boot block. Typically, you want to make partition 'a' be the root (/) filesystem and 'b' be swap space on a bootable system slice. Some things assume these designations. Then you newfs partitions a, d, e, f, g, h or as many as you use. But don't touch c and don't newfs b if it is to be swap. jerry Error mounting /mnt/dev/X on /mnt/usr. No such file or directory Using only 4 slices seems to have solved this error, however I'd like the disk layout to use 5 slices as follows: / = 512MB swap = 2048MB (the machine has 1024MB RAM) /tmp = 512MB /var = 2048MB /usr = whatever remains I noticed that when having 5 slices, the last slice (/usr) would be named X rather than ad2s5 as I'd expect (the drive was detected as ad2). Is this behaviour related to the error in any way? Also, is the above disk layout good for a server intended to run both a web server (Apache) and a database server (PostGreSQL) ? Finally after installation (using only 4 slices) the system will only boot if the FreeBSD boot manager is used. That is probably because you have created what is referred to in the documentation as a dangerously dedicated disk. You can make it work that way. FreeBSD can handle it. But other systems will not play nicely with it. This in turn causes a 4 menu options, all of them named FreeBSD to appear during startup despite only the / slice having been set as bootable in fdisk which appears to be indicated by an A in the flag column. Again, because you tried to do it the wrong way. You created 4 FreeBSD slices, probably each with an MBR and so the BIOS and the first MBR think they are all bootable. Selecting the first menu item by pressing F1 will make the system boot as expected. It seems rather silly though to use a boot manager when FreeBSD is the only operating system that is installed (and ever will be installed) on the machine. You can put in the other non-boot manager block during installation if you want and it will only boot FreeBSD. But, something is needed. I forget what they call it in the sysinstall screen, but you might just as well put in the FreeBSD boot manager (MBR). If the FreeBSD boot manager is not used however and only the MBR is set during installation, the system will fail at startup with error Invalid Partition Table. Is this because the harddrive is installed as the Secondary Master on the IDE bus? No, it is because you did not create any partition table (with bsdlabel). jerry Appreciate any input on this Cheers Jona ___ freebsd-questions@freebsd.org mailing list
Re: FreeBSD 7.0 fdisk issue during installation
Hi Jerry, Thank you for the swift and very thorough response. If I understand you correctly, then I should only create 1 slice of the entire disk (seeing as FreeBSD will be the only OS) using fdisk and then partition the slice using bsdlabels from sysinstall? Previously I was aiming for 5 slices, each of which had a single partition as described below. From your explanation I take it that slices are what Windows refers to as Primary Partitions? If that's the case then I understand the behaviour I experienced. Is it possible to make a slice non-bootable? And would there be any benefits (less fragmentation, faster access time etc.) in using slices rather than partitions to layout the harddrive or should slices only be used to represent a physical harddrive? Appreciate the clarification Cheers Jona On Fri, Nov 21, 2008 at 8:55 PM, Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Nov 21, 2008 at 08:03:58PM +0100, Jonatan Evald Buus wrote: Greetings, I tried to install FreeBSD 7.0 on an old server earlier today and ran in to a number of issues related to slicing and labeling the disk using fdisk. The drive in the machine is a 40GB Seagate Barracude (ST34001A) installed as a Secondary Master on the IDE bus using LBA. The BIOS reports that the drive has 16 sectors pr block, but little else. When accessing fdisk during install, fdisk complains that the disk geometry is invalid and sets it to the default geometry for 40GB: Cylinders: 4865 Heads: 255 Sectors: 63 I've tried with the following configuration based on what was reported by the BIOS: Cylinders: 19150 Heads: 255 Sectors: 16 Looking in the manual: http://www.seagate.com/support/disc/manuals/ata/cuda7200pm.pdf, Seagate is specifying the following logical characteristic: Cylinders: 16383 Read / Write heads: 16 Sectors pr track: 63 Which of these settings should be the correct one for the fdisk geometry? Let the system set it and just go with what it does. Geometry is virtual nowdays. Except in some unusual situations (on IDE) Cylinders, heads and sectors most often do not mean what they used to. The system drivers have it all figured out. The important thing for you is the total number of blocks/sectors. If that doesn't work, you will have to do some diagnosis, but in about 10 out of 9 times, accepting how FreeBSD sets it is correct and works. Additionally I encountered problems during installation if splitting the disk into more than 4 slices. This would cause the following error to be thrown during prior to the install files being copied (when sysinstall was executing the newfs commands): You cannot have more than 4 slices. The system limits you to 4 slices, identified by numbers 1..4 Once you divide in to slices, each can be further divided in to up to 8 partitions, although it is really 7 because partition 'c' has special meaning and is not really available to be a real partition. Partitions are identified with alpha letters a..h - with 'c' being used to identify the whole slice. You use fdisk to create the slices (and write the MBR and set the bootable flag). Then you use bsdlabel (formerly called disklabel) to create the partitions within a slice (plus write the slice boot block. Typically, you want to make partition 'a' be the root (/) filesystem and 'b' be swap space on a bootable system slice. Some things assume these designations. Then you newfs partitions a, d, e, f, g, h or as many as you use. But don't touch c and don't newfs b if it is to be swap. jerry Error mounting /mnt/dev/X on /mnt/usr. No such file or directory Using only 4 slices seems to have solved this error, however I'd like the disk layout to use 5 slices as follows: / = 512MB swap = 2048MB (the machine has 1024MB RAM) /tmp = 512MB /var = 2048MB /usr = whatever remains I noticed that when having 5 slices, the last slice (/usr) would be named X rather than ad2s5 as I'd expect (the drive was detected as ad2). Is this behaviour related to the error in any way? Also, is the above disk layout good for a server intended to run both a web server (Apache) and a database server (PostGreSQL) ? Finally after installation (using only 4 slices) the system will only boot if the FreeBSD boot manager is used. That is probably because you have created what is referred to in the documentation as a dangerously dedicated disk. You can make it work that way. FreeBSD can handle it. But other systems will not play nicely with it. This in turn causes a 4 menu options, all of them named FreeBSD to appear during startup despite only the / slice having been set as bootable in fdisk which appears to be indicated by an A in the flag column. Again, because you tried to do it the wrong way. You created 4 FreeBSD slices, probably each with an MBR and so the BIOS and the first MBR think they are all bootable. Selecting the first menu
Re: FreeBSD 7.0 fdisk issue during installation
On Fri, 21 Nov 2008 22:41:07 +0100, Jonatan Evald Buus [EMAIL PROTECTED] wrote: If I understand you correctly, then I should only create 1 slice of the entire disk (seeing as FreeBSD will be the only OS) using fdisk and then partition the slice using bsdlabels from sysinstall? Yes, that's the usual way. Sysinstall suggest this way, too, but you can use fdisk and bsdlabel manually, if you want. Previously I was aiming for 5 slices, each of which had a single partition as described below. Not neccessary, as you see. By the way, if you would want to have one disk (harddisk) for your home directories, you wouldn't make any slice on it, you could create just one partition there, for example: /dev/ad0s1b = swap /dev/ad0s1a = / /dev/ad0s1d = /tmp /dev/ad0s1e = /var /dev/ad0s1f = /usr /dev/ad2= /home From your explanation I take it that slices are what Windows refers to as Primary Partitions? Yes. If that's the case then I understand the behaviour I experienced. You understood it correctly. Is it possible to make a slice non-bootable? Yes, by not setting the bootable flag in the slice editor. And would there be any benefits (less fragmentation, faster access time etc.) in using slices rather than partitions to layout the harddrive or should slices only be used to represent a physical harddrive? I don't think it will give you any speed gains when you have, let's say, /dev/ad[0s[12345]c instead of /dev/ad0s1[adefg]. Speed limitations usually occur according to the order harddisks are placed on the (P)ATA bus and how you copy data from one partition to another, for example, a master - slave copy usually is slower than a master - master copy; copies between partitions on the same drive tend to be slower than copies between two physical drives. In daily use, I don't think your suggestion would be of a significant benefit - if it was, it would have been done this way for years already. :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 fdisk issue during installation
On Fri, Nov 21, 2008 at 10:41:07PM +0100, Jonatan Evald Buus wrote: Hi Jerry, Thank you for the swift and very thorough response. If I understand you correctly, then I should only create 1 slice of the entire disk (seeing as FreeBSD will be the only OS) using fdisk and then partition the slice using bsdlabels from sysinstall? Yes. Or you don't have to use sysinstall. You can do it manually. But, using sysinstall makes it easy. You don't absolutely have to slice or bsdlabel it. You can either just newfs the device /dev/da0 or you can create a slice and just newfs that /dev/da0s1. Then you get that 'dangerously dedicated' disk which FreeBSD can use, but nothing else can including some non-FreeBSD boot managers. Some people do that to save a couple thousand bytes of space, but on a multi-gigabyte drive, who cares about a couple thousand bytes. Previously I was aiming for 5 slices, each of which had a single partition as described below. Yup. That won't work. From your explanation I take it that slices are what Windows refers to as Primary Partitions? If that's the case then I understand the behaviour I experienced. Yes. There is that conflict of terminology. But, FreeBSD has called it slices from the beginning. Is it possible to make a slice non-bootable? Yes. Just don't put in an MBR and don't mark it bootable in the fdisk stage. And would there be any benefits (less fragmentation, faster access time etc.) in using slices rather than partitions to layout the harddrive or should slices only be used to represent a physical harddrive? There is no advantage in making a slice non-bootable, except you might be able to save a few bytes of storage - storage that is not normally used anyway. There is no advantage in speed or access time and fragmentation is only a MS worry. It is not an issue in superior UNIX filesystems - at least in FreeBSD's. I don't understand the last line of that paragraph. Pretty much everything is virtual in disk drive addressing nowdays. It doesn't matter which level you refer to. The slice and its limit to 4 is a feature of standard BIOS basically. All the other things, partitions, extended partitions, etc are ways of getting around the limits.The only real reason nowdays to have more than one slice on a drive in FreeBSD is if you want to put more than one bootable system on the drive. For example, the machine I am typing on has MS-XP and FreeBSD, plus a Dell diagnostic slice - so three slices are used. I could squish those slices down and add one more, say for Linux or a different version of FreeBSD if I wanted, but I don't. Generally, when I make a machine intended only for FreeBSD, I put all the disk in one bootable slice. Then I partition that slice to suit me. My pattern is usually: a / (root) b swap (125% of memory size) c defines the slice - not a real partition d /tmp (used as scratch space by many utilities) e /usr f /var (size depends on logging and databases which live here) g /home(user home directories, plus I put some of the things that can grow unexpectedly such as /var/mail, /var/spool /usr/ports, /usr/local here and make symlinks to them) Some people make just one big partition for root plus some for swap. I like the control I have over things my way a little better and I can get by with backing up and restoring more manageable chunks my way. If the machine is to be a dual boot as this one is, I carve it up in to slices - one for each bootable system.If it already has some MS thing loaded, I use some tool such as Gparted or Partition Magic to shrink the MS primary partition and create two or three or four of them. Then I use fdisk to set up the FreeBSD slice to be bootable and bsdlabel to partition that slice. By the way, 'dual boot' is kind of a generic term referring to any number of bootable slices more than one. So, it could refer to two, three or four actual bootable systems on the drive. Except for something like the hidden Dell diagnostic slice (HP and probably other vendors like to do that as well), MS must be in the first slice because it doesn't like to play well with other systems. But, it does overlook the 'hidden' slices OK. That 'hidden' attribute is ignored by FreeBSD. But, since it doesn't care which slice it is in, that is no problem. When I have a second (or third, etc) disk on the machine, I generally do not make those disks bootable. I make them just one plain slice each and generally, since they mostly get used as mass data storage, I create just one partition in that slice. But, I have created more when it was useful. One I am thinking about, it was useful to make more partitions in the second drive because I was using it to build a system to distribute to other machines and I could isolate that in one separate partition that
Re: FreeBSD 7.0-RELEASE (GENERIC) firefox3 /usr/bin/ld: cannot find -lgio-2.0
On Sun, Oct 26, 2008 at 11:10:48AM -0700, David Christensen wrote: freebsd-questions: Try freebsd-ports for this question, as your issue is with a port. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE (GENERIC) firefox3 /usr/bin/ld: cannot find -lgio-2.0
--- On Sun, 10/26/08, David Christensen [EMAIL PROTECTED] wrote: From: David Christensen [EMAIL PROTECTED] Subject: FreeBSD 7.0-RELEASE (GENERIC) firefox3 /usr/bin/ld: cannot find -lgio-2.0 To: Freebsd-Questions freebsd-questions@freebsd.org Date: Sunday, October 26, 2008, 2:10 PM freebsd-questions: If I understand the above, the linker is unable to find the file gio-2.0. STFW I found something similar: The answer is to upgrade your devel/glib20 port to the latest version, then try to install or upgrade libgiofam, then install the other software. - mdh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE (GENERIC) firefox3 /usr/bin/ld: cannot find -lgio-2.0
mdh wrote: The answer is to upgrade your devel/glib20 port to the latest version, then try to install or upgrade libgiofam, then install the other software. Thank you for your response. :-) Here's my attempt to carry out your suggestions: 20081026-122203 [EMAIL PROTECTED] ~ # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. ... Building new INDEX files... done. 20081026-122344 [EMAIL PROTECTED] ~ # cd /usr/ports/devel/glib20 20081026-122615 [EMAIL PROTECTED] /usr/ports/devel/glib20 # make ... gmake[1]: Leaving directory `/usr/ports/devel/glib20/work/glib-2.16.5' 20081026-125854 [EMAIL PROTECTED] /usr/ports/devel/glib20 # cd ../gio-fam-backend 20081026-125954 [EMAIL PROTECTED] /usr/ports/devel/gio-fam-backend # make === Building for gio-fam-backend-2.16.5 /bin/sh ../../libtool --tag=CC --mode=link cc -DG_LOG_DOMAIN=\GLib-GIO\ -I.. /.. -I../../glib -I../../gmodule -I../../gio -DG_DISABLE_CAST_CHECKS -DGIO_MODUL E_DIR=\/usr/local/lib/gio/modules\ -DGIO_COMPILATION -DG_DISABLE_DEPRECATED -O 2 -fno-strict-aliasing -pipe -Wall -export_dynamic -avoid-version -module -no-un defined -export-symbols-regex '^g_io_module_(load|unload)' -L/usr/local/lib -lin tl -o libgiofam.la -rpath /usr/local/lib/gio/modules libgiofam_la-fam-helper.lo libgiofam_la-fam-module.lo libgiofam_la-gfamdirectorymonitor.lo libgiofam_la-gfa mfilemonitor.lo -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lfam rm -fr .libs/libgiofam.exp generating symbol list for `libgiofam.la' /usr/bin/nm -B .libs/libgiofam_la-fam-helper.o .libs/libgiofam_la-fam-module.o .libs/libgiofam_la-gfamdirectorymonitor.o .libs/libgiofam_la-gfamfilemonitor.o | sed -n -e 's/^.*[ ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ ]*\([_A- Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | /usr/bin/sed 's/.* //' | sort | uniq .libs /libgiofam.exp /usr/bin/grep -E -e ^g_io_module_(load|unload) .libs/libgiofam.exp .libs/ libgiofam.expT mv -f .libs/libgiofam.expT .libs/libgiofam.exp cc -shared .libs/libgiofam_la-fam-helper.o .libs/libgiofam_la-fam-module.o .lib s/libgiofam_la-gfamdirectorymonitor.o .libs/libgiofam_la-gfamfilemonitor.o -Wl, --rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/local/lib -L/usr/local/lib /usr/ local/lib/libintl.so -lgio-2.0 /usr/local/lib/libgobject-2.0.so /usr/local/lib/l ibglib-2.0.so /usr/local/lib/libfam.so -Wl,-soname -Wl,libgiofam.so -Wl,-retain -symbols-file -Wl,.libs/libgiofam.exp -o .libs/libgiofam.so /usr/bin/ld: cannot find -lgio-2.0 gmake: *** [libgiofam.la] Error 1 *** Error code 2 Stop in /usr/ports/devel/gio-fam-backend. So, I'm back where I started -- /usr/bin/ld: cannot find -lgio-2.0 Any suggestions? David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE (GENERIC) firefox3 /usr/bin/ld: cannot find -lgio-2.0
David Christensen [EMAIL PROTECTED] wrote: mdh wrote: The answer is to upgrade your devel/glib20 port to the latest version, then try to install or upgrade libgiofam, then install the other software. Thank you for your response. :-) Here's my attempt to carry out your suggestions: 20081026-122203 [EMAIL PROTECTED] ~ # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. ... Building new INDEX files... done. 20081026-122344 [EMAIL PROTECTED] ~ # cd /usr/ports/devel/glib20 20081026-122615 [EMAIL PROTECTED] /usr/ports/devel/glib20 # make ... Do these ellipses include a 'make install'? Otherwise, that is likely your problem; devel/glib20 is not actually installed. -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE (GENERIC) firefox3 /usr/bin/ld: cannot find -lgio-2.0
David Christensen wrote: mdh wrote: The answer is to upgrade your devel/glib20 port to the latest version, then try to install or upgrade libgiofam, then install the other software. Thank you for your response. :-) Here's my attempt to carry out your suggestions: 20081026-122203 [EMAIL PROTECTED] ~ # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Since I use csup and have no experience with portsnap I can't speak to it's efficacy. Building new INDEX files... done. 20081026-122344 [EMAIL PROTECTED] ~ # cd /usr/ports/devel/glib20 20081026-122615 [EMAIL PROTECTED] /usr/ports/devel/glib20 # make If you previously had glib20-2.14.6 installed, you will need to do a 'make deinstall' prior to 'make reinstall'. gmake[1]: Leaving directory `/usr/ports/devel/glib20/work/glib-2.16.5' 20081026-125854 [EMAIL PROTECTED] /usr/ports/devel/glib20 # cd ../gio-fam-backend This is wrong somehow. You should be able to make make deinstall make reinstall the glib20 port without it going anywhere else. 20081026-125954 [EMAIL PROTECTED] /usr/ports/devel/gio-fam-backend # make Also please note that both the glib20 port *and* the gio-fam-backend both utilize the same glib20 tarball. It's just you need to build/install the glib20 (current version == 2.16.5) port first, then follow up by doing the gio-fam-backend port. Something is wrong with your setup as I just successfully built the gio-fam-backend port on my test machine with no difficulties encountered. -Mike [snip] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE (GENERIC) firefox3 /usr/bin/ld: cannot find -lgio-2.0
Sahil Tandon wrote: Do these ellipses include a 'make install'? Otherwise, that is likely your problem; devel/glib20 is not actually installed. Michael Powell wrote: If you previously had glib20-2.14.6 installed, you will need to do a 'make deinstall' prior to 'make reinstall'. ... then follow up by doing the gio-fam-backend port. Thank you both for your help. :-) I didn't understand the need to do a make deinstall/ reinstall on glib20. So I tried again: http://holgerdanske.com/node/392 devel/glib20 and gio-fam-backend seemed to go okay. I think I got further into firefox3, but it failed: configure: error: Library requirements (cairo = 1.6.0 freetype2 fontconfig) not met What's next? TIA, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE (GENERIC) firefox3 /usr/bin/ld: cannot find -lgio-2.0
On Sun, Oct 26, 2008 at 11:01 PM, David Christensen [EMAIL PROTECTED] wrote: Sahil Tandon wrote: Do these ellipses include a 'make install'? Otherwise, that is likely your problem; devel/glib20 is not actually installed. Michael Powell wrote: If you previously had glib20-2.14.6 installed, you will need to do a 'make deinstall' prior to 'make reinstall'. ... then follow up by doing the gio-fam-backend port. Thank you both for your help. :-) I didn't understand the need to do a make deinstall/ reinstall on glib20. So I tried again: http://holgerdanske.com/node/392 devel/glib20 and gio-fam-backend seemed to go okay. I think I got further into firefox3, but it failed: configure: error: Library requirements (cairo = 1.6.0 freetype2 fontconfig) not met What's next? TIA, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] install these three cairo = 1.6.0 freetype2 fontconfig make sure your ports tree is up to date as well with portsnap ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE (GENERIC) firefox3 /usr/bin/ld: cannot find -lgio-2.0
David Christensen wrote: [snip] devel/glib20 and gio-fam-backend seemed to go okay. I think I got further into firefox3, but it failed: checking for cairo = 1.6.0 freetype2 fontconfig... Requested 'cairo = 1.6.0' but version of cairo is 1.4.10 This is telling you the cairo you have installed is old and needs to be updated, probably freetype2 and fontconfig as well. Essentially you have out of date dependencies, with the most common reason for this is having installed packages straight from the release ISOs and subsequently not upgrading them. Many old time FreeBSD'ers only install the system from the ISO, update their ports tree, and then install software. This ensures everything is current and all dependencies are tracked. What you have is a jumble of outdated dependencies which require updating. configure: error: Library requirements (cairo = 1.6.0 freetype2 fontconfig) not met What's next? [snip] You can update things manually one or two at a time[1], as you did for the glib20 port. Or you can automate the process. I use portupgrade for this. Now portupgrade has it's own learning curve, but it can make it easier to keep large numbers of ports all up to date. You probably need to learn a little more about how the ports system works. Once you have a more in depth understanding of how to install and maintain software on a FreeBSD system you won't see this kind of situation again. So rather than fixate on just bouncing from dependency to dependency, ad infinitum ad nauseum, try going back and reading up on this subject some more until you understand the process. -Mike [1] Like you did with glib20: make make deinstall make reinstall ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 installation problems.Please help!
Write failure on transfer! (wrote -1 bytes of 1425408 bytes) Unable to transfer the GENERIC distribution from acd0 I'm a bit of a n00b too. There's a whole host of things that have given me that issue - bad cd drive, scratched disk, etc. More importantly, I've seen sysinstall never actually format the disk, so then it can't write to it. The way I fixed it is by hitting w (write) before q (quit) in both the fdisk and partition pages of sysinstall. I've seen this behavior on both 6.2 and 7.0, and I've never paid enough attention to repeat it or figure out what I did wrong - I just use the write command manually and things seem happier. Make sure you see a box pop up on the partition/label page when you hit write that mentions something about doing newfs , otherwise just start over. I think that's the magic step. Hope this helps, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 installation problems.Please help!
On Fri, Sep 26, 2008 at 01:58:41PM -0700, Steve Franks wrote: Write failure on transfer! (wrote -1 bytes of 1425408 bytes) Unable to transfer the GENERIC distribution from acd0 I'm a bit of a n00b too. There's a whole host of things that have given me that issue - bad cd drive, scratched disk, etc. More importantly, I've seen sysinstall never actually format the disk, so then it can't write to it. The way I fixed it is by hitting w (write) before q (quit) in both the fdisk and partition pages of sysinstall. I've seen this behavior on both 6.2 and 7.0, and I've never paid enough attention to repeat it or figure out what I did wrong - I just use the write command manually and things seem happier. Make sure you see a box pop up on the partition/label page when you hit write that mentions something about doing newfs , otherwise just start over. I think that's the magic step. I don't remember the necessary letter just at this moment, but you must hit the letter to tell it to actually write the stuff or it won't do it. That is normal behavior. jerry Hope this helps, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freeBSD 7.0 supports ACE Proactor?
Mungyung Ryu wrote: freebsd-questions@freebsd.orgHi freeBSD users, I've developed couple of server applications on Windows platform with ACE Proactor and it worked quite well. But, because of the expensive Windows Server, I wanna move to Linux or freeBSD. Recently, I'm considering to build a server application on freeBSD but the important issue is whether the freeBSD supports ACE Proactor framework. I googled about it and Linux doesn't support it well because Linux doesn't support AIO (asynchronous I/O) on socket. Moreover, most of the ACE professionals recommend to use Reactor framework on Linux. My questions is.. 1. freeBSD supports AIO on socket? Yes. 2. I can use ACE Proactor on freeBSD 7.0 without any problem? Is it stable? Probably nobody tried to use it before. I haven't heard about it before but it looks like it's a IO library. If you can port your code to libevent (http://monkey.org/~provos/libevent/) it would be much better supported on both FreeBSD and Linux. signature.asc Description: OpenPGP digital signature
Re: FreeBSD 7.0 install on Acer Aspire AM1640-U1401A
Quoting Christer Hermansson [EMAIL PROTECTED]: Joseph Olatt wrote: Hello, I have tried installing the following versions of FreeBSD: - 7.0 Release - 6.2 Release - 6.1 Release on an ACER Aspire AM1640-U1401A computer and the install program is not detecting the SATA hard drive. Does anybody else on the list have the above computer and have they succeeded in installing FreeBSD on it? I have an Acer Aspire AMD and had issues initially installing FBSD. What are you seeing when booting the installion cd? Do you get any errors? ed Any hints or feedback will be greatly appreciated. regards, joseph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Maybe this is a very late reply but I haven't read this list for a while and this post/problem seems unsolved so I make a reply. Maybe you need to adjust the settings in the bios. I have the experience that to install and run Windows XP I need to *disable* native sata in the bios on some notebooks, e.g. HP 6710B, but to install and run Linux I must *enable* native sata in the bios. -- Christer Hermansson http://www.chdevelopment.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd 7.0 and jail
Make sure your buildworld /usr/obj is updated. Good idea is to erase your /usr/obj and buildworld again before going on with the jails. fc On Mon, Sep 8, 2008 at 7:28 PM, gahn [EMAIL PROTECTED] wrote: Hello: I am trying to build jails on 7.0 system and got errors: / Installing everything -- cd /usr/src; make -f Makefile.inc1 install === share/info (install) === lib (install) === lib/csu/i386-elf (install) gcc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/csu/i386-elf/../common -I/usr/src/lib/csu/i386-elf/../../libc/include -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c crt1.c gcc:No such file or directory *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 /// looks like the code of jail is broken, did anyone have similar problem? I am working in an environment that is able to use freebsd-update script. Thanks in Advance ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd 7.0 and jail
thanks for the advice. it worked out after i did make world ... first, then make installworld ... it doesn't work if one just do make installworld ... best --- On Wed, 9/10/08, Primeroz lists [EMAIL PROTECTED] wrote: From: Primeroz lists [EMAIL PROTECTED] Subject: Re: freebsd 7.0 and jail To: [EMAIL PROTECTED] Cc: free bsd [EMAIL PROTECTED], freebsd general questions freebsd-questions@freebsd.org Date: Wednesday, September 10, 2008, 1:51 AM Make sure your buildworld /usr/obj is updated. Good idea is to erase your /usr/obj and buildworld again before going on with the jails. fc On Mon, Sep 8, 2008 at 7:28 PM, gahn [EMAIL PROTECTED] wrote: Hello: I am trying to build jails on 7.0 system and got errors: / Installing everything -- cd /usr/src; make -f Makefile.inc1 install === share/info (install) === lib (install) === lib/csu/i386-elf (install) gcc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/csu/i386-elf/../common -I/usr/src/lib/csu/i386-elf/../../libc/include -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c crt1.c gcc:No such file or directory *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 /// looks like the code of jail is broken, did anyone have similar problem? I am working in an environment that is able to use freebsd-update script. Thanks in Advance ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd 7.0 and jail
On Mon, Sep 08, 2008 at 11:28:09AM -0700, gahn wrote: Hello: I am trying to build jails on 7.0 system and got errors: / Installing everything -- cd /usr/src; make -f Makefile.inc1 install === share/info (install) === lib (install) === lib/csu/i386-elf (install) gcc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/csu/i386-elf/../common -I/usr/src/lib/csu/i386-elf/../../libc/include -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c crt1.c gcc:No such file or directory *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 /// looks like the code of jail is broken, did anyone have similar problem? I am working in an environment that is able to use freebsd-update script. Check your date: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2003-05/0059.html Btw. you don't have to build jails by yourself. You can use sysutils/ezjail to install, update and manage your jails. ezjail can use source or the prebuilt ftp packages to setup the jail. http://erdgeist.org/arts/software/ezjail/ Great piece of software. -- Oliver PETER, email: [EMAIL PROTECTED], ICQ# 113969174 If it feels good, you're doing something wrong. -- Coach McTavish ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE getting terrible throughput using sk0 adapter
still seeing really slow download speeds. I then decided to see if something was wrong with the system by downloading the same image from the same source that I downloaded on linux in order to bootstrap freebsd and the speed difference was appaling. It had downloaded at 10.29 MB/s. Once freebsd was installed, It will only go at 60KB/s.. looks like problems with speed/duplex autoconfiguration with the switch, or bad support for PHY in FreeBSD. what you describe is quite common case when one side gets configured for full duplex, other for half duplex. as it works for linux, maybe PHY support in FreeBSD is buggy. try setting up speed and duplex options manually ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 7.0-RELEASE getting terrible throughput using sk0 adapter
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Wojciech Puchar Sent: Sunday, August 31, 2008 11:21 AM To: David Polak Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 7.0-RELEASE getting terrible throughput using sk0 adapter still seeing really slow download speeds. I then decided to see if something was wrong with the system by downloading the same image from the same source that I downloaded on linux in order to bootstrap freebsd and the speed difference was appaling. It had downloaded at 10.29 MB/s. Once freebsd was installed, It will only go at 60KB/s.. looks like problems with speed/duplex autoconfiguration with the switch, or bad support for PHY in FreeBSD. what you describe is quite common case when one side gets configured for full duplex, other for half duplex. as it works for linux, maybe PHY support in FreeBSD is buggy. try setting up speed and duplex options manually I have set the duplex to full-duplex and it has increased the speed to about 200kb/s on the same file. As far as phy support, I guess I really don't know, but the drivers for the chipset have been around for a while. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 7.0-RELEASE getting terrible throughput using sk0 adapter
David Polak wrote: [snip] try setting up speed and duplex options manually I have set the duplex to full-duplex and it has increased the speed to about 200kb/s on the same file. As far as phy support, I guess I really don't know, but the drivers for the chipset have been around for a while. Try disabling usb and firewire in BIOS. You may need to have a tech there do it for you. Your box has the sk NIC and usb sharing an irq. The NIC driver is MPSAFE but the usb stack is still under the GIANT lock. Disable usb and the NIC driver should perform better. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE getting terrible throughput using sk0 adapter
Try disabling usb and firewire in BIOS. You may need to have a tech there do it for you. Your box has the sk NIC and usb sharing an irq. The NIC driver is MPSAFE but the usb stack is still under the GIANT lock. Disable usb and the NIC driver should perform better. Alternatively, to avoid involving the provider's tech support, could the OP get the same effect by building a kernel without USB? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 7.0-RELEASE getting terrible throughput using sk0 adapter
Try disabling usb and firewire in BIOS. You may need to have a tech there do it for you. Your box has the sk NIC and usb sharing an irq. The NIC driver is MPSAFE but the usb stack is still under the GIANT lock. Disable usb and the NIC driver should perform better. Alternatively, to avoid involving the provider's tech support, could the OP get the same effect by building a kernel without USB? From server support live chat: Steven H. - Server Support: Submit a trouble ticket and we will look into it further. I'm pretty sure they will not disable usb since the DC technicians need to boot from USB in some cases. So is there any other way to verify that this is indeed the problem? Perhaps as Perry suggested, building a kernel without usb/firewire, or possibly setting the irq manually so it's not shared? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 on Xen
2008/8/8 Elwell, Richard [EMAIL PROTECTED]: Sorry about the premature sending. Here is the complete question: Greetings, I am attempting to follow the directions located at http://www.freebsd.org/doc/en/books/handbook/virtualization-guest.html and load a FreeBSD Xen DomU instance. The document says: Download the FreeBSD domU kernel for Xen 3.0 and disk image from http://www.fsmware.com/ * kernel-current http://www.fsmware.com/xenofreebsd/7.0/download/kernel-current * mdroot-7.0.bz2 http://www.fsmware.com/xenofreebsd/7.0/download/mdroot-7.0.bz2 * xmexample1.bsd http://www.fsmware.com/xenofreebsd/7.0/download/config/xmexample1.bsd ... I want to add my following questions because in the handbook are they unfortunately _not_ explained: 1) What is this kernel-current ? And how can I make myself this kernel-current using the base system and the tools in it ? 2) What is mdroot ? And how can I build a mdroot? 3) Where are the Xen sources located? Does The FreeBSD project just write patches which are then used to modify the original sources to get Xen run on FreeBSD OR is there a fork like source repository where the FreeBSD Xen is maintained? I hope that someone can answer me these questions but also I think including the answers to the Handbook would be a great help for all who want to use Xen on FreeBSD. regards Gueven ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 7.0 on Xen
Sorry about the premature sending. Here is the complete question: Greetings, I am attempting to follow the directions located at http://www.freebsd.org/doc/en/books/handbook/virtualization-guest.html and load a FreeBSD Xen DomU instance. The document says: Download the FreeBSD domU kernel for Xen 3.0 and disk image from http://www.fsmware.com/ * kernel-current http://www.fsmware.com/xenofreebsd/7.0/download/kernel-current * mdroot-7.0.bz2 http://www.fsmware.com/xenofreebsd/7.0/download/mdroot-7.0.bz2 * xmexample1.bsd http://www.fsmware.com/xenofreebsd/7.0/download/config/xmexample1.bsd The link for kernel-current does not work. Do you know where I can find the kernel? I tried to compile a kernel with PAE support, modify it using the objcopy instructions given in the handbook, and use it, but I get the error xc-dom-compat-check: guest type xen-3.0-x86_32 not supported by xen kernel. It looks like I need a guest type xen-3.0-x86_32p. I thought compiling a kernel with PAE enabled would give me that, but I get the same error. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 on Xen
I have a working config for non-HVM systems, its stable enough to play with but not for production, if you have however a HVM machine, FreeBSD runs great under linux KVM On Friday 08 August 2008 22:46:11 Elwell, Richard wrote: Sorry about the premature sending. Here is the complete question: Greetings, I am attempting to follow the directions located at http://www.freebsd.org/doc/en/books/handbook/virtualization-guest.html and load a FreeBSD Xen DomU instance. The document says: Download the FreeBSD domU kernel for Xen 3.0 and disk image from http://www.fsmware.com/ * kernel-current http://www.fsmware.com/xenofreebsd/7.0/download/kernel-current * mdroot-7.0.bz2 http://www.fsmware.com/xenofreebsd/7.0/download/mdroot-7.0.bz2 * xmexample1.bsd http://www.fsmware.com/xenofreebsd/7.0/download/config/xmexample1.bsd The link for kernel-current does not work. Do you know where I can find the kernel? I tried to compile a kernel with PAE support, modify it using the objcopy instructions given in the handbook, and use it, but I get the error xc-dom-compat-check: guest type xen-3.0-x86_32 not supported by xen kernel. It looks like I need a guest type xen-3.0-x86_32p. I thought compiling a kernel with PAE enabled would give me that, but I get the same error. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 on Xen
On Fri, Aug 8, 2008 at 12:04 PM, OutBackDingo [EMAIL PROTECTED] wrote: I have a working config for non-HVM systems, its stable enough to play with but not for production, if you have however a HVM machine, FreeBSD runs great under linux KVM What host OS are you using for dom0? I'm considering setting this up on my second box, so I can run 7.0-STABLE and 8.0-CURRENT simultaneously (and use the full capabilities/speed of the processor), but I've heard of limited success, depending on the host/dom0 OS. Thanks, Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 on Xen
CentOS 5.2 On Fri, Aug 8, 2008 at 12:04 PM, OutBackDingo [EMAIL PROTECTED] http://www.nabble.com/user/SendEmail.jtp?type=postpost=18896047i=0 wrote: I have a working config for non-HVM systems, its stable enough to play with but not for production, if you have however a HVM machine, FreeBSD runs great under linux KVM What host OS are you using for dom0? I'm considering setting this up on my second box, so I can run 7.0-STABLE and 8.0-CURRENT simultaneously (and use the full capabilities/speed of the processor), but I've heard of limited success, depending on the host/dom0 OS. Thanks, Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 7.0 Hardware Requirement.
Date: Thu, 31 Jul 2008 07:43:07 -0700 From: [EMAIL PROTECTED] To: freebsd-questions@FreeBSD.org CC: Subject: FreeBSD 7.0 Hardware Requirement. Hello I've tried to find hardware requirement for FreeBSC 7.0 but I couldn't found that. Can you please send me the hardware requirement? I have laptop(celeron 1.4, 256 ram) so Can you suggest me which verson is suitable for my hardware. Thanks and Regards, Ketan. ___ http://www.freebsd.org/releases/7.0R/hardware.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 Hardware Requirement.
ketan tada wrote: Hello I've tried to find hardware requirement for FreeBSC 7.0 but I couldn't found that. Can you please send me the hardware requirement? I have laptop(celeron 1.4, 256 ram) so Can you suggest me which verson is suitable for my hardware. Thanks and Regards, Ketan. You need the i386 version. The hardware notes are here: http://www.freebsd.org/releases/7.0R/hardware.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 Hardware Requirement.
Im using 7.0 on my Dell Latitude C400 and works very fine (Pentium3 1.2, 256 ram). Sure, because I'm sometimes paranoic about performane even with slow machines, I'm using xfce. On Thu, Jul 31, 2008 at 11:43, ketan tada [EMAIL PROTECTED] wrote: Hello I've tried to find hardware requirement for FreeBSC 7.0 but I couldn't found that. Can you please send me the hardware requirement? I have laptop(celeron 1.4, 256 ram) so Can you suggest me which verson is suitable for my hardware. Thanks and Regards, Ketan. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Daniel de Oliveira Network and System Analyst Security Specialist IBM RISC Specialist IBM Storage Specialist Linux/Unix Specialist Linux User #: 405334 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 amd64 FAMP Server RAM problem
On 2008.07.24 17:49:56, Benjamin Adams wrote: Hello everyone. I'm running a website (http://www.FreeBSD-World.com/) When the RAM is used up and moves to inactive the pages stop loading 100%. Pages will stop halfway and sometimes I will get a display of what is in the httpd.access log. Just to clarify: the user accessing the page will get the contents of http.access displayed to them? ~Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and RAM limit
On Sat, Jul 5, 2008 at 8:01 AM, Robert Heron [EMAIL PROTECTED] wrote: Hi, I use: FreeBSD 7.0-R on i386 server with motherboard S5000VSA and 6GB RAM onboard. BIOS version - 88 (the latest) Kernel includes: optionsMAXMEM=(6*1024*1024) And FreeBSD reports only: real memory = 2680160256 (2556 MB) avail memory = 2617892864 (2496 MB) Why? What is wrong that FreeBSD sees only about 2.5GB instead of 6GB? Robert - Look at system memory map: http://www.codinghorror.com/blog/images/intel-system-memory-map.png As a 32-bit system, your limit is 4 GB, subtracting PCI devices, sound and so on like the linked PNG. Rodolfo Bojo Pellegrino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and RAM limit
Robert Heron wrote: Hi, I use: FreeBSD 7.0-R on i386 server with motherboard S5000VSA and 6GB RAM onboard. BIOS version - 88 (the latest) Kernel includes: optionsMAXMEM=(6*1024*1024) You generally shouldn't touch MAXMEM as it's autotuned. And FreeBSD reports only: real memory = 2680160256 (2556 MB) avail memory = 2617892864 (2496 MB) Why? What is wrong that FreeBSD sees only about 2.5GB instead of 6GB? Having only 2.5 GB is a bit severe (do you have lots of PCI hardware? video cards with lots of memory?), but PAE could be your solution. See here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/compatibility-memory.html signature.asc Description: OpenPGP digital signature
Re: FreeBSD 7.0 and RAM limit
At 2008-07-05T13:04:19+02:00, Robert Heron wrote: FreeBSD 7.0-R on i386 server with motherboard S5000VSA and 6GB RAM onboard. BIOS version - 88 (the latest) Kernel includes: options MAXMEM=(6*1024*1024) And FreeBSD reports only: real memory = 2680160256 (2556 MB) avail memory = 2617892864 (2496 MB) Why? What is wrong that FreeBSD sees only about 2.5GB instead of 6GB? (I ran into this question recently when buying a computer, and did some homework on it, however my understanding may be off the mark.) As mentioned in earlier replies, the problem isn't caused by the OS, but is a limitation of the i386 architecture, in which each byte of memory is indexed by a 32-bit integer. This means that an i386 machine can use only 2^32 bytes, i.e., 4 GB, of memory --- unless one uses pae(4). Some of the 2^32 addresses are used by devices like the video card, and by the BIOS. For instance, if the machine has a video card with 512 MB of video RAM, this means that less than 3.5 GB of memory can be used. It seems a safe bet in such a case to install at most 3 GB of memory. There is more info at http://www.codinghorror.com/blog/archives/000811.html http://en.wikipedia.org/wiki/Memory_address Raghavendra. -- N. Raghavendra [EMAIL PROTECTED] | http://www.retrotexts.net/ Harish-Chandra Research Institute | http://www.mri.ernet.in/ See message headers for contact and OpenPGP information. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and RAM limit
Hello, You might try the 64bit FreeBSD, I think your system is 64bit capable. That has much higher limits on memory addressing and should get around the issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and RAM limit
Robert Heron wrote: Hi, I use: FreeBSD 7.0-R on i386 server with motherboard S5000VSA and 6GB RAM onboard. BIOS version - 88 (the latest) Kernel includes: optionsMAXMEM=(6*1024*1024) And FreeBSD reports only: real memory = 2680160256 (2556 MB) avail memory = 2617892864 (2496 MB) Why? What is wrong that FreeBSD sees only about 2.5GB instead of 6GB? The i386 architecture cannot address more than 4GB (== 2^32) of RAM unless you use PAE (i.e. the PAE kernel). You don't need to set MAXMEM either, since it's autodetected. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and RAM limit
use amd64 On Sat, 5 Jul 2008, Robert Heron wrote: Hi, I use: FreeBSD 7.0-R on i386 server with motherboard S5000VSA and 6GB RAM onboard. BIOS version - 88 (the latest) Kernel includes: optionsMAXMEM=(6*1024*1024) And FreeBSD reports only: real memory = 2680160256 (2556 MB) avail memory = 2617892864 (2496 MB) Why? What is wrong that FreeBSD sees only about 2.5GB instead of 6GB? Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.0 Release and Camera?
I'm not sure about getting FreeBSD to recognize the camera; but if it has a removable memory card, you should be able to access it through a memory card reader. Best regards, Andrew On Fri, Jun 27, 2008 at 3:40 PM, chip [EMAIL PROTECTED] wrote: Anyone know how to get FBSD 7-R to recognize my Canon S3 IS and download pics from it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.0 Release and Camera?
* chip [EMAIL PROTECTED] [2008-06-27 13:40:59+]: Anyone know how to get FBSD 7-R to recognize my Canon S3 IS and download pics from it? Nowadays mostly everyone gets a cheap (less than $10US) USB card reader and reads it that way. Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.0 Release and Camera?
A little more info - I now have gphoto2 recognizing and downloading my images, but only in a terminal window. I am using XFCE and want to create a shortcut on the toolbar or the desktop that will open a terminal window and run the command. I have a shortcut set up but it just opens a terminal window and quickly closes, I don't know what's wrong, but it's not downloading the images. Any suggestions on how to get a shortcut to a terminal window app to work on XFCE? Thanks. chip wrote: Anyone know how to get FBSD 7-R to recognize my Canon S3 IS and download pics from it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.0 Release and Camera? Almost got it figured out
Heheh, got that working, had to add sudo to the beginning of the command. Now the problem has to do with permissions. The pics are downloaded with the owner being root, so I have to view the pics as root. Whats the workaround? Thanks. chip wrote: A little more info - I now have gphoto2 recognizing and downloading my images, but only in a terminal window. I am using XFCE and want to create a shortcut on the toolbar or the desktop that will open a terminal window and run the command. I have a shortcut set up but it just opens a terminal window and quickly closes, I don't know what's wrong, but it's not downloading the images. Any suggestions on how to get a shortcut to a terminal window app to work on XFCE? Thanks. chip wrote: Anyone know how to get FBSD 7-R to recognize my Canon S3 IS and download pics from it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.0 Release and Camera? Almost got it figured out
chip wrote: Heheh, got that working, had to add sudo to the beginning of the command. Now the problem has to do with permissions. The pics are downloaded with the owner being root, so I have to view the pics as root. Whats the workaround? Thanks. chip wrote: A little more info - I now have gphoto2 recognizing and downloading my images, but only in a terminal window. I am using XFCE and want to create a shortcut on the toolbar or the desktop that will open a terminal window and run the command. I have a shortcut set up but it just opens a terminal window and quickly closes, I don't know what's wrong, but it's not downloading the images. Any suggestions on how to get a shortcut to a terminal window app to work on XFCE? Thanks. chip wrote: Anyone know how to get FBSD 7-R to recognize my Canon S3 IS and download pics from it? First off, please bottom respond. Easier to follow the thread. Secondly, chown would do the job. sudo chown youruser:yourgroup * (or file*) -- Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.0 Release and Camera? Almost got it figured out
Ryan Coleman wrote: chip wrote: Heheh, got that working, had to add sudo to the beginning of the command. Now the problem has to do with permissions. The pics are downloaded with the owner being root, so I have to view the pics as root. Whats the workaround? Thanks. chip wrote: A little more info - I now have gphoto2 recognizing and downloading my images, but only in a terminal window. I am using XFCE and want to create a shortcut on the toolbar or the desktop that will open a terminal window and run the command. I have a shortcut set up but it just opens a terminal window and quickly closes, I don't know what's wrong, but it's not downloading the images. Any suggestions on how to get a shortcut to a terminal window app to work on XFCE? Thanks. chip wrote: Anyone know how to get FBSD 7-R to recognize my Canon S3 IS and download pics from it? First off, please bottom respond. Easier to follow the thread. Secondly, chown would do the job. sudo chown youruser:yourgroup * (or file*) -- Ryan So that is after loading the pics. Is there anything I can do beforehand so the whole process can be done under my normal user login? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.0 Release and Camera? Almost got it figured out
chip wrote: Ryan Coleman wrote: chip wrote: Heheh, got that working, had to add sudo to the beginning of the command. Now the problem has to do with permissions. The pics are downloaded with the owner being root, so I have to view the pics as root. Whats the workaround? Thanks. chip wrote: A little more info - I now have gphoto2 recognizing and downloading my images, but only in a terminal window. I am using XFCE and want to create a shortcut on the toolbar or the desktop that will open a terminal window and run the command. I have a shortcut set up but it just opens a terminal window and quickly closes, I don't know what's wrong, but it's not downloading the images. Any suggestions on how to get a shortcut to a terminal window app to work on XFCE? Thanks. chip wrote: Anyone know how to get FBSD 7-R to recognize my Canon S3 IS and download pics from it? First off, please bottom respond. Easier to follow the thread. Secondly, chown would do the job. sudo chown youruser:yourgroup * (or file*) -- Ryan So that is after loading the pics. Is there anything I can do beforehand so the whole process can be done under my normal user login? RTFM: http://gphoto.sourceforge.net/doc/manual/permissions-serial.html#ex-serial-anybody-access Really, man... RTFM :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
