Panic: vrele: negative ref cnt
I received a panic message (see Subject) yesterday following a GNOME upgrade. The upgrade was successful but I encountered subsequent problems trying to access Firefox websites and my mail site in Thunderbird. I noticed a Plugin error message in Firefox and prepared to paste it into a message to the mailing list but was unable to get a connection and eventually lost it. I reset my modem several times then decided to reboot. First, I re-enabled my firewall then entered shutdown -r now. Next I received the panic message and a repeat of the following: READ_DMA ad0:Timeout - Read_DMA retrying (2 retries left) LBA = 28162271 READ_DMA ad0: FAILURE -READ_DMA status=51 READY, DSC, ERROR error = 40 Uncorrectable LBA =28162271 Unfortunately, this may not have been exactly how the message read. I was sort of in a panic state myself. Another message indicated there was no request/requirement to dump. I run FreeBSD 5.4 RELEASE. Your advice is appreciated. Thnx, Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Panic: vrele: negative ref cnt
-Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Sunday, May 07, 2006 3:20 PM To: Robert H. Perry Cc: freebsd-questions@freebsd.org Subject: Re: Panic: vrele: negative ref cnt On Sun, May 07, 2006 at 03:16:46PM -0400, Robert H. Perry wrote: I received a panic message (see Subject) yesterday following a GNOME upgrade. The upgrade was successful but I encountered subsequent problems trying to access Firefox websites and my mail site in Thunderbird. I noticed a Plugin error message in Firefox and prepared to paste it into a message to the mailing list but was unable to get a connection and eventually lost it. I reset my modem several times then decided to reboot. First, I re-enabled my firewall then entered shutdown -r now. Next I received the panic message and a repeat of the following: READ_DMA ad0:Timeout - Read_DMA retrying (2 retries left) LBA = 28162271 READ_DMA ad0: FAILURE -READ_DMA status=51 READY, DSC, ERROR error = 40 Uncorrectable LBA =28162271 Your hard drive is dying. This may have caused the panic as a secondary effect after the read failed. Thanks for taking the time to respond. Not good news obviously, but could be worse. This is my mule machine. I was using it as a gateway, to develop some networking skills, and had installed SAMBA and was also trying to install HylaFAX . Fortunately it has a second hard drive which currently holds the /var slice. Out with the bad and in with the good. BTW, can the data on this drive be copied to the surviving drive? What commands do I need to review? My initial thoughts were to simply install 6.0 and go on from there. Any hints/suggestions are appreciated. Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolved: Need Assistance Upgrading Ethereal-0.10.13_3 to 0.10.14
Nagilum wrote: Hi Bob, It seems you caught the port in a unstable moment where the patch could not be applied for some reason. This was probably only a very brief moment so the next cvsup/portsnap update fixed the problem. Kind regards, Robert H. Perry wrote: Original Message Subject: Need Assistance Upgrading Ethereal-0.10.13_3 to 0.10.14 Date: Sat, 31 Dec 2005 00:52:21 -0500 From: Robert H. Perry [EMAIL PROTECTED] To: freebsd-questions@freebsd.org FreeBSD sphinx.my.domain 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Ran into the following error while running portupgrade on ethereal: == applying extra patch /usr/ports/net/ethereal/files/extra-patch-capture_loop.c ***Error code 1 Stop in usr/ports/net/ethereal. Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade43330.26 make ** Fix the problem and try again. The recommendation Fix the problem and try again. seems relatively straightforward, however... Is this an error I should know how to easily fix? Please advise. Thnx Just want to report that the error noted above did not re-occur during this week's upgrade. Have no idea how, or why. Nagilum, Thanks for the explanation. If I come across another message like this, I'll know to use a little patience as my first step. Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Resolved: Need Assistance Upgrading Ethereal-0.10.13_3 to 0.10.14
Original Message Subject: Need Assistance Upgrading Ethereal-0.10.13_3 to 0.10.14 Date: Sat, 31 Dec 2005 00:52:21 -0500 From: Robert H. Perry [EMAIL PROTECTED] To: freebsd-questions@freebsd.org FreeBSD sphinx.my.domain 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Ran into the following error while running portupgrade on ethereal: == applying extra patch /usr/ports/net/ethereal/files/extra-patch-capture_loop.c ***Error code 1 Stop in usr/ports/net/ethereal. Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade43330.26 make ** Fix the problem and try again. The recommendation Fix the problem and try again. seems relatively straightforward, however... Is this an error I should know how to easily fix? Please advise. Thnx Just want to report that the error noted above did not re-occur during this week's upgrade. Have no idea how, or why. Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Need Assistance Upgrading Ethereal-0.10.13_3 to 0.10.14
FreeBSD sphinx.my.domain 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Ran into the following error while running portupgrade on ethereal: == applying extra patch /usr/ports/net/ethereal/files/extra-patch-capture_loop.c ***Error code 1 Stop in usr/ports/net/ethereal. Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade43330.26 make ** Fix the problem and try again. The recommendation Fix the problem and try again. seems relatively straightforward, however... Is this an error I should know how to easily fix? Please advise. Thnx ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fax App Recommendations
Daniel wrote: On 11/30/05, Robert H. Perry [EMAIL PROTECTED] wrote: Robert H. Perry wrote: Robert H. Perry wrote: Currently running FreeBSD RELEASE 5.4 and a MultiTech Voice/Data/Fax modem for dialup internet service on a server-type machine. I also run another machine with 3 operating systems (FreeBSD 5.4, Suse 9.2, and Windows XP). My original objective was to install Hylafax on the server and share it with the other 3 systems. I ran into a couple of errors early on and seeked some help from the mailing list. Got one response suggesting I reinstall the app from source. I was preparing to respond to a reply when Thunderbird sent the original to never-never-land. Sorry. Here's the problem I encountered. I was running the sendfax command to test my installation and received an unexpected error message. I used the command taken from the sendfax man page as follows: sendfax -n -d (destination fax#) /etc/passwd sendfax: no files to send usage:... I reran it using the -x debug option and the message indicated: What version of hylafax was installed? hylafax-4.2.1_3 Make sure you install gawk. gawk-3.1.1_1 installed The native awk binary in FBSD is nawk (not gawk) which caused me some greif with hylafax scripts. So, update ports. Remove hylafax. Install gawk. Reinstall hylafax. Hope you noticed the second note sent last night. This one was sent unfinished. Also note that I have mgetty-1.1.33 installed. Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fax App Recommendations
Daniel wrote: On 12/1/05, Robert H. Perry [EMAIL PROTECTED] wrote: Daniel wrote: On 11/30/05, Robert H. Perry [EMAIL PROTECTED] wrote: Robert H. Perry wrote: Robert H. Perry wrote: Currently running FreeBSD RELEASE 5.4 and a MultiTech Voice/Data/Fax modem for dialup internet service on a server-type machine. I also run another machine with 3 operating systems (FreeBSD 5.4, Suse 9.2, and Windows XP). My original objective was to install Hylafax on the server and share it with the other 3 systems. I ran into a couple of errors early on and seeked some help from the mailing list. Got one response suggesting I reinstall the app from source. I was preparing to respond to a reply when Thunderbird sent the original to never-never-land. Sorry. Here's the problem I encountered. I was running the sendfax command to test my installation and received an unexpected error message. I used the command taken from the sendfax man page as follows: sendfax -n -d (destination fax#) /etc/passwd sendfax: no files to send usage:... I reran it using the -x debug option and the message indicated: What version of hylafax was installed? hylafax-4.2.1_3 Make sure you install gawk. gawk-3.1.1_1 installed The native awk binary in FBSD is nawk (not gawk) which caused me some greif with hylafax scripts. So, update ports. Remove hylafax. Install gawk. Reinstall hylafax. Hope you noticed the second note sent last night. This one was sent unfinished. Also note that I have mgetty-1.1.33 installed. I don't have mgetty installed, but I do have hylafax 4.2.1_1 installed, gawk 3.1.1_1, and some mime ports (mime-support and metamail) to allow for sending electronic faxes via e-mail to people in our company. I issued the exact same sendfax command: # sendfax -n -d 5551212 /etc/passwd Of course changing 5551212 for one of my faxes and it sent fine. When I started this course of action in setting up hylafax I had no idea about faxes either. I basically followed the instructions on http://www.hylafax.org/howto/install.html#ss2.2 I skipped section 2.2.3 because hylafax was installed. I didn't install mgetty either. I added the line: cuaa0 /usr/local/sbin/faxgetty dialup on secure Into /etc/ttys under serial consoles (location probably don't matter) and then ran: init q to rescan the /etc/ttys file. You also want to copy /usr/local/etc/rc.d/hylafax.sh.sample to /usr/local/etc/rc.d/hylafax.sh. This doesn't use rcng so you can just run /usr/local/etc/rc.d/hylafax.sh start which will/should fire up the hylafax daemon. You don't need to worry about the cronjobs (they're there for cleaning up and can be delt with later). So at this point, make sure you do init q and run the rc.d/hylafax.sh start or just reboot. Provided that you completed 2.2.4 (adding modems and configuring setup in general) without any dramas at all from the howto you should be able to run the sendfax command. Are you also certain your modem is operating correctly? You could run the bash shell and then type echo atdt089231414141414 /dev/cuaa0 and the modem should dial whatever number after atdt and you should either hear it through the modem speaker, see it with the lites on the modem or the phone should ring (if you put your phone number or mobile number in). You should also try using the basic default settings for adding new modems. If you havn't removed hylafax and reinstalled (making sure that the deinstall deleted everything) I'd do that now. To make sure all files it creates are gone you could run: pkg_info -L hylafax\* hylafax-files Then deinstall hylafax Then: cat hylafax-files and see if any of the files listed still exist. I hope this helps a bit more. Dan, This will be a tremendous help. I already see answers to questions I hadn't posted yet and suggestions which will help me better understand some of the printed material. Will keep you posted. Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fax App Recommendations
Currently running FreeBSD RELEASE 5.4 and a MultiTech Voice/Data/Fax modem for dialup internet service on a server-type machine. I also run another machine with 3 operating systems (FreeBSD 5.4, Suse 9.2, and Windows XP). My original objective was to install Hylafax on the server and share it with the other 3 systems. I ran into a couple of errors early on and seeked some help from the mailing list. Got one response suggesting I reinstall the app from source. I don't have a lot expertise with modems and facsimiles so I'm considering starting with something a little less complex. Can anyone recommend a fax app for a newbie? Thnx, Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fax App Recommendations
Robert H. Perry wrote: Currently running FreeBSD RELEASE 5.4 and a MultiTech Voice/Data/Fax modem for dialup internet service on a server-type machine. I also run another machine with 3 operating systems (FreeBSD 5.4, Suse 9.2, and Windows XP). My original objective was to install Hylafax on the server and share it with the other 3 systems. I ran into a couple of errors early on and seeked some help from the mailing list. Got one response suggesting I reinstall the app from source. I don't have a lot expertise with modems and facsimiles so I'm considering starting with something a little less complex. Can anyone recommend a fax app for a newbie? Thnx, Bob Perry I was preparing to respond to a reply when Thunderbird sent the original to never-never-land. Sorry. Here's the problem I encountered. I was running the sendfax command to test my installation and received an unexpected error message. I used the command taken from the sendfax man page as follows: sendfax -n -d (destination fax#) /etc/passwd sendfax: no files to send usage:... I reran it using the -x debug option and the message indicated: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fax App Recommendations
Robert H. Perry wrote: Robert H. Perry wrote: Currently running FreeBSD RELEASE 5.4 and a MultiTech Voice/Data/Fax modem for dialup internet service on a server-type machine. I also run another machine with 3 operating systems (FreeBSD 5.4, Suse 9.2, and Windows XP). My original objective was to install Hylafax on the server and share it with the other 3 systems. I ran into a couple of errors early on and seeked some help from the mailing list. Got one response suggesting I reinstall the app from source. I don't have a lot expertise with modems and facsimiles so I'm considering starting with something a little less complex. Can anyone recommend a fax app for a newbie? Thnx, Bob Perry I was preparing to respond to a reply when Thunderbird sent the original to never-never-land. Sorry. Here's the problem I encountered. I was running the sendfax command to test my installation and received an unexpected error message. I used the command taken from the sendfax man page as follows: sendfax -n -d (destination fax#) /etc/passwd sendfax: no files to send usage:... I reran it using the -x debug option and the message indicated: WARNING: are you sure that this is a G3 fax file? Doesn't seem to be... My understanding is that sendfax automatically converts ASCII-text documents through to the server, so I'm a little confused. Before responding, please also understand that I know very little about modems, and facsimiles. Don't assume anything please. Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Startx Missing Following Portupgrade
David Armour wrote: hello rob, from /usr/ports/UPDATING: 20051113: AFFECTS: users of x11/xterm, x11/xorg-clients, x11/XFree86-4-clients AUTHOR: [EMAIL PROTECTED] Xterm no longer installs with '-static' prefix. Users should upgrade XFree86-clients to 4.5.0_1 or xorg-clients to 6.8.2_1 or newer before attempting upgrade of xterm to 206_1 or newer. Previous versions remove xterm on deinstall so CONFLICTS have been set accordingly. i only discovered this myself recently. hth. Thanks David, I read the warning in UPDATING. My problem was performing the upgrade while half asleep. I paid a price during the GNOME upgrade as well. Thanks again for taking the time to respond. Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Startx Missing Following Portupgrade
Hi, I'm running FreeBSD 5.4-RELEASE #0 on two machines and just CVSup'd my systems last night finishing with portupgrade this morning. I ran into a problem with machine #1. I ran portupgrade and stumbled with the xterm and x11-fonts/linux-fontconfig upgrades. I tried to run startx to google the problems but got: command not found. Reinstalling linux-base seemed to resolve the x11-fonts problem. I then deinstalled, and reinstalled xorg-clients to upgrade it and ran portupgrade -aRr. No more apparent problems. However, still unable to run startx. I searched /usr/X11R6/bin and couldn't locate the file either. The second machine was also upgrading and I noticed the same/similar failure to install xterm 206_1 due to a conflict with xorg-clients. I haven't attempted to fix it yet for fear of losing startx here also. I'm thinking of deinstalling/reinstalling one, or more ports to reinstall startx on machine #1. (Not sure which ones, however). Any suggestions? Thnx, Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Inconsistency Running IPF Against FTPs
Kevin Kinsey wrote: Robert H. Perry wrote: I'm running FreeBSD RELEASE 5.4 and recently installed IPF Firewall. I rarely download files using FTP but have little choice using portupgrade. Now, during an upgrade, I often see the error message, No route to host... while connecting with an FTP site. If I disable the IPF/IPNAT rules the problem no longer exists. I've followed installation instructions in the Handbook paying particular attention to the section on IPNAT rules. (I do not claim to entirely understand what I read however.) My immediate question however is how current are the instructions? There is a caveat immediately following the IPF Firewall Section title: This section is work in progress. The contents might not be accurate at all times. If it is accurate and should resolve my FTP problems, I'll simply re-read it until I get it right. Any other hints are also appreciated. This would probably fall under your other hints category. Your firewall should be allowing extant connections to continue --- IOW, showing stateful behavior. Some FTP data connections use high-numbered ports, and it sounds as if these are being blocked by your firewall. YMMV. Note that setting FTP_PASSIVE_MODE in your environment might be worth a shot. I am sorry that I'm not an IPF user and can't give more detailed help. Good luck with your issue. Kevin Kinsey Thank you for your suggestions. I do run stateful rules and may try passive FTP. I just upgraded with portupgrade and noticed some FTP issues (i.e. no route to host) so I flushed out the ipnat tables and things improved. Is that my imagination or just coincidence? And Daniel, thanks for your suggestions including the active/passive illustrations. Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Startx Missing Following Portupgrade
Robert H. Perry wrote: Hi, I'm running FreeBSD 5.4-RELEASE #0 on two machines and just CVSup'd my systems last night finishing with portupgrade this morning. I ran into a problem with machine #1. I ran portupgrade and stumbled with the xterm and x11-fonts/linux-fontconfig upgrades. I tried to run startx to google the problems but got: command not found. Reinstalling linux-base seemed to resolve the x11-fonts problem. I then deinstalled, and reinstalled xorg-clients to upgrade it and ran portupgrade -aRr. No more apparent problems. However, still unable to run startx. I searched /usr/X11R6/bin and couldn't locate the file either. The second machine was also upgrading and I noticed the same/similar failure to install xterm 206_1 due to a conflict with xorg-clients. I haven't attempted to fix it yet for fear of losing startx here also. I'm thinking of deinstalling/reinstalling one, or more ports to reinstall startx on machine #1. (Not sure which ones, however). Any suggestions? Thnx, Bob Perry Pls disregard. Xorgclients was missing entirely. Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Inconsistency Running IPF Against FTPs
Kevin Kinsey wrote: Robert H. Perry wrote: I'm running FreeBSD RELEASE 5.4 and recently installed IPF Firewall. I rarely download files using FTP but have little choice using portupgrade. Now, during an upgrade, I often see the error message, No route to host... while connecting with an FTP site. If I disable the IPF/IPNAT rules the problem no longer exists. I've followed installation instructions in the Handbook paying particular attention to the section on IPNAT rules. (I do not claim to entirely understand what I read however.) My immediate question however is how current are the instructions? There is a caveat immediately following the IPF Firewall Section title: This section is work in progress. The contents might not be accurate at all times. If it is accurate and should resolve my FTP problems, I'll simply re-read it until I get it right. Any other hints are also appreciated. This would probably fall under your other hints category. Your firewall should be allowing extant connections to continue --- IOW, showing stateful behavior. Some FTP data connections use high-numbered ports, and it sounds as if these are being blocked by your firewall. YMMV. Note that setting FTP_PASSIVE_MODE in your environment might be worth a shot. I am sorry that I'm not an IPF user and can't give more detailed help. Good luck with your issue. Thanks for your suggestions. Do all other firewalls share the same, or similar problems, with FTP data connections? Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Inconsistency Running IPF Against FTPs
I'm running FreeBSD RELEASE 5.4 and recently installed IPF Firewall. I rarely download files using FTP but have little choice using portupgrade. Now, during an upgrade, I often see the error message, No route to host... while connecting with an FTP site. If I disable the IPF/IPNAT rules the problem no longer exists. I've followed installation instructions in the Handbook paying particular attention to the section on IPNAT rules. (I do not claim to entirely understand what I read however.) My immediate question however is how current are the instructions? There is a caveat immediately following the IPF Firewall Section title: This section is work in progress. The contents might not be accurate at all times. If it is accurate and should resolve my FTP problems, I'll simply re-read it until I get it right. Any other hints are also appreciated. Thnx, Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GNOME Upgrade on a non-GNOME Machine
Kan Cai wrote: Yes. I did it a few days as /usr/ports/UPDATING suggests. It worked but it took too much time (1.5 days). This is because a lot packages depend on glib and gtk, so they have to be upgraded as well. I am just wondering if there is any way to accerlerate the process. cheers, --ken On 11/11/05, *Robert H. Perry* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I have a box which needs to upgrade gconf, glib, gnomevfs, and gtk based on the latest CVSup. Just want to confirm that I should still run the gnome_upgrade.sh even though GNOME itself is not installed. Thnx, Bob Perry ___ freebsd-questions@freebsd.org mailto:freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] That's what I wanted to hear. Thanks for your response. Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GNOME Upgrade on a non-GNOME Machine
I have a box which needs to upgrade gconf, glib, gnomevfs, and gtk based on the latest CVSup. Just want to confirm that I should still run the gnome_upgrade.sh even though GNOME itself is not installed. Thnx, Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading the kernel
Ryan Thompson wrote: Robert H. Perry wrote to FreeBSD-Questions: I'm upgrading from 4.7 RELEASE to 4.8 RELEASE soon. My understanding is that once you have built the world with buildworld, it's time to build and install the new kernel. In your scenario, yes, you'll definitely want to build a new kernel. In fact, I hope you elected to go with the security branch (RELENG_4_8), so that you get the 13 or so security related fixes that have been applied since 4.8 was released. Hadn't intended to, but now I'll have to consider it. This is my first upgrade and I was sticking with the basics. My current kernel is customized with a sound card device and nothing else. That's fine; you can continue to use your kernel config. (/usr/src/sys/i386/conf/WHATEVERYOUCALLEDYOURKERNELCONFIG) The FreeBSD Handbook indicates that the safest way to do this is to build and install a kernel based on GENERIC. After booting from GENERIC and verifying that your system works you can then customize your kernel. Well, you can if you want, but you won't have any issues from 4.7 - 4.8. I'd just go with your custom kernel config. Can I use the commands, # make buildkernel and # make installkernel, or are #make buildkernel KERNCONF=GENERIC and # make installkernel KERNCONF=GENERIC the correct commands? Have you specified KERNCONF in /etc/make.conf? No. If not, then it defaults to GENERIC. In your case, though, again, you shouldn't have any problems building from your custom conf. Just to clarify then, is the following OK: # cd /usr/src # make buildkernel KERNCONF=CUSTOM # make installkernel KERNCONF=CUSTOM CUSTOM is the name of my kernel config file. - Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Resolved: How to Handle Stale Dependencies in pkgdb -F
Lee Harr wrote: Is docbook-3.0_2 still registered as installed on your system? I think that is the one it is looking for. It is possible that when upgrading one of the others, that one was removed inadvertently. No, it is not registered as installed. As a matter of fact, none of the docbooks mentioned are installed except dockbook-xsl-1.62.3. In addition, the sgmlformat port is not installed either. I always understood that stale dependencies indicated that a change was necessary. In this situation, the 6 dependencies in question, including the port itself, weren't even registered or installed yet. I just feel that something is missing here. However, I think I'm ready to move on to the next step which is how to respond to the prompt: New dependency? (? to help) : If you hit ?, you'll see: [Enter] to skip, [Ctrl] + [D] to delete, [.][Enter] to abort, [Tab] to complete. I looked at the R-deps listed with the port description and they also correspond to the 6 shown above. As a result, I feel confident that they should be registerd and installed with the port and not the one pkgdb suggests, dockbook-xsl-1.62.3. I assume that I can delete dockbook-xsl-1.62.3, but is that what [Ctrl]+[D] will accomplish? In other words, does new dependency refer to the dependent that it sees as the closest match, dockbook-xsl-1.62.3, or the one that is recorded by the port, docbook-3.1_2? Which would I be deleting? Not sure. Good question though :o) I think there are 2 possibilities: - delete the dependency on docbook-3.1_2 (not the package itself) - delete the entire entry for sgmlformat I am pretty sure that nothing you do at that prompt will affect docbook-xsl in any way. (other than to create a dependency on it) My sense is that it would delete the dependency. In other words, you would be saying sgmlformat no longer depends on docbook-3.1_2 and there is no dependency to replace it In your case, where none of these things are in your package database, I think you have to decide if these are packages you require, and if so, start rebuilding and reinstalling them to recreate their entries. Otherwise, you could pkg_deinstall the one that is giving you problems and move on. I just started using portupgrade myself (after a couple of years of doing these things by hand *erk*) so maybe someone else will chime in and let us know if we are on the right track. Lee, I think you were on the right track from the beginning. The program found sgmlformat-1.7_2 but couldn't locate the dependents it was pointing to so it suggested it's own, dockbook-xsl-1.62.3. Should have focused on the docbook ports at that point. I simply couldn't deal with the idea that installing the docbook dependents would help when the main port, sgmlformat-1.7_2, hadn't been installed yet. Furthermore, I was simply too focused on resolving the issue by using the New dependency prompt. I installed the docbook ports (ran docbook-1.2_1 and the rest followed as deps), followed by pkgdb -F, and everything was OK. Thanks again for your help. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to Handle Stale Dependencies in pkgdb -F
Lee Harr wrote: pkg_info -ro sgmlformat-1.7_2, I get the following: Information for sgmlformat-1.7_2: Depends on: Dependency: xmlcatmgr-1.1 Dependency: iso8879-1986_2 Dependency: jade-1.2.1_5 Dependency: linuxdoc-1.1_1 Dependency: docbook-4.1_2 Dependency: docbook-4.0_2 Dependency: docbook-3.1_2 This is from the dockbook-310 port. The _2 is the port revision. Dependency: docbook-3.0_2 Dependency: docbook-241_2 Dependency: docbook-1.2_1 Origin: textproc/sgmlformat Or, since docbook already depends on all of those other docbook components, maybe you can just point the dependency at the docbook package Do you mean that I can answer the New dependency? prompt with Ctrl-Del? Well... I am not using docbook, so I am not exactly sure. It looks to me like the docbook port may be a meta port to pull in all of those docbook versions. I am not sure if you have that one installed, or if you just have all of the pieces. Is docbook-3.0_2 still registered as installed on your system? I think that is the one it is looking for. It is possible that when upgrading one of the others, that one was removed inadvertently. No, it is not registered as installed. As a matter of fact, none of the docbooks mentioned are installed except dockbook-xsl-1.62.3. In addition, the sgmlformat port is not installed either. I see now that a major part of the problem was that I never understood what was happening when I ran pkgdb -F. And it wasn't until I read your original note a second time that things became clearer. You wrote: The dependency is recorded as docbook-3.1_2 and it does not see that package, so it is suggesting the package it believes is the closest match. (dockbook-xsl-1.62.3) I always understood that stale dependencies indicated that a change was necessary. In this situation, the 6 dependencies in question, including the port itself, weren't even registered or installed yet. I just feel that something is missing here. However, I think I'm ready to move on to the next step which is how to respond to the prompt: New dependency? (? to help) : If you hit ?, you'll see: [Enter] to skip, [Ctrl] + [D] to delete, [.][Enter] to abort, [Tab] to complete. I looked at the R-deps listed with the port description and they also correspond to the 6 shown above. As a result, I feel confident that they should be registerd and installed with the port and not the one pkgdb suggests, dockbook-xsl-1.62.3. I assume that I can delete dockbook-xsl-1.62.3, but is that what [Ctrl]+[D] will accomplish? In other words, does new dependency refer to the dependent that it sees as the closest match, dockbook-xsl-1.62.3, or the one that is recorded by the port, docbook-3.1_2? Which would I be deleting? Thanks again. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to Handle Stale Dependencies in pkgdb -F
Hi, Just ran my weekly cvsup program followed by portsbd -Uu. Tried running portsversion -l and received a message indicating that I should run pkgdb -F to deal with a stale dependency. Note following: Stale dependency: sgmlformat-1.7_2 - docbook-3.1_2 (textproc/docbook-310): docbook-xsl-1.62.3 (score:43%) ? ([y]es/[n]o/[a]ll) My understanding here is that I'm to choose between the dependency the port has recorded, docbook-3.1_2, or the one installed, docbook-xsl-1.62.3. I took a look at the sgmlformat-1.7_2 port and found the following: R-deps: docbook-1.2_1 docbook-241_2 docbook-3.0_2 docbook-3.1_2 docbook-4.0_2 do cbook-4.1_2 iso8879-1986_2 jade-1.2.1_5 linuxdoc-1.1_1 xmlcatmgr-1.1 I went back to the prompt in the pkgdb program and indicated no. This was followed by: New dependency? (? to help): Wasn't sure how to respond, so I aborted the program and ran pkgdb -Fa which didn't fix the dependencies either. It did, however repeat the stale dependency prompt for all 6 of the docbook dependencies shown above. Can anyone help me understand what the program is looking for at the new dependency prompt? I was about to respond with a delete command but wasnt' sure what I would be deleting? I did backup /var/db/pkg. Thank you. Bob Perry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to Handle Stale Dependencies in pkgdb -F
Lee Harr wrote: Just ran my weekly cvsup program followed by portsbd -Uu. Tried running portsversion -l and received a message indicating that I should run pkgdb -F to deal with a stale dependency. Note following: Stale dependency: sgmlformat-1.7_2 - docbook-3.1_2 (textproc/docbook-310): docbook-xsl-1.62.3 (score:43%) ? ([y]es/[n]o/[a]ll) My understanding here is that I'm to choose between the dependency the port has recorded, docbook-3.1_2, or the one installed, docbook-xsl-1.62.3. Not exactly. The dependency is recorded as docbook-3.1_2 and it does not see that package, so it is suggesting the package it believes is the closest match. (note however that it only scores docbook-xsl at 43%) I took a look at the sgmlformat-1.7_2 port and found the following: R-deps: docbook-1.2_1 docbook-241_2 docbook-3.0_2 docbook-3.1_2 docbook-4.0_2 do cbook-4.1_2 iso8879-1986_2 jade-1.2.1_5 linuxdoc-1.1_1 xmlcatmgr-1.1 Seems strange that it would depend on all of those different docbook versions. That may be part of the problem... did you uninstall any of those (or maybe portupgrade did it for you?) Looking at the docbook port, it depends on dockbook-241,300,310,400, and 410 I went back to the prompt in the pkgdb program and indicated no. This was followed by: Good idea, given the low score. New dependency? (? to help): Wasn't sure how to respond, so I aborted the program and ran pkgdb -Fa which didn't fix the dependencies either. It did, however repeat the stale dependency prompt for all 6 of the docbook dependencies shown above. Can anyone help me understand what the program is looking for at the new dependency prompt? I was about to respond with a delete command but wasnt' sure what I would be deleting? I did backup /var/db/pkg. I think if it were me, I would check to see if the docbook-310 port were still installed correctly, and if not, install it and then try pkgdb -F again. Not sure I understanad the need to examine docbook-310. When I run pkg_info -ro sgmlformat-1.7_2, I get the following: Information for sgmlformat-1.7_2: Depends on: Dependency: xmlcatmgr-1.1 Dependency: iso8879-1986_2 Dependency: jade-1.2.1_5 Dependency: linuxdoc-1.1_1 Dependency: docbook-4.1_2 Dependency: docbook-4.0_2 Dependency: docbook-3.1_2 Dependency: docbook-3.0_2 Dependency: docbook-241_2 Dependency: docbook-1.2_1 Origin: textproc/sgmlformat Or, since docbook already depends on all of those other docbook components, maybe you can just point the dependency at the docbook package Do you mean that I can answer the New dependency? prompt with Ctrl-Del? Anyhow. I am no expert :o) Hope this helps. _ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail ___ [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]
RELENG_4_8_0_RELEASE vs RELENG_4_8
I'm upgrading from 4.7 RELEASE and intended to build and install 4.8 RELEASE. It was recommended that I consider RELENG_4_8 because it contained some 13 security fixes. I came across a CVS website indicating that the code was for security advisories and other seriously critical fixes. Does this mean that RELENG_4_8 does not have all of the code as RELEASE 4.8? Is it any more or less stable? Thank you. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_4_8_0_RELEASE vs RELENG_4_8
Jeremy Faulkner wrote: On Sun, Oct 26, 2003 at 11:52:11AM -0500, Robert H. Perry wrote: I'm upgrading from 4.7 RELEASE and intended to build and install 4.8 RELEASE. It was recommended that I consider RELENG_4_8 because it contained some 13 security fixes. I came across a CVS website indicating that the code was for security advisories and other seriously critical fixes. Does this mean that RELENG_4_8 does not have all of the code as RELEASE 4.8? Is it any more or less stable? Thank you. Bob RELENG_4_8 contains the same code as RELENG_4_8_0_RELEASE with the necessary changes to fix the security bugs that were discovered after 4.8 was Released. Thanks much for taking the time to respond Jeremy. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrading the kernel
I'm upgrading from 4.7 RELEASE to 4.8 RELEASE soon. My understanding is that once you have built the world with buildworld, it's time to build and install the new kernel. My current kernel is customized with a sound card device and nothing else. The FreeBSD Handbook indicates that the safest way to do this is to build and install a kernel based on GENERIC. After booting from GENERIC and verifying that your system works you can then customize your kernel. Can I use the commands, # make buildkernel and # make installkernel, or are #make buildkernel KERNCONF=GENERIC and # make installkernel KERNCONF=GENERIC the correct commands? Thank you, Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading the kernel
Ryan Thompson wrote: Robert H. Perry wrote to Ryan Thompson: In your scenario, yes, you'll definitely want to build a new kernel. In fact, I hope you elected to go with the security branch (RELENG_4_8), so that you get the 13 or so security related fixes that have been applied since 4.8 was released. Hadn't intended to, but now I'll have to consider it. This is my first upgrade and I was sticking with the basics. Yep. If you're upgrading from source anyway, upgrading to RELENG_4_8 is no harder than -RELEASE. If not, then it defaults to GENERIC. In your case, though, again, you shouldn't have any problems building from your custom conf. Just to clarify then, is the following OK: # cd /usr/src # make buildkernel KERNCONF=CUSTOM # make installkernel KERNCONF=CUSTOM CUSTOM is the name of my kernel config file. Yes. For the full how-to, follow the instructions in: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html - Ryan Ryan, Thanks for your time and assistance. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade to 4.8 RELEASE
Hello, I'm making plans to upgrade from 4.7 RELEASE to 4.8 RELEASE. My previous attempt was a binary upgrade from 4.5 to 4.7 which did not go very well. I eventually purchased the 4.7 CD. The FreeBSD Handbook stresses backing up the system and implies that /dump/ is a better backup program. Chapter 12.9.8.1 of the handbook recommends having a copy of the boot and fixit floppies available and making sure they have all your devices, otherwise you'll need to prepare two bootable custom floppies that contain /fdisk, disklabel, newfs, mount, /and your backup program. It goes on to say that these programs must be statically linked. I understand hard and soft links but I'm not familiar with static links. The handbook also provides a script for creatinng a bootable floppy. A static link is a firm link:) Seriously, static linking has nothing to do with filesystem links. A statically linked program just uses no shared libraries. AFAICT the programs in /stand (and /bin and /sbin) are statically linked (note that those in /stand are also a crunchbox, that is, a single monolithic program which runs differently depending on the name it was run as). You really have to mess with this only if you are going to write your own program to run from a boot floppy. You can use file(1) if you want to see if a program is staticlally linked: $ file /usr/bin/find /usr/bin/find: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 4.8, dynamically linked (uses shared libs), stripped $ file /stand/find /stand/find: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 4.8, statically linked, stripped Thanks for the education Sergey. This makes a lot more sense now. I never prepared a boot floppy when I initially installed 4.7 so I thought the handbook was suggesting a necessary alternative (?). If it's not absolutely necessary, I'll skip it. Any suggestions relative to the upgrade process is also appreciated. In fact, a source update isn't as dangerous as you expect. That's what I've heard and I suspect you're right. However, AFAICT, past failures have usually come as a result of not following the handbook. Maybe this floppy is a bit of overkill though. Thanks again. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrade to 4.8 RELEASE
Hello, I'm making plans to upgrade from 4.7 RELEASE to 4.8 RELEASE. My previous attempt was a binary upgrade from 4.5 to 4.7 which did not go very well. I eventually purchased the 4.7 CD. The FreeBSD Handbook stresses backing up the system and implies that /dump/ is a better backup program. Chapter 12.9.8.1 of the handbook recommends having a copy of the boot and fixit floppies available and making sure they have all your devices, otherwise you'll need to prepare two bootable custom floppies that contain /fdisk, disklabel, newfs, mount, /and your backup program. It goes on to say that these programs must be statically linked. I understand hard and soft links but I'm not familiar with static links. The handbook also provides a script for creatinng a bootable floppy. Can someone help me understand static link? Secondly, can I assume that the script must be reviewed for likely modifications? I'm just learning shell programming and if significant modifications are necessary, I may end up purchasing a CD for 4.8. Any suggestions relative to the upgrade process is also appreciated. Thanks, Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
