Aw: Re: Aw: Xorg vs Wayland (and MIR?) - future for NetBSD X ?
John Nemeth <jnem...@cue.bc.ca> wrote: > On Dec 28, 6:36am, Carsten Kunze wrote: > } already try to copy Linux (+ZFS) just to attract users. Indeed, > > ZFS comes from Solaris, not Linux. If you're going to talk > smack, at least be accurate. Also, there is nothing wrong with > adopting good things from other sources. If I say "Linux + something" this *maybe* means that this something is not from Linux ;-)
Aw: Xorg vs Wayland (and MIR?) - future for NetBSD X ?
This will be the time to leave NetBSD and go to OpenBSD. Or to Linux. Why not using the original when NetBSD would try to copy Linux? Will systemd on NetBSD be the next step? FreeBSD does already try to copy Linux (+ZFS) just to attract users. Indeed, Slackware is much more UNIX like than FreeBSD. One of the reasons that users prefer NetBSD might be that it is UNIX and not like modern Linux. If this will change I'm glad that there is still OpenBSD.
What is the suggested way to use a C compiler with sanitizers?
Hello, if one wants to use the sanitizer features of the C compiler, what is the suggested way? If I e.g. compile and link with options -O2 -g -O0 -fno-omit-frame-pointer -fno-optimize-sibling-calls -Wall -Wextra -Wsign-compare -Wcast-align -Wcast-qual -Wmissing-prototypes -Wunused-parameter -Wunused-function -Wshadow -fno-common -fsanitize=address -fsanitize=undefined -fsanitize=float-divide-by-zero -fsanitize=float-cast-overflow (-O2 is from CFLAGS which should be reset by -O0) I get something like ui.c:2017:11: runtime error: member access within misaligned address 0xbebebebebebebebe for type 'struct filediff', which requires 8 byte alignment 0xbebebebebebebebe: note: pointer points here test ASAN:SIGSEGV = ==1372==ERROR: AddressSanitizer: SEGV on unknown address 0x72d42a8a5000 (pc 0x004229c5 bp 0x7f7fff49c710 sp 0x7f7fff49c460 T0) #0 0x4229c4 () #1 0x421dd7 () #2 0x44b9be () #3 0x42a329 () #4 0x4488ad () #5 0x413a90 () #6 0x410e02 () #7 0x4054ae () #8 0x4044ba () AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV ??:0 ?? ==1372==ABORTING on errors. What needs to be configured to make the symbolizer work? (Binary is not stripped.) Carsten
Re: Suspend to RAM failes
co...@sdf.org wrote: > ... as a really horrible and otherwise transparent hack, you could probably > detach USB before & reattach (drvctl -r) after. This did help again, thank you! Now suspend works. But it boots when I press the power button in suspended state (pressing a keyboard key did nothing). dmesg now is: nfiguration mode 1 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok pchb0 at pci0 dev 0 function 0: vendor 8086 product 0c04 (rev. 0x06) ppb0 at pci0 dev 1 function 0: vendor 8086 product 0c01 (rev. 0x06) ppb0: PCI Express capability version 2 x16 @ 8.0GT/s pci1 at ppb0 bus 1 pci1: i/o space, memory space enabled, rd/line, wr/inv ok radeon0 at pci1 dev 0 function 0: vendor 1002 product 6606 (rev. 0x00) i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 0416 (rev. 0x06) drm: Memory usable by graphics device = 2048M drm: Supports vblank timestamp caching Rev 2 (21.10.2013). drm: Driver supports precise vblank timestamp query. i915drmkms0: interrupting at ioapic0 pin 16 (i915) intelfb0 at i915drmkms0 i915drmkms0: info: registered panic notifier intelfb0: framebuffer at 0x80008e5dd000, size 1920x1080, depth 32, stride 7680 wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0 wsmux1: connecting to wsdisplay0 hdaudio0 at pci0 dev 3 function 0: HD Audio Controller hdaudio0: interrupting at ioapic0 pin 16 hdaudio0: timeout leaving reset state hdaudio0: device driver failed to attach vendor 8086 product 8c3a (miscellaneous communications, revision 0x04) at pci0 dev 22 function 0 not configured puc0 at pci0 dev 22 function 3: Intel 8 Series KT (com) com2 at puc0 port 0 (16550-compatible): ioaddr 0xf0e0, interrupting at ioapic0 pin 19 com2: ns16550a, working fifo wm0 at pci0 dev 25 function 0: I217 LM Ethernet Connection (rev. 0x04) wm0: interrupting at msi0 vec 0 wm0: PCI-Express bus wm0: 2048 words FLASH wm0: Ethernet address f0:1f:af:4e:d5:85 ihphy0 at wm0 phy 2: i217 10/100/1000 media interface, rev. 4 ihphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto ehci0 at pci0 dev 26 function 0: vendor 8086 product 8c2d (rev. 0x04) ehci0: interrupting at ioapic0 pin 16 ehci0: BIOS has given up ownership ehci0: EHCI version 1.0 usb0 at ehci0: USB revision 2.0 hdaudio1 at pci0 dev 27 function 0: HD Audio Controller hdaudio1: interrupting at ioapic0 pin 22 hdafg0 at hdaudio1: vendor 10ec product 0292 hdafg0: DAC00 2ch: Speaker [Built-In], HP Out [Jack] hdafg0: DAC01 2ch: Speaker [Jack] hdafg0: 2ch/0ch 32000Hz 44100Hz 48000Hz 88200Hz 96000Hz 192000Hz PCM16 PCM20 PCM24 AC3 audio0 at hdafg0: full duplex, playback, capture, mmap, independent ppb1 at pci0 dev 28 function 0: vendor 8086 product 8c10 (rev. 0xd4) ppb1: PCI Express capability version 2 x1 @ 5.0GT/s pci2 at ppb1 bus 2 pci2: i/o space, memory space enabled, rd/line, wr/inv ok ppb2 at pci0 dev 28 function 2: vendor 8086 product 8c14 (rev. 0xd4) ppb2: PCI Express capability version 2 x1 @ 5.0GT/s ppb2: link is x1 @ 2.5GT/s pci3 at ppb2 bus 3 pci3: i/o space, memory space enabled, rd/line, wr/inv ok iwn0 at pci3 dev 0 function 0: vendor 8086 product 088e (rev. 0x24) iwn0: interrupting at ioapic0 pin 18 iwn0: MIMO 2T2R, AGN, address b4:b6:76:df:7f:00 iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ppb3 at pci0 dev 28 function 4: vendor 8086 product 8c18 (rev. 0xd4) ppb3: PCI Express capability version 2 x1 @ 5.0GT/s pci4 at ppb3 bus 4 pci4: i/o space, memory space enabled, rd/line, wr/inv ok ppb4 at pci0 dev 28 function 5: vendor 8086 product 8c1a (rev. 0xd4) ppb4: PCI Express capability version 2 x1 @ 5.0GT/s pci5 at ppb4 bus 5 pci5: i/o space, memory space enabled, rd/line, wr/inv ok ppb5 at pci0 dev 28 function 6: vendor 8086 product 8c1c (rev. 0xd4) ppb5: PCI Express capability version 2 x1 @ 5.0GT/s pci6 at ppb5 bus 6 pci6: i/o space, memory space enabled, rd/line, wr/inv ok ppb6 at pci0 dev 28 function 7: vendor 8086 product 8c1e (rev. 0xd4) ppb6: PCI Express capability version 2 x1 @ 5.0GT/s ppb6: link is x1 @ 2.5GT/s pci7 at ppb6 bus 14 pci7: i/o space, memory space enabled, rd/line, wr/inv ok sdhc0 at pci7 dev 0 function 0: vendor 1217 product 8520 (rev. 0x01) sdhc0: interrupting at ioapic0 pin 19 sdhc0: SDHC 4.0, rev 6, SDMA, 5 kHz, HS SDR50 DDR50 SDR104 HS200 1.8V 3.3V, re-tuning mode 1, 2048 byte blocks sdmmc0 at sdhc0 slot 0 ehci1 at pci0 dev 29 function 0: vendor 8086 product 8c26 (rev. 0x04) ehci1: interrupting at ioapic0 pin 21 ehci1: BIOS has given up ownership ehci1: EHCI version 1.0 usb1 at ehci1: USB revision 2.0 ichlpcib0 at pci0 dev 31 function 0: vendor 8086 product 8c4f (rev. 0x04) timecounter: Timecounter "ichlpcib0" frequency 3579545 Hz quality 1000 ichlpcib0: 24-bit timer tco0 at ichlpcib0: TCO (watchdog) timer configured. tco0: Min/Max interval 1/367
Suspend to RAM failes
Hello, sysctl -w hw.acpi.sleep.state=3 failes with acpi0: entering state S3 Devices without power management support: hdaudio0 acpi0: aborting suspend Above in dmesg is found: hdaudio0 at pci0 dev 3 function 0: HD Audio Controller hdaudio0: interrupting at ioapic0 pin 16 hdaudio0: timeout leaving reset state hdaudio0: device driver failed to attach A similar problem was discussed in https://mail-index.netbsd.org/netbsd-users/2011/12/07/msg009717.html Is it somehow possible to handle this without compiling the kernel? E.g. by manually remove hdaudio0 or force the suspend somehow? --Carsten dmesg: Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 7.99.42 (GENERIC.201611250700Z) total memory = 8097 MB avail memory = 7842 MB cpu_rng: RDRAND rnd: seeded with 128 bits timecounter: Timecounters tick every 10.000 msec Kernelized RAIDframe activated timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 Dell Inc. Latitude E6540 (01) mainbus0 (root) ACPI: RSDP 0x000EF980 24 (v02 DELL ) ACPI: XSDT 0xC8FD3098 B4 (v01 DELL CBX3 01072009 AMI 00010013) ACPI: FACP 0xC8FE4AF0 00010C (v05 DELL CBX3 01072009 AMI 00010013) ACPI: DSDT 0xC8FD31E0 01190D (v02 DELL CBX3 0014 INTL 20120711) ACPI: FACS 0xCA7ED080 40 ACPI: APIC 0xC8FE4C00 72 (v03 DELL CBX3 01072009 AMI 00010013) ACPI: FPDT 0xC8FE4C78 44 (v01 DELL CBX3 01072009 AMI 00010013) ACPI: SLIC 0xC8FE4CC0 000176 (v03 DELL CBX3 01072009 MSFT 00010013) ACPI: LPIT 0xC8FE4E38 5C (v01 DELL CBX3 AMI. 0005) ACPI: SSDT 0xC8FE4E98 000228 (v01 INTEL sensrhub INTL 20120711) ACPI: SSDT 0xC8FE50C0 000160 (v01 Intel zpodd1000 INTL 20120711) ACPI: SSDT 0xC8FE5220 00051F (v01 PmRef Cpu0Ist 3000 INTL 20120711) ACPI: SSDT 0xC8FE5740 000AD8 (v01 PmRef CpuPm3000 INTL 20120711) ACPI: HPET 0xC8FE6218 38 (v01 DELL CBX3 01072009 AMI. 0005) ACPI: SSDT 0xC8FE6250 0003D2 (v01 SataRe SataTabl 1000 INTL 20120711) ACPI: MCFG 0xC8FE6628 3C (v01 DELL CBX3 01072009 MSFT 0097) ACPI: SSDT 0xC8FE6668 001044 (v01 SgRef SgPeg1000 INTL 20120711) ACPI: ASF! 0xC8FE76B0 A5 (v32 INTEL HCG 0001 TFSM 000F4240) ACPI: SSDT 0xC8FE7758 000589 (v01 AMITCG PROC 0001 INTL 20120711) ACPI: DMAR 0xC8FE7CE8 B0 (v01 INTEL HSW 0001 INTL 0001) ACPI: SSDT 0xC8FE7D98 00109B (v01 AmdRef AmdTabl 1000 INTL 20120711) ACPI: TCPA 0xC8FE8E38 32 (v02 APTIO4 NAPAASF 0001 MSFT 0113) ACPI: Executed 1 blocks of module-level executable AML code ACPI: Executed 1 blocks of module-level executable AML code ACPI: 9 ACPI AML tables successfully acquired and loaded ioapic0 at mainbus0 apid 8: pa 0xfec0, version 0x20, 24 pins cpu0 at mainbus0 apid 0 cpu0: Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz, id 0x306c3 cpu1 at mainbus0 apid 2 cpu1: Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz, id 0x306c3 cpu2 at mainbus0 apid 1 cpu2: Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz, id 0x306c3 cpu3 at mainbus0 apid 3 cpu3: Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz, id 0x306c3 acpi0 at mainbus0: Intel ACPICA 20160930 acpi0: X/RSDT: OemId , AslId acpi0: MCFG: segment 0, bus 0-63, address 0xf800 ACPI: Dynamic OEM Table Load: ACPI: SSDT 0xFE822CC32810 0003D3 (v01 PmRef Cpu0Cst 3001 INTL 20120711) ACPI: Dynamic OEM Table Load: ACPI: SSDT 0xFE810E7DA810 0005AA (v01 PmRef ApIst3000 INTL 20120711) ACPI: Dynamic OEM Table Load: ACPI: SSDT 0xFE810E727A50 000119 (v01 PmRef ApCst3000 INTL 20120711) acpi0: SCI interrupting at int 9 timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000 hpet0 at acpi0: high precision event timer (mem 0xfed0-0xfed00400) timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000 acpiec0 at acpi0 (ECDV, PNP0C09-0) : io 0x930,0x934 FWHD (INT0800) at acpi0 not configured LDRC (PNP0C02) at acpi0 not configured attimer1 at acpi0 (TIMR, PNP0100): io 0x40-0x43,0x50-0x53 irq 0 CWDT (INT3F0D) at acpi0 not configured RMSC (PNP0C02) at acpi0 not configured pckbc1 at acpi0 (PS2K, DLLK05BE) (kbd port): io 0x60,0x64 irq 1 pckbc2 at acpi0 (PS2M, DLL05BE) (aux port): irq 12 UAR1 (PNP0501) at acpi0 not configured LPTE (PNP0401) at acpi0 not configured ACD0 (INT33CA) at acpi0 not configured DFUD (INT33D7) at acpi0 not configured acpivga0 at acpi0 (PEGP): ACPI Display Adapter acpivga0: connected output devices: acpivga0: 0x0100: Ext. Monitor, head 0 acpivga0: 0x0400: Unknown Output Device, head 0
Aw: Re: ext2fs mount issue maybe just a temporary problem
Swift Griggswrote: > Just out of curiosity, since I also use ext2fs somewhat often, did you > create the file system with NetBSD or with Linux? I've noticed a lot more > problems when I create the file system under Linux. I always created them on Linux since I did expect fewer problems then. Actually I never had problems beside severe performance issues. But this may now have changed significantly because of disabling the atime update. But thanks for the tip, I'll create them on NetBSD next time. Maybe this also improves performance. --Carsten
Unexpected error while trying to mount ext2fs
Hello, I have a USB flash drive with ext2fs as second and third MBR slice (no slice 1 and 4 exists). Slice 2 and 3 are mapped to partition sd0e and sd0f. When I try to mount partition sd0e I get an unexpected error: # disklabel sd0 # /dev/rsd0d: type: SCSI disk: DataTraveler 2.0 label: fictitious flags: removable bytes/sector: 512 sectors/track: 32 tracks/cylinder: 255 sectors/cylinder: 8160 cylinders: 7531 total sectors: 61457664 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 6 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] d: 61457664 0 unused 0 0# (Cyl. 0 - 7531*) e: 9026816 52430848 Linux Ext2 0 0# (Cyl. 6425*- 7531*) f: 31457280 20973568 Linux Ext2 0 0# (Cyl. 2570*- 6425*) disklabel: boot block size 0 disklabel: super block size 0 # mount /dev/sd0e /mnt/usb mount: no match for `sd0e': No such process What does "no match" and "no such process" mean? It did work when there had only been sd0e. Now sd0f is added "below" (note the offset) sd0e. Maybe this causes issues? --Carsten
Aw: Re: mount_ext2fs: -o atime: option not supported
Eric Haszlakiewiczwrote: > The noatime flag looks like it's handled in the ext2fs kernel code, with > "atime" as the default. Do you get the same error when you try to pass "-o > noatime" on the command line? Perhaps the mount_ext2fs program just needs a > slight tweak to handle it. I have already send a second mail to the topic but my mails arive with hours...days delay. I've seen that the kernel seems to handle the option. What I have tested is # mount -o noatime /dev/sd0e /mnt Which gives the error for an unsupported option. Indeed it looks like just a change to mount_ext2fs(8) should fix it. --Carsten
Ext2fs and noatime
Hello, mount_ext2fs(8) says that it doesn't support option "noatime": # mount_ext2fs -o atime mount_ext2fs: -o atime: option not supported Unfortunately the manpage of mount_ext2fs(8) doesn't specify which mount options are available. Looking at the code at http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/ufs/ext2fs/ext2fs_readwrite.c shows that options relatime and noatime seems to be processed. So why does the mount tool not support these options? BTW: Why is directory src/sys not downloaded with the kernel code when doing $ export CVSROOT="anon...@anoncvs.netbsd.org:/cvsroot" $ cd /usr $ cvs checkout -A -P src ? --Carsten
mount_ext2fs: -o atime: option not supported
Hello, does mount_ext2fs: -o atime: option not supported that access time is never set or always set? If it is always set, is there any chance to implement option "noatime"? (Or disabling atime update for ext2fs?) --Carsten
Aw: Re: Use of encfs failed
Hi, with encfs on NetBSD 7.99.19 (GENERIC.201506211200Z) I have errors again: encfs: perfuse_open: setsockopt SO_SNDBUF to 540672 failed: No buffer space available encfs: perfuse_open: setsockopt SO_RCVBUF to 540672 failed: No buffer space available encfs: perfuse_open: setsockopt SO_SNDBUF to 540672 failed: No buffer space available encfs: perfuse_open: setsockopt SO_RCVBUF to 540672 failed: No buffer space available perfused: puffs_mount: cannot open /dev/puffs perfuse_fs_init: puffs_mount failed: Permission deniedfuse failed. Common problems: - fuse kernel module not installed (modprobe fuse) - invalid options -- see usage message --Carsten
Aw: Aw: Re: Use of encfs failed
perfused: puffs_mount: cannot open /dev/puffs perfuse_fs_init: puffs_mount failed: Permission deniedfuse failed. Common problems: This needs to be done as root of course. Sorry for the noise.
Use of encfs failed
Hello, I tried to use encfs (compiled from https://github.com/vgough/encfs) but it did not work for me: $ encfs /mnt/usb /tmp/usb The directory /tmp/usb does not exist. Should it be created? (y,n) y EncFS Password: encfs: perfuse_open: setsockopt SO_SNDBUF to 540672 failed: No buffer space available encfs: perfuse_open: setsockopt SO_RCVBUF to 540672 failed: No buffer space available encfs: perfuse_open: setsockopt SO_SNDBUF to 540672 failed: No buffer space available encfs: perfuse_open: setsockopt SO_RCVBUF to 540672 failed: No buffer space available perfuse_init: setrlimit failed: Operation not permitted: Operation not permittedfuse failed. Common problems: - fuse kernel module not installed (modprobe fuse) - invalid options -- see usage message Does one have an idea how this could be solved? (It did work on Linux. My system here is a three weeks old NetBSD-Current (amd64) with pkgsrc-current.) --Carsten
Aw: Re: Aw: Re: No option -p for make?
chris...@astron.com (Christos Zoulas) wrote: The question is what should -p do? It does output the internally defined macros (like what is defined for e.g. ${CC}) and e.g. suffix rules (like what is defined for .c.o). Of course one can redefine everything he uses, then these internally definitions don't matter but using them keeps the files short and makes it possible to use system depending settings (which makes sense for e.g. ${CFLAGS}). Of course using tool internal information doesn't help portability but on debugging make issues it can help. I just searched for the 4.xBSD manual pages--it looks like 4.xBSD didn't support -p neither ... That would explain and justify it ... Then sorry for the noise! Carsten
Aw: Re: No option -p for make?
Dan LaBell dan4l-nos...@verizon.net wrote: Because, it's Berkeley not UNIX ;-) ... but BSD started out of UNIX (Edition 6 I think) Before, Berkeley and UNIX got together, that's not that, much, that's great about UNIX. NO TCP/IP, and a line editor as the STANDARD editor. Neat-oh, so you don't have to enter your scripts into the system with a punch card reader is what, I feel most people in software development should think at the time. Before POSIX, and X/OPEN, etc, UNIX vendors would copy in Bell's Sys Five features with their own little nuances, and 'creature features'. This may be all true. But having some standard for portability (hey, we are on NetBSD!) isn't a bad thing. Before POSIX there had been the UNIX wars and divergence... It is good to use a UNIX standard to have portability without much configuring. Maybe having option -p for make is not really important but it can be a debugging aid.
No option -p for make?
Hello, why doesn't the NetBSD make(1)s have a -p option? Is'nt that option suggested by posix? (Compare e.g. http://pubs.opengroup.org/onlinepubs/009695399/utilities/make.html) Although it doesn't help portability to use this internal information it would at least help to check that the internal rules are POSIX. Carsten
Aw: Re: File system encryption which is compatible to Linux
http://pkgsrc.se/filesystems/fuse-encfs for a live system. The package in pkgsrc-current is unfortunately very outdated (1.2.0 vs 1.7.5) and does not compile (at least under NetBSD amd64 7.99.15) :(
Aw: Re: File system encryption which is compatible to Linux
Julian Suschlik julian.susch...@gmail.com wrote: I use tar + openssl enc -aes-256-cbc for backups and http://pkgsrc.se/filesystems/fuse-encfs for a live system. It need to be a live system. I had found encfs too, but when I read at the homepage that it stores number of files and length of filename information as clear text I asked if there is something better. But maybe I should try it. Thanx, Carsten
Aw: Re: Re: Request to reconsider removal of groff from base system
Thor Lancelot Simon t...@panix.com wrote: mandoc(1) does not process roff. Very simplified described it acts somehow like nroff -mandoc ... or troff -mandoc There it understands a large subset of the nroff/troff language. (Only a few useres need real nroff/troff for typesetting other documents than manpages.) Carsten
Aw: RE: Re: Re: Request to reconsider removal of groff from base system
Again this is an enhancement? Can mandoc handle tbl and pic input? It can handle tbl input. I'm not shure about pic but there may not be many manpages using pic. UNIX has had the *roff tool suite for a long time. A text formatter is how they got support from management to continue work on UNIX. I doubt we would be talking about UNIX today if it wasn't for the suite. This is all true. And no one intends to remove groff. But it should not make a difference if groff is in the base or you need just a simple pkgin install groff to get it, so the situation would not change much from now.
NetBSD 6.1.5: firefox24 crashes
Hello, I have just upgraded 6.1.4 - 6.1.5, now firefox24 immediately crashes at start with Memory fault. This did not happen on 6.1.4. I have a amd64 system (actually qemu-kvm on Linux, but that should not matter). I did pkgin update and full-upgrade but that did not help. (Is there any ongoing work on a newer firefox version? An outdated firefox may be one of the biggest security issues ...) Carsten
Aw: Re: problem with mount_psshfs
What's the full command you use to launch your guest? Is it a a raw file or a real partition? Have you enabled tunnels? Are you using bridges, tun/tap, etc. It's a raw file, did not know that partition also would work ;) I use a bridge. Don't know about tunnels. I hav really big problems with perl operating on this sshfs. (Memory fault and other unexpected internal errors I never saw before.) Maybe this has also to do with that. qemu-kvm\ -m 2048\ -hda /mnt/qemu/nbsd614.qemu\ -netdev bridge,id=hn0\ -device virtio-net-pci,netdev=hn0,id=nic1,mac=52:54:00:12:34:57\ -vga std\ -sdl -no-frame\ -usb -usbdevice mouse\ -name NetBSD\ -alt-grab\ -soundhw all
Aw: Re: Re: problem with mount_psshfs
Have you started qemu as root or standard user? I start it as root. And, just to make sure the problem is not in the bridge, could you start qemu with user mode networking and enable redirection (check the manual for the -redir argument). Long time ago I used user mode networking but now I don't get it working. The -redir option seems not to be well documented--maybe it's obsoltete? (I use qemu 1.2.0.) I think I use Linux to mount a NetBSD filesystem for the time being... Thank you all...
Aw: Re: problem with mount_psshfs
My guess is that if mount_psshfs is even sort of working, and it's about ro vs rw files, then the OP is not having a networking problem. That makes sense. What is strange is that cp(1) does not work when the target file is not present (in a 700 dir). It does only work if a writeable file is present. Unfortunately I can't use it anyway at the moment. My backup system uses p5-Tk which seems to cause random memory faults which I saw when testing with ktrace(1).
Aw: Re: Aw: Re: problem with mount_psshfs
That does not sound so odd to me. cp likely has different code paths to open an existing file for writing vs a new file. If the directory is 755, or some other mode, did this not happen? When I copy a file (NetBSD) with 644 perms and owner 1000:0 into a dir (Linux) with 700 perms and owner 1000:1000 I get: $ ls -al total 36028797018963967 drwx-- 2 carsten carsten 60 Aug 7 17:38 ./ drwxrwxrwt 8 rootwheel 180 Aug 7 17:36 ../ -rw-r--r-- 1 4294967295 42949672956 Aug 7 17:43 a This scares me... (the number after total and the senseless owner ids) When I now change the local file to 400 I get: $ cp /tmp/a . cp: ./a: Operation not permitted But the file is created *empty* (dir had been empty): $ ls -la total 0 drwx-- 2 carsten carsten 60 Aug 7 17:43 ./ drwxrwxrwt 8 root wheel180 Aug 7 17:36 ../ -r 1 carsten carsten0 Aug 7 17:44 a If the dir has 755 it is the same. The problem is the 400 of the source file. If the source file is 600 it works. After some tests also the owner ids are ok. Not very reliable...
p5-Tk crashes
Hello, I have very often crashes on using p5-Tk. On error message is Memory fault a others is: 7f7ff5340a98 is not a hash at /usr/pkg/lib/perl5/vendor_perl/5.20.0/x86_64-netbsd-thread-multi/Tk/MainWindow.pm line 53. Abort (The address changes, but it is always MainWindow.pm line 53) ktrace on the Memory fault crash says: ... 1429 1 perl CALL read(4,0x7f7ff4fab000,0x4000) 1429 1 perl GIO fd 4 read 1723 bytes /*\n * (c) Copyright 1990 1991 Tektronix Inc.\n * All Rights Reserved\n *\n * Permission to use, copy, modify, and distribute this software and its\n * docum\ entation for any purpose and without fee is hereby granted,\n * provided that the above copyright notice appear in all copies and that\n * both that copyright noti\ ce and this permission notice appear in\n * supporting documentation, and that the name of Tektronix not be used\n * in advertising or publicity pertaining to dist\ ribution of the software\n * without specific, written prior permission.\n *\n * Tektronix disclaims all warranties with regard to this software, including\n * all\ implied warranties of merchantability and fitness, in no event shall\n * Tektronix be liable for any special, indirect or consequential damages or\n * any damages\ whatsoever resulting from loss of use, data or profits,\n * whether in an action of contract, negligence or other tortious action,\n * arising out of or in connec\ tion with the use or performance of this\n * software.\n *\n *\n * NAME\n *Xcms.txt\n *\n *DESCRIPTION\n * Sample Color Name D\ atabase\n *\n */\n\n\nThis device-independent color name database is provided just as an example.\nThere are no claims that these color specifications are or shoul\ d be bound\nto the corresponding color name.\n\nAs you can see, the start of the database is indicated by \XCMS_COLORDB_START\.\nAnything before this is assumed \ to be comments. The \0.1\ indicates the\nversion number of the format/syntax used in this file. The color name is\ndelimited from the color specification by on\ e or more tabs.\n\nXCMS_COLORDB_START 0.1\ncms red CIEXYZ:0.3811/0.2073/0.0213\ncms green CIEXYZ:0.3203/0.6805/0.1430\ncms blue \ CIEXYZ:0.2483/0.1122/1.2417\nXCMS_COLORDB_END\n 1429 1 perl RET read 1723/0x6bb 1429 1 perl CALL lseek(4,0,0,1) 1429 1 perl RET lseek 1723/0x6bb 1429 1 perl CALL close(4) 1429 1 perl RET close 0 1429 1 perl CALL poll(0x7f7fd280,1,0x) 1429 1 perl RET poll 1 1429 1 perl CALL writev(3,0x7f7fd350,3) 1429 1 perl GIO fd 3 wrote 20 bytes U\^A\^E\0 \0\0\0\^E\0CCBlack\0\0\0 1429 1 perl RET writev 20/0x14 1429 1 perl CALL poll(0x7f7fd260,1,0x) 1429 1 perl RET poll 1 1429 1 perl CALL read(3,0x7f7ff4f60074,0x1000) 1429 1 perl GIO fd 3 read 32 bytes \^A\0\^U\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^?\^?\0\0 1429 1 perl RET read 32/0x20 1429 1 perl CALL read(3,0x7f7ff4f60074,0x1000) 1429 1 perl RET read -1 errno 35 Resource temporarily unavailable 1429 1 perl CALL read(3,0x7f7ff4f60074,0x1000) 1429 1 perl RET read -1 errno 35 Resource temporarily unavailable 1429 1 perl PSIG SIGSEGV SIG_DFL: code=SEGV_MAPERR, addr=0xc, trap=6) File descriptor 3 could be something like /tmp/.X11-unix/X0. Does anyone has an idea? --Carsten
Aw: Re: pkgin: mplayer-1.1.1nb1 is not available on the repository
Are not all packages available for all amd64 NetBSD releases? And if yes--why did pkgin not know this? You cannot distribute useful binary package for MPlayer for legal reasons. I know that from Linux, but had not expected it on NetBSD. But if that's the reason why does pkgin avail list it? Or do I have do setup an alternative server path to be able to install it?
Aw: Re: pkgin: mplayer-1.1.1nb1 is not available on the repository
Did you do a pkgin up The system had been installed 3 days ago. I did not made an update, but if I do it does not change anything. by any chance? When I do a pkgin av it shows that mplayer-1.1.1nb3 Fast, cross-platform movie player is available. Exactly what I am saying. It thinks it is available but it is not (I get the same output like you, but if I do the install it is not there.)
Aw: Re: Using USB stick in a qemu NetBSD guest on a Linux host
FYI, remember that disks and partitions within disks are named differently in NetBSD than in Linux. /dev/sda in Linux is like saying /dev/sd0 in NetBSD. Maybe that's why you can't see the USB stick inside the NetBSD VM. I could attach the device with qemu monitor with usb_add host:VendorID:ProductID but then mouse and keyboard does not work anymore. If I use -usbdevice host:VendorID:ProductID the device is not recognized ...
Aw: Re: Using USB stick in a qemu NetBSD guest on a Linux host
FYI, remember that disks and partitions within disks are named differently in NetBSD than in Linux. /dev/sda in Linux is like saying /dev/sd0 in NetBSD. Maybe that's why you can't see the USB stick inside the NetBSD VM. The USB device is /dev/sde, there is only one primary partition /dev/sde1. I use the option -hdb /dev/sde1. There is nothing in dmesg and usbdevs reports only the mouse. What would be the correct option? Carsten
Aw: Re: Using USB stick in a qemu NetBSD guest on a Linux host
FYI, remember that disks and partitions within disks are named differently in NetBSD than in Linux. /dev/sda in Linux is like saying /dev/sd0 in NetBSD. Maybe that's why you can't see the USB stick inside the NetBSD VM. Thank you, it has been a problem with a script I use. It works indeed with -hdb /dev/sde1.
Using USB stick in a qemu NetBSD guest on a Linux host
Hello, I am using NetBSD as a qemu guest on a Linux host. I'd like to use a USB stick and tried e.b. -hdb /dev/sdb or -usbdevice disk::/dev/sdb but nothing works. Has anyone done this successfully? --Carsten