Re: best way to make dvd appear to me a .iso file to the FS
El 01/10/2013 03:46, Aryeh Friedman aryeh.fried...@gmail.com escribió: bhyveload(8) only let's you use .ISO's for install media and I want to make it so I can just insert a DVD (/dev/cd0) and bhyve can read it as if it was a just a normal file and not a device... short of copying it to the hard drive is there any other solution anyone can think of? You could use mkisofs/growisofs to create such file from the mounted CD/DVD. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: best way to make dvd appear to me a .iso file to the FS
Iso creating is probably necessary in general case, since some media contain bootable part of cd, which are not seen as files but required to boot. Of course passthrough of cd/dvd/bd device is interesting, but I think for most usages of bhyve as virt platform correct work with iso is enough. Regards, Alexander Yerenkow 01.10.2013 9:05 пользователь Fernando Apesteguía fernando.apesteg...@gmail.com написал: El 01/10/2013 03:46, Aryeh Friedman aryeh.fried...@gmail.com escribió: bhyveload(8) only let's you use .ISO's for install media and I want to make it so I can just insert a DVD (/dev/cd0) and bhyve can read it as if it was a just a normal file and not a device... short of copying it to the hard drive is there any other solution anyone can think of? You could use mkisofs/growisofs to create such file from the mounted CD/DVD. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Is freebsd-update braindamaged, or I'm using it wrong?
This is the first time I've used freebsd-update in years, and I'm immediately flagging it as something I won't use in the future. For the last half hour it has been forcing me to manually resolve, one by one, in an editor, hundreds of merge conflicts such as these: 1 current version 2 # $FreeBSD: release/9.0.0/etc/gettytab 209954 2010-07-12 19:09:18Z bcr $ 3 === 4 # $FreeBSD: release/9.2.0/etc/gettytab 243623 2012-11-27 19:23:54Z peterj $ 5 9.2-RELEASE 6 # from: @(#)gettytab 5.14 (Berkeley) 3/27/91 7 # This is fairly ridiculous. Then, at a random file it has proposed its own merge and asked the prompt Does this look reasonable?. It was not, but when I answered it with n it stopped the whole process (instead of maybe opening the file in the editor for me to merge again). I've since retried the process and it behaves the same, and then tried it on another system and again - the same type of manual merges and the same exit from the process when answering n to a botched merge. In both cases, I'm upgrading from either 9.0-RELEASE or 9.1-RELEASE to 9.2-RELEASE and the command line was freebsd-update upgrade -r 9.2-RELEASE. Am I doing something wrong, or is freebsd-update simply quirky and not that useful? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Is freebsd-update braindamaged, or I'm using it wrong?
Le 01/10/2013 11:16, Ivan Voras a écrit : This is fairly ridiculous. Then, at a random file it has proposed its own merge and asked the prompt Does this look reasonable?. It was not, but when I answered it with n it stopped the whole process (instead of maybe opening the file in the editor for me to merge again). You can merge files from freebsd-update, using (m) if I remember well. Then you choose right or left for each step. But there is something strange since you have hundreds of conflicts… Did you built each release from sources? -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Is freebsd-update braindamaged, or I'm using it wrong?
On 2013-10-01 11:16, Ivan Voras wrote: This is the first time I've used freebsd-update in years, and I'm immediately flagging it as something I won't use in the future. For the last half hour it has been forcing me to manually resolve, one by one, in an editor, hundreds of merge conflicts such as these: 1 current version 2 # $FreeBSD: release/9.0.0/etc/gettytab 209954 2010-07-12 19:09:18Z bcr $ 3 === 4 # $FreeBSD: release/9.2.0/etc/gettytab 243623 2012-11-27 19:23:54Z peterj $ 5 9.2-RELEASE 6 # from: @(#)gettytab 5.14 (Berkeley) 3/27/91 7 # I've had the same expierience during some upgrades. I've never been able to find the exact reason. But my theory is that the mergemaster reacts on some specific settings on the affected systems - it be env or config files. Unfortunately I've reinstalled the affected system (in rage) so further bug hunting is not possible. On newer installs the problem has not shown up... /Uffe ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Is freebsd-update braindamaged, or I'm using it wrong?
On 01/10/2013 10:16, Ivan Voras wrote: This is the first time I've used freebsd-update in years, and I'm immediately flagging it as something I won't use in the future. For the last half hour it has been forcing me to manually resolve, one by one, in an editor, hundreds of merge conflicts such as these: 1 current version 2 # $FreeBSD: release/9.0.0/etc/gettytab 209954 2010-07-12 19:09:18Z bcr $ 3 === 4 # $FreeBSD: release/9.2.0/etc/gettytab 243623 2012-11-27 19:23:54Z peterj $ 5 9.2-RELEASE 6 # from: @(#)gettytab 5.14 (Berkeley) 3/27/91 7 # This is fairly ridiculous. Then, at a random file it has proposed its own merge and asked the prompt Does this look reasonable?. It was not, but when I answered it with n it stopped the whole process (instead of maybe opening the file in the editor for me to merge again). I've since retried the process and it behaves the same, and then tried it on another system and again - the same type of manual merges and the same exit from the process when answering n to a botched merge. In both cases, I'm upgrading from either 9.0-RELEASE or 9.1-RELEASE to 9.2-RELEASE and the command line was freebsd-update upgrade -r 9.2-RELEASE. Am I doing something wrong, or is freebsd-update simply quirky and not that useful? It is a little quirky, you arent the first to note this. For example http://freebsd.1045724.n5.nabble.com/Should-I-be-able-to-use-mergemaster-with-freebsd-update-td5822457.html not that useful? is subjective, some machines I've used it on happily, I'm more likely to build and use mergemaster though. Vince ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Is freebsd-update braindamaged, or I'm using it wrong?
To make better tool (than current behaviour of mergemaster regarding configs/source files) which could make merge an easy task it *must* have such things: a) way to get Original configs/files from revision from you are upgrading ($Rev1) b) way to get Original configs/files from revision to you are upgrading ($Rev100) c) have ability to ignore differencies in comments d) have ability to treat special cases (as $FreeBSD$ - just took newer line) Then, your each new file will be $Rev100 + diff_changes(CURRENT, $Rev1) + diff_changes($Rev100, $Rev1). Note, that in case that your diffs are none diff_changes(CURRENT, $Rev1) = 0, then you can simply get new file. Same thing in case that only $FreeBSD$ changed. I have some PoC-es for this, but not in shell, maybe I'll come up someday with full tool. 2013/10/1 Ivan Voras ivo...@freebsd.org This is the first time I've used freebsd-update in years, and I'm immediately flagging it as something I won't use in the future. For the last half hour it has been forcing me to manually resolve, one by one, in an editor, hundreds of merge conflicts such as these: 1 current version 2 # $FreeBSD: release/9.0.0/etc/gettytab 209954 2010-07-12 19:09:18Z bcr $ 3 === 4 # $FreeBSD: release/9.2.0/etc/gettytab 243623 2012-11-27 19:23:54Z peterj $ 5 9.2-RELEASE 6 # from: @(#)gettytab 5.14 (Berkeley) 3/27/91 7 # This is fairly ridiculous. Then, at a random file it has proposed its own merge and asked the prompt Does this look reasonable?. It was not, but when I answered it with n it stopped the whole process (instead of maybe opening the file in the editor for me to merge again). I've since retried the process and it behaves the same, and then tried it on another system and again - the same type of manual merges and the same exit from the process when answering n to a botched merge. In both cases, I'm upgrading from either 9.0-RELEASE or 9.1-RELEASE to 9.2-RELEASE and the command line was freebsd-update upgrade -r 9.2-RELEASE. Am I doing something wrong, or is freebsd-update simply quirky and not that useful? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org -- Regards, Alexander Yerenkow ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Is freebsd-update braindamaged, or I'm using it wrong?
Another thing I'd like to see: * Have the tool prompt per-directory first, then per-file. For example: There are 30 changed files in /etc/rc.d. Update all? [y/N] If you hit 'y' it updates all of them right away. If you hit 'N, it will prompt you for each separate file. Tim On Oct 1, 2013, at 2:38 AM, Alexander Yerenkow yeren...@gmail.com wrote: To make better tool (than current behaviour of mergemaster regarding configs/source files) which could make merge an easy task it *must* have such things: a) way to get Original configs/files from revision from you are upgrading ($Rev1) b) way to get Original configs/files from revision to you are upgrading ($Rev100) c) have ability to ignore differencies in comments d) have ability to treat special cases (as $FreeBSD$ - just took newer line) Then, your each new file will be $Rev100 + diff_changes(CURRENT, $Rev1) + diff_changes($Rev100, $Rev1). Note, that in case that your diffs are none diff_changes(CURRENT, $Rev1) = 0, then you can simply get new file. Same thing in case that only $FreeBSD$ changed. I have some PoC-es for this, but not in shell, maybe I'll come up someday with full tool. 2013/10/1 Ivan Voras ivo...@freebsd.org This is the first time I've used freebsd-update in years, and I'm immediately flagging it as something I won't use in the future. For the last half hour it has been forcing me to manually resolve, one by one, in an editor, hundreds of merge conflicts such as these: 1 current version 2 # $FreeBSD: release/9.0.0/etc/gettytab 209954 2010-07-12 19:09:18Z bcr $ 3 === 4 # $FreeBSD: release/9.2.0/etc/gettytab 243623 2012-11-27 19:23:54Z peterj $ 5 9.2-RELEASE 6 # from: @(#)gettytab 5.14 (Berkeley) 3/27/91 7 # This is fairly ridiculous. Then, at a random file it has proposed its own merge and asked the prompt Does this look reasonable?. It was not, but when I answered it with n it stopped the whole process (instead of maybe opening the file in the editor for me to merge again). I've since retried the process and it behaves the same, and then tried it on another system and again - the same type of manual merges and the same exit from the process when answering n to a botched merge. In both cases, I'm upgrading from either 9.0-RELEASE or 9.1-RELEASE to 9.2-RELEASE and the command line was freebsd-update upgrade -r 9.2-RELEASE. Am I doing something wrong, or is freebsd-update simply quirky and not that useful? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org -- Regards, Alexander Yerenkow ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: what's going on after upgrade to svn-latest 9.
On Fri, Jun 21, 2013 at 01:17:31PM +0200, Wojciech Puchar wrote: i'm getting this on my computer. disk seems OK, smart shows nothing, dd reads whole partition without problem. no other errors from disk itself (AHCI timeout or so). started exactly after i rebooted with new kernel. everything unchanged. userland is in sync thanks for help g_vfs_done():ada0s3d.eli[WRITE(offset=30653186048, length=1048576)]error = 11 i've just tried recent 10.0-alpha4 on my laptop (normally running 8-stable) and start to see this shit as well. smart does not report anything wrong with my disks, and 8-stable never yielded anything like these messages, so it looks like some kind of false alarm. any clues? ./danfe ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: what's going on after upgrade to svn-latest 9.
on 01/10/2013 22:29 Alexey Dokuchaev said the following:
On Fri, Jun 21, 2013 at 01:17:31PM +0200, Wojciech Puchar wrote:
i'm getting this on my computer.
disk seems OK, smart shows nothing, dd reads whole partition without
problem.
no other errors from disk itself (AHCI timeout or so).
started exactly after i rebooted with new kernel. everything
unchanged. userland is in sync
thanks for help
g_vfs_done():ada0s3d.eli[WRITE(offset=30653186048,
length=1048576)]error = 11
i've just tried recent 10.0-alpha4 on my laptop (normally running 8-stable)
and start to see this shit as well. smart does not report anything wrong
with my disks, and 8-stable never yielded anything like these messages, so
it looks like some kind of false alarm. any clues?
It looks like the error comes from unmapped I/O code in GEOM and is caused by
KVA shortage:
if (vmem_alloc(transient_arena, size, M_BESTFIT | M_NOWAIT, addr)) {
if (transient_map_retries != 0
retried = transient_map_retries) {
g_io_deliver(bp, EDEADLK/* XXXKIB */);
You could try to experiment with kern.geom.transient_map_retries
--
Andriy Gapon
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: cause of reboot
Please help I need to find cause of reboot.. i would recommend the reconfigure of syslog too. attention on all.log and/or console.log there are examples with explanations not all console messages flow into messages. ;-) memory test, disk tests cpu temperature, i had exactly the same error caused by an defective cpu-cooler. cpu got hot during the nightly periodc scripts and silently rebooted. watch the time of the reboot and compare it to the cron/periodic scripts. determine whats running at the time of the reboot. hth ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: UFS related panic (daily - find)
Ok, here is another one, same case, just this time under 9.1-RELEASE-p7 == Fatal trap 12: page fault while in kernel mode fault virtual address = 0x25 fault code = supervisor read, page not present instruction pointer = 0x20:0xc082c552 stack pointer = 0x28:0xe7eed7a8 frame pointer = 0x28:0xe7eed7ac code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 63645 (find) trap number = 12 panic: page fault Uptime: 11h16m47s Physical memory: 1014 MB Dumping 143 MB: 128 112 96 80 64 48 32 16 No symbol stopped_cpus in current context. No symbol stoppcbs in current context. Reading symbols from /boot/kernel/nfscl.ko...Reading symbols from /boot/kernel/nfscl.ko.symbols...done. done. Loaded symbols for /boot/kernel/nfscl.ko Reading symbols from /boot/kernel/nfslock.ko...Reading symbols from /boot/kernel/nfslock.ko.symbols...done. done. Loaded symbols for /boot/kernel/nfslock.ko Reading symbols from /boot/kernel/nfssvc.ko...Reading symbols from /boot/kernel/nfssvc.ko.symbols...done. done. Loaded symbols for /boot/kernel/nfssvc.ko Reading symbols from /boot/kernel/krpc.ko...Reading symbols from /boot/kernel/krpc.ko.symbols...done. done. Loaded symbols for /boot/kernel/krpc.ko Reading symbols from /boot/kernel/nfscommon.ko...Reading symbols from /boot/kernel/nfscommon.ko.symbols...done. done. Loaded symbols for /boot/kernel/nfscommon.ko Reading symbols from /boot/kernel/nfsd.ko...Reading symbols from /boot/kernel/nfsd.ko.symbols...done. done. Loaded symbols for /boot/kernel/nfsd.ko Reading symbols from /boot/kernel/nfslockd.ko...Reading symbols from /boot/kernel/nfslockd.ko.symbols...done. done. Loaded symbols for /boot/kernel/nfslockd.ko Reading symbols from /usr/local/modules/fuse.ko...done. Loaded symbols for /usr/local/modules/fuse.ko Reading symbols from /usr/local/lib/oss/modules/osscore.ko...done. Loaded symbols for /usr/local/lib/oss/modules/osscore.ko Reading symbols from /usr/local/lib/oss/modules/oss_audigyls.ko...done. Loaded symbols for /usr/local/lib/oss/modules/oss_audigyls.ko Reading symbols from /boot/kernel/cpuctl.ko...Reading symbols from /boot/kernel/cpuctl.ko.symbols...done. done. Loaded symbols for /boot/kernel/cpuctl.ko #0 doadump (textdump=1) at pcpu.h:244 244 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=1) at pcpu.h:244 #1 0xc06564e9 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #2 0xc065671f in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:636 #3 0xc08aa97a in trap_fatal (frame=0xe7eed768, eva=37) at /usr/src/sys/i386/i386/trap.c:1018 #4 0xc08aaa64 in trap_pfault (frame=0xe7eed768, usermode=0, eva=37) at /usr/src/sys/i386/i386/trap.c:870 #5 0xc08ab711 in trap (frame=0xe7eed768) at /usr/src/sys/i386/i386/trap.c:545 #6 0xc0898d4c in calltrap () at /usr/src/sys/i386/i386/exception.s:169 #7 0xc082c552 in inodedep_find (inodedephd=Variable inodedephd is not available. ) at /usr/src/sys/ufs/ffs/ffs_softdep.c:2073 #8 0xc0830bf0 in inodedep_lookup (mp=0xc47a77bc, inum=2051635, flags=0, inodedeppp=0xe7eed7f8) at /usr/src/sys/ufs/ffs/ffs_softdep.c:2105 #9 0xc0834c39 in softdep_load_inodeblock (ip=0xc6ca7658) at /usr/src/sys/ufs/ffs/ffs_softdep.c:11527 #10 0xc0843893 in ffs_vgetf (mp=0xc47a77bc, ino=2051635, flags=2097152, vpp=0xe7eed8ec, ffs_flags=Variable ffs_flags is not available. ) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1742 #11 0xc08439ae in ffs_vget (mp=0xc47a77bc, ino=2051635, flags=2097152, vpp=0xe7eed8ec) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1625 #12 0xc084ffc1 in ufs_lookup_ino (vdp=0xc704b990, vpp=0xe7eedae8, cnp=0xe7eedafc, dd_ino=0x0) at /usr/src/sys/ufs/ufs/ufs_lookup.c:749 #13 0xc0850054 in ufs_lookup (ap=0xe7eed954) at /usr/src/sys/ufs/ufs/ufs_lookup.c:214 #14 0xc08c2022 in VOP_CACHEDLOOKUP_APV (vop=0xc0983080, a=0xe7eed954) at vnode_if.c:187 #15 0xc06cb77b in vfs_cache_lookup (ap=0xe7eed9e4) at vnode_if.h:80 #16 0xc08c3f81 in VOP_LOOKUP_APV (vop=0xc0983520, a=0xe7eed9e4) at vnode_if.c:123 #17 0xc06d2e24 in lookup (ndp=0xe7eedabc) at vnode_if.h:54 #18 0xc06d3dd2 in namei (ndp=0xe7eedabc) at /usr/src/sys/kern/vfs_lookup.c:297 #19 0xc06e54e3 in kern_statat_vnhook (td=0xc4fae2e0, flag=512, fd=-100, path=0x28450638 Address 0x28450638 out of bounds, pathseg=UIO_USERSPACE, sbp=0xe7eedbe8, hook=0) at /usr/src/sys/kern/vfs_syscalls.c:2432 #20 0xc06e562c in kern_statat (td=0xc4fae2e0, flag=512, fd=-100, path=0x28450638 Address 0x28450638 out of bounds, pathseg=UIO_USERSPACE, sbp=0xe7eedbe8) at /usr/src/sys/kern/vfs_syscalls.c:2413 #21 0xc06e5664 in kern_lstat (td=0xc4fae2e0, path=0x28450638 Address 0x28450638 out of bounds, pathseg=UIO_USERSPACE, sbp=0xe7eedbe8)
