Have the expanded rcorder behaviour merged to RELENG_5?
Hello, I saw in the Porters Handbook this OSVERSION macro: 6.0-STABLE after incorporating scripts from the local_startup directories into the base rcorder(8) http://www.FreeBSD.org/cgi/man.cgi?query=rcordersektion=8. 600101 I think that change has been merged to the RELENG_5 branch but I1m not sure. If so, could somebody tell me what is the corresponding OSVERSION for RELENG_5? And if it has been merged, this should be also listed in the Porters Handbook. Thanks, Gabor Kovesdan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UPDATE 5.4R to Stable
MoonblueZ wrote: i just update my box from 5.4R to 5.4-Stable but i got a wrong update version.. here the uname sample cidomo# uname -a FreeBSD cidomo.moonbluez.or.id 5.5-PRERELEASE FreeBSD 5.5-PRERELEASE #0: Sat Mar 11 09:28:12 WIT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CIDOMO i386 anyone know how to fix this problem? pls help me.. You got the right version. The 5.X stable branch is now called 5.5-PRERELEASE. After 5.5 gets release it becomes 5.5-STABLE. Similarly, the stable branch for 6.X is now 6.1-PRERELASE and it will be called 6.1-STABLE after 6.1 comes out. Gabor Kovesdan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UPDATE 5.4R to Stable
MoonblueZ wrote: OK... Thnx im understand about this work now but if that 5.5 is released, is that important to running update again to get to stable branch? On 3/12/06, * Kövesdán Gábor* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: MoonblueZ wrote: i just update my box from 5.4R to 5.4-Stable but i got a wrong update version.. here the uname sample cidomo# uname -a FreeBSD cidomo.moonbluez.or.id http://cidomo.moonbluez.or.id 5.5-PRERELEASE FreeBSD 5.5-PRERELEASE #0: Sat Mar 11 09:28:12 WIT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CIDOMO i386 anyone know how to fix this problem? pls help me.. You got the right version. The 5.X stable branch is now called 5.5-PRERELEASE. After 5.5 gets release it becomes 5.5-STABLE. Similarly, the stable branch for 6.X is now 6.1-PRERELASE and it will be called 6.1-STABLE after 6.1 comes out. Gabor Kovesdan It depends on your demand. If you feel like updating again, do so, if not, that's no problem. The stable branches are changing quite fluently, it's up to you, how often you update. If you don't have any problem with your installation, you don't need to update very often. Gabor Kovesdan P.S.: Please, do not top-post. Here in the list we prefer writing and reading replies below the original message. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: Release schedule for 2006
Wilko Bulte wrote: On Sat, Dec 17, 2005 at 01:54:34PM -0800, Joe Rhett wrote.. On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: There will be three FreeBSD 6 releases in 2006. While this is nice, may I suggest that it is time to put aside/delay one release cycle and come up with a binary update mechanism supported well by the OS? Increasing the speed of releases is good. Increasing the number of deployed systems out of date because there are no easy binary upgrade mechanisms is bad. It has been bad, it's getting worse. So, when will you fix it? Or hire someone to fix it? FreeBSD after all is mostly a volunteer operation. I agree. And after all, tracking a security branch isn't too difficult, but the most people think that they have to do a complete make buildworld after a security advisory, but this isn't true. For example there was that cvsbug issue in September: ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:20.cvsbug.asc One can read here: b) Execute the following commands as root: # cd /usr/src # patch /path/to/patch # cd /usr/src/gnu/usr.bin/cvs/cvsbug # make obj make depend make make install # cd /usr/src/gnu/usr.bin/send-pr # make obj make depend make make install Is that difficult? I don't think so. No reboot required and it doesn't take more than 5 minutes even on a slower machine. Only the vulnerabilities in the kernel are problematic for servers, since they require a reboot. I think I'll submit a PR with a patch to clarify this in Handbook. Do you consider this useful? Regards, Gabor Kovesdan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! 6.0-RELEASE coming
Felipe openglx wrote: On 10/28/05, Scott Long [EMAIL PROTECTED] wrote: You'll need to work with the X11 developers. X is only something that FreeBSD includes as a 3rd party package, it's not something that we work on as part of the OS. That's odd, because X11 always worked on that machine, on any linux distro and even on freebsd (4.x, 5.x, but NOT 6.x). Maybe some kernel driver changed and broke the compatibility between X11 and FreeBSD for that video card? Was that working X11 X.Org or XFree86? Older releases contains XFree86 and 6.0 contains X.Org. You can find both as a FreeBSD port under x11-servers category. Give XFree86 a try, maybe it is better for You. Cheers, Gabor Kovesdan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nve0 nvidia onboard ethernet dies daily on 6.0 beta1
alan bryan wrote: I'm still having problems with my onboard ethernet. It usually runs for a day or two and then I see this in the dmesg: ... nve0: device timeout (63) nve0: link state changed to DOWN nve0: link state changed to UP nve0: device timeout (63) nve0: link state changed to DOWN nve0: link state changed to UP nve0: device timeout (64) nve0: link state changed to DOWN nve0: link state changed to UP ... It seems that once it counts up to 64 that it then dies. What does that number count stand for? Is there a way to prevent this? Why does the link state keep going up/down (although I haven't noticed any problems and web/shh seem to work fine until it dies) This is on a Shuttle XPC SN25P system running 6.0 beta1. Thanks, Alan Bryan The nve driver has a lot of problems. You experienced just device timeouts, but other people - including me - experiences system crashes. As for me, I've had two kind of kernel panics, and device timeouts too. Cheers, Gabor Kovesdan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nve0 nvidia onboard ethernet dies daily on 6.0 beta1
alan bryan wrote: --- Kövesdán Gábor [EMAIL PROTECTED] wrote: The nve driver has a lot of problems. You experienced just device timeouts, but other people - including me - experiences system crashes. As for me, I've had two kind of kernel panics, and device timeouts too. Cheers, Gabor Kovesdan Do you (or does anyone else here) have any recommendations then on a good PCI express (no plain PCI slots) ethernet card that doesn't use the nve driver? Maybe an Intel card? Gigabit speeds preferably. I could then use that until the nve driver gets fixed (Is somebody even working on fixing it?). Thanks, Alan No, unfortunately I don't know about a good alternative. I don't think anybody is working on it now. Maxime Henrion and Quinton Dolan committed changes to that driver, but unfortunately it didn't make things better. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Summary about nve network interface driver
Hi, I've experineced serious errors with the nve driver and I've seen quite many people would like to use it, but they also experiences these error. There are open PR's and unfortunately nobody has volunteered to fix this issue, the PR's have the default Responsible field, nobody has changed it. Maxime Henrion has tried to fix the crashes, however, and asked me to test his commits in HEAD, but unfortunately things haven't become better. I've also seen, that Quinton Dolan, the original developer of this driver, has also committed something to HEAD, he was the last committer to that file when I checked HEAD, but unfortunately at moment RELENG_6 has this buggy version and so has HEAD. I've checked both. The problem is complicated, the experineced errors are quite different: -Sometimes it crashes with an attempted use of a free mbuf. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=83943 I've experineced and reported this issue in RELENG_6. There is an another report by Dmitry Selin: http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/82555 - I've also exprienced a general protection fault and I suspect it must be related to the nve driver. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=84133 I've experineced this issue in RELENG_6 and in HEAD. - Some people have device timeouts with nve. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/84027 I've also experienced it, but haven't reported, I wanted to get the crashes fixed first. I'm very interested in fixing this driver, because I would like to use FreeBSD 6.0 as my desktop os, but unfortunately I don't have the knowledge to fix this driver. If somebody would volunteer to take care, I'd do the testing in RELENG_6 or HEAD or I'd do what I'd been told to do. It would be really nice if it got fixed by the time 6.0-RELEASE gets released. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with PHP4-extensions
On 7/23/05, Jack Raats [EMAIL PROTECTED] wrote: I had installed Apache, PHP4.40 and imap on a FreeBSD 5.4-STABLE server. It worked OK. I had to recompile IMAP and after this apache refuses to start. I have to recompile the php4-imap part of php. How to do this? Deinstall php4 completely and then reinstall it or Can i use the extensions to recompile only a part? Met vriendelijke groeten Jack Raats Just delete only php4-imap with pkg_delete, then mkdir to /usr/ports/lang/php4-extensions and make config. Make only imap part selected and make FORCE_PKG_REGISTER=YES install. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
What to do when panic?
Hello, I've never debugged FreeBSD, but now I've decided to help the testing process of FreeBSD 6. I installed it, and then I had a panic. I got a debugger prompt, but I don't know what to do with that. I don't know the debugger commands. Please let me know what should I do when I have an another panic. What should I type and what kind of information should I send as a PR. Thanks, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Silent crash on FreeBSD 6.0-BETA1
Hi, I've installed FreeBSD 6.0-BETA1 and if I use more consoles I have a silent crash. The cursor won't move and I can't change back to another console. It has happened three times so far when I was using two consoles. (I was using make + ee in the first two cases and in the third case cvsup + less.) How can I find out what's wrong? I suspect it is some kind of hardware support issue since I have a fairly new PC. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
rcNG issue
Hello, I have a problem with my rcNG scripts. There are three scripts: named.sh, apache2.sh and proftpd.sh. Apache and ProFTPd require hostname resolving thus named should start firstly. The headers of my scripts are: named.sh: #!/bin/sh # # PROVIDE: named # REQUIRE: SERVERS # BEFORE: apache2 proftpd mysqld # KEYWORD: FreeBSD shutdown . /etc/rc.subr apache2.sh: #!/bin/sh # # PROVIDE: apache2 # REQUIRE: NETWORKING SERVERS named # BEFORE: DAEMON # KEYWORD: FreeBSD shutdown . /etc/rc.subr proftpd.sh: #!/bin/sh # # PROVIDE: proftpd # REQUIRE: DAEMON # BEFORE: LOGIN # KEYWORD: FreeBSD shutdown . /etc/rc.subr And when I enable all the three scripts in rc.conf, the apache hangs because it can't resolve the computer's hostname. It's really annoying, I have to manually start it after a reboot, or wait for the cronscript that checks whether it is running. What's wrong? Thanks in advance, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND vs. mac_portacl
David Malone wrote: If you don't actually want to use IPv6, you could give explicit addresses to named using the listen-on and query-source directives. Alternatively, a kernel without IPv6 might work. I don't have IPv6 support in the kernel. Anyway, I tried to set those directives in named.conf, but I got the same error. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
BIND vs. mac_portacl
Hello, I've loaded the mac_portacl module but BIND doesn't properly work with it. My sysctl values: net.inet.ip.portrange.reservedlow: 0 net.inet.ip.portrange.reservedhigh: 0 security.mac.portacl.rules: uid:55:tcp:53,uid:55:udp:53,uid:55:tcp:953,uid:55:udp:953 security.mac.portacl.port_high: 1023 security.mac.portacl.suser_exempt: 1 security.mac.portacl.enabled: 1 Thus, my system behaves in the standard UNIX way, root should be able to bind to privileged ports. It is very common that softwares bind to a privileged port as root and then change tu an unprivileged user. So does BIND with the -u switch, but when I start it in this way with this command line: /usr/local/bind/sbin/named -u bind -t /usr/local/bind -c /etc/named.conf , I get: Jul 4 23:58:13 server named[18476]: socket.c:2885: unexpected error: Jul 4 23:58:13 server named[18476]: bind: Operation not permitted Jul 4 23:58:13 server named[18476]: socket.c:2885: unexpected error: Jul 4 23:58:13 server named[18476]: bind: Operation not permitted Jul 4 23:58:13 server named[18476]: socket.c:2885: unexpected error: Jul 4 23:58:13 server named[18476]: bind: Operation not permitted Jul 4 23:58:13 server named[18476]: socket.c:2885: unexpected error: Jul 4 23:58:13 server named[18476]: bind: Operation not permitted Jul 4 23:58:13 server named[18476]: socket.c:2885: unexpected error: Jul 4 23:58:13 server named[18476]: bind: Operation not permitted The bind user has the uid 55. I've added a rule for it, as You can see, but it doesn't help. I get this error with the ruleset can be seen above, and also without any rules. But apache works. It can change to the www user. Proftpd can change to the proftpd user. BIND is the only one that doesn't work. What's wrong? Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Old messages
So did I. Andy Gilligan wrote: Ok, is it just me or did anyone else receive a bunch of mails to -stable from about 6-7 months ago? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctls issue
Hello, I think the net.link.ether.inet.log_arp_movements and net.link.ether.inet.log_arp_wrong_iface sysctls should control the arp messages in /var/log/messages. I don't want to see this kind of errors, thus I've set them to 0. Now there mustn't be any arp logs in /var/log/messages, must they? Actually, there has been one since I set the two sysctls: Jun 28 12:51:42 server kernel: arplookup 195.70.50.6 failed: host is not on local network Before I set them to 0, there had been much more arplookup messages, just the same as I wrote above. Have I missed something? Or should I post this issue as a bugreport? Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdextended mac module question
I think you'll need to allow stat permission too - say rxs not just rx. You may also want to think about what this rule does to /tmp. David. Works fine in this way, thanks. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
bsdextended mac module question
Hello, I try to make a bsdextended mac policy and when I add the following rule, I can't login with a simple user: ugidfw add subject not uid root object uid root mode rx This rule is for protecting root's files from others in any case. And I've got the following message: /libexec/ld-els.so.1: Cannot fstat /lib/libedit.so.4 Jun 27 10:36:25 localhost login: _secure_path: cannot stat /etc/login.conf: Permission denied What's wrong? Btw, could somebody tell what the a mode means in bsdextended rules? Thanks, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: index.php
Maher Mohamed wrote: how can i make my server link to be redirected to the index.php i hve a web page at http://150.140.210.79:2005/~mahmoh the thing is that if i make the index.html to index.php the whenever i go to the url above i have to add the extra /index.php can i get rid of that? is there a way? -- Mohamed M. Maher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] You should modify your DirectoryIndex line in httpd.conf in such way: DirectoryIndex index.html index.html.var index.php index.phtml According to that, the webserver firstly looks for index.html, if it doesn't exist, then for index.html.var... The index.php is the third in this example, but You can use a different order. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: auto cvsup
Maher Mohamed wrote: how can i upgrade my cvsup weekly with an auto way? You should use crondaemon. Place the following line to the end of /etc/crontab: 15 4 * * 6 rootcvsup /some/path/to/supfile The number six represents the sixth day of the week, the 15 is the minute number and the second is the hour, thus this will run on every Friday (if I remember correctly, I'm not sure the numbering starts with Sunday) at 4:15. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/local/etc/rc.d/*.sh not working?
For scripts in /usr/local/etc/rc.d You should add an entry to /etc/rc.conf. For example, if You script is somedaemon.sh, then add somedaemon_enable='YES' to /etc/rc.conf and it will run at the next boot. Cheers, Gábor Kövesdán Michael W. Lucas wrote: I'm certain this is documented somewhere, but danged if I can find it. I have a whole variety of custom scripts in /usr/local/etc/rc.d. For years now, simply giving them a name ending in .sh and making them executable has been sufficient to make them start on boot. On 5.x, it's not. And now, having upgraded to 4.11-s on some older boxes and running portupgrade -a, it's not. Obviously these scripts need something else. There's no fancy rcNG infrastructure in them; is rcNG a requirement for startup scripts now? Any pointers on where I can find the right documentation? Thanks, ==ml ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CPUTYPE for Sempron
Hello, use CFLAGS=-march=atlhlon-xp. CPUTYPE overrides CFLAGS, so it doesn't provide You such sophisticated optimizations. If You plan to make buildworld, use: CFLAGS=-O2 -pipe -march=athlon-xp Anyway, if You just use ports collection, and don't make buildworld CFLAGS=-O3 -pipe -march=athlon-xp is also reliable, but it might make some trouble when making buildworld. Cheers, Gábor Kövesdán Mike Jakubik wrote: Which CPUTYPE should be used for the AMD Sempron CPU? I'm assuming this is similiar to an athlon-xp. Perhaps an alias or a new entry should be created for this CPU? --- CPU: AMD Sempron(tm) Processor 3000+ (1799.81-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x10fc0 Stepping = 0 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xc050NX,AMIE,DSP,3DNow! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Abort rap from cron
No, I don't have anything in syslog, but I've relaized, when I run make, these errors happen more often. You mentioned, there this is a common problem on SMP systems when one start more processes simultaneously, but it is a single processor system. Might this error also exist on single processor systems? Gábor OK, some binary is probably calling abort() explicitly then. You should have a record in your syslog. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Abort rap from cron
Hello, since I upgraded to 5.3-p15 from 5.3 the cron daemon sometimes send me an e-mail, that contains Abort trap. Nothing seems to go wrong anyway, but it might be a source of troubles, if my cron scripts can't run normally. Do You know anything about this effect? Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Abort rap from cron
It is a single processor system. Those cron scripts are to verify whether my processes are run. So, there isn't such simultaneous runs. They are small scripts, that send a SIGCHLD to the processes they are responsible for, and if they don't find the processes running, they restarts them. I've been surprised because this hadn't happened before I upgraded to 5.3-p13. Not only my scripts caused this, even the atrun, which is a default entry in the stock /etc/crontab. This can happen on SMP machines if you exec a lot of processes at once (more than 16 simultaneous execs). 5.4 contains the vm.exec_map_entries tunable that allows you to increase this number. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 forgets some of my users
Gordon Tetlow wrote: Don't edit the /etc/passwd and /etc/master.passwd files directly, you get into a lot of trouble. Use vipw or the pw command. I haven't done that... I always add a user with adduser and delete it with pw userdel. Also, please don't crosspost between current and stable. Please post to whichever branch your machine is following. -gordon Okay, I won't, I apologize. I've been already told that by the postmaster. I just thought that it might be present in current. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 forgets some of my users
Thanks for your suggestion. I use 'files' lookup. As You wrote I checked the syntax with pwd_mkdb -C /etc/passwd' and it returned nothing. Then I did a rebuild with -p, and now it seems to be okay, the two accounts that had gone away are working now. Anyway I haven't changed the nsswitch.conf, I have the default one: [EMAIL PROTECTED] less /etc/nsswitch.conf group: compat group_compat: nis hosts: files dns networks: files passwd: compat passwd_compat: nis shells: files Cheers, Gábor Kövesdán What are you using for user lookups? Are you using nss_ldap or something other than the default 'files' lookup? Can you post the contents of /etc/nsswitch.conf? I'd also check your master.passwd file for any syntax errors or odd characters and then force a rebuild with: pwd_mkdb -p /etc/master.passwd as root. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Making release with EXTSRC tag
Hello, I'm about to build an own install disc from 5.3-RELEASE-p15 but I don't want to mirror the whole CVS repo. I have my RELENG_5_3 source tree in /usr/src and according to this I edited my /usr/src/release/Makefile. I set the EXTSRC macro to /usr/src and I did a 'make buildworld' to fill /usr/obj with the system binariesand then I changed to /usr/src/release directory and I typed: 'make MAKE_ISOS=YES MAKE_FLOPPIES=YES CVSROOT=/usr/src release'. I had to set CVSROOT macro, because the Makefile requires it even if I use EXTSRC and do not want to checkout anything. The release process stopped with this: if [ -f /etc/resolv.conf ]; then cp -p /etc/resolv.conf /home/tux/release/etc; fi rm -rf /home/tux/release/usr/src cd /home/tux/release/usr cp -R -H /usr/src src rm -rf /home/tux/release/usr/ports cd /home/tux/release/usr cvs -R -d /usr/src co -P ports cvs [checkout aborted]: /usr/src/CVSROOT: No such file or directory *** Error code 1 Stop in /usr/src/release. Do You have any experience with this? What can I do now? Btw, I uploaded the Makefile: http://tux.t-hosting.hu/Makefile Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3 forgets some of my users
Hello there, there is a strange thing FreeBSD 5.3 randomly frogets some of my users. Sometimes I see in the first column of the ps aux output the uid number instead of the login name, but next when I run it, there is the login name. Besides, I tried to chown a directory to an existing user, but the I get an error message, that there wasn't such user. I immediately checked passwd, group and master.passwd files in /etc but the entry for that user was present there. The pw userdel was unable to delete that user, so I had to manually remove it from those three files and create it again. It worked then, but a bit later there was the same result. I'm quite annoyed now. This state isn't safe enough, I have to do something to get around with this. Do You have similar experiences? Or do You now some kinda workaround? Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CUPDS reboot the whole system
Try this: nohup /usr/local/sbin/cupsd /dev/null The nohup cmd executes the parameter and it will be still running if You log off. The sign means that the command should run in the background, and /dev/null redirects the stdout of cupsd to dev/null. I often use that way and it is fine for me. Todor Dragnev wrote: Hello, Before a couple of days ago I started /usr/local/sbin/cupsd manualy from console. When I press CTRL+C to interrupt a program, the system change runlevel and going to reboot. This was on FreeBSD V5.3, today I installed fresh new 5.4 but the problem is the same. cups-base-1.1.23.0_3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making a FreeBSD iso
Yes, it seem to be easy if You download the whole CVS repo. In my case I don't want to do this since I only want to build a RELENG_5_4 system for productional use with optimized CFLAGS, and with some other customizing in make.conf. (e. g. I don't want to build named, I prefer installing it via ports collection, I don't want to build PPP-related stuffs since they are useless for me, etc.) If You read through the Makefile in /usr/src/release (/usr/src is the directory where the RELENG_5_4 source is located), You can find that there is an EXTSRC knob for this purpose, but unfortunately it didn't work, the make complained about the missing CVS repo. If somebody knows a solution for this trouble, please let me know. I'll provide the actual error message and the whole Makefile if neccessary. Cheers, Gábor Kövesdán Tommi Lätti wrote: On 16 May 2005, at 15:24, Jack Raats wrote: I want to make a FreeBSD ISO so I can install it on other machines. I have a working FreeBSD machine with the latest kernel and binaries. Is there a port or other utilities? Where can I find info about this (URL's please) How about using Google at least once before posting questions? letsee... www.google.com... making a freebsd iso and then click I'm feeling lucky *chichinng* It seems I was lucky :) first hit: http://romana.now.ie/writing/customfreebsdiso.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alright you primitive screwheads, LISTEN UP!!
Dear Bill and everyone, just a little comment: as far as I know there are two countries where the first name and the family name is used in different order, and these two countries are Japan and Hungary. I'm Hungarian thus my name often get people confused. Since I write from my private address, You can read in the From field my name in the Hungarian order: family name, first name, but I sign every mail in the English order. Thus my first name is Gábor, and my family name is Kövesdán. If You read international mailing lists, You should take note of that. Cheers, Gábor Kövesdán Bill Paul wrote: Ok everyone, PAY ATTENTION! Drop whatevery your doing for the next five minutes and READ THIS!! You see that header on this e-mail? You see the From: line? Go and read it to yourself. Read the name. Say it to yourself, out loud. No no, go back and do it again. Again! You see what is says? It says Bill Paul. It does *NOT* say Paul Bill, does it now. WELL DOES IT!!?!?! No, it damn well doesn't! And yet, for some incomprehensible reason. the majority of you nitwits seem to think it does!! Get this through your miserable little heads: my first name is BILL!!! Understand that? Bill! BEE EYE ELL ELL!!! _ ___ _ | _ \ |_ _| | | | | | | | | | |_) | | | | | | | | | | | | _ | | | | | | | | | | | |_) | _| |_ | | | | |_| |_| |/ |_| |__| |__| (_) (_) I can carve it into your skull with a rusty railroad spike if that would make it easier to remember! Do **NOT*** send me e-mails opening with Dear Paul! That is _NOT_ my name! I don't care if you don't speak english as a first language, are distracted, tired, confused, retarded or the President of the United States: if you can't manage to scrape together enough neurons to correctly choose which one of two lousy syllables to use when addressing me, then I would rather never hear from you at all!! I am not kidding around here! I've been beating my brains out for you rotten bastards for ten lousy years, and after all that time I expect you to at least do me the courtesty of GETTING MY STUPID NAME RIGHT! This crap has been going on for years. It ends now. Anybody who's dumb enough to send me an e-mail addressed to Paul instead of Bill will be permanently banned from my inbox. I don't care if you're on fire and need me to put you out: you will become persona non grata and you will stay that way. Furthermore, anybody who screws up and gets my name wrong in person will quickly find themselves beaten, ground into a fine powder and sprinkled over Richard Stallman's oatmeal!!! And no, I don't want to hear your lousy comments on the matter! Don't follow up!! Don't reply!! Just nod quietly and DON'T MAKE THIS MISTAKE AGAIN -Bill SEE!!! LOOK!!! IT'S RIGHT THERE! IDIOTS! -- = -Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu [EMAIL PROTECTED] | Wind River Systems = adamw you're just BEGGING to face the moose = ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: securelevel and make installworld
Ronald Klop wrote: On Wed, 20 Apr 2005 16:28:06 -0500, Jon Noack [EMAIL PROTECTED] wrote: On 04/20/05 15:16, Ronald Klop wrote: Can make installworld complain on startup if I try to run it with securelevel 0. It will fail half way through on some files with nochg flags or something like that. Design feature: 'schg' is the system immutable flag. Some system files are installed with 'schg' for security reasons; installworld must remove this flag in order to install a new version of these files. However, when securelevel 0 system immutable flags may not be turned off (see init(8)). An attempt to remove the system immutable flag (set 'noschg') will therefore fail. As a result, installworld fails. Canonical answer: Reboot into single user mode to perform the installworld as documented in UPDATING and section 19.4.1 of the handbook. I understand the problem, otherwise I wouldn't have securelevel 0. Doing a remote install in single user mode isn't always possible. And than it isn't very nice to break the installworld with an error. Using the idea of 'fail early' it would be very nice too have a check for securelevel in the installworld Makefile. Ronald. Check in the Makefile? Why don't You check Your securelevel with sysctl -a | grep kern.securelevel? But how don't You remember which securelevel are You using? You probably have your own habits in system administration. As for me I always use 2, which is convenient for me, because I often have to modify ipf/ipfw rules. Anyway, make installworld is the most secure in single user mode. I had a critical failure by making installworld without booting single user mode and my system didn't boot any more. I had to reinstall everything. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
Marc Olzheim wrote: On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. Any reasons for not using NFS ? I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . (same pb with a 5.3). Am I missing something obvious? I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the loader isn't. A workaround, no using NFS, could be to tftp a second filesystem image on boot and mount that from the root filesystem. Marc I assume that the PXE clients are diskless clients. If so, do they have enough memory to handle this extremely large image? As for tfpt, it uses UDP. UDP is usually used for transfer small datagrams, for instance DNS replies. It is also said to be an unreliable protocol. The client should repeat the request when no data receives. I doubt this solution is reliable and flexible enough. My idea for a workaround is creating a ramdisk from a small boot image, and transfer the less necessary userland binaries from the boot server to the ramdisk using normal ftp connection. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Question About System Update
This is generally not the case. Unix lets you continue to access a file after it has been deleted, so long as the process hangs on to a file descriptor. This lets you replace programs in use, without running into the same problems that platforms like Windows have. Though this is true, I discourage You to upgrade a running system. I tried to upgarde 5.3-RELEASE to 5-STABLE without booting to single user mode. I simply sent a TERM signal to most of the processes, and tried to make installworld. There was some error messages, the system crashed and didn't boot anymore... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
