Re: Is FTP install broken?
On 17 Apr 2007 at 17:18, Kris Kennaway boldly uttered: > On Tue, Apr 17, 2007 at 01:45:44PM -0700, Philip J. Koenig wrote: > > Re: Kris's assertion, I guess I could have lived with that if it > > weren't for the fact that the installer doesn't give you any clue of > > this. > > > > Thought I was going to avoid the time to download and burn a couple > > of CD's, and now it's sucked up way more of my time than making those > > CD's ever would have... > > > > Thanks for the answers/input. > > No special casing happens for the snapshot builds, i.e. sysinstall is > not specially modified to disable the FTP install option. > > It should be mentioned in the documentation; but for all I know it > already is :) > > Kris Well I looked at all the docs I could find and nothing stood out. (BTW, there are still some other user interface errors in sysinstall, ie things that lead to unexpected results, but I can't remember specifics now.) -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is FTP install broken?
On 17 Apr 2007 at 11:34, Sean Murphy boldly uttered: > Kris Kennaway wrote: > On Tue, Apr 17, 2007 at 04:51:19AM -0700, Philip J. Koenig wrote: > > I'm trying to install the 200703 snapshot of 6.2-STABLE, and no > matter what server I select, no matter what variant I try of various > length paths specified in a custom URL to a server that I *know* has > the files (ftp.freebsd.org), I get the following message: > > Warning: Can't find the '6.2-STABLE-200703' distribution on this > FTP server. You may need to visit a different server for > the release you are trying to fetch or go to the Options > menu and to (sic) set the release name to explicitly match what's > available on ftp.freebsd.org (or set to "any"). > > Would you like to select another FTP server? > > > I am booting from the 200703 snapshot i386 bootdisk-only ISO image. > > > I don't think FTP installs are possible for snapshots, i.e. only the > ISO images are provided. > During the choice for the ftp server selection there are two servers > close to the top of the list that are named "snapshot.se.freebsd.org" > and "snapshot.jp.freebsd.org" you might want to try those. Tried both before I posted my message here. I got the "can't find" message on both of them. Re: Kris's assertion, I guess I could have lived with that if it weren't for the fact that the installer doesn't give you any clue of this. Thought I was going to avoid the time to download and burn a couple of CD's, and now it's sucked up way more of my time than making those CD's ever would have... Thanks for the answers/input. -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Is FTP install broken?
For probably the 2nd time in history for me, I am trying an FTP install. It's been a good while since I've done a FBSD install, and I assumed things had gotten more polished since 4.x.. I'm trying to install the 200703 snapshot of 6.2-STABLE, and no matter what server I select, no matter what variant I try of various length paths specified in a custom URL to a server that I *know* has the files (ftp.freebsd.org), I get the following message: Warning: Can't find the '6.2-STABLE-200703' distribution on this FTP server. You may need to visit a different server for the release you are trying to fetch or go to the Options menu and to (sic) set the release name to explicitly match what's available on ftp.freebsd.org (or set to "any"). Would you like to select another FTP server? I am booting from the 200703 snapshot i386 bootdisk-only ISO image. TIA, Phil -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: New FreeBSD logo
Sorry to be jumping into this late. On 15 May 2006 at 8:57, "Ted Mittelstaedt" <[EMAIL PROTECTED]> wrote: > No, you get to vote on the selection of various bits of code changes. That sounds more realistic to me than assuming committers are also the sole FreeBSD "esthetic committee" too. > But > no amount of your voting is going to instantly change the recognized logo > of FreeBSD from Beastie to the sex-toy. Ranting on questions has far more > ability to make or break use of the sex-toy logo by the FreeBSD userbase > than voting on current. I must admit that logo seemed a bit strange to me when I saw it on the website. Sorta cold and a bit too abstract for my taste. It reminds me of what Mozilla did with their dragon - removed it from the browser's splash-screen because some minority of people thought it was "demonic" or "evil" or something. So sad. I think people need to get over themselves and personally I think the "beastie" is nicely irreverent and has a palpable "personality" one can relate to, especially since you can be sure that very few "gargantuan publicly-held companies" would ever get away with using something similiar. I wonder if anyone has heard Kirk McKusick's input on this.. then again, perhaps he's a bit biased? :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh keepalives
On 9 Jul 2003 at 23:03, Paulius Bulotas boldly uttered: > On 03 07 09, Philip J. Koenig wrote: > > > Apply this patch to OpenSSH, if you are running FreeBSD: > > > http://www.sc.isc.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html > > > > Considering that the author of the patch greatly discourages usage of > > the older OpenSSH code, and considering that my recently updated 4.8- > > STABLE box is still using OpenSSH 3.5p1 rather than the latest 3.6p1 > > mentioned in the patch, I'm a little disinclined to do this patch > > because I'll have to re-patch it every time I build/install world. > > > > If there's any possibility this patch will make it into the > > mainstream distribution I'll just wait for that. Will wait and see, > > but thanks very much for the tip! > > I really don't know that ;) But it worked without a problem with 3.4 and > 3.5 versions for me, the only thing could be - you will have to apply > some peaces of code manually, because of any differences of OpenSSH in > base FreeBSD vs stock OpenSSH portable. But still, IMO that's the only > option with dynamic ipfw rules ;) Not sure what you're saying there - if I have a vanilla install of OpenSSH as provided in the base 4.8-STABLE system, am _not_ using ipfw, will I have to do additional work in addition to running the patch against the existing files? -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh keepalives
On 9 Jul 2003 at 20:24, Paulius Bulotas boldly uttered: > Hi, > > a bit late answer, but I'm not able to keep up with my email traffic ;) > > Apply this patch to OpenSSH, if you are running FreeBSD: > http://www.sc.isc.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html > > and use Heartbeat option with something less then dynamic rules life ;) > > Regards, > Paulius Aha, now this is a very interesting response! Considering that the author of the patch greatly discourages usage of the older OpenSSH code, and considering that my recently updated 4.8- STABLE box is still using OpenSSH 3.5p1 rather than the latest 3.6p1 mentioned in the patch, I'm a little disinclined to do this patch because I'll have to re-patch it every time I build/install world. If there's any possibility this patch will make it into the mainstream distribution I'll just wait for that. Will wait and see, but thanks very much for the tip! > On 03 07 01, Philip J. Koenig wrote: > > > > I'm having a problem with premature termination of ssh sessions after > > an idle period of a few minutes, getting a "connection reset by peer" > > message. I presume this is due to intermediate stateful firewalls > > closing the connection when no traffic passes for a period of time. > > > > In the past I've addressed this issue when I have control of the > > destination host, by including the following parameters in > > sshd_config: > > > > ClientAliveInterval 30 > > ClientAliveCountMax 4 > > > > > > However in this case I don't have control over the destination. It's > > a self-contained network device. > > > > man 5 ssh_conf says that "KeepAlive" is the default with ssh. Is > > there any other tactic I can use to keep these connections from > > closing after a few minutes of inactivity? > > > > Currently on FreeBSD 4.8-stable with OpenSSH_3.5p1 -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh keepalives
On 8 Jul 2003 at 11:10, Viktor Lazlo boldly uttered: > On Thu, 3 Jul 2003, Philip J. Koenig wrote: > > > One of those firewalls is quite flexible about protocol state > > timeouts, I can set this on a service-by-service basis. (ie I could > > increase it for SSH and no other service) > > > > Unfortunately the firewall on the other side isn't so accommodating. > > It has a single timeout setting that affects all traffic that > > traverses the firewall, and I'd rather not increase that too high. > > If there is no option then run a low-bandwidth application in the > background to keep the connection alive, or script something to generate > some activity at frequent enough intervals to do so. Well that goes without saying, but the idea was whether the protocol itself contained a "keepalive" function. It's still a pain to have to go through that just so a connection will not die after 5 mins. I would think this is a common enough issue to justify an enhancement request to the open-ssh people. -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is the mailing list search system broken?
> Date: Fri, 04 Jul 2003 11:16:10 -0400 > From: Bill Moran <[EMAIL PROTECTED]> > > stan wrote: > > I can't seem to get any results, no matter what I search for. > > > > Is this broken? > > It certainly appears so ... your email is about the fifth complaining > of this in the last 48 hours. > > A few temporary workarounds are: > 1) Go to the mailman home page for the particular list you want to > search and use that local search. For example: > http://lists.freebsd.org/pipermail/freebsd-questions/ > 2) Use the advanced search on a search engine (such as google) Long ago I stopped bothering much with the mailing list search function on the freebsd.org page because it was never good enough to find what I wanted, and the list archives were not readable by thread. (finally when they switched to Mailman, you can read archives by thread) Same goes for some of the most common list archive sites - ie geocrawler - no threaded reading, and no search at all! So personally I got in the habit of using groups.google.com when I want to do a search of the FreeBSD lists. Their search facility is superior, I limit the newsgroups to "*freebsd*", and it will return results from the usenet groups which are gatewayed from the mailing lists (a small subset admittedly, but questions@ is one of them), and also the usenet groups which are separate from the mailing lists. -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh keepalives
> Date: Wed, 2 Jul 2003 15:04:51 +0200 > From: Christian Stigen Larsen <[EMAIL PROTECTED]> > > Quoting Steve Coile ([EMAIL PROTECTED]): > | On Tue, 1 Jul 2003, Philip J. Koenig wrote: > | > I'm having a problem with premature termination of ssh sessions [...] > | > | Is this a common problem with firewalls? We suffer from this problem > | here, also, and I've thought it must be a misconfiguration with the > | firewall or elsewhere in the netwrok. But since you mentioend it, > | I'm rethinking my assessment. > > As Michal F. Hanula, it might be due to the firewall dropping idle TCP > connections. I'm quite sure this is the case, and I know this is a characteristic of the stateful firewalls on both sides. (which I administer) One of those firewalls is quite flexible about protocol state timeouts, I can set this on a service-by-service basis. (ie I could increase it for SSH and no other service) Unfortunately the firewall on the other side isn't so accommodating. It has a single timeout setting that affects all traffic that traverses the firewall, and I'd rather not increase that too high. > At work I use PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/) for > my outbound ssh sessions, and it supports a useful option: > > "Sending of null packets to keep session active" > > Settings this to, say, 60 seconds effectively prevents my sessions from being > cut off. Unfortunately I haven't found any similar feature in the OpenSSH > clients. Do they support such a feature? I've used that feature with PuTTY and it's handy. As far as I can tell there is no equivalent in OpenSSH. The "KeepAlive" feature appears to be used primarily to detect if a connection has died due to a broken link. (probably the thing that allows the client to report "connection reset by peer" right away without sitting there for a hour before figuring it out) -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ssh keepalives
I'm having a problem with premature termination of ssh sessions after an idle period of a few minutes, getting a "connection reset by peer" message. I presume this is due to intermediate stateful firewalls closing the connection when no traffic passes for a period of time. In the past I've addressed this issue when I have control of the destination host, by including the following parameters in sshd_config: ClientAliveInterval 30 ClientAliveCountMax 4 However in this case I don't have control over the destination. It's a self-contained network device. man 5 ssh_conf says that "KeepAlive" is the default with ssh. Is there any other tactic I can use to keep these connections from closing after a few minutes of inactivity? Currently on FreeBSD 4.8-stable with OpenSSH_3.5p1 -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gd2 portupgrade problem
When I try to portupgrade gdchart, it wants to install gd2. (current version of gd installed is 1.8.4_6) When portupgrade tries to install gd2, it fails with the following messages: /usr/X11R6/lib/libXpm.so.4: undefined reference to 'XDefaultScreen' /usr/X11R6/lib/libXpm.so.4: undefined reference to 'XCreateImage' (..and many other similiar messages.) I assume this is because I don't have X installed on this box. However in the makefile for gd2, it seems to try to account for this, with the following section; .ifndef WITHOUT_XPM #Temporary hack, until X-less XPM building is added to USE_XPM: .ifndef WITHOUT_X11 USE_XPM= yes .else LIB_DEPENDS+= Xpm:$[PORTSDIR}/graphics/xpm .endif .else MAKE_ARGS+= -DWITHOUT_XPM .endif I have "WITHOUT_X11= yes" defined in my make.conf file. Is there something else I need to do so this will build without X installed? Thx.. -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Traceroute with ASNs?
On 25 Jan 2003 at 23:50, Ugen boldly uttered: > I happen to be an author of ASN feature (and the latest version of ) > LFT - TCP based traceroute. You can download it at : > http://www.mainnerve.com/lft > > It is a plain old C application, though it does require libpcap (available > in any FreeBSD installation). > --Ugen Sounds great - maybe you can help me with an install problem though. I get the following when doing "make install" after copying the makefile.bsd to Makefile: install -s -o root -m 4755 lft /usr/local/bin/lft install -o root -m 444 /usr/share/man/man8/lft.8 usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] -m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/local/src/LFT/lft-2.0. > Philip J. Koenig wrote: > > >On 25 Jan 2003 at 22:36, Dan Nelson boldly uttered: > > > > > > > >>In the last episode (Jan 25), Philip J. Koenig said: > >> > >> > >>>On 25 Jan 2003 at 20:45, Dan Nelson boldly uttered: > >>> > >>> > >>> > >>>>Try prtraceroute, from ports/net/irrtoolset. > >>>> > >>>> > >>>OK sounds good, but are these X programs? I started to install it > >>>and when it started to retrieve TK (/usr/ports/x11-toolkits/tk83) I > >>>killed it. It also apparently wants XFree86-libraries-4.2.1_5. > >>> > >>>I don't know if I mentioned that I want something that is character- > >>>based. I don't have X on this box and I don't want another situation > >>>where a port ends up installing all that baggage.. > >>> > >>> > >>Some of the tools are graphical, but prtraceroute is commandline. > >> > >> > > > > > >So is there any way to compile just prtraceroute? I don't see any > >obvious switches in the Makefile. > > > >It does say "GNU_CONFIGURE= Yes", does this mean I can type > >"configure" to override defaults after fetching the distfiles? > > > >Thx, > > > >Phil -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Traceroute with ASNs?
On 25 Jan 2003 at 22:36, Dan Nelson boldly uttered: > In the last episode (Jan 25), Philip J. Koenig said: > > On 25 Jan 2003 at 20:45, Dan Nelson boldly uttered: > > > > > Try prtraceroute, from ports/net/irrtoolset. > > > > > > OK sounds good, but are these X programs? I started to install it > > and when it started to retrieve TK (/usr/ports/x11-toolkits/tk83) I > > killed it. It also apparently wants XFree86-libraries-4.2.1_5. > > > > I don't know if I mentioned that I want something that is character- > > based. I don't have X on this box and I don't want another situation > > where a port ends up installing all that baggage.. > > Some of the tools are graphical, but prtraceroute is commandline. So is there any way to compile just prtraceroute? I don't see any obvious switches in the Makefile. It does say "GNU_CONFIGURE= Yes", does this mean I can type "configure" to override defaults after fetching the distfiles? Thx, Phil -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Traceroute with ASNs?
On 25 Jan 2003 at 20:45, Dan Nelson boldly uttered: > Try prtraceroute, from ports/net/irrtoolset. OK sounds good, but are these X programs? I started to install it and when it started to retrieve TK (/usr/ports/x11-toolkits/tk83) I killed it. It also apparently wants XFree86-libraries-4.2.1_5. I don't know if I mentioned that I want something that is character- based. I don't have X on this box and I don't want another situation where a port ends up installing all that baggage.. Thx, Phil -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Traceroute with ASNs?
Once upon a time I installed a port called "traceroute-991603" which had the ability to show ASNs of each hop. Turns out it only worked on RIPE registered ASNs. Does anyone know of another traceroute utility for FreeBSD that can do this for all ASNs? Doesn't appear to be one in ports. If necessary I can download and compile something that isn't native. TIA, Phil -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: More Portupgrade questions
On 26 Dec 2002 at 14:31, Kent Stewart boldly uttered:
> On Thursday 26 December 2002 02:21 pm, Philip J. Koenig wrote:
> > Running "make index" fills the screen with lots more error messages
> > than "portsdb -Uu".. :-)
> >
> > Mostly "..no entry for.." messages, some "..Duplicate INDEX entry:.."
> > messages.
>
> That was when "make index" was broken. If you do it today, you don't see
> that. You get a message about generating the index and that is it.
Actually that was when I ran it just before writing that email.
Just before writing this message, I re-cvsup'd ports-all. As I am
writing this, I did "make index" again. No more "no entry for"
errors, but I did get 4 "Duplicate INDEX entry" errors.
Progress. :-)
Continued below.
> > [other error msgs snipped]
> >
> > > > make_index: no entry for: /usr/ports/x11-toolkits/itk
> > > > make_index: no entry for: /usr/local
> > > > Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f
> > >
> > > Re-cvsup your ports tree and see if this still happens.
> >
> > I just cvsup'd it yesterday, this was the prerequisite to trying to
> > update portupgrade and the rest of the ports.
> >
> > FYI - if I'm not mistaken, "cvsup-without-gui-16.1f" shares the same
> > code as the "with gui" cvsup port, but with a different build option.
>
> I have without-gui installed. I log everything and there isn't any point
> to building the gui and then running it from a shell script that tees
> the output.
The only reason I mentioned that port is because it showed up in the
list of port errors.
It looks like all these duplicate errors are for ports which
reference another port but just change the build options slightly.
IE the Makefile for cvsup-without-gui has just the following 2 lines:
MASTERDIR= ${.CURDIR}/..cvsup
WITHOUT_X11=yes
This is starting to make sense now.
As a matter of fact, after removing some orphaned ports and fixing up
some dependencies, everything is looking copacetic. Now for some
actual port upgrading. Thanks for all the help folks.
--
Philip J. Koenig [EMAIL PROTECTED]
Electric Kahuna Systems -- Computers & Communications for the New Millenium
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: More Portupgrade questions
On 26 Dec 2002 at 13:39, Kent Stewart boldly uttered: > On Thursday 26 December 2002 01:32 pm, Philip J. Koenig wrote: > > When running "portsdb -uU" as recommended in the Portupgrade > > documentation I'm currently getting some errors, and not sure if I > > have to do something about them or what I should do. Couldn't find > > any suggestions in the Portsdb manpage. > > Until just recently "make index" was broken and the only choice was > using -uU. There was a ~2 day band where "make index" was really > broken. > > For some time now, the only way to get a full list of ports is to do a > "make index" from /usr/ports. You make get a duplicate port message but > it works. The -U options fills screens with messages as it encounters > ports that it can't deal with. Running "make index" fills the screen with lots more error messages than "portsdb -Uu".. :-) Mostly "..no entry for.." messages, some "..Duplicate INDEX entry:.." messages. Continued below. On 26 Dec 2002 at 21:37, Stacey Roberts boldly uttered: > portsdb -U is broken / has been broken for ages. Use the following > sequence instead: > make index > pkgdb -Fv > portsdb -u When running "pkgdb -Fv" after "make index", I now get: > /usr/ports/INDEX:1:Port info line must consist of 10 fields. [repeats 3 times] > > Skip this for now? [yes] Not sure what I should do here. "Make Index" has created a mis- formatted INDEX file? Sigh. [other error msgs snipped] > > make_index: no entry for: /usr/ports/x11-toolkits/itk > > make_index: no entry for: /usr/local > > Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f > > > > Re-cvsup your ports tree and see if this still happens. I just cvsup'd it yesterday, this was the prerequisite to trying to update portupgrade and the rest of the ports. FYI - if I'm not mistaken, "cvsup-without-gui-16.1f" shares the same code as the "with gui" cvsup port, but with a different build option. -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Upgrading the Portupgrade port
On 26 Dec 2002 at 13:21, Kent Stewart boldly uttered: > On Thursday 26 December 2002 12:59 pm, Philip J. Koenig wrote: > > On 26 Dec 2002 at 11:56, Kent Stewart boldly uttered: > > > On Thursday 26 December 2002 03:35 am, Philip J. Koenig wrote: > > > > [snip] > > > > Thanks for the tip, although I must admit I'm kinda surprised that a > > 5-month-old version of anything is considered so "ancient" as to be > > "un-upgradeable"... particularly a program designed to upgrade other > > programs.. > > The break point is around 20020907 and I can't be precise. Anything > before that can't deal with ports that have disappeared. If you have a > version before that, the easiest way is to delete portupgrade and its > dependancies and reinstall it. Everything from ruby-1.6.8 to > portupgrade is new so you don't lose any time but you do get a clean > install on the first try. > > Running portsdb -F produces signal errors when you have a port installed > that is no longer in the port tree. I don't remember if -fu worked at > that point or not. Yeah I have noticed some issue with ports that have gone away also. I think it's part of what I was seeing in my other post about the errors I see when running Portsdb -uU. BTW, I assume you meant "pkgdb -F" rather than "portsdb -F". -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
More Portupgrade questions
When running "portsdb -uU" as recommended in the Portupgrade documentation I'm currently getting some errors, and not sure if I have to do something about them or what I should do. Couldn't find any suggestions in the Portsdb manpage. I recently removed all the Ruby stuff and portupgrade and upgraded to the latest version, but I got about the same errors with a version from July 02. Examples: "/usr/ports/Mk/bsd.ruby.mk", line 135: "Ruby 1.7 is obsolete; set RUBY_VER to 1.8 instead." *** Error code 1: malformed entry: *** Error code 1 'all' not remade because of errors.: guile-gnome-0.20_5:"" non-existent -- dependency list incomplete l-1.1.3:/usr/ports/www/gtkhtml: malformed entry: l- 1.1.3:/usr/ports/www/gtkhtml: /usr/X11R6/share/gnome/ .keep_me:/usr/ports/misc/gnomehier make_index: no entry for: /usr/ports/x11-toolkits/itk make_index: no entry for: /usr/local Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Upgrading the Portupgrade port
On 26 Dec 2002 at 11:56, Kent Stewart boldly uttered: > On Thursday 26 December 2002 03:35 am, Philip J. Koenig wrote: [snip] > > Have things improved in the meantime? Is there an easy way to > > upgrade Portupgrade without removing everything and re-installing? I > > currently have the 20020706 version installed. > > You version is so far back that the upgrade is hopeless. You have things > that no long exist as parts of portupgrade and your version can't deal > with that. It is easier if you delete the portupgrade, ruby-*, > pkg_tartup, and what ever is left and reinstall it. > > FWIW, it works flawlessly now. I just recently upgraded to the 1216 > version by using "portupgrade -rpuf ruby". Thanks for the tip, although I must admit I'm kinda surprised that a 5-month-old version of anything is considered so "ancient" as to be "un-upgradeable"... particularly a program designed to upgrade other programs.. But I'm not really complaining, portupgrade is a boon to all humanity. :-) -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Upgrading the Portupgrade port
Once upon a time it was said that one of the cool things about
Portupgrade, was that you could use it to upgrade itself.
("portupgrade -{|r|R} portupgrade")
But this never worked for me - caused all sorts of weird Ruby and
dependency problems, orphaned Ruby shim thingies, etc.
So I got into the habit of completely removing Portupgrade and
everything associated with it including all the Ruby stuff, and
reinstalling them all, in order to upgrade. (it was the only way that
worked for me)
Have things improved in the meantime? Is there an easy way to
upgrade Portupgrade without removing everything and re-installing? I
currently have the 20020706 version installed.
TIA,
Phil
--
Philip J. Koenig
[EMAIL PROTECTED]
Electric Kahuna Systems -- Computers & Communications for the New
Millenium
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Digest oddities (was Re: Ping to broadcast ok from subnet, not ok otherwise)
On 9 Oct 2002 at 13:26, questions-digest boldly uttered: > Date: Wed, 9 Oct 2002 10:58:19 -0400 (EDT) > From: "TheGlenMann" <[EMAIL PROTECTED]> > Subject: Ping to broadcast ok from subnet, not ok otherwise > > Hi all- > > (Is this list working right? - I'm getting lots of wierd stuff in the > digests...but anyway...) > The following string that Roman Neuhauser <[EMAIL PROTECTED]> is using as a signature is confusing my mailreader into thinking the digest has attachments whenever he posts a message, and it truncates the digest in the normal reader at that point too: > - -- > begin 666 nonexistent.vbs > FreeBSD 4.7-RC > 7:48PM up 22 days, 3:03, 18 users, load averages: 0.43, 0.26, 0.15 > end > -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
"amnesiac" disklabel on RAID logical drive
mounts > # of network filesystems before modifying this file. > # > # DeviceMountpoint FStype Options DumpPass# > /dev/amrd0s2b noneswapsw 0 0 > /dev/amrd0s2a / ufs rw 1 1 > /dev/amrd0s2f /objufs rw 2 2 > /dev/amrd0s2g /usrufs rw 2 2 > /dev/amrd0s2e /varufs rw 2 2 > /dev/acd0c /cdrom cd9660 ro,noauto 0 0 > proc/proc procfs rw 0 0 -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: When is FreeBSD going to work properly with KVM switches?
On 17 Jul 2002, at 23:23, Steve Wingate boldly uttered: > There are actually more than one issue in this thread, I think. > One relates to low-end KVM's that don't have dedicated keyboard/mouse > microprocessors for EACH port on the unit. If the KVM doesn't have > dedicated processors then the KVM has to be pointed to a server as it > boots up, otherwise the server will boot but the keyboard won't be > active. I have a 4-port Belkin OmniView SE where this is the case. > The second issue relates to some ps/2 mice freaking out when you switch > KVM ports. This shows up as countless psmintr errors on the console when > you switch ports. I had this issue constantly with a Microsoft > Intellimouse w/Intellieye. I tried every trick in the archives to get > rid of it and failed. If I switched to an old IBM mouse with the lil > eraser head wheel the errors went away but I HATED the eraser head. > Several months ago I switches to a Logitech wheel mouse, with the > intellieye doohickey, and I haven't seen the errors since. I do believe that typically KVM vendors strive to support and emulate the baseline, standard keyboard and mouse behavior for the most part. Any additional features (ie Intellimouse, etc.) is really 'gravy' and subject to a particular vendor explicitly supporting it. Many KVM manufacturers will specifically say whether they do or don't support ie Intellimouse wheels (fairly common nowadays but didn't use to be), etc. I'm typing this on a nice IBM Trackpoint keyboard (with one of those eraser-heads you dislike :-), which I find very handy because I can plug my trackball into it and use either pointing device as convenient. However, IBM makes it quite clear that the PS/2 passthru port does NOT support anything but standard 2-button mouse functionality. (and indeed it doesn't, but I live with it because I appreciate the other benefits) -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: When is FreeBSD going to work properly with KVM switches?
On 17 Jul 2002, at 16:37, Michael Wells boldly uttered: > > > > I also have the problem that the KVM must be set to the machine being > booted > > > > in order for the mouse and keyboard to work properly. This is a know > problem > > > > and there was discussion on it. The problem seems to have appeared > with 4.2. > > > > I saw a fix in the freebsd-stable archives: > > > > > > > >FROM: John Baldwin, > > > >DATE: 11/20/2000 16:43:35 > > > > > > > > Basically the proposed solution was to remove the `flags 0x1' from the > > > > atkbd0 device line in the i386/conf/file > > > > > > > > This fixed the problem I was having with the Omni Cube 4-Port. I have > > > > not checked if this problem still occurs with 4.6. > > > > > > > > > > Actually, if one searches through the archives you'll find the mouse/kvm > > > issue dates back to the 3.x days. Apparently it isn't a high priority so > > > I wouldn't hold my breath for an always working fix. > > > > > > I really really really wouldn't be so quick to assume the problem is > > FreeBSD. In my experience, Belkin's are not very good KVMs, I won't > > use them any more, personally. I've had problems with them not > > correctly initializing keyboard or mouse ports with Windows as well. > > Never had a problem with FreeBSD and KVM switches, personally. > > > > If you want a good KVM, stick with either Avocent (my personal > > preference - used to be Cybex and Apex), Raritan, Rose, or one of the > > companies that OEMs the Avocent switches. (ie Compaq, HP, Dell) The > > cheapo KVMs are cheap for a reason. > > > > (Then you've got "RichardH" saying Belkin's are overpriced, LOL.. > > well I never tried D-link KVMs, maybe they're OK for a cheapo > > model :-) > > > > > I have a Belkin 4 port OmniView that works just fine with FreeBSD and > w2k. I had to add a flag to my kernel to keep things study when > switching back and forth, but other than that it's been just fine. If I'm interpreting the "fix" right, what it does is force the OS to think there's a keyboard present even if there may not be. (the flag, which is not on by default, makes FreeBSD check for a keyboard) There are 2 primary functions of a KVM from the standpoint of a computer's keyboard interface: looking like a keyboard when the PC boots and checks the keyboard interface, and maintaining state on the keyboard signals so they are restored when that particular PC is un- selected and re-selected. In summary, the whole point of a KVM is to make the connected computer see what looks like a regular, connected keyboard. If you have to do anything to the OS to get it to act as it normally does without a KVM, the KVM isn't doing its job right. -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: When is FreeBSD going to work properly with KVM switches?
> Date: 16 Jul 2002 18:07:12 -0700 > From: Steve Wingate <[EMAIL PROTECTED]> > > On Tue, 2002-07-16 at 10:33, [EMAIL PROTECTED] wrote: > > > > I also have the problem that the KVM must be set to the machine being booted > > in order for the mouse and keyboard to work properly. This is a know problem > > and there was discussion on it. The problem seems to have appeared with 4.2. > > I saw a fix in the freebsd-stable archives: > > > >Message: 4695118, > >FROM: John Baldwin, > >DATE: 11/20/2000 16:43:35 > >SUBJECT: RE: 4.2 Showstopper? Belkin KVM switch problems with FreeBSD 4.2 > > > > Basically the proposed solution was to remove the `flags 0x1' from the > > atkbd0 device line in the i386/conf/file > > > > This fixed the problem I was having with the Omni Cube 4-Port. I have > > not checked if this problem still occurs with 4.6. > > > > Actually, if one searches through the archives you'll find the mouse/kvm > issue dates back to the 3.x days. Apparently it isn't a high priority so > I wouldn't hold my breath for an always working fix. I really really really wouldn't be so quick to assume the problem is FreeBSD. In my experience, Belkin's are not very good KVMs, I won't use them any more, personally. I've had problems with them not correctly initializing keyboard or mouse ports with Windows as well. Never had a problem with FreeBSD and KVM switches, personally. If you want a good KVM, stick with either Avocent (my personal preference - used to be Cybex and Apex), Raritan, Rose, or one of the companies that OEMs the Avocent switches. (ie Compaq, HP, Dell) The cheapo KVMs are cheap for a reason. (Then you've got "RichardH" saying Belkin's are overpriced, LOL.. well I never tried D-link KVMs, maybe they're OK for a cheapo model :-) Phil -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
