Re: fsck inadequacies
Do you have soft updates enabled? If not, you may want to reenable them next time you go up there. Mardoc Inc wrote: I run a FreeBSD system at a remote site. It costs me over $4000 to visit the site (northern arctic). It, along with some other equipment, runs off 2 x 50 kW diesel generators which are swapped by a mechanic once per week. The swap-over takes less than a minute. The computer runs off a UPS, which easily holds its charge during the swap. But, unlike the other windows systems that run up there, the FreeBSD system seems incredibly prone to disk corruption. Often the system will not reboot, and hangs while it asks for a file check. I can't do that remotely - it has to be a person. I frequently need to run fsck, and that does not always work. It is hard to instruct a diesel mechanic on such matters from such a distance. "fsck -y" usually does not work either. Is there any way I can make the disk a bit less sensitive? e.g. some clever additional command when I mount it in the fstab file which says "don't be too fussy - boot up even if I don't feel that well'. It seems someone only needs to sneeeze and it goes into panic mode. I would happily live with the odd corrupt disk track or so if it means I can keep it running and at least be able to access it remotely. Please don't advise me to be more careful and get a better power supply etc - it simply is not possible. This is a very remote site, the humidity is low, static electricity is always a problem. thanks Wayne Hocking ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Really Dumb Question
Thanks for the suggestions. I figured it out, su was no longer suid root. I forgot, I had to copy /usr back and forth a few times when setting it up on vinum. Everything is cool, I have my user in their own group as primary and also in wheel. Dan Tim Tonway wrote: This is probably a dumb question. I need to add a user that can su to root. So I add the user with adduser, invite the user into the wheel group (GID 0) then add the user to the wheel group in /etc/group su still fails. What am I missing? It's go to be something really dumb. It might help to know what error you are getting. It is impossible to know what exactly you tried and what exactly you saw as the result, so it is difficult to know what to tell you. But, a comment anyway. You do not need to make the primary group be 'wheel', although I suppose you can if you like. The primary group for a user is the one they are assigned in the /etc/passwd (master.passwd) file. It is the one you give them with adduser. I would suggest making the user's primary group, whatever group you would make them for other than the 'su' consideration. Then, add them to the wheel group as one of their secondary groups by editing the /etc/group file and adding the user on to the wheel group. If, for example, the username is privuser, just add ',privuser' on to the end of the line defining the wheel group (minus the quote marks and without a space before the comma). Just edit /etc/group with vi. This way, you can move the user in to and out of the wheel group without affecting group ownership of the user's files. If you make the user's primary group to be wheel, the user's files will most likely end up with wheel for group ownership and you would have to change all that if you wanted to remove that user from the wheel group, but not delete the account. jerry You can also use pw for this. To set primary: pw usermod -g group -n user To add a secondary group: Typo Edit: pw usermod -G group -n user -Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Really Dumb Question
This is probably a dumb question. I need to add a user that can su to root. So I add the user with adduser, invite the user into the wheel group (GID 0) then add the user to the wheel group in /etc/group su still fails. What am I missing? It's go to be something really dumb. Thanks for any help. Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Errors with Freebsd 4.10
Thank you for your help Kent. I was successsfully able to rebuild FreeBSD and get 4.10 working. Dan Kent Stewart wrote: On Thursday 27 May 2004 05:47 pm, Dan Ferris wrote: I started out with 4.9-STABLE iso images. My cvsup file: *default host=cvsup2.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_4 What may be biting you is you didn't copy the stable-supfile correctly. You probably need *default delete use-rel-suffix and you may also need # If your network link is a T1 or faster, comment out the following line. #*default compress Don't compress the files. People use the context to see what you did wrong. If you don't use something, add a "#" to column 1 like I did on the compress line. Kent src-all make.conf: NOPROFILE=true CFLAGS=" -O -pipe" You don't use quotes on the CFLAG argument. Dan Kent Stewart wrote: On Thursday 27 May 2004 11:45 am, Dan Ferris wrote: Been habving problems making a new kernel with 4.10: /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:371: syntax error at end of input *** Error code 1 This is the result of make when building the kernel with both GENERIC and my custom configuration. It even occurs when I comment out USB in the config files. make buildworld doesn't work for me either. /usr.bin/binutils/gdb/kvm-fbsd.c /usr/src/gnu/usr.bin/binutils/gdb/kvm-fbsd.c:739: macro `SOLIB_ADD' used with too many (4) args mkdep: compile failed *** Error code 1 You aren't supposed to try a kernel if the buildworld doesn't work because buildkernel depends on a current buildworld. What version did you start out with. I just finished adding 4-10 to 5 machines and didn't have a problem. So, what did you do different. You might try "make cleandir" twice in /usr/src and see if that helps. Hardware is a dual processor P3 at 450MHz with 1GB of RAM and a 40GB hard disk. I don't know the exact make of the motherboard, but I'm pretty sure that it's an Intel. Hardware at this point doesn't mean anything. You have something wrong with your processing of source. For example, did you cvsup src-all and do you have any WITH type of entries in your /etc/make.conf. Kent ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Errors with Freebsd 4.10
Been habving problems making a new kernel with 4.10: /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:363: `ohci_methods' undeclared (first use in this function) /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:363: (Each undeclared identifier is reported only once /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:363: for each function it appears in.) /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:367: storage class specified for parameter `ohci_devclass' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: storage class specified for parameter `ohci_pci_driver_list' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: parameter `ohci_pci_driver_list' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: warning: initialization from incompatible pointer type /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: storage class specified for parameter `ohci_pci_driver_mod' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: parameter `ohci_pci_driver_mod' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: storage class specified for parameter `ohci_pci_mod' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: parameter `ohci_pci_mod' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: storage class specified for parameter `ohci_pcimodule_sys_init' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: parameter `ohci_pcimodule_sys_init' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: storage class specified for parameter `__set_sysinit_set_sym_ohci_pcimodule_sys_init' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: parameter `__set_sysinit_set_sym_ohci_pcimodule_sys_init' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: syntax error before `__asm' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:369: warning: empty declaration /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: storage class specified for parameter `ohci_cardbus_driver_list' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: parameter `ohci_cardbus_driver_list' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: warning: initialization from incompatible pointer type /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: storage class specified for parameter `ohci_cardbus_driver_mod' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: parameter `ohci_cardbus_driver_mod' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: storage class specified for parameter `ohci_cardbus_mod' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: parameter `ohci_cardbus_mod' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: storage class specified for parameter `ohci_cardbusmodule_sys_init' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: parameter `ohci_cardbusmodule_sys_init' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: storage class specified for parameter `__set_sysinit_set_sym_ohci_cardbusmodule_sys_init' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: parameter `__set_sysinit_set_sym_ohci_cardbusmodule_sys_init' is initialized /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: syntax error before `__asm' /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:370: warning: empty declaration /usr/src/sys/modules/usb/../../dev/usb/ohci_pci.c:371: syntax error at end of input *** Error code 1 This is the result of make when building the kernel with both GENERIC and my custom configuration. It even occurs when I comment out USB in the config files. make buildworld doesn't work for me either. /usr.bin/binutils/gdb/kvm-fbsd.c /usr/src/gnu/usr.bin/binutils/gdb/kvm-fbsd.c:739: macro `SOLIB_ADD' used with too many (4) args mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/gdb. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Hardware is a dual processor P3 at 450MHz with 1GB of RAM and a 40GB hard disk. I don't know the exact make of the motherboard, but I'm pretty sure that it's an Intel. Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
