Re: HEADS UP: databases/postgresql72 is dying
Ade Lovett wrote: FYI. Prior to the postgresql new-world-order in ports/, I have now tagged databases/postgresql72 (current version 7.2.5) as DEPRECATED, with it being removed from the tree on or about 1st January 2005. You are *strongly* urged to upgrade to either 7.3.x or 7.4.x Have you considered that 7.2 is the last Version that doesn't have schemas. Out there may be some / are lot of applications that depend on this behaviour. I'd vote not to remove the port. Just my personal opinion Sebastian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd 5.3 have any problem with vinum ?
Am Mittwoch, 3. November 2004 21:27 schrieb secmgr: > Just ran into this myself. I had a perfectly happy raid 5 plex under > 5.3 RC1. I upgrade to RC2, and the whole plex goes stale. I deleted > everything from the volume on down (except for the drives), and tried > to recreate the vol/plex/sd's. gvinum creates them, but they come > back (like the undead) as stale and unusable (just like they were > before). I'm finding commands documented (in help), but unimplemented > (checkparity? init?). Did you try to simply 'start' the plex? This works for initialisation of a newly created RAID5-Plex as well as for recalculating parity informations on a degraded RAID5-Plex. It's that simple (at least for me on 5-STABLE) but admittedly undocumented. -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F pgptKVpJvEOEJ.pgp Description: PGP signature
Re: freebsd 5.3 have any problem with vinum ?
Am Mittwoch, 3. November 2004 21:27 schrieb secmgr: > I hate to sound like a whiney baby, but WTF > is going on? It feels like vinum from 4.x has basicly been abandoned > (short of crashes with no workaround), and gvinum ain't near ready > for primetime. If you mean the 'dangling vnode'-problem with "vinum-classic": Try to start 'classic' vinum *after* the system has come up. Either manually or perhaps with a script in /usr/local/etc/rc.d. This works for me until now under 5-STABLE (a.k.a. RELENG_5). -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F pgpme8ARVpsD3.pgp Description: PGP signature
PCMCIA modem heating
Hi all! Don't wonna make stupid quiestions, but this is something I have to know to make reclamation if neces- sary. After 5-10 minutes of inter- net connection, when detached, my pccard modem is hot as fur- nace. I can barely take it in my hand. Is it normal beha- veour? Model is Zoltrix, has "cirrus" on the sticker. Best regards ZK ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: databases/postgresql72 is dying
On Sat, 6 Nov 2004, [ISO-8859-1] Sebastian B?ck wrote: SB> Ade Lovett wrote: SB> > FYI. Prior to the postgresql new-world-order in ports/, I have now tagged SB> > databases/postgresql72 (current version 7.2.5) as DEPRECATED, with it SB> > being removed from the tree on or about 1st January 2005. SB> > SB> > You are *strongly* urged to upgrade to either 7.3.x or 7.4.x SB> SB> Have you considered that 7.2 is the last Version that doesn't have SB> schemas. Out there may be some / are lot of applications that depend SB> on this behaviour. SB> SB> I'd vote not to remove the port. SB> SB> Just my personal opinion Hmm, have you any info regarding schema-aware postgresql doing counter-intuitive when not using dot-notation? The only thing I'm thinking about is splitting system relations and user relations between two schemas in 7.4, but even that should not be an issue as lookup method is (or at least seems) safe to this. Any thoughts? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: why was /etc/defaults/make.conf not updated
Could be many reasons, e.g.: You didn't do a mergemaster while upgrading the base system, or you upgrade from 4.x to 5.x, which no longer has /etc/defaults/make.conf ... But either case, looking at /usr/src/UPDATING and /usr/ports/UPDATING is a good idea. On Fri, 5 Nov 2004 19:37:14 +0100, Michael Schuh <[EMAIL PROTECTED]> wrote: > Hi, > > ich have found an entry in /usr/local/ports/UPDATING, that the > Variable XFREE_VERSION in /etc/make.conf was outdated and changed. > So we shall use X_WINDOW_SYSTEM=xorg. > > I have searched an representing entry in /usr/src/etc/defaults/make.conf, > and it is not shown. Now i have also shown that the XFree4.4-ports are marked > as IGNORE. And i questioning me self why is the /etc/defaults/make.conf > not changed. I have already read that the change should coming. > > Is this the right sign to change to Xorg's XFree? > > Has anyone an information when this come true, or when the change was > maked in /usr/src/etc/defaults/make.conf? > > The reason to change to Xorg is clearly for me, may not why the > defaults/make.conf isn't already changed. > > Thanks to all and > best regards > > Michael > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Groups 12 and 14
Can anyone tell me which groups 12 and 14 are, on a 4.10 system please. I keep getting this from 340.noid Check for files with an unknown user or group: /usr/compat/linux/var/lock /usr/compat/linux/var/spool/mail $ ls -ld /usr/compat/linux/var/lock /usr/compat/linux/var/spool/mail drwxrwxr-x 3 root 14 512B Apr 18 2004 /usr/compat/linux/var/lock drwxrwxr-x 2 root 12 512B Feb 6 1996 /usr/compat/linux/var/spool/mail FreeBSD 4.10-STABLE #0: Fri Nov 5 21:32:19 GMT 2004 Cheers -- However, never daunted, I will cope with adversity in my traditional manner ... sulking and nausea. -- Tom K. Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Groups 12 and 14
"S. Anthony Sequeira" <[EMAIL PROTECTED]> probably said: > Can anyone tell me which groups 12 and 14 are, on a 4.10 system please. http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/group?rev=1.19.2.3&content-type=text/x-cvsweb-markup > $ ls -ld /usr/compat/linux/var/lock /usr/compat/linux/var/spool/mail > drwxrwxr-x 3 root 14 512B Apr 18 2004 /usr/compat/linux/var/lock > drwxrwxr-x 2 root 12 512B Feb 6 1996 > /usr/compat/linux/var/spool/mail Those are not part of the base system, they're part of the linux port. Mine are the same. P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Groups 12 and 14
On Sat, Nov 06, 2004 at 07:15:45PM +, S. Anthony Sequeira wrote: > Can anyone tell me which groups 12 and 14 are, on a 4.10 system please. > > I keep getting this from 340.noid > > Check for files with an unknown user or group: > /usr/compat/linux/var/lock > /usr/compat/linux/var/spool/mail > > $ ls -ld /usr/compat/linux/var/lock /usr/compat/linux/var/spool/mail > drwxrwxr-x 3 root 14 512B Apr 18 2004 /usr/compat/linux/var/lock > drwxrwxr-x 2 root 12 512B Feb 6 1996 > /usr/compat/linux/var/spool/mail > > FreeBSD 4.10-STABLE #0: Fri Nov 5 21:32:19 GMT 2004 They aren't assigned to anything by default under FreeBSD. What you are seeing are the default group assignments under Linux -- I believe that GID 12 is 'mail', but I have no idea what gid 14 is for. On my system, that file ends up as group 54: % find /usr/compat/ -nogroup -ls 1669302 drwxr-xr-x3 root 54512 Nov 3 08:00 /usr/compat/linux/var/lock 1825292 drwxr-xr-x2 root 12512 Feb 6 1996 /usr/compat/linux/var/spool/mail Which might be a difference due to having a different version of linux-base installed: % pkg_info -I linux\*base\* linux_base-8-8.0_4 Base set of packages needed in Linux mode (only for i386) As the /compat/linux stuff uses the base /etc/passwd data for it's UID and GID information, those group ownerships are arguably incorrect; however, I don't think that they really make any sort of difference. You could try experimenting with changing the group ownership of those files and see if anything breaks... Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgptRprKHc2Dz.pgp Description: PGP signature
Re: HEADS UP: databases/postgresql72 is dying
Sebastian Böck wrote: Have you considered that 7.2 is the last Version that doesn't have schemas. Out there may be some / are lot of applications that depend on this behaviour. I've considered lots of things. Nothing is *forcing* you to upgrade, and there will be packages for this port all the way up to 5.3-RELEASE (those that use older databases tend to stick with older OS releases, too). Speculations as to software that *may* be out there, that *does* want to run on a brand new 5.3+ OS, are not useful without concrete evidence to back them up. -aDe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Groups 12 and 14
On Sat, 2004-11-06 at 13:40, Matthew Seaman wrote: > On Sat, Nov 06, 2004 at 07:15:45PM +, S. Anthony Sequeira wrote: > > Can anyone tell me which groups 12 and 14 are, on a 4.10 system please. > > > > I keep getting this from 340.noid > > > > Check for files with an unknown user or group: > > /usr/compat/linux/var/lock > > /usr/compat/linux/var/spool/mail > > > > $ ls -ld /usr/compat/linux/var/lock /usr/compat/linux/var/spool/mail > > drwxrwxr-x 3 root 14 512B Apr 18 2004 /usr/compat/linux/var/lock > > drwxrwxr-x 2 root 12 512B Feb 6 1996 > > /usr/compat/linux/var/spool/mail > > > > FreeBSD 4.10-STABLE #0: Fri Nov 5 21:32:19 GMT 2004 > > They aren't assigned to anything by default under FreeBSD. What you > are seeing are the default group assignments under Linux -- I believe > that GID 12 is 'mail', but I have no idea what gid 14 is for. On my > system, that file ends up as group 54: > > % find /usr/compat/ -nogroup -ls > 1669302 drwxr-xr-x3 root 54512 Nov 3 > 08:00 /usr/compat/linux/var/lock > 1825292 drwxr-xr-x2 root 12512 Feb 6 > 1996 /usr/compat/linux/var/spool/mail > > Which might be a difference due to having a different version of > linux-base installed: > > % pkg_info -I linux\*base\* > linux_base-8-8.0_4 Base set of packages needed in Linux mode (only for i386) > > As the /compat/linux stuff uses the base /etc/passwd data for it's UID > and GID information, those group ownerships are arguably incorrect; > however, I don't think that they really make any sort of difference. > You could try experimenting with changing the group ownership of those > files and see if anything breaks... > > Cheers, > > Matthew > On my Fedora 2 system they match as follows: mail:x:12:mail uucp:x:14:uucp lock:x:54: ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Groups 12 and 14
On Sat, 2004-11-06 at 19:36, Peter Radcliffe wrote: > "S. Anthony Sequeira" <[EMAIL PROTECTED]> probably said: > > Can anyone tell me which groups 12 and 14 are, on a 4.10 system please. > > http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/group?rev=1.19.2.3&content-type=text/x-cvsweb-markup > > > $ ls -ld /usr/compat/linux/var/lock /usr/compat/linux/var/spool/mail > > drwxrwxr-x 3 root 14 512B Apr 18 2004 /usr/compat/linux/var/lock > > drwxrwxr-x 2 root 12 512B Feb 6 1996 > > /usr/compat/linux/var/spool/mail > > Those are not part of the base system, they're part of the linux port. > Mine are the same. > > P. OK, thanks. -- "A verbal contract isn't worth the paper it's printed on." - Samuel Goldwyn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Don's changes to fsck on 4.x ...
Well, finally had a reason to use it, and its running right now ... seems a bit slower in phase 2 then before ... is to be expected? Looking through the patch, it seems that all pass's were affected, so this might be now the norm ... after ~39minutes running on a very large file system, hitting ctl-T periodically, I'm up to about 50% through Phase 2 ... so far *knock on wood* no errors being generated by fsck itself, but that doesn't mean anything :) Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPv6 bridge + gif tunnel
Hi, I would like to make my problems clear. I have two questions about bridge function in the following figure. (1) Can we use bridge function over psuedo devices such as gif and tun? box3# ifconfig bge0 inet 133.149.0.2 netmask 255.255.255.0 box2# ifconfig create gif0 box2# gifconfig gif0 inet 133.149.0.2 133.149.1.2 box2# sysctl net.link.ether.bridge: 1 box2# sysctl net.link.ether.bridge_cfg: fxp0,gif0 box3# ifconfig bge1 inet 133.149.1.2 netmask 255.255.255.0 box3# ifconfig create gif1 box3# gifconfig gif1 inet 133.149.1.2 133.149.0.2 box3# sysctl net.link.ether.bridge: 1 box3# sysctl net.link.ether.bridge_cfg: gif1,fxp0 (2) Can any protocols go through between IPv6 MC router and IPv6 terminal in this step2 figure? Are there any limitations? Is IPv6 packet available? > <> IPv6 bridge cascaded by gif tunnel > > +--box#2--+ > [IPv6 MC router ]-+-+-(fxp0) IPv6 bridge | > | | > | | > (IPv4)133.149.0.2 +--+-(bge0) IPv6 bridge and IPv4 | >| | (gif0) IPv6 over IPv4 | >| +-+ >| > >| >| +---box#3-+ > (IPv4)133.149.1.2 +--+-(bge1) IPv6 bridge and IPv4 | > | (gif1) IPv6 over IPv4 | > | | > | | > | | >+--+-(fxp0) IPv6 bridge | >| +-+ >| >|term#2 >+-[IPv6 terminal(NDP client)] > Thanks in advance Hidei Yamamoto From: Hideki Yamamoto <[EMAIL PROTECTED]> Subject: IPv6 bridge + gif tunnel Date: Thu, 04 Nov 2004 01:53:41 +0900 (JST) Message-ID: <[EMAIL PROTECTED]> > > Hi, > > I am considering a network application test environments with FreeBSD > boxes as following. In the following, we show three step > architectures. This is an example for IPv6 VPN using IPv4 network. I would > like to use the IPv6 address assigned by IPv6 router on the remote the > IPv6 terminal. And the packets from/to IPv6 MC router, which supports > MLDv1 or v2 specification, are also transfered to/from the IPv6 > terminal. > > At the first step, I think it seems to be possible by using ipf bridge > function. I wonder if it is possible to implement the second step or > later. Are there any information about this issue? Any information > are welcomed. Thanks in advance. > > <> Simple IPv6 bridge > +--box#1-+ > [IPv6 MC router ]-+-+-(fxp0) IPv6 bridge | > || > || >+--+-(bge0) IPv6 bridge | >| ++ >| >|term#1 >+-[IPv6 terminal(NDP client)] > > > <> IPv6 bridge cascaded by gif tunnel > > +--box#2--+ > [IPv6 MC router ]-+-+-(fxp0) IPv6 bridge | > | | > | | >+--+-(bge0) IPv6 bridge and IPv4 | >| | (gif0) IPv6 over IPv4 | >| +-+ >| > >| >| +---box#3-+ >+--+-(bge1) IPv6 bridge and IPv4 | > | (gif1) IPv6 over IPv4 | > | | > | | > | | >+--+-(fxp0) IPv6 bridge | >| +-+ >| >|term#2 >+-[IPv6 terminal(NDP client)] > > > <> IPv6 bridge cascaded by gif tunnel with tun device > > +--box#4--+ > [IPv6 MC router ]-+-+-(fxp0) IPv6 bridge | > | |
FreeBSD 5.3-RELEASE Announcement
It is my great pleasure and privilege to announce the availability of FreeBSD 5.3-RELEASE. This release marks a milestone in the FreeBSD 5.x series and the beginning of the 5-STABLE branch of releases. Some of the many changes since 5.2.1 include: - A binary compatibility interface has been introduced for the i386 platform that allows running Microsoft Windows NDIS network drivers natively in the kernel. - The network and socket subsystems are now multi-threaded and reentrant. This allows for much better use of SMP parallelism when processing and forwarding local and remote network traffic. - The development environment has been updated to GCC 3.4.2, Binutils 2.15, and GDB 6.1 - The choices for graphical environments have been updated to include X.org 6.7, Gnome 2.6.2 and KDE 3.3.0. There has also been a significant focus on testing and bug-fixing with this release, as well as the freezing of most kernel and userland APIs. Users and vendors are encouraged to consider transitioning to it as FreeBSD 5.x is no longer considered a 'New Technology' release series. Information on migrating from FreeBSD 4.x to 5.x can be found at http://www.FreeBSD.org/releases/5.3R/migration-guide.html For a complete list of new features and known problems, please see the release notes and errata list, available at: http://www.FreeBSD.org/releases/5.3R/relnotes.html http://www.FreeBSD.org/releases/5.3R/errata.html For more information about FreeBSD release engineering activities, please see: http://www.FreeBSD.org/releng Availability - FreeBSD 5.3-RELEASE supports the i386, pc98, alpha, sparc64, amd64, and ia64 architectures and can be installed directly over the net using bootable media or copied to a local NFS/FTP server. Distributions for all architectures are available now. Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 5.3 based products: FreeBSD Mall, Inc.http://www.freebsdmall.com/ Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html If you can't afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from the following sites. MD5 checksums for the release images are included at the bottom of this message. Bittorrent -- Bittorrent distribution is being tested on an experimental basis. A collection of trackers for the release ISO images is available at http://people.freebsd.org/~scottl/5.3-torrent FTP --- ftp://ftp.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.FreeBSD.org/pub/FreeBSD/ ftp://ftp3.FreeBSD.org/pub/FreeBSD/ ftp://ftp4.FreeBSD.org/pub/FreeBSD/ ftp://ftp5.FreeBSD.org/pub/FreeBSD/ ftp://ftp6.FreeBSD.org/pub/FreeBSD/ ftp://ftp7.FreeBSD.org/pub/FreeBSD/ ftp://ftp10.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.au.FreeBSD.org/pub/FreeBSD/ ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/ ftp://ftp.fr.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.jp.FreeBSD.org/pub/FreeBSD/ ftp://ftp1.ru.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.tw.FreeBSD.org/pub/FreeBSD/ ftp://ftp3.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp10.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp11.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp15.us.FreeBSD.org/pub/FreeBSD/ FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, Amylonia, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom. Before trying the central FTP site, please check your regional mirror(s) first by going to: ftp://ftp..FreeBSD.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. More information about FreeBSD mirror sites can be found at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html Acknowledgments Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 5.3 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, Sandvine, Inc., FreeBSD Systems, Inc, and NTT/Verio. The release engineering team for 5.3-RELEASE includes: Scott Long <[EMAIL PROTECTED]> Release Engineering,
Re: freebsd 5.3 have any problem with vinum ?
On Monday, 1 November 2004 at 10:05:16 +1100, Carl Makin wrote: > Greg 'groggy' Lehey wrote: > >> On Monday, 25 October 2004 at 14:21:33 -0600, secmgr wrote: >> >> >> >> It's beginning to look like that's a bad idea. Lukas is >> (understandably) working only on gvinum, and since I know it's nearly >> there, I'm not going to do any further work on Vinum in FreeBSD 5. >> Given the problems, I'd suggest that we yank it. > > Do you want to yank it in 5 or 6-CURRENT? Well, it's been yanked in -CURRENT. My understanding was that it should also be yanked in 5.x: a number of changes have been made that effectively break old Vinum, > There are a *lot* of people using vinum and yanking it in 5-STABLE > would force us all to use the 5.3 security branch until gvinum > caught up. Yes, I'm afraid so. I can think of better ways that this could have been managed, but I haven't had much influence. Greg -- See complete headers for address and phone numbers. pgpaGayfYyURY.pgp Description: PGP signature
Re: Don's changes to fsck on 4.x ...
On 6 Nov, Marc G. Fournier wrote: > > Well, finally had a reason to use it, and its running right now ... seems > a bit slower in phase 2 then before ... is to be expected? Looking > through the patch, it seems that all pass's were affected, so this might > be now the norm ... after ~39minutes running on a very large file system, > hitting ctl-T periodically, I'm up to about 50% through Phase 2 ... so far > *knock on wood* no errors being generated by fsck itself, but that doesn't > mean anything :) Under normal circumstances, there shouldn't be any noticeable difference in performance. If there are a lot of zero link count files, phase 1 should be very slightly faster because the zero link count file list no longer needs to be allocated, and phase 4 should be a lot faster. Most of the time in phases 1 and 2 is consumed by disk reads. The only change to phase 2 was the addition of the new inode states to a couple of case statements and an if statement which should not affect the amount of I/O done and CPU time would only be affected by a miniscule amount, so I would not expect any change to the performance of that phase. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Don's changes to fsck on 4.x ...
On Sat, 6 Nov 2004, Don Lewis wrote: On 6 Nov, Marc G. Fournier wrote: Well, finally had a reason to use it, and its running right now ... seems a bit slower in phase 2 then before ... is to be expected? Looking through the patch, it seems that all pass's were affected, so this might be now the norm ... after ~39minutes running on a very large file system, hitting ctl-T periodically, I'm up to about 50% through Phase 2 ... so far *knock on wood* no errors being generated by fsck itself, but that doesn't mean anything :) Under normal circumstances, there shouldn't be any noticeable difference in performance. If there are a lot of zero link count files, phase 1 should be very slightly faster because the zero link count file list no longer needs to be allocated, and phase 4 should be a lot faster. Most of the time in phases 1 and 2 is consumed by disk reads. The only change to phase 2 was the addition of the new inode states to a couple of case statements and an if statement which should not affect the amount of I/O done and CPU time would only be affected by a miniscule amount, so I would not expect any change to the performance of that phase. Hindsight is 20/20, but I should have trap' the output ... I saw several 'ZERO LENGTH DIRECTORY' messages in Phase 4 still ... should I have seen any at all? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
'ifconfig fxp0 -alias' wipes out all IPs on device
I hate to report an email, but after being laughed at by both Linux and Windows users, I'm kinda concerne at the lack of response to my originals ... is this truly the desired behaviour? And, if so ... can someone put some sort of warning/notice about it in the man page(s)? == I just made one of my 4.x remote servers inaccessible and just tested it on my 5.x laptop, and it does the same thing ... not sure if this is considered a 'desirable' effect, or a but ... but ... 'ifconfig -alias' will wipe out all IPs on the device: mobile# ifconfig -a lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 rl0: flags=8843 mtu 1500 options=8 inet 192.168.0.5 netmask 0xff00 broadcast 192.168.0.255 ether 00:0d:88:22:78:e4 media: Ethernet 10baseT/UTP status: active mobile# ifconfig rl0 -alias mobile# ifconfig -a lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 rl0: flags=8843 mtu 1500 options=8 ether 00:0d:88:22:78:e4 media: Ethernet 10baseT/UTP status: active I was running a script that happened to pick up a 'zero length' IP (and I hadn't properly tested for it), so erased all the IPs configured on that device, instead of generating an error ... Checking the man page, if this *is* desired effect, a bit of a warning might be in order: " -alias Remove the network address specified. This would be used if you incorrectly specified an alias, or it was no longer needed. If you have incorrectly set an NS address having the side effect of specifying the host portion, removing all NS addresses will allow you to respecify the host portion." "Remove the network address specified.", to me, means that if one isn't specified, nothing should/would happen :( Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 'ifconfig fxp0 -alias' wipes out all IPs on device
At 1:02 AM -0400 11/7/04, Marc G. Fournier wrote: I hate to report an email, but after being laughed at by both Linux and Windows users, I'm kinda concerned at the lack of response to my originals ... is this truly the desired behaviour? And, if so ... can someone put some sort of warning/notice about it in the man page(s)? I imagine you received no response simply because several of the main developers have been swamped trying to finish off 5.3. I remember seeing your earlier report, but I don't remember which mailing list it was sent to. I'll respond enough to say that the behavior you saw seems undesirable to me. But I'm not a networking guy, so that doesn't mean much... -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
iptables under linux-emulation (debian?), can it be done?
hi, im trying to get some use of the linux emulation :), ive got a debian box just for iptables tryouts (thats a waste of a machine:). i guess the best choice is to get it to work in my fbsd5 and play there, but, linux_base-debian y marked a broken some time now, should i expect it working soon?, i guess not for 5-stable :/ i prefer not to use redhat base, but if you say it is the only way, i would :(, now, can i play well with iptables on linux emulation? (it will be too complicated?). thanks in advance ps: maybe not the right list, but related to the mail topic: shouldnt be more practical to have /usr/ports//linux- under /usr/ports/linux// (i have it shadowed right now, and i found it more practical, what do you think?). (sorry for the bad english) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd 5.3 have any problem with vinum ?
No, I mean self corrupting raid5 sets during initialization. Discussed about 2-3 weeks ago. On Sat, 2004-11-06 at 05:09, Matthias Schuendehuette wrote: > > If you mean the 'dangling vnode'-problem with "vinum-classic": > > Try to start 'classic' vinum *after* the system has come up. Either > manually or perhaps with a script in /usr/local/etc/rc.d. This works > for me until now under 5-STABLE (a.k.a. RELENG_5). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd 5.3 have any problem with vinum ?
I did a gvinum start. On Sat, 2004-11-06 at 04:16, Matthias Schuendehuette wrote: > Am Mittwoch, 3. November 2004 21:27 schrieb secmgr: > > Just ran into this myself. I had a perfectly happy raid 5 plex under > > 5.3 RC1. I upgrade to RC2, and the whole plex goes stale. I deleted > > everything from the volume on down (except for the drives), and tried > > to recreate the vol/plex/sd's. gvinum creates them, but they come > > back (like the undead) as stale and unusable (just like they were > > before). I'm finding commands documented (in help), but unimplemented > > (checkparity? init?). > > Did you try to simply 'start' the plex? This works for initialisation of > a newly created RAID5-Plex as well as for recalculating parity > informations on a degraded RAID5-Plex. > > It's that simple (at least for me on 5-STABLE) but admittedly > undocumented. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Don's changes to fsck on 4.x ...
On 7 Nov, Marc G. Fournier wrote: > On Sat, 6 Nov 2004, Don Lewis wrote: > >> On 6 Nov, Marc G. Fournier wrote: >>> >>> Well, finally had a reason to use it, and its running right now ... seems >>> a bit slower in phase 2 then before ... is to be expected? Looking >>> through the patch, it seems that all pass's were affected, so this might >>> be now the norm ... after ~39minutes running on a very large file system, >>> hitting ctl-T periodically, I'm up to about 50% through Phase 2 ... so far >>> *knock on wood* no errors being generated by fsck itself, but that doesn't >>> mean anything :) >> >> Under normal circumstances, there shouldn't be any noticeable difference >> in performance. If there are a lot of zero link count files, phase 1 >> should be very slightly faster because the zero link count file list no >> longer needs to be allocated, and phase 4 should be a lot faster. Most >> of the time in phases 1 and 2 is consumed by disk reads. The only >> change to phase 2 was the addition of the new inode states to a couple >> of case statements and an if statement which should not affect the >> amount of I/O done and CPU time would only be affected by a miniscule >> amount, so I would not expect any change to the performance of that >> phase. > > Hindsight is 20/20, but I should have trap' the output ... I saw several > 'ZERO LENGTH DIRECTORY' messages in Phase 4 still ... should I have seen > any at all? Yes. The behaviour should be exactly the same as before. The only difference is that phase 4 should run a lot faster if there are a lot of UNREF files and directories. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Don's changes to fsck on 4.x ...
On Sat, 6 Nov 2004, Don Lewis wrote: Yes. The behaviour should be exactly the same as before. The only difference is that phase 4 should run a lot faster if there are a lot of UNREF files and directories. 'k, everything seemed to run faster except the first two, but the uptime was only 5 days on taht server also, so not alot of time to build up the 'stale files' ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
