6.1-RELEASE disk hangs after loading kernel on sparc64
I've downloaded 6.1-RELEASE-sparc64-disc1.iso and try to boot. loader boots kernel and hangs on message: jumping to kernel entry at 0x... What can I do? PS. It's sun 480 with 4 CPU. I have no complete info on the configuration. -- Dixi. Sem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Messages from rc-scripts are not displayed at all
Hello. Yesss!!! At last we found the source of problem! The problem with displaying messages from rc-scripts caused by option dcons_crom in kernel (dumb console on Firewire). When it is enabled on PC with FireWire port, all output goes there instead of system console. Disabling this option solved the problem. So I have one more question - why this option causes so strange effect? This is a bug or a feature? -- .O. | Sergei Mozhaisky ..O | http://frenzy.org.ua/ OOO | http://frenzytechnix.livejournal.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-RELEASE disk hangs after loading kernel on sparc64
On Mon, 2006-06-19 at 12:08 +0400, Sergey Matveychuk wrote: I've downloaded 6.1-RELEASE-sparc64-disc1.iso and try to boot. loader boots kernel and hangs on message: jumping to kernel entry at 0x... What can I do? PS. It's sun 480 with 4 CPU. I have no complete info on the configuration. The Sun 480 is Ultrasparc-III processors and is not supported at this time. Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-RELEASE disk hangs after loading kernel on sparc64
Gavin Atkinson wrote: On Mon, 2006-06-19 at 12:08 +0400, Sergey Matveychuk wrote: I've downloaded 6.1-RELEASE-sparc64-disc1.iso and try to boot. loader boots kernel and hangs on message: jumping to kernel entry at 0x... What can I do? PS. It's sun 480 with 4 CPU. I have no complete info on the configuration. The Sun 480 is Ultrasparc-III processors and is not supported at this time. And CURRENT too? -- Dixi. Sem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-RELEASE disk hangs after loading kernel on sparc64
Sergey Matveychuk wrote: Gavin Atkinson wrote: On Mon, 2006-06-19 at 12:08 +0400, Sergey Matveychuk wrote: I've downloaded 6.1-RELEASE-sparc64-disc1.iso and try to boot. loader boots kernel and hangs on message: jumping to kernel entry at 0x... What can I do? PS. It's sun 480 with 4 CPU. I have no complete info on the configuration. The Sun 480 is Ultrasparc-III processors and is not supported at this time. And CURRENT too? Sorry, found the info on web site. BTW OpenBSD supports UltraSparc III. (http://kerneltrap.org/node/6668) -- Dixi. Sem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade failure
After upgrading to the latest portupgrade: dns root:~#portupgrade -v portupgrade 2.0.1 (2006/06/18) I got a failure on 2 out of 4 boxes. Now when I use portversion, portupgrade, or pkgdb I get: backup root:/usr/ports#portversion [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 34 packages found (-0 +0) Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ Any pointers on how to fix this would be appreciated. Thanks Elliot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
bridge.ko, sysctrl.conf and ifconfig_XXX_name, SCSI as a boot device
Hello list, I have two minor problems: First one: I want to make bridging on two of my interfaces but have problem when I use ifconfig_XXX_name directrive in rc.conf . After each restart of machine I must enter manually commands for sysctrl to enable bridging. After reboot dmesg shows: interface net0 Not found in bridge interface net2 Not found in bridge /etc/rc.conf: ifconfig_rl0_name=net0 ifconfig_rl1_name=net1 ifconfig_rl2_name=net2 /etc/sysctrl.conf: net.link.ether.bridge.enable=1 net.link.ether.bridge.config=net0,net2 Second problem: I have SCSI controller with 40GB hard disk and two ATA disks. My FreeBSD is installed on da0 (SCSI). Last night I connect USB stick to the box and transfer some files. On morning I found that machine is restarted because of power outage and refuse to boot. After first wave of panic I found that USB Flash Disk is still attached and kernel change naming order of SCSI devices: Now ad0 was USB Flash, SCSI -FUJITSU - ad1. I thing that is not good idea to naming USB devices first and after this real SCSI devices. So, what is the right workaround of these problems? Regards, Todor Dragnev ad0: 238475MB Seagate ST3250824A 3.AAE at ata0-master UDMA100 ad2: 152627MB Seagate ST3160023A 8.01 at ata1-master UDMA100 da0 at sym0 bus 0 target 15 lun 0 da0: FUJITSU MAP3367NP 0106 Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 35046MB (71775284 512 byte sectors: 255H 63S/T 4467C) umass0: Generic Mass Storage Device, rev 2.00/1.02, addr 2 da1 at umass-sim0 bus 0 target 0 lun 0 da1: Multi Flash Reader 1.00 Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: 982MB (2012160 512 byte sectors: 64H 32S/T 982C) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: puc and sio
On Mon, 2006-06-19 at 02:56 +0400, Dmitry Morozovsky wrote: Dear colelagues, playing with puc compatible MOXA card I found that it's rather useless with contemporary DEFAULT kernel: - sio compiled in, puc as module - puc identified, but no sio ports detected, even when puc.ko is loaded by loader - sio and puc both loaded as modules - all sio ports detected, but comconsole cannot be activated - sio and puc compiled in kernel - all work flawlessly Maybe it's time to consider including puc in GENERIC? Yes - this has been brought up a few times before. Another alternative is the patch in http://lists.freebsd.org/pipermail/freebsd-current/2005-December/058909.html - but there was at least one objection to it. I'm not convinced the current status quo is acceptable, though. Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bridge.ko, sysctrl.conf and ifconfig_XXX_name, SCSI as a boot device
On Jun 19, 2006, at 4:38 PM, Todor Dragnev wrote: First one: I want to make bridging on two of my interfaces but have problem when I use ifconfig_XXX_name directrive in rc.conf . After each restart of machine I must enter manually commands for sysctrl to enable bridging. /etc/sysctrl.conf: There's no 'r' in sysctl. Maybe that's why? ;) -- Alban Hertroys Sometimes you wake up and you think: Galileo was right, the world does turn !DSPAM:74,4496dd3d333521941817249! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADSUP: default for hw.acpi.reset_video changed
I thought this would be a small change (since the default was already supposed to be this way) but as usual with acpi, there is a lot of variation out there. I think it's split about 50/50 between systems where enabling this feature is helpful/neutral and those that it is harmful. The default value of the tunable/sysctl for hw.acpi.reset_video has changed from 1 to 0 (off). This means the BIOS video reset method will not be called automatically on resume. If you want the previous behavior, set hw.acpi.reset_video=1 in /boot/loader.conf or /etc/sysctl.conf. If a committer could throw the 2nd paragraph in UPDATING, that would be nice, thanks. Thanks, -- Nate ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bridge.ko, sysctrl.conf and ifconfig_XXX_name, SCSI as a boot device
On Mon, Jun 19, 2006 at 05:38:43PM +0300, Todor Dragnev wrote: Hello list, I have two minor problems: First one: I want to make bridging on two of my interfaces but have problem when I use ifconfig_XXX_name directrive in rc.conf . After each restart of machine I must enter manually commands for sysctrl to enable bridging. After reboot dmesg shows: interface net0 Not found in bridge interface net2 Not found in bridge /etc/rc.conf: ifconfig_rl0_name=net0 ifconfig_rl1_name=net1 ifconfig_rl2_name=net2 /etc/sysctrl.conf: net.link.ether.bridge.enable=1 net.link.ether.bridge.config=net0,net2 /etc/sysctl.conf is processed really early in the startup process so the renaming hasn't happend yet. Using the origional names would work, but would be confusing. If you want the naming, I'd suggest switching to if_bridge which can be configured entierly using rc.conf variables. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp7uA3pAqIdP.pgp Description: PGP signature
Re: ath problems when in if_bridge mode
On Saturday 10 June 2006 18:00, Andrew Thompson wrote: On Tue, Jun 06, 2006 at 11:53:30AM -0300, JoaoBR wrote: Hi I find some problems when running ath cards in if_bridge mode. I have continuous UP/DOWN events on the uplink card. The connection is really interrupted for a second or so which results in dns lookup errors downloads are going through, only the download speed is not stable please look close, the problem is not on the hostap card the problem is not hw related, I can switch both cards and the problem stays on the uplink card I can take the bridge off and stay connected without UP/DOWN events (same machine/same HW) Bridging a wireless client is not supported, you can read this thread for more into (especially the last couple of posts) sorry for the delay I was underway seems I posted the wrong ifconfig output but setting the uplink card into adhoc mode the same thing happens I am not sure if this belongs to you Andrew but if I do not set the cards in bridge mode then the device up/down event do *not* appear, the uplink card stays connected without a word soon I put it in if_bridge mode I have this continuous up/down events João -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atheros 'device timeout'
As was spoken by Sam Leffler on 06/16/06 22:14~ Reid Linnemann wrote: On 6/14/2006, Sam Leffler [EMAIL PROTECTED] wrote: Reid Linnemann wrote: Thanks Sam, I've disabled power save mode in both wireless windows clients and I'll see if the problem lightens up. Also, do you know why device timeouts would be spat out by the driver when no stations are associated with the AP? The device timeouts persisted after my clients were shut down, and no other stations appear to be in the area. No idea. The problem with buffered mcast frames is because the h/w xmit queue for the frames stops running and blocks the lower priority queues causing the watchdog timer to fire (and generate the device timeout msg). I'm pretty sure this is a race between ath_tx_start and ath_beacon_proc but I've not had time to rework the code and test (this problem does not exist in the linux version but it's structured very differently). If no clients are associated (or associated w/ power save enabled) then no frames should be buffered and this problem should not occur. To debug you can enable reset msgs in the driver (athdebug reset) and look to see what h/w q the frame(s) were on when the reset was done. Note that to do that you must enable ATH_DEBUG. Sam Sam, I grabbed a clean 6-STABLE tree today, recompile, and I got another timeout captured. The debug output does look slightly different: ath0: device timeout ath_draintxq: beacon queue 0x3e9ab000 ath_tx_stopdma: tx queue [0] 0, link 0 ath_tx_stopdma: tx queue [1] 0x3e9af0c0, link 0xed0d80f0 ath_tx_stopdma: tx queue [2] 0, link 0 ath_tx_stopdma: tx queue [3] 0, link 0 ath_tx_stopdma: tx queue [8] 0, link 0 Q1[ 0] (DS.V:0xed0dd700 DS.P:0x3e9b4700) L:3e9b4730 D:3e624836 F:043 01240110 01001020 0001 001b (DS.V:0xed0dd730 DS.P:0x3e9b4730) L:3e9b4e80 D:30bcf00e F:043 00ec 0001 001b f1710001 c6d1 Q1[ 1] (DS.V:0xed0dde80 DS.P:0x3e9b4e80) L:3e9b4eb0 D:312f2036 F:043 0124011f 01001020 0001 001b (DS.V:0xed0ddeb0 DS.P:0x3e9b4eb0) L:3e9b6500 D:307f500e F:043 00fb 0001 001b e5f20001 e883 Q1[ 2] (DS.V:0xed0df500 DS.P:0x3e9b6500) L:3e9b6530 D:3e76b236 F:043 0124011f 01001020 0001 001b (DS.V:0xed0df530 DS.P:0x3e9b6530) L:3e9b5ba0 D:310c800e F:043 00fb 0001 001b e5f50001 e885 Q1[ 3] (DS.V:0xed0deba0 DS.P:0x3e9b5ba0) L:3e9b5bd0 D:30639836 F:043 01240084 01001020 0001 001b (DS.V:0xed0debd0 DS.P:0x3e9b5bd0) L:3e9b5d80 D:3e62433e F:043 0060 0001 001b e6110001 e887 Q1[ 4] (DS.V:0xed0ded80 DS.P:0x3e9b5d80) L:3e9b5db0 D:3e6aac36 F:043 01240084 01001020 0001 001b (DS.V:0xed0dedb0 DS.P:0x3e9b5db0) L:3e9b6e60 D:3e76b43e F:043 0060 0001 001b e6130001 e889 Q1[ 5] (DS.V:0xed0dfe60 DS.P:0x3e9b6e60) L:3e9b6e90 D:3e607136 F:0413 21240084 01001020 0001 001b (DS.V:0xed0dfe90 DS.P:0x3e9b6e90) L:3e9b59c0 D:3e60733e F:0413 0060 0001 001b e6140001 e88b Q1[ 6] (DS.V:0xed0de9c0 DS.P:0x3e9b59c0) L:3e9b59f0 D:3e569336 F:043 01240084 01001020 0001 001b (DS.V:0xed0de9f0 DS.P:0x3e9b59f0) L:3e9b6320 D:3e72583e F:043 0060 0001 001b e6150001 e88d Q1[ 7] (DS.V:0xed0df320 DS.P:0x3e9b6320) L:3e9b6350 D:3e569936 F:043 01240084 01001020 0001 001b (DS.V:0xed0df350 DS.P:0x3e9b6350) L:3e9b6c80 D:30b3e03e F:043 0060 0001 001b e6160001 e88f Q1[ 8] (DS.V:0xed0dfc80 DS.P:0x3e9b6c80) L:3e9b6cb0 D:3077a136 F:043 0124011f 01001020 0001 001b (DS.V:0xed0dfcb0 DS.P:0x3e9b6cb0) L:3e9b79a0 D:30eca80e F:043 00fb 0001 001b e6190001 e891 Q1[ 9] (DS.V:0xed0e09a0 DS.P:0x3e9b79a0) L:3e9b79d0 D:3e725b36 F:043 01240084 01001020 0001 001b (DS.V:0xed0e09d0 DS.P:0x3e9b79d0) L:3e9b7040 D:3e60783e F:043 0060 0001 001b edb70001 2893 Q1[ 10] (DS.V:0xed0e0040 DS.P:0x3e9b7040) L:3e9b7070 D:3e607036 F:0413 21240084 01001020 0001 001b (DS.V:0xed0e0070 DS.P:0x3e9b7070) L:3e9acb40 D:3e76b13e F:0413 0060 0001 001b edb80001 2895 Q1[ 11] (DS.V:0xed0d5b40 DS.P:0x3e9acb40) L:3e9acb70 D:3e725636 F:043 01240084 01001020 0001 001b (DS.V:0xed0d5b70 DS.P:0x3e9acb70) L:3e9ac1e0 D:3e4a803e F:043 0060 0001 001b edb90001 2897 Q1[ 12] (DS.V:0xed0d51e0 DS.P:0x3e9ac1e0) L:3e9ac210 D:3e624736 F:043 01240084 01001020 0001 001b (DS.V:0xed0d5210 DS.P:0x3e9ac210) L:3e9b77c0 D:3e569d3e F:043 0060 0001 001b edba0001 2899 Q1[ 13] (DS.V:0xed0e07c0 DS.P:0x3e9b77c0) L:3e9b77f0 D:3e569536 F:043 01240084 01001020 0001 001b (DS.V:0xed0e07f0 DS.P:0x3e9b77f0) L:3e9ad680 D:3e6aae3e F:043
Re: bridge.ko, sysctrl.conf and ifconfig_XXX_name, SCSI as a boot device
Thanks, I will use if_bridge from now. Anyone have ideas about second problem? Maybe I must remove device usb from GENERIC config and recompile kernel ? On 6/19/06, Brooks Davis [EMAIL PROTECTED] wrote: /etc/sysctl.conf is processed really early in the startup process so the renaming hasn't happend yet. Using the origional names would work, but would be confusing. If you want the naming, I'd suggest switching to if_bridge which can be configured entierly using rc.conf variables. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 -- There are no answers, only cross references ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
make rerelease broken at camcontrol...
Thanks to all who answered my 'make release' questions; now that I have done the initial release cut, now I am trying out 'make rerelease', and it's bombing at the stage 4.4: building everything stage. -=- === sbin/camcontrol (all) cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -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 -o camcontrol camcontrol.o util.o modeedit.o -lcam -lsbuf modeedit.o(.text+0xd14): In function `mode_edit': : undefined reference to `mode_sense' modeedit.o(.text+0xd5c): In function `mode_edit': : undefined reference to `mode_sense' modeedit.o(.text+0xdf9): In function `mode_edit': : undefined reference to `mode_sense' modeedit.o(.text+0xe86): In function `mode_edit': : undefined reference to `mode_select' modeedit.o(.text+0xebf): In function `mode_edit': : undefined reference to `mode_sense' modeedit.o(.text+0x11ec): In function `mode_list': : undefined reference to `mode_sense' *** Error code 1 Stop in /usr/src/sbin/camcontrol. *** Error code 1 Stop in /usr/src/sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. + exit 1 + umount /dev *** Error code 1 (ignored) -=- Looking in CVS; modeedit.c hasn't changed in two years, so I am perplexed at what is going on here. Any ideas? The make rerelease command used is: make -i rerelease NODOC=YES NO_FLOPPIES=YES CHROOTDIR=/hog/release \ BUILDNAME=6.1-RELEASE-p2 CVSROOT=/hog/FreeBSD-CVS RELEASETAG=RELENG_6_1 (no optimizations, etc.) Thanks - Peter signature.asc Description: OpenPGP digital signature
RE: save-entropy
Olivier,
That process is meant to be there. I don't know why it has the '--' argument
but it isn't likely to be a symptom of the problem you are having.
Try
sh -x /usr/libexec/save-entropy
To get more insight into when it is failing. This will show you surrounding
commands which will give you a better chance of working out what is failing in
the script.
At least 20% of my students run into this sort of problem when I have them
configure FreeBSD systems. While normally its their rc.conf file that gets
messed up, in your case it apparently isn't so I suppose I'm still suggesting
ways of finding out what file/line has the problem.
Good luck,
Brian
-Original Message-
From: olivier.taylor [mailto:[EMAIL PROTECTED]
Sent: Friday, 16 June 2006 3:47 PM
To: Scott, Brian
Cc: freebsd-stable@freebsd.org
Subject: Re: save-entropy
Thanks Scott,
But unfortunately, that's not the case...
With ps ax I found a process
1 ?? ILs0:00.00 /sbin/init --
Strange stuff, grrr
The server is on a datacenter, I don't see the startup messages...
Olivier
Scott, Brian a écrit :
That would be the old 'accidentally deleted a # from a line in rc.conf'
problem. There are likely to be several lines beginning '# -- ' in the file.
New users often accidentally remove the # making the '--' into a command.
There will also be a few messages during startup that will also complain
about the '--' command but most people ignore these.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of olivier.taylor
Sent: Thursday, 15 June 2006 8:59 PM
To: [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Subject: Re: save-entropy
freebsd 5.4
#!/bin/sh
#
# Copyright (c) 2001-2005 Douglas Barton, [EMAIL PROTECTED]
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in
the
#documentation and/or other materials provided with the
distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS''
AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE
LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF
# SUCH DAMAGE.
#
# $FreeBSD: src/libexec/save-entropy/save-entropy.sh,v 1.2.12.1
2005/04/14 21:49:13 dougb Exp $
# This script is called by cron to store bits of randomness which are
# then used to seed /dev/random on boot.
# Originally developed by Doug Barton, [EMAIL PROTECTED]
PATH=/bin:/usr/bin
# If there is a global system configuration file, suck it in.
#
if [ -r /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
source_rc_confs
elif [ -r /etc/rc.conf ]; then
. /etc/rc.conf
fi
case ${entropy_dir} in
[Nn][Oo])
exit 0
;;
*)
entropy_dir=${entropy_dir:-/var/db/entropy}
;;
esac
entropy_save_sz=${entropy_save_sz:-2048}
entropy_save_num=${entropy_save_num:-8}
if [ ! -d ${entropy_dir} ]; then
umask 077
mkdir ${entropy_dir} || {
logger -is -t $0 The entropy directory ${entropy_dir} does
not \
exist, and cannot be created. Therefore no entropy can be saved. ;
exit 1;}
/usr/sbin/chown operator:operator ${entropy_dir}
chmod 0700 ${entropy_dir}
fi
umask 377
for file_num in `jot ${entropy_save_num} ${entropy_save_num} 1`; do
if [ -e ${entropy_dir}/saved-entropy.${file_num} ]; then
if [ -f ${entropy_dir}/saved-entropy.${file_num} ]; then
new_num=$(($file_num + 1))
if [ ${new_num} -gt ${entropy_save_num} ]; then
rm -f ${entropy_dir}/saved-entropy.${file_num}
else
mv ${entropy_dir}/saved-entropy.${file_num} \
${entropy_dir}/saved-entropy.${new_num}
fi
else
logger -is -t $0 \
Re: make rerelease broken at camcontrol...
Peter Losher wrote: Thanks to all who answered my 'make release' questions; now that I have done the initial release cut, now I am trying out 'make rerelease', and it's bombing at the stage 4.4: building everything stage. -=- === sbin/camcontrol (all) cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -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 -o camcontrol camcontrol.o util.o modeedit.o -lcam -lsbuf modeedit.o(.text+0xd14): In function `mode_edit': : undefined reference to `mode_sense' modeedit.o(.text+0xd5c): In function `mode_edit': : undefined reference to `mode_sense' modeedit.o(.text+0xdf9): In function `mode_edit': : undefined reference to `mode_sense' modeedit.o(.text+0xe86): In function `mode_edit': : undefined reference to `mode_select' modeedit.o(.text+0xebf): In function `mode_edit': : undefined reference to `mode_sense' modeedit.o(.text+0x11ec): In function `mode_list': : undefined reference to `mode_sense' *** Error code 1 Stop in /usr/src/sbin/camcontrol. *** Error code 1 Stop in /usr/src/sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. + exit 1 + umount /dev *** Error code 1 (ignored) -=- Looking in CVS; modeedit.c hasn't changed in two years, so I am perplexed at what is going on here. Any ideas? The make rerelease command used is: make -i rerelease NODOC=YES NO_FLOPPIES=YES CHROOTDIR=/hog/release \ BUILDNAME=6.1-RELEASE-p2 CVSROOT=/hog/FreeBSD-CVS RELEASETAG=RELENG_6_1 (no optimizations, etc.) Thanks - Peter camcontrol.o probably got truncated or corrupted. Remove it and the build should work. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
