Re: [summary] Re: burncd 'blank' not terminating ?
Hello! On Tue, 26 Dec 2006, Luigi Rizzo wrote: I suggest the following two fixes: 1. change burncd.c as below, so that if CDRIOCGETPROGRESS does not return anything good, it calls CDIOCRESET to determine when the command is complete. This can be improved by calling CDIOCRESET unconditionally as a termination test 2. change atapi-cd.c to return something even if ATA_SENSE_VALID is unset. Apparently there is a lot of non-complying hardware around so restricting to what the spec says is like shooting ourselves in the foot. Again, if burncd.c uses CDIOCRESET to determine the completion of the 'blank' operation, we don't care if the return value from CDRIOCGETPROGRESS is incorrect, because we don't rely on it. Patches below (to be improved to make CDIOCRESET unconditional). Does this satisfy all ? Thanks, Luigi, you rule OK! As I've said before, atapi-cd.c part of these changes seems to be effectively NOOP with my TEAC's drive acd0: CDRW CD-W540E/1.0C at ata1-master UDMA33 But burncd.c patch definitely works! It's output is somehow ugly: [EMAIL PROTECTED] burncd -f /dev/acd0 -s 10 blank blanking CD - 17sec 0 % done -1(interim status) blanking CD - 39sec 0 % done 0 (final status) [EMAIL PROTECTED] but the operation finishes w/o pressing Ctrl-C. Now I can use aggregate commands such as 'blank data xxx fixate': [EMAIL PROTECTED] burncd -f /dev/acd0 -s 10 blank data memtest86+-1.65.iso fixate blanking CD - 39sec 0 % done 0 next writeable LBA 0 writing from file memtest86+-1.65.iso size 900 KB written this track 900 KB (100%) total 900 KB fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error [EMAIL PROTECTED] Fixate still issues 'ioctl(CDRIOCFIXATE): Input/output error', but AFAICT the resulting media is OK. Thank you again for digging this problem! cheers luigi Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Loader reboots while loading kernel
Hi there! I'm facing really strange problem - after upgrading from 6.1-prerelease to 6.1-stable, and then - to 6.2, the new loader can't load neither my custom kernel, nor generic one. I've posted a PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/104473) Some guys suggested me to change my motheroard to new one, I recently upgraded to ASUS P5PE-VM (i865) - but that didn't solve the issue - the loader still reboots before it loads kernel. The old loader from 6.1 prerelease works great. Is there anything I can do with that, may be modify some files/add some debug statements to loader etc? -- Eugene N Dzhurinsky ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possibility for FreeBSD 4.11 Extended Support
Robert Joosten wrote: Someone pointed out to disable rpc.lockd completely but that doesn't help either. Unless the pxe-clients have to do something on their end I'm not aware of. Another stated rpc.lockd is broken for years now and we should implement a dummy one accepting and positively ack all locks while doing nothing actually. That should work as long as you know what you're doing :-D My pxe clients all have separate directories so concurrent locks on one specific file shouldn't occur. In that case you can savely mount with the -L option (a.k.a. -o nolockd), an everything will just work. No need for rpc.lockd at all. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll. -- Frank Klemm, de.comp.os.unix.discussion ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possibility for FreeBSD 4.11 Extended Support
Hi, In that case you can savely mount with the -L option (a.k.a. -o nolockd), an everything will just work. No need for rpc.lockd at all. Hmm, yes. Fiddling in etc/fstab and /etc/rc.d/initdiskless didn't help. Where am I expected to fiddle to enable this ? Browsig through archives I learned this was told me once before; I already thought -L sounded sooo familiar... Thanks for pointing me once again :-) Kind regards, Robert Joosten ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
rsync fails to write
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, I use:
FreeBSD m.mycompany.com 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #2:
Thu Nov 2 13:58:09 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/m amd64
I use rsync to synchronize 2 servers (rsync versions are same on both
machines).
Most of the directories are copied fine, however, some huge ones give
me strange output.
Rsync guys detected this problem as:
So the write fails on descriptor 3, which I think is the socket to the
daemon. I Googled FreeBSD write EPERM and turned up the following
FreeBSD bug, which you might be seeing:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F95559
here is the detailed output of the error:
truss rsync -atlrpogHvv [EMAIL PROTECTED]::public
- - --password-file=/root/rsync_pass /home/public
lstat(Company/General/2006 OLD
ARRIVALS/ARRV112106.xls,0x7fffc620) ERR#2 'No such file or directory'
lstat(Company/General/2006 OLD
ARRIVALS/ARRV112206.xls,0x7fffc620) ERR#2 'No such file or directory'
lstat(Company/General/2006 OLD
ARRIVALS/ARRV112706.xls,0x7fffc620) ERR#2 'No such file or directory'
lstat(Company/General/2006 OLD
ARRIVALS/ARRV112806.xls,0x7fffc620) ERR#2 'No such file or directory'
lstat(Company/General/2006 OLD
ARRIVALS/ARRV112906.xls,0x7fffc620) ERR#2 'No such file or directory'
select(5,{4},{3},0x0,{60 0}) = 1 (0x1)
write(3,0xc2,4092) ERR#1 'Operation not permitted'
rsync: writefd_unbuffered failed to write 4092 bytes [generator]:
Operation not permitted (1)write(2,0x7fffa4f0,93) = 93 (0x5d)
write(2,0x80083ce67,1) = 1 (0x1)
sigaction(SIGUSR1,{ SIG_IGN
0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|NODEFER|NOCLDWAIT|SIGINFO ss_t
},0x0) = 0 (0x0)
sigaction(SIGUSR2,{ SIG_IGN
0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|NODEFER|NOCLDWAIT|SIGINFO ss_t
},0x0) = 0 (0x0)
getpid() = 42660 (0xa6a4)
kill(0xa6a5,0x1e)= 0 (0x0)
rsync error: received SIGUSR1 (code 19) at main.c(1095) [receiver=2.6.8]
rsync error: error in rsync protocol data stream (code 12) at
io.c(1124) [generator=2.6.8]write(2,0x7fffa480,90) = 90 (0x5a)
write(2,0x80083ce67,1) = 1 (0x1)
SIGNAL 20 (SIGCHLD)
SIGNAL 20 (SIGCHLD)
wait4(0x,0x7fffb394,0x1,0x0) = 42661 (0xa6a5)
wait4(0x,0x7fffb394,0x1,0x0) ERR#10 'No child
processes'
sigreturn(0x7fffb3b0)= 524288 (0x8)
exit(0xc)
process exit, rval = 3072
Please advice me what to do next. Thank you in advance.
Ilya.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFko4PbE0+gtjqpZoRAuULAJ9pbOFgVSEdi6/ZVsTXMGGQXiFJhQCfdBA7
78tbKyYfXt5GWbKEKGFctJA=
=E50t
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: aaccli on recent conrollers?
On Dec 27, 2006, at 10:31 AM, Andrew N. Below wrote: Latest Adaptec drivers released at 25 Oct 2006, aaccli says Copyright 1998-2002... Maybe someone already tried to contact Adaptec? I did a diff of the adaptec sources and the ones in freebsd 6.2- PRERELEASE and there are mostly minor differences (the device name changes, for example.) I'm in touch with Scott Long regarding sponsoring some work in this area to create a command line utility for monitoring the status on these new controllers. He's waiting for some libraries from Adaptec at this point. If you're interested in sharing the cost of this work please let me know. So far everyone else who's contacted me regarding this issue has not committed any money, which is fine. If I have to pay for the whole thing I will, because I believe in giving back to the community.
Re: aaccli on recent conrollers?
Hi Vivek and oths... - Original Message - From: Vivek Khera [EMAIL PROTECTED] To: FreeBSD Stable freebsd-stable@freebsd.org Sent: 10 ноября 2006 г. 19:42 Subject: aaccli on recent conrollers? I have just built a new SunFire X4100 server with an Adaptec 2230SLP RAID card using FreeBSD 6.2-PRE kernel (from September 20). Everything is working extremely well except I cannot run the aaccli utility on this controller. When I try to open the controller, it gives this error: Command Error: The current AFAAPI.DLL is too old to work with the current controller software. The same error I get with Adaptec SATA RAID 2420S (aac0 controller device, aacdX volume devices) with latest controller firmware. I have just tried to install aacu.ko module from original Adaptec's drivers, but still got no success: aacu0: Adaptec SATA RAID 2420SA mem 0xb8a0-0xb8bf,0xb8c0-0xb8c00fff irq 24 at device 3.0 on pci6 aacu0: New comm. interface enabled aacu0: Adaptec Raid Controller 2.0.7-1 aacdu0: RAID 1 (Mirror) on aacu0 aacdu0: 238289MB (488015872 sectors) aacdu1: Volume on aacu0 aacdu1: 238289MB (488015872 sectors) CLI open aac0 Executing: open aac0 Command Error: The current AFAAPI.DLL is too old to work with the current controller software. Latest Adaptec drivers released at 25 Oct 2006, aaccli says Copyright 1998-2002... Maybe someone already tried to contact Adaptec? -- Andrew N. Below Zenon N.S.P. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Status of FreeBSD 6.2?
On Tuesday 26 December 2006 01:49 pm, Martin Blapp wrote: Build 6.2-RC2 24 December 2006Begin building the second release candidate build for all Tier-1 platforms. http://www.freebsd.org/releases/6.2R/schedule.html Note: Only the actual column for RC2 has been updated. The expected column for everything that follows still lists dates in Oct/Nov timeframe. I think this is what Brett is asking about: and update on the expected timeframe. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
What ever happened to FreeBSD 6.2 RELEASE?
And then I suddenly see a new thread about FreeBSD 6.2 status appear ... after I sent the email. Sorry for the noise. I have been following the release candidates for some time. Suddenly, progress seems to have halted, but checking this list from time to time have revealed no discussion that I have noticed. According to this site, it was expected more than one month ago? http://www.freebsd.org/releases/6.2R/schedule.html Can anybody explain what is going on? Thanks in advance, Tom Veldhouse ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
What ever happened to FreeBSD 6.2 RELEASE?
I have been following the release candidates for some time. Suddenly, progress seems to have halted, but checking this list from time to time have revealed no discussion that I have noticed. According to this site, it was expected more than one month ago? http://www.freebsd.org/releases/6.2R/schedule.html Can anybody explain what is going on? Thanks in advance, Tom Veldhouse ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Status of FreeBSD 6.2?
If memory serves me right, Freddie Cash wrote: On Tuesday 26 December 2006 01:49 pm, Martin Blapp wrote: Build 6.2-RC2 24 December 2006Begin building the second release candidate build for all Tier-1 platforms. http://www.freebsd.org/releases/6.2R/schedule.html Note: Only the actual column for RC2 has been updated. The expected column for everything that follows still lists dates in Oct/Nov timeframe. I think this is what Brett is asking about: and update on the expected timeframe. The bits for 6.2-RC2 are making their way to the FTP mirrors now (if they're not there already). I think it should be possible to announce 6.2-RC2 today. The current, tentative plan is to start building 6.2-RELEASE about a week and a half after the 6.2-RC2 announce date (again, that might be today), and then announce 6.2-RELEASE a few days later. This assumes that there aren't any (more) last-minute problems. The situation has been fairly fluid over the last month or so, due to various problems that keep showing up at inconvenient times...everything from last-minute bugs to ftp-master's RAID blowing up. I admit we haven't been real communicative about the status of the release. :-p Bruce. signature.asc Description: OpenPGP digital signature
Re: What ever happened to FreeBSD 6.2 RELEASE?
On Wed, Dec 27, 2006 at 11:31:02AM -0600, Thomas T. Veldhouse wrote.. I have been following the release candidates for some time. Suddenly, progress seems to have halted, but checking this list from time to time have revealed no discussion that I have noticed. According to this site, it was expected more than one month ago? http://www.freebsd.org/releases/6.2R/schedule.html Can anybody explain what is going on? Holy smokes... don't you people ever read the mailing lists? There have been numerous posts explaining that various problems, incl. hardware failures in the FreeBSD.org machine farm have delayed the release process. -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: bus_dmamap_load_mbuf_sg still there
Hi, this panic has been reported a few times in the past, both by me and other people; I just updated my Soekris box to 6.2-RC2 and it's still happening. panic: bus_dmamap_load_mbuf_sg: no mbuf packet header! KDB: stack backtrace: panic(c06128c3,c060f93c,c055b9af,c0db804e,c0db803e,...) at panic+0xef bus_dmamap_load_mbuf_sg(c0d18e00,0,c0db8000,c0d627d8,c0d627b8,1) at bus_dmamap_load_mbuf_sg+0x4ec ath_start(c0d55000,35000,36,0,c100,...) at ath_start+0x26f ether_output_frame(c0d55000,c0fee600,c106,0,1,...) at ether_output_frame+0x226 ether_output(c0d55000,c0fee600,c56f6bb0,c0feb840) at ether_output+0x2de ip_output(c0fee600,0,c56f6bac,1,0,0) at ip_output+0xaad ip_forward(c0cf9648,c56f6c78,c04e14dd,c066ca40,1,...) at ip_forward+0x120 ip_input(c0fee600,18,c0673378,c56f6cec,c0541fd7,...) at ip_input+0x8d5 netisr_processqueue(c0d12240,c0cef400,0,c56f6d0c,c04bd93b,...) at netisr_processqueue+0x13 swi_net(0,c0cef438,c0cfaa80,c04bd740,c0cf9648,...) at swi_net+0x97 ithread_loop(c0ce8750,c56f6d38,c0ce8750,c04bd740,0,...) at ithread_loop+0x1fb fork_exit(c04bd740,c0ce8750,c56f6d38) at fork_exit+0x83 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xc56f6d6c, ebp = 0 --- KDB: enter: panic [thread pid 13 tid 13 ] Stopped at kdb_enter+0x2c: leal0(%esi),%esi It has been suggested that it may be pf-related, but I don't have a clue on how to go about digging more info out. Any idea? Bye, Andrea -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2-RC2 Available
First, sorry for the long dry spell on information about 6.2-RELEASE. I should have been sending out periodic status reports when we started to hit a few delays. Since RC1 we have been working out a few more bugs in device drivers, a few device drivers were updated, BIND was updated, and bugs in several other areas of the kernel have been worked out. We also wound up having hardware problems with the primary distribution machine that took some time to resolve. All problems we felt needed to be addressed before 6.2 could be released have been taken care of. Unless further testing turns up something new RC2, which is available now for dowloading, will be the last of the Release Candidates and 6.2-RELEASE should be ready in about 2 weeks. Your continued help with testing would be greatly appreciated. If you notice any problems with RC2 you can submit a PR or send mail to this list. Checksums for ISOs: MD5 (6.2-RC2-alpha-bootonly.iso) = e6ea204d3e3b0e20ebc561c7b1d52150 MD5 (6.2-RC2-alpha-disc1.iso) = a3578cfd41bf9fb0fb258ea0da64a085 MD5 (6.2-RC2-amd64-bootonly.iso) = 11cbf691c78322f9a0d2a14e0651df19 MD5 (6.2-RC2-amd64-disc1.iso) = f1477df9bc3ba45a3ea6521708b09b35 MD5 (6.2-RC2-amd64-disc2.iso) = 0420385ee1617b807ca304efef815d97 MD5 (6.2-RC2-amd64-docs.iso) = e5312592494c0a2d8c9dff37c4ceab5d MD5 (6.2-RC2-i386-bootonly.iso) = 3438ecae6bd8b8c5fd832bbf1e4b87e2 MD5 (6.2-RC2-i386-disc1.iso) = 1703e562f4e265debc56712165b1c32f MD5 (6.2-RC2-i386-disc2.iso) = b2a80388bf05b637a9d8a5ed6a030454 MD5 (6.2-RC2-i386-docs.iso) = f0e796a1e66f982f337dcbca48daf513 MD5 (6.2-RC2-ia64-bootonly.iso) = 490f249e24e640e74e2b5d7f2f5f7043 MD5 (6.2-RC2-ia64-disc1.iso) = fb594f597af2b266ed541e80f500012b MD5 (6.2-RC2-ia64-disc2.iso) = e0721e4bf39043198a8764ec7ef16508 MD5 (6.2-RC2-ia64-docs.iso) = 199b62b4d388689766fced2ca320f0e2 MD5 (6.2-RC2-ia64-livefs.iso) = e499b3fc6fdbb54129a77c9b603c6ae3 MD5 (6.2-RC1-pc98-bootonly.iso) = 43df2d851438b5212faa81e456190ae5 MD5 (6.2-RC1-pc98-disc1.iso) = ba33bc96d1c416f16e123d43c88110da MD5 (6.2-RC2-sparc64-bootonly.iso) = b978eb34fd5862a50332a0cb3bb880fa MD5 (6.2-RC2-sparc64-disc1.iso) = 04cff1890eb3b798ade0e2d0f64753a9 MD5 (6.2-RC2-sparc64-disc2.iso) = 2775c4325fc14a16226228969ff4221d MD5 (6.2-RC2-sparc64-docs.iso) = 54e2a7ed7efd4f985bc9ae1d0e7fc369 SHA256 (6.2-RC2-alpha-bootonly.iso) = 19321abedf91c58972c43319281f0786c10ad8d17c3d43fca6d1abd1967af7df SHA256 (6.2-RC2-alpha-disc1.iso) = 497f1b96960b1025f0100cbfcee1c714bdf7f6e9960646f59dbff3abdd779026 SHA256 (6.2-RC2-amd64-bootonly.iso) = 28650201578ad75ff09d2e4b61794a08e46e65076c6f794c1b8688c69d37ec21 SHA256 (6.2-RC2-amd64-disc1.iso) = 43c934950d65c8b2412ed4b367ef3ec08eb46ab103620165bad093ef90d478a6 SHA256 (6.2-RC2-amd64-disc2.iso) = 2e370e2d5c637a18ff0413c12f72b3c8a6332a164b033683387e8513bdd96831 SHA256 (6.2-RC2-amd64-docs.iso) = 605a045b5b44677f0a717310f871dd6988e0cd8d1edc82a52180210d3696d027 SHA256 (6.2-RC2-i386-bootonly.iso) = 1e3aefc186d37b2813b0d6e00ad6879f4906de8a4f4c0c156e0c30d0ece9cf9f SHA256 (6.2-RC2-i386-disc1.iso) = 900561ee5b32ef5dd5c68444f759c941f59f7dea310dd08d09d3c233fad61618 SHA256 (6.2-RC2-i386-disc2.iso) = 01e586f5eb834de9eadde2ab6d3cb8e498a0ec4d6012963eb8cdbc2f652fc4bb SHA256 (6.2-RC2-i386-docs.iso) = 8f7f40922c4cd254e419c674a7441e9f15c3f4a017c93dbf5c7011b5a584c400 SHA256 (6.2-RC2-ia64-bootonly.iso) = c4c567856768e72273f40d8d6a2871df1b8e740e074415842d8a709b736a5023 SHA256 (6.2-RC2-ia64-disc1.iso) = 194797ed6e8617af1614f400c8f08f6614e20a2734e24bdfa05d2ba0e67503e2 SHA256 (6.2-RC2-ia64-disc2.iso) = cc74718f913e7d8e6626429cd618f064fe00dd2559f43d2e2c7f289b9d87e8ad SHA256 (6.2-RC2-ia64-docs.iso) = 954bac255cc799a885d1035bd65add6a5e0fda7f8645fcb44873459ed82fa26f SHA256 (6.2-RC2-ia64-livefs.iso) = 4f4f4693792b185359f11609b71ef6e2f23b5509576d0a616fe10a67a6f6f8bf SHA256 (6.2-RC1-pc98-bootonly.iso) = 66d30a5a3ca1b296cf9370a9116a1cce282d5f25d1843be36c21d731b4225bf6 SHA256 (6.2-RC1-pc98-disc1.iso) = 1a1ff42156d8e201feb54c6a1e36c3b07a682b22fc7ba8a13fee0ebef2316c26 SHA256 (6.2-RC2-sparc64-bootonly.iso) = 8415d46707c881fca685ebc044cf8dc450a30c51eb049f37a7a4ec8054914ea1 SHA256 (6.2-RC2-sparc64-disc1.iso) = 7c6a9fde09e99bfcc44308ce02c2e3b1cfb7b558da7b48f3685e8ed4e9ea7748 SHA256 (6.2-RC2-sparc64-disc2.iso) = 545f6952590c3642ccdee0ac292bd20647cf26bd2f9499a1e7f9d430d4ec06d0 SHA256 (6.2-RC2-sparc64-docs.iso) = a2ee235f2dcb9e8695dbd77c71084a5f92165feb9d1fd1f260758ec7882aa5dc -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: /etc/rc.d/jail: losing IPs if jail_x_interface set and syntax error in jails /etc/rc?
Philipp Wuensche wrote:
Raphael H. Becker wrote:
Hi *,
I recently triggered an error when setting up a jail-host: I configured
the jail(s) like evry jail I set up in the past:
Yes, this is a bug in rc.d/jail and was introduced in this change:
http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/jail.diff?r1=1.31r2=1.32.
When a jail fails to start, in your case a broken rc.conf in the jail,
the jail is stopped and the ipaddr-alias is unconfigured from the
interface with the following command: ifconfig ${jail_interface} -alias
${jail_ip}
Unfortunately in the change above the variables were renamed to
_interface and _ip, this leads to ifconfig getting executed without a
specified ipaddr. and therefore the first alias is unconfigured, which
is in most cases the ipaddr. you are having access to the remote host.
${jail_interface} is only the correct interface out of luck, so it
should be changed to _interface too.
I think the correct way would be to call jail_stop() instead of doing
the cleanup by hand but in the current implementation this would leave
the ipaddr-alias configured on the interface.
I think I already mentioned once that I don't like this interface and
ipaddr. configuration feature in rc.d/jail at all.
Anyway, the quick fix is trivial and should be included in 6.2.
Otherwise we have a possible DoS security problem with the new release.
--- rc.d/jail.old Fri Dec 22 03:09:27 2006
+++ rc.d/jail Fri Dec 22 03:10:07 2006
@@ -228,8 +228,8 @@
echo ${_jail_id} /var/run/jail_${_jail}.id
else
jail_umount_fs
- if [ -n ${jail_interface} ]; then
- ifconfig ${jail_interface}
-alias ${jail_ip}
+ if [ -n ${_interface} ]; then
+ ifconfig ${_interface} -alias ${_ip}
fi
echo cannot start jail \${_jail}\:
tail +2 ${_tmp_jail}
Patch looks good. Would be indeed nice to have this fixed before 6.2R is
released.
--
Florent Thoumie
[EMAIL PROTECTED]
FreeBSD Committer
signature.asc
Description: OpenPGP digital signature
Migrating vinum to gvinum
I have a 5.2.1 box that I want to upgrade to 5.5-RELENG and in doing so need to upgrade/migrate the current vinum setup to gvinum. It is a simple vinum mirror (just 2 drives with one vinum slice each). Having done some googling on the matter I really haven't found a definitive best approach to doing this. The choices would be: 1) making buildworld and making kernel. Remove the vinum-specific entries in rc.conf and adding geom_vinum_load=YES to /boot/loader.conf. Rebooting and [optionally] running gvinum saveconfig. or 2) clear the current vinum config (which would leave the data intact on each part of the mirror?). Making buildworld, making kernel, adding the loader.conf line. Then rebooting, installing world and rebuild the gvinum device by creating a mirror with one disk and then adding the second disk. Anyone have experience in this migration process? Alternatively has anyone converted a (g)vinum mirror into a gmirror setup? Thanks Sven ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Serial console configured ... break to DDB still doesn't work ..
Just FYI, hints aren't. Er, acpi ignores them. We found that if ACPI wants 2F8 on a given sio port, it was better ... er, only worked ;-) if we configured device.hints to match what ACPI expected. FYI, you might find -dH in /boot.config to be more useful that the console setting in loader.conf. It sets console=comconsole by default, but leaves you able to override it from the vid console if you are at the keyboard when it boots. Very useful. On Dec 16, 2006, at 9:34 PM, Marc G. Fournier wrote: kernel is built so that it uses COM2 (0x2F8) as comconsole, and I have the following in my /boot/loader.conf: hint.sio.0.flags=0x30 hint.sio.0.port=0x2F8 hint.sio.0.irq=3 console=comconsole vidconsole comconsole_speed=115200 boot_multicons=yes Now, I had missed a step from the handbook, and that was to configure my boot blocks for the change in com port ... or, rather, I added the settings to /etc/make.conf, 'cd /sys/boot; ...' and installed them, just forgot to do the bsdlabel ... type'd reboot, slap'd my forehead for not remembering, but, everything came up as expected ... so, does the hint.sio stuff above override the requirement to set things in /etc/make.conf and do bsdlabel? The handbook instructions seem to be from pre-6.x days as it is, as it still talks about configuring sio via the kernle config ... So, I reboot, on my VSP, I get all of the normal device probe stuff that one would expect, and, thanks to my getty on port ttyd0,I get a login prompt ... all great. Now, through telnet to ilo, I do: ^]send break nadda, doesn't drop me to the debugger ... so, I suspect that ilo is trapping the break and not passing it to the backend / DDB? Now, funny thing ... I did do a reset of iLO, which proceeded to drop the system into DDB ... so, somehow, I have to get iLO to send that break ... ? I'm double checking with ALT_BREAK_TO_DEBUGGER set, to see if I can get *that* to work ... but, if anyone has any thoughts on this, please, I'm all ears ... I'm sooo close ... - Marc G. Fournier Hub.Org Networking Services (http:// www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFhNbR4QvfyHIvDvMRAixhAJ9e9cCiPwiNKNmG0NMXiu/n4LICYACgjo1u kxN3oWOD+d4W1cKpAKleexo= =E40d -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable- [EMAIL PROTECTED] -- Jo Rhett senior geek Silicon Valley Colocation ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
A better gvinum raid-5 guide?
Hello, I am trying to learn a bit more on how gvinum works out in a day-to-day situation. For this purpose, I have a server which has four identical disks in addition to ad0, on which I have installed FreeBSD 6.x. It looks like this: [EMAIL PROTECTED] uname -a FreeBSD kg-fil.kg4.no 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #9: Tue Oct 3 23:08:46 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FIL60 amd64 [EMAIL PROTECTED] atacontrol list ATA channel 0: Master: ad0 SAMSUNG SP0822N/WA100-33 ATA/ATAPI revision 7 Slave: no device present ATA channel 1: Master: acd0 NEC DVD RW ND-3550A/1.05 ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 SAMSUNG SP2504C/VT100-33 Serial ATA II Slave: no device present ATA channel 3: Master: ad6 SAMSUNG SP2504C/VT100-33 Serial ATA II Slave: no device present ATA channel 4: Master: ad8 SAMSUNG SP2504C/VT100-33 Serial ATA II Slave: no device present ATA channel 5: Master: ad10 SAMSUNG SP2504C/VT100-33 Serial ATA II Slave: no device present As you can see, the ad0 disk is PATA, and the other disks are SATA. I would like to set up the four sata disks as a raid-5. I have read the Handbook chapter on (g)vinum: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-vinum.html I wonder; are there any guides on setting up gvinum out there that are easier to follow than this? I tried googling, but only found articles on hardware raid, and on software raid-1, which isn't what I want to do. A step-by-step guide for setting up 4 disks in a raid-5 plex would have been welcome. -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
dhclient with bge failing
Hi, I've just cvsup'd my Latitude D820 laptop with a Broadcom BCM5752 to the latest 6-STABLE, and I seem to experiencing some problems with the dhcp client on the base system. The dhcp-client program fails to request an IP address from the DHCP server running isc-dhcp3-server. With a Windows based DHCP server, it succeeds more often, but seems to fail perhaps 1 out of 10 times. I thought it could the NIC itself, but when booting under Windows, there doesn't to be any problems with the Windows DHCP client requesting an IP address from either the Windows DHCP server or ISC-DHCP server. Is anyone else seeing this? Cheers. -- Jonathan Chen [EMAIL PROTECTED] -- Beer. Now there's a temporary solution. - Homer Simpson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: bus_dmamap_load_mbuf_sg still there
I have a Soekris board, so I'm interested. What's the PR number for the bug? How frequently does it occur? It is good to log all of the details to the PR. - Andrea Campi [EMAIL PROTECTED] wrote: Hi, this panic has been reported a few times in the past, both by me and other people; I just updated my Soekris box to 6.2-RC2 and it's still happening. panic: bus_dmamap_load_mbuf_sg: no mbuf packet header! KDB: stack backtrace: panic(c06128c3,c060f93c,c055b9af,c0db804e,c0db803e,...) at panic+0xef bus_dmamap_load_mbuf_sg(c0d18e00,0,c0db8000,c0d627d8,c0d627b8,1) at bus_dmamap_load_mbuf_sg+0x4ec ath_start(c0d55000,35000,36,0,c100,...) at ath_start+0x26f ether_output_frame(c0d55000,c0fee600,c106,0,1,...) at ether_output_frame+0x226 ether_output(c0d55000,c0fee600,c56f6bb0,c0feb840) at ether_output+0x2de ip_output(c0fee600,0,c56f6bac,1,0,0) at ip_output+0xaad ip_forward(c0cf9648,c56f6c78,c04e14dd,c066ca40,1,...) at ip_forward+0x120 ip_input(c0fee600,18,c0673378,c56f6cec,c0541fd7,...) at ip_input+0x8d5 netisr_processqueue(c0d12240,c0cef400,0,c56f6d0c,c04bd93b,...) at netisr_processqueue+0x13 swi_net(0,c0cef438,c0cfaa80,c04bd740,c0cf9648,...) at swi_net+0x97 ithread_loop(c0ce8750,c56f6d38,c0ce8750,c04bd740,0,...) at ithread_loop+0x1fb fork_exit(c04bd740,c0ce8750,c56f6d38) at fork_exit+0x83 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xc56f6d6c, ebp = 0 --- KDB: enter: panic [thread pid 13 tid 13 ] Stopped at kdb_enter+0x2c: leal0(%esi),%esi It has been suggested that it may be pf-related, but I don't have a clue on how to go about digging more info out. Any idea? Bye, Andrea -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ 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]
