Re: freenx server
On Fri, Dec 21, 2007 at 10:41:59AM -0600, Jack Barnett wrote: Anyone get the freeNX server working from nomachine? When I try to build it from /usr/ports/net/freenx it says it is broken under xorg 7.2 I've upgrade to xorg 7.3.x and modified the make file and it builds everything but nxagent, so it fails to `make install` install: /usr/ports/net/nxserver/work/nx-X11/programs/Xserver/nxagent: No such file or directory *** Error code 71 Yeah, I tried messing around with this a few months ago, it tried to compile and at the end (which was a lengthy job) it turned out to be a waste. I was told before to get in touch with the maintainer of the port and discuss it further. Funny though, mine failed on nxnode :P From portsmon.freebsd,org, the mantainer of freenx and nxserver is [EMAIL PROTECTED] Hope this helps, Russell Doucette ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: amd64 native boot loader?
snowcrash+freebsd wrote: hi, i've FBSD/amd64 62Rp9 installed. kernel world are my own builds from latest cvsup. on boot I see: FreeBSD/i386 bootstrap loader odd. i'd expect a native loader ... checking in, /usr/src/sys/boot ls Makefile alpha/arm/ efi/ forth/ia64/ pc98/ sparc64/ READMEarc/ common/ ficl/ i386/ ofw/ powerpc/ other arches seem to be there ... just not amd64. where's the src for the amd64? AMD64 CPUs are backwards compatible with i386; they boot in 16-bit real mode and only get switched into 64-bit 'long mode' by the kernel later on. Since both i386 and amd64 start booting in the same way, there's no need for separate bootloaders. -- Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
xclients and remote display (WAS: Re: freenx server)
Thanks, yea, but I don't think he's maintaining it any longer? In ports it's version 1.4.x, but nomachine.com has latest version has 3.5.x My friend emailed nomachine.com and he said they refused to support any of the xBSD or offer any help on getting a working port for the xBSD world. I'm guessing that is the reason why it's so out of date and broken. :/ Are their any alternatives besides VNC? We have that and it's working good (TightVNC tunneled though SSH), but would like to just run one 'window' and have it displayed on our workstation. For example, Run an xterm on FreeBSD server and have it displayed on an XP or Linux workstation. User Ota wrote: On Fri, Dec 21, 2007 at 10:41:59AM -0600, Jack Barnett wrote: Anyone get the freeNX server working from nomachine? When I try to build it from /usr/ports/net/freenx it says it is broken under xorg 7.2 I've upgrade to xorg 7.3.x and modified the make file and it builds everything but nxagent, so it fails to `make install` install: /usr/ports/net/nxserver/work/nx-X11/programs/Xserver/nxagent: No such file or directory *** Error code 71 Yeah, I tried messing around with this a few months ago, it tried to compile and at the end (which was a lengthy job) it turned out to be a waste. I was told before to get in touch with the maintainer of the port and discuss it further. Funny though, mine failed on nxnode :P From portsmon.freebsd,org, the mantainer of freenx and nxserver is [EMAIL PROTECTED] Hope this helps, Russell Doucette ___ [EMAIL PROTECTED] mailing list [3]http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [4][EMAIL PROTECTED] References 1. mailto:[EMAIL PROTECTED] 2. mailto:freebsd-questions@freebsd.org 3. http://lists.freebsd.org/mailman/listinfo/freebsd-questions 4. mailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: timekeeping on jail servers
In response to John Webster : --On Friday, December 21, 2007 13:51:29 -0500 Bill Moran wrote: In response to John Webster : Not generally suitable for cron because it can take longer to slew than it does for the next cron execution to occur, which would then result in multiple ntpdate programs fighting each other (not sure what the effect of this would be). If I were doing it I would write a script with locking in order to ensure multiple jobs don't fight. Simple. Umm At that point, why not just run ntpd? You've basically replaced it with a script anyway. My suggestions are based on the OP about ntpd binding to everything. Besides, it's not that easy. As Chuck pointed out, ntpdate calls adjtime() and exits, which means an adjustment might already be in progress when you you call it again. I don't know if ntpdate checks the return pointer from adjtime() to avoid multiple adjustment requests. Just out of curiosity, why run it more that once a day? Or for that matter every couple of days? There is the matter of how accurate does your time really need to be? I worked a place where many computers were used for employees to clock in/clock out. Synchronizing time once a day, the clocks would drift enough that employees who showed up on time and left on time would appear to have arrived late and/or left early (up to 5 minutes a day drift). Of course, this is hardware-dependent and even environmentally dependent (computers connected to clean power sources with consistent environmental temperature seem to keep more accurate time in my experience) Other common applications are even more sensitive. If you run NFS or other file sharing, you can run into all sorts of ugliness if time skews more than a few seconds. Web applications can be notoriously buggy if either the server or the client is off by more than a few seconds. With all those potential problems looming, why would you use anything other than a full-blown ntp daemon? I just can't see the excuse for making up other solutions. -- Bill Moran http://www.potentialtech.com Hello Bill, The only system running ntpd that I have it's a FileServer and is acting also like NTP Server for workstations, especially to avoid the issue with different timing for client-server that you mentioned. Finally running ntpdate once per day from cron is fine if you do not have to meet strict requirements. But this depends on the admin. Merry Chistmas everybody. BR, Catalin Miclaus - Never miss a thing. Make Yahoo your homepage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: incompetent for BIO_WRITE
Hi! Just a few minutes ago, I noticed one of my machines was stuck with this message on the console: GEOM_RAID5: KASSERT in line 1352 panic: incompetent for BIO_WRITE cpuid = 0 Uptime: 1h33m15s GEOM_RAID5: raid5/raid5: device is still open, so it cannot be definitely removed. GEOM_RAID5: raid5: worker thread exiting. I am concerned that it neither dumped core nor rebooted.. it just stuck there. Is this intended behavior for such a panic, or do I need to fiddle with some knobs to make sure it comes back up afterwards, and preferably leaves me with some evidence with which to debug the panic? Thanks! -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xclients and remote display (WAS: Re: freenx server)
On Sat, Dec 22, 2007 at 03:40:48AM -0600, Jack Barnett wrote: Thanks, yea, but I don't think he's maintaining it any longer? In ports it's version 1.4.x, but nomachine.com has latest version has 3.5.x My friend emailed nomachine.com and he said they refused to support any of the xBSD or offer any help on getting a working port for the xBSD world. I'm guessing that is the reason why it's so out of date and broken. :/ Are their any alternatives besides VNC? We have that and it's working good (TightVNC tunneled though SSH), but would like to just run one 'window' and have it displayed on our workstation. For example, Run an xterm on FreeBSD server and have it displayed on an XP or Linux workstation. Not really, all I know of is FreeNX and VNC. As for their refusal, is it out of pure ignorance that they don't wish to support BSD? I thought they had at one time supported FreeBSD (the assumption is based on the fact that it exists in the ports tree). Too bad, though. I tested FreeNX on a debian install (unfortunately) and the client ran smooth on my windows machine, with the unfortunate exception that it has 0 dual-monitor support in fullscreen mode. I found this though: http://www.deweyonline.com/nx/freebsd.html Highly betting that the maintainer's page for this (if that is the maintainer) that first section looks promising. The link works to download the 6.2-RELEASE version. It's possible that might work with X.Org versions later than 7.1; I haven't personally tested it myself. Btw, which FreeBSD release are you running? Russell Doucette ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to install with journaled /?
Hello, my problem is that I cannot really turn on gjournal for existing filesystems, just only if the journal is placed onto another partition. So, how can I make a journaled root filesystem? I have to do the partitioning manually, since sysinstall does not support that. But how can I do that easily? The livefs CD does not work, there is no gjournal utility there. I'd give FreeSBIE or Frenzy a try, but their existing releases are based on 6.2, not 7.0, thus no gjournal there. Do you have any ideas? How did you solve such a problem? Thanks in advance, -- Gabor Kovesdan FreeBSD Volunteer EMAIL: [EMAIL PROTECTED] .:|:. [EMAIL PROTECTED] WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to install with journaled /?
On Sat, Dec 22, 2007 at 11:07:29AM +0100, Gabor Kovesdan wrote: Hello, my problem is that I cannot really turn on gjournal for existing filesystems, just only if the journal is placed onto another partition. So, how can I make a journaled root filesystem? I have to do the partitioning manually, since sysinstall does not support that. But how can I do that easily? The livefs CD does not work, there is no gjournal utility there. I'd give FreeSBIE or Frenzy a try, but their existing releases are based on 6.2, not 7.0, thus no gjournal there. Do you have any ideas? How did you solve such a problem? Thanks in advance, -- Gabor Kovesdan FreeBSD Volunteer EMAIL: [EMAIL PROTECTED] .:|:. [EMAIL PROTECTED] WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org Only way that I have found - crossinstall system to another HDD, boot from it and make required changes. Sadly enough, /stand/geom isn't aware of journal class, returning `Invalid class name'. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to install with journaled /?
On Sat, Dec 22, 2007 at 11:07:29AM +0100, Gabor Kovesdan wrote: Hello, my problem is that I cannot really turn on gjournal for existing filesystems, just only if the journal is placed onto another partition. So, how can I make a journaled root filesystem? I have to do the partitioning manually, since sysinstall does not support that. But how can I do that easily? The livefs CD does not work, there is no gjournal utility there. I'd give FreeSBIE or Frenzy a try, but their existing releases are based on 6.2, not 7.0, thus no gjournal there. Do you have any ideas? How did you solve such a problem? I'd try the following: 1. 2 PC's: boot one from another using PXE and NFS 2. 2 HDD's: install on one, partition the other as needed and dump-restore data to it 3. Swap hack: install the root stuff in the swap slice, then enable gjournal on the first one and dump-restore data. Then bsdlabel swap as swap. I can probably come up with more :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPFW: Blocking me out. How to debug?
Warning: overlong message. I'm moving this to questions@ from security@ as it's a usage issue. Anyone wishing to follow the up to here can read from: http://lists.freebsd.org/pipermail/freebsd-security/2007-December/004541.html On Fri, 21 Dec 2007, W. D. wrote: Date: Fri, 21 Dec 2007 01:30:11 -0600 From: W. D. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Ian Smith [EMAIL PROTECTED] Never been to Uzbekistan and don't know this bloke :) At 05:45 12/20/2007, Ian Smith, wrote: Thanks for your reply Ian. This is the kind of information I am looking for. Firstly, this really belongs over on freebsd-net@ if not freebsd-questions@, but anyway .. I'll be glad to move it there if you would like. I figured that since IPFW/Firewalls are security related, that FreeBSD-Security would be the most appropriate place. On Thu, 20 Dec 2007, W. D. wrote: At 03:49 12/17/2007, Tuomo Latto wrote: W. D. wrote: How do I tell which rule is blocking me out? SSH *is* working, but others are not. It all depends on what you mean by blocking you out and others. True; it's not really clear what you're trying to do, whether this is a single server with a single net interface with no NAT or what, but based on your present rules I'll have to make that assumption. OK, sorry. I guess I just assumed that it would be obvious that this is a Web server. (Never assume anything, my good fellow - Sherlock Holmes). Ok, and sorry I needed a days' sleep + $life before getting back to you. Here are many people who can and likely will offer opinions and advice. By the way, it is/will be running Plesk server management software, if it matters: http://www.swsoft.com/en/products/plesk/reqs/ I know nothing of Plesk, but doubt it's relevant to this now. Also, this server is on an internal LAN before I subject it to the wild, untamed, InterWeb, with its dangerous internets darting back and forth inside all of the tubes. Really good idea :) add allow all from any to any via lo0 add deny ip from any to 127.0.0.0/8 add deny ip from 127.0.0.0/8 to any Ok. # Allow established connections: add allow tcp from any to any established That's ok. It may help you in debugging what's happening to use: allow [log] tcp from any to any in established allow [log] tcp from any to any out established I assume here that [log] means to insert log for debugging like this: allow log tcp from any to any in established allow log tcp from any to any out established rather than including the square brackets, [ ], correct? Yeah sorry, I meant [log] as in optionally just for debugging. I have done that and have included my latest ruleset below. and really, using 'any to any' without specifying on which interfaces or whether 'any' is your box or the outside world is a bit too general, but moving on .. OK. What should I do? I only plan on having one Ethernet interface. What would be more secure? In that case 'me to any' or 'any to me' provides unambiguous direction where appropriate. As shown in your ipfw show below, direction can help make things clear, and clarity means safety when it comes to firewalls, even if it means a slightly larger ruleset. # Deny fragmented packets: add deny ip from any to any frag # Show pings: add count icmp from any to any icmptypes 8 in That's inbound ping requests. Don't forget that 'inbound' means coming into the firewall, not necessarily from the outside world. Your own ping requests _from_ this box also have to both come in, and go out. Hmmm. OK. Outbound Ping will be rarely used, but should be allowed. Isn't that included in the next rule? Yes it is, so here ambiguous directionality works ok, as long as you're well aware of it. # Allow pings, ping replies, and host unreach: add allow icmp from any to any icmptypes 0,8,3 Add icmptype 11 as well if you want traceroutes to work .. Traceroutes want to see 'TTL exceeded in transit' icmp messages. # Allow UDP traceroutes: add allow udp from any to any 33434-34458 in add allow udp from any 33434-34458 to any out Ok, though udp rules are often better done statefully. See below. # Allow DNS with name server add allow udp from any to any domain out add allow udp from any domain to any in Nope. You want to watch out here. This allows udp packets from any address with source port 53 to connect with any open udp port on your system, and allows the responses as well. It's a simple matter using such as netcat to source packets from port 53. Should I restrict it by specifically stating the service? How can I be safe? What would the rule
Updating ports
Hi, I want to update some ports. I'm using FreeBSD 6.2. I was reading in the handbook and there are two ways to update them through the portupdate and portmanager. What's the difference between them? -- Robe. En el verdadero amor, el alma oculta al cuerpo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: Turkish character sorting on PostgreSQL
Hello Ivan,
Here is the test result. It seems that the problem is on FreeBSD
(6.2) . Because ö and ş are before then z in Turkish alphabet.
# cat a.c
#include locale.h
int main() {
setlocale(LC_COLLATE, tr_TR.ISO8859-9);
printf(%d\n,strcoll(ö, z));
printf(%d\n,strcoll(ü, z));
}
ftpfreebsd[~]# ./a
124
130
ftpfreebsd[~]#
By the way, LC_COLLATE is link to the ../la_LN.US-ASCII/LC_COLLATE
in /usr/share/locale/tr_TR.ISO8859-9 directory. Does this mean that
LC_COLLATE is missing for tr_TR.ISO8859-9 ?
# ls -al /usr/share/locale/tr_TR.ISO8859-9/
total 14
drwxr-xr-x2 root wheel 512 Jul 9 15:32 .
drwxr-xr-x 157 root wheel 4096 Dec 4 2006 ..
lrwxr-xr-x1 root wheel28 Jul 9 15:32 LC_COLLATE -
../la_LN.US-ASCII/LC_COLLATE
lrwxr-xr-x1 root wheel26 Jul 9 15:32 LC_CTYPE -
../la_LN.US-ASCII/LC_CTYPE
-r--r--r--1 root wheel18 Jul 9 15:32 LC_MESSAGES
-r--r--r--1 root wheel34 Jul 9 15:32 LC_MONETARY
-r--r--r--1 root wheel 8 Jul 9 15:32 LC_NUMERIC
-r--r--r--1 root wheel 352 Jul 9 15:32 LC_TIME
and there is no file spesicific to the tr_TR.ISO8859-9 in
/usr/src/share/colldef/
# ls /usr/src/share/colldef/
Makefileel_GR.ISO8859-7.src la_LN.ISO8859-15.src
map.ISO8859-1 ru_RU.CP1251.src
README en_DK.example la_LN.ISO8859-2.src
map.ISO8859-13 ru_RU.CP866.src
be_BY.CP1131.srces_ES.ISO8859-1.src la_LN.ISO8859-4.src
map.ISO8859-15 ru_RU.ISO8859-5.src
be_BY.CP1251.srces_ES.ISO8859-15.srcla_LN.US-ASCII.src
map.ISO8859-2 ru_RU.KOI8-R.src
be_BY.ISO8859-5.src et_EE.ISO8859-15.srclt_LT.ISO8859-13.src
map.ISO8859-4 sl_SI.ISO8859-2.src
bg_BG.CP1251.srchi_IN.ISCII-DEV.src lt_LT.ISO8859-4.src
map.ISO8859-5 sr_YU.ISO8859-5.src
ca_ES.ISO8859-1.src hy_AM.ARMSCII-8.src map.ARMSCII-8
map.ISO8859-7 sv_SE.ISO8859-1.src
ca_ES.ISO8859-15.srcis_IS.ISO8859-1.src map.CP1131
map.KOI8-R sv_SE.ISO8859-15.src
cs_CZ.ISO8859-2.src is_IS.ISO8859-15.srcmap.CP1251
map.KOI8-U uk_UA.CP1251.src
de_DE.ISO8859-1.src kk_KZ.PT154.src map.CP866
map.PT154 uk_UA.ISO8859-5.src
de_DE.ISO8859-15.srcla_LN.ISO8859-1.src map.ISCII-DEV
pl_PL.ISO8859-2.src uk_UA.KOI8-U.src
Thursday, December 20, 2007, 12:44:34 PM, you wrote:
Ismail YENIGUL wrote:
Hello,
I am using PostgreSQL 8.2.5 on FreeBSD 6.2. But I have a problem with
sorting Turkish characters. They are listed after z character.
I initialized the PostgreSQL with the following values:
initdb -E UNICODE --locale=tr_TR.UTF-8 and
Unicode (UTF-8) collations (sorting) don't work on FreeBSD. You can use
PostgreSQL 8.1 and the ICU patch for it.
initdb -E LATIN5 --locale tr_TR.ISO8859-9
This could work, if the locale is properly defined in the system locale
database. Try creating a small C program that sorts your strings using
strcoll() to verify this - if the small C program works, it's a
PostgreSQL problem.
--
+
+ http://www.enderunix.org/ismail http://www.endersys.com.tr +
+ EnderUNIX SDT @ Tr Endersys Consultancy Ltd.+
+ ismail ~ enderunix.org ismail.yenigul ~ endersys.com.tr +
+ Volunteer, Core Team Member Project Manager +
+
TCP/IP ve Ağ güvenliği kitabının 2. baskısı çıktı!
http://dukkan.acikakademi.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating ports
On Dec 22, 2007 11:39 AM, Robe [EMAIL PROTECTED] wrote: Hi, I want to update some ports. I'm using FreeBSD 6.2. I was reading in the handbook and there are two ways to update them through the portupdate and portmanager. What's the difference between them? -- Robe. Each one offers some unique features, read the man pages to see if you need specific functionality that isn't present in one of them (I doubt it). Mostly it comes down to your preference. I personally recommend portmaster because it's a shell script and requires no additional software to be installed. To update everything on your system just run 'portmaster -ad'. The -a flag automatically updates all out-of-date ports, -d removes old distfiles without asking. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to install with journaled /?
On Sat, 22 Dec 2007 11:07:29 +0100 Gabor Kovesdan [EMAIL PROTECTED] wrote: Hello, my problem is that I cannot really turn on gjournal for existing filesystems, just only if the journal is placed onto another partition. So, how can I make a journaled root filesystem? Is there any particular need to do this? Typically, nothing much is written to the root partition, and it's too small for a normal fsck to take any significant time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: amd64 native boot loader?
On Dec 22, 2007, at 3:32 AM, Bruce Cran wrote: AMD64 CPUs are backwards compatible with i386; they boot in 16-bit real mode and only get switched into 64-bit 'long mode' by the kernel later on. Since both i386 and amd64 start booting in the same way, there's no need for separate bootloaders. -- Bruce I've thought about this too, but do wonder why the boot loader couldn't go into long mode in one of the loader stages. I don't know if there'd be any significant improvements or drawbacks other than duplication of some code(which I imagine isn't changed often). Somewhat offhand, can the OpenBSD loader chain boot FreeBSD? Due to my dvd drive being sata over atapi, it wasn't recognized by the 6 branch until recently(many thanks to whoever committed the change). But I recall that the boot cd for FreeBSD wouldn't boot, but the boot cd for OpenBSD would. Of course that does primarily relate to cdboot and not boot0. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Realtek 8101E NIC and FreeBSD 4.11
Hello all, has anyone tried to compile the Realtek driver (rtl_bsd_drv_v174.tgz) on FreeBSD 4.x? From http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1PNid=7PFid=7Level=5Conn=4DownTypeID=3GetDown=false#RTL8100E/RTL8101E/RTL8102E-GR Readme.txt says: 1. Method 1 advises to just copy the .ko module to /modules, but there is no .ko file in the tgz archive. That is even ok since I guess they would have to put a .ko module in tgz archive for all popular versions of FreeBSD (4.x/5.x/6.x) and their kernel versions. 2. Method 2 advises to go for compilation of kernel modules using the .c, .h and Makefile from the tgz archive. I made backups of original files, compiled new kernel without rl, rebooted (everything from step 1 and 2), copied everything from tgz archive in place, edited if_rlreg.h so that the first #define lines would look like this (for 4.11): #define VERSION(_MainVer,_MinorVer) ((_MainVer)*10+(_MinorVer)) #define OS_VER VERSION(4,11) /*#if __FreeBSD_version 50*/ /*#define VERSION(_MainVer,_MinorVer) ((_MainVer)*10+(_MinorVer)*1)*/ /*#else*/ /*#define VERSION(_MainVer,_MinorVer) ((_MainVer)*10+(_MinorVer)*1000)*/ /*#endif*/ /*#define OS_VER __FreeBSD_version*/ (uncommented first 2 lines, commented next 6 lines). Then in the /usr/src/sys/modules/rl I ran make clean (which is ok) and then make and it started to complain: host# make Warning: Object directory not changed from original /usr/src/sys/modules/rl @ - /usr/src/sys machine - /usr/src/sys/i386/include touch opt_bdg.h perl @/kern/makeops.pl -h @/kern/device_if.m perl @/kern/makeops.pl -h @/kern/bus_if.m perl @/kern/makeops.pl -h @/pci/pci_if.m cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -I/usr/include -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -c /usr/src/sys/modules/rl/../../pci/if_rl.c In file included from /usr/src/sys/modules/rl/../../pci/if_rl.c:73: @/pci/if_rlreg.h:506: field `mtx' has incomplete type /usr/src/sys/modules/rl/../../pci/if_rl.c: In function `rl_attach': /usr/src/sys/modules/rl/../../pci/if_rl.c:257: warning: implicit declaration of function `mtx_init' /usr/src/sys/modules/rl/../../pci/if_rl.c:257: `MTX_NETWORK_LOCK' undeclared (first use in this function) /usr/src/sys/modules/rl/../../pci/if_rl.c:257: (Each undeclared identifier is reported only once /usr/src/sys/modules/rl/../../pci/if_rl.c:257: for each function it appears in.) /usr/src/sys/modules/rl/../../pci/if_rl.c:257: `MTX_DEF' undeclared (first use in this function) /usr/src/sys/modules/rl/../../pci/if_rl.c:524: warning: passing arg 2 of `ether_ifattach' makes integer from pointer without a cast /usr/src/sys/modules/rl/../../pci/if_rl.c:555: `IFM_1000_T' undeclared (first use in this function) /usr/src/sys/modules/rl/../../pci/if_rl.c: In function `rl_detach': /usr/src/sys/modules/rl/../../pci/if_rl.c:588: warning: implicit declaration of function `mtx_lock' /usr/src/sys/modules/rl/../../pci/if_rl.c:590: warning: implicit declaration of function `mtx_unlock' /usr/src/sys/modules/rl/../../pci/if_rl.c:596: too few arguments to function `ether_ifdetach' /usr/src/sys/modules/rl/../../pci/if_rl.c:618: warning: implicit declaration of function `mtx_destroy' /usr/src/sys/modules/rl/../../pci/if_rl.c: In function `rl_start': /usr/src/sys/modules/rl/../../pci/if_rl.c:993: warning: passing arg 1 of `bpf_mtap' from incompatible pointertype /usr/src/sys/modules/rl/../../pci/if_rl.c:1067: warning: passing arg 1 of `bpf_mtap' from incompatible pointer type /usr/src/sys/modules/rl/../../pci/if_rl.c: In function `rl_rxeof': /usr/src/sys/modules/rl/../../pci/if_rl.c:1533: structure has no member named `if_input' /usr/src/sys/modules/rl/../../pci/if_rl.c:1630: structure has no member named `if_input' /usr/src/sys/modules/rl/../../pci/if_rl.c: In function `rl_intr': /usr/src/sys/modules/rl/../../pci/if_rl.c:1723: structure has no member named `if_link_state' /usr/src/sys/modules/rl/../../pci/if_rl.c:1723: `LINK_STATE_UP' undeclared (first use in this function) /usr/src/sys/modules/rl/../../pci/if_rl.c:1724: syntax error before `/' /usr/src/sys/modules/rl/../../pci/if_rl.c:1729: structure has no member named `if_link_state' /usr/src/sys/modules/rl/../../pci/if_rl.c:1729: `LINK_STATE_DOWN' undeclared (first use in this function) /usr/src/sys/modules/rl/../../pci/if_rl.c:1730: syntax error before `/' /usr/src/sys/modules/rl/../../pci/if_rl.c: In function `rl_setmulti': /usr/src/sys/modules/rl/../../pci/if_rl.c:1830: structure has no member named `tqh_first' /usr/src/sys/modules/rl/../../pci/if_rl.c:1830: structure has no member named `tqe_next'
Re: Re[2]: Turkish character sorting on PostgreSQL
On 22/12/2007, Ismail YENIGUL [EMAIL PROTECTED] wrote: By the way, LC_COLLATE is link to the ../la_LN.US-ASCII/LC_COLLATE in /usr/share/locale/tr_TR.ISO8859-9 directory. Does this mean that LC_COLLATE is missing for tr_TR.ISO8859-9 ? Yes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating ports
What's the difference between them? The main difference that is relevant to me personally is that portmanager makes no attempt to be too smart about avoiding compilation, and it is fully restartable without affecting the results. It rebuilds ports in such a way that the result is, in theory, supposed to be equivalent to what you would have gotten had you installed them all from scratch with your current ports tree. In particular, given a re-build (e.g. upgraded) port X, all ports depending on X will also be re-built regardless of whether that is required according to the dependency relation. This is handled in such a way that it is not dependent on the entire procedure completing in one session, as you are with portupgrade (meaning it's restartable, as mentioned above). In practice, I find this is the most useful upgrading method. I have never been able to use portupgrade for more than a week or two on a real machine without running into issues (stale dependencies, failed builds due to weak dependency information, etc). That said, it's not perfect. The implementation is buggy in some ways, and there are fundamental problems with that upgrading approach (e.g., files moving between packages can cause problems). In the end I tend to either build binary packages from scratch and use portupgrade -afPP to upgrade, or do in-place upgrading with portmanager. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller [EMAIL PROTECTED]' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org signature.asc Description: This is a digitally signed message part.
recommendations wanted for best audioo wwebsite. slightly OT.
A couple months ago I happened upon what appeared to be a high end website for audiophiles. All nature of sound clips, in various formats. Looks like I did not bookmark the site and now I can't locate it. Does anybody on-list have some preferred audio site.This is, obviously, for when/if I get a working sound card swapped back it! tia, guys, gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating ports
--On December 23, 2007 1:19:21 AM +0100 Peter Schuller [EMAIL PROTECTED] wrote: In particular, given a re-build (e.g. upgraded) port X, all ports depending on X will also be re-built regardless of whether that is required according to the dependency relation. This is handled in such a way that it is not dependent on the entire procedure completing in one session, as you are with portupgrade (meaning it's restartable, as mentioned above). I don't understand this statement. I have killed portupgrade on numerous occasions, both locally and remotely, and have never had a problem restarting later. If you mean portupgrade doesn't restart where it left off, then yes, that's true, but only in the sense that it goes through all the ports checking for upgrades before returning to the build you left off at. In practice, I find this is the most useful upgrading method. I have never been able to use portupgrade for more than a week or two on a real machine without running into issues (stale dependencies, failed builds due to weak dependency information, etc). I *really* don't understand this. I can count on one hand the number of times that I've run into dependency problems with portupgrade, and all of those were addressed in /usr/port/UPDATING or by simply deinstalling and reinstalling the port in question. Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating ports
On Sat, 22 Dec 2007 18:47:52 -0600 Paul Schmehl [EMAIL PROTECTED] wrote: --On December 23, 2007 1:19:21 AM +0100 Peter Schuller [EMAIL PROTECTED] wrote: In particular, given a re-build (e.g. upgraded) port X, all ports depending on X will also be re-built regardless of whether that is required according to the dependency relation. This is handled in such a way that it is not dependent on the entire procedure completing in one session, as you are with portupgrade (meaning it's restartable, as mentioned above). I don't understand this statement. I have killed portupgrade on numerous occasions, both locally and remotely, and have never had a problem restarting later. Something like portupgrade -fr perl is pretty hard to restart efficiently. In practice, I find this is the most useful upgrading method. I have never been able to use portupgrade for more than a week or two on a real machine without running into issues (stale dependencies, failed builds due to weak dependency information, etc). I *really* don't understand this. I can count on one hand the number of times that I've run into dependency problems with portupgrade, and all of those were addressed in /usr/port/UPDATING or by simply deinstalling and reinstalling the port in question. It was really intended to handle major upgrades where multiple UPDATING instructions run together. And back in the days when Gnome upgrades involved wrapping portupgrade in a shell script run in single-user mode with a 50:50 chance of success, portmanager just took it in its stride. I think it is a useful approach because it trades a lot of cpu cycle for me not having to sober-up and think about things - and that always a win. Unfortunately, it's gone without developer support for too long now and I'm getting a bit wary about it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Understand process priority
Hi all $ ps -o pri,ni,rtprio,command -p `pgrep amarok` PRI NI RTPRIO COMMAND 20 0 normal amarokapp 1) Are there are 3 priority values per process, or just one? 2) How should I read above? Is it Priority=20, ie. NI=0, RTPRIO=normal? Does it all mean the same thing, like the bytes=1048576 and KB=1024 and MB=1? 3) The rtprio(1) says Priority is an integer between 0 and RTP_PRIO_MAX (usually 31). 0 is the highest priority. But when I run following command: $ ps aux -o pri,ni,rtprio,command USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND PRI NI RTPRIO COMMAND root 10 99.2 0.0 0 8 ?? RL7:40PM 0:00.00 [idle: cpu1] 171 0 idle:25 [idle: cpu1] root 26 0.0 0.0 0 8 ?? WL7:40PM 0:00.02 [irq18: envy24ht -80 0 intr:4 [irq18: envy24ht test 1212 0.0 9.3 58544 48176 ?? S 8:06PM 0:06.15 amarokapp 20 0 normal amarokapp That is, PID PRI NI RTPRIO 10 171 0 idle:25 26 -80 0 intr:4 1212 20 0 normal This shows priority ranges at least from -80 to 171 contrary to the range mentioned in rtprio(1). Does this means PID=26 has a higher priority than PID=1212? 4) Can a PRI=0 be considered Realtime? 5) What is the meaning of priority=0 in /etc/login.conf? Is it Realtime? 6) What is the value should I set for priority in /etc/login.conf if I want Realtime? Kind Regards Unga Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.3 or 7.0 Release?
Hi everyone, Mi question is because checking the FreeBSD 6.3 and 7.0 Release schedule, I note that version 6.3 is upcoming and few days later 7.0 will be releaced, anyone know if this schedule is updated or is in time? or only one of both will be released? Thanks and Regards, --- Julian Bolivar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.3 or 7.0 Release?
Julian Bolivar wrote: Mi question is because checking the FreeBSD 6.3 and 7.0 Release schedule, I note that version 6.3 is upcoming and few days later 7.0 will be releaced, anyone know if this schedule is updated or is in time? or only one of both will be released? My guess, informed only by knowledge of where things are currently at and how these things usually go, is that we'll see 6.3-RELEASE some time in the first week of January, and 7.0-RELEASE two or three weeks later. Colin Percival ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Redirecting STDOUT
# command file this will redirect both STDERR and STDOUT to file -- Best regards, Michael mailto:[EMAIL PROTECTED] Thank you to everyone for their help. I have this working now. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
The FreeBSD Diary: 2007-12-02 - 2007-12-22
The FreeBSD Diary contains a large number of practical examples and how-to guides. This message is posted weekly to freebsd-questions@freebsd.org with the aim of letting people know what's available on the website. Before you post a question here it might be a good idea to first search the mailing list archives http://www.freebsd.org/search/search.html#mailinglists and/or The FreeBSD Diary http://www.freebsddiary.org/. These are the articles posted during this period: 17-Dec : PC-BSD PC-BSD has a lot going for it http://freebsddiary.org/pcbsd.php?2 9-Dec : IMAP - getting Dovecot running POP implies one computer. IMAP allows many. http://freebsddiary.org/dovecot.php?2 -- Dan Langille BSDCan - http://www.BSDCan.org/ - BSD Conference ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Understand process priority
On Sat, Dec 22, 2007 at 07:09:47PM -0800, Unga wrote: Hi all $ ps -o pri,ni,rtprio,command -p `pgrep amarok` PRI NI RTPRIO COMMAND 20 0 normal amarokapp 1) Are there are 3 priority values per process, or just one? There is really only one priority that is used when scheduling processes. The other two fields (nice and rtprio) modifies how the priority is set, but do not directly affect the priority. The actual priority is handled internally in the kernel and cannot be modified directly from userland. It is always the case that if two (or more) processes both want to use the CPU at the same time, then it is the one with the highest priority which gets to use it. (The term 'highest priority' can be slightly confusing, since it is normally the process with the lowest value in the 'PRI' field which has the highest priority.) For those processes that has a real time priority (rtprio) of 'normal', i.e. most normal processes, the priority is adjusted dynamically depending on how long it has waited for CPU, and how much CPU it used the last time it ran, etc. The 'nice' value affects how quickly the priority is adjusted up or down. A high nice value means that the priority will only increase slowly and decrease quickly, while it is the other way around for processes with a low nice value. Note however that even a process with a high nice value will get at least a little CPU time now and then, even if there are processes around that are much less nice that want the CPU too. For processes with a real time priority of something other than 'normal' the priority is not adjusted dynamically. Processes with rtprio=idle always have lower priority than all other processes. Processes with an actual real time priority set will always have higher priority than non-real time processes. 2) How should I read above? Is it Priority=20, ie. NI=0, RTPRIO=normal? It is: Priority=20; Nice=0; Real time priority=normal Does it all mean the same thing, like the bytes=1048576 and KB=1024 and MB=1? No. 3) The rtprio(1) says Priority is an integer between 0 and RTP_PRIO_MAX (usually 31). 0 is the highest priority. But when I run following command: $ ps aux -o pri,ni,rtprio,command USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND PRI NI RTPRIO COMMAND root 10 99.2 0.0 0 8 ?? RL7:40PM 0:00.00 [idle: cpu1] 171 0 idle:25 [idle: cpu1] root 26 0.0 0.0 0 8 ?? WL7:40PM 0:00.02 [irq18: envy24ht -80 0 intr:4 [irq18: envy24ht test 1212 0.0 9.3 58544 48176 ?? S 8:06PM 0:06.15 amarokapp 20 0 normal amarokapp That is, PID PRI NI RTPRIO 10 171 0 idle:25 26 -80 0 intr:4 1212 20 0 normal This shows priority ranges at least from -80 to 171 contrary to the range mentioned in rtprio(1). Does this means PID=26 has a higher priority than PID=1212? rtprio(1) does not set the PRI field directly. It sets the RTPRIO field. In your example these are 'idle:25' 'intr:4' and 'normal' indicating that these are run with idle priority, interrupt priority, and normal priority respectively. (The 'intr' value in the rtprio field can probably only be set directly by the kernel for interrupt threads, and is a bit outside the normal real time priorities.) The actual idel/real time priority value set by rtprio(1)/idprio(1) is not displayed by ps(1), but can be shown by rtprio(1)/idprio(1). Yes, PID=26 has a much higher priority than PID=1212, as it should considering that PID=26 is an interrupt thread, while PID=1212 is just an ordinary, non-real time, process. 4) Can a PRI=0 be considered Realtime? No, not really. If a process does not have rtprio set to something other than 'normal' or 'idle' it is not a real time process. 5) What is the meaning of priority=0 in /etc/login.conf? Is it Realtime? No, the 'priority' field in /etc/login.conf sets the nice value. 6) What is the value should I set for priority in /etc/login.conf if I want Realtime? You can't do that. You should also not set any process to a real-time priority unless you know exactly what you are doing and why you are doing it. The normal way of setting the relative priorities of processes on Unix systems is by setting the nice value (and only root is allowed to lower the nice value.) -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
