Re: Home NAS

2019-11-17 Thread Patrick Marchand
Hi,

On 11/17, Predrag Punosevac wrote:
> Patrick Marchand  wrote:
> > On 11/15, Predrag Punosevac wrote:
> > > Patrick Marchand wrote:
> > > > I'll be playing around with DragonflyBSD Hammer2 (and multiple offsite
> > > > backups) for a home NAS over the next few weeks. I'll probably do a
> > > > presentation about the experience at the Montreal BSD user group
> > > > afterwards. It does not require as many ressources as ZFS or BTRFS,
> > > > but offers many similar features.
> > > >
> > >
> > > Been there, done that!
> > Cool ! I might ping you off-list with questions when I get to it.
> >
>
> Any time. Either this private email or at my work predr...@cs.cmu.edu
> I wish I was a bit closer to Montreal to come to your monthly meeting. I
> love Quebec and Montreal in particular.
Thanks !

> > I'm not planning on using jails much, instead I'll be using the
> > DFly NFS with OpenBSD to experiment with virtualization.
> >
>
>
> I am not sure that I am following. How is DF NFS server related to
> OpenBSD (if I understand correctly) virtualization. Are you trying to
> store OpenBSD vmm images on the NFS share exported from a DF server?
> That is a really, really bad idea.
>
>
> https://marc.info/?l=dragonfly-users=140384130921709=2
MirageOS and PXE booted OpenBSD is what I really want to play with,
but well see as I go along, breaking stuff is kind of the idea here.

>
> > > DragonFly which gets it software RAID discipline through old
> > > unmaintained FreeBSD natacontrol utility. Hardware RAID cards are not
> > > frequently tested and community seems to be keen on treating DF as a
> > > desktop OS rather than a storage workhorse. Having said that HDD are
> > > cheap this days and home users probably don't need anything bigger than
> > > a 12TB mirror.
> > I dont store much anyways, so I'll see as I go.
> >
>
> 12 TB is the sweet spot when it comes GB/dollar for platter HDDs.
As it's more for an experiment and maybe some bsd systems work and
it will be running in my room, I started with a 1TB ssd.



Re: Home NAS

2019-11-17 Thread Patrick Marchand
Hello,

On 11/15, Predrag Punosevac wrote:
> Patrick Marchand wrote:
> > I'll be playing around with DragonflyBSD Hammer2 (and multiple offsite
> > backups) for a home NAS over the next few weeks. I'll probably do a
> > presentation about the experience at the Montreal BSD user group
> > afterwards. It does not require as many ressources as ZFS or BTRFS,
> > but offers many similar features.
> >
>
> Been there, done that!
Cool ! I might ping you off-list with questions when I get to it.

> H2 lacks built in backup mechanism. I was hoping that H2 will get some
> kind "hammer mirror-copy" of H1, or "zfs send/receive". My server is
> still on H1 and I really enjoy being able to continuously back it up.
> That's the only thing I am missing in H2. On the positive note H2 did
> get support for boot environment manager last year.
>
> https://github.com/newnix/dfbeadm
>
> Also DF jails are stuck in 2004 or something like that. I like their
> NFSv3.
I'm not planning on using jails much, instead I'll be using the
DFly NFS with OpenBSD to experiment with virtualization.

> DragonFly which gets it software RAID discipline through old
> unmaintained FreeBSD natacontrol utility. Hardware RAID cards are not
> frequently tested and community seems to be keen on treating DF as a
> desktop OS rather than a storage workhorse. Having said that HDD are
> cheap this days and home users probably don't need anything bigger than
> a 12TB mirror.
I dont store much anyways, so I'll see as I go.

Regards



Re: Home Nas -> Montreal BUG

2019-11-16 Thread Patrick Marchand
Hey,

Since I'm getting off-list questions from more than one person,
I'll post here as well.

On 11/15, Patrick Marchand wrote:
> I'll be playing around with DragonflyBSD Hammer2 (and multiple offsite
> backups) for a home NAS over the next few weeks. I'll probably do a
> presentation about the experience at the Montreal BSD user group afterwards.
> It does not require as many ressources as ZFS or BTRFS, but offers many
> similar features.

It's brand spanking new and I havent advertised much beyond Mastodon
and l'Agenda du Libre. (Somebody at work posted it in the work owned
meetup, but that's not a platform I want as a main base).

The actual link for the next event (on the 27th of november) is
here: https://agendadulibre.qc.ca/events/2050, I'm planning it as
a free (as in free of scheduled activities) session where people
will have access to food, drinks and wifi so they can ask configuration
questions, install a BSD, work on a port, etc..

We've had one meeting already (https://agendadulibre.qc.ca/events/2038),
where I presented my experience with building an OpenBSD based home
router and we had a round table of discussion on BSD systems in
general. Including me and two work colleagues, we were 10 people
(I honestly thought nobody would come at first, so I'm happy!).
I'll post the slides online soon.

Format wise I'm thinking of holding it monthly, alternating
presentations and free sessions. Presentations can be given in the
language of your choice, but french is encouraged. Nothing is set
in stone yet, so we'll see how it evolves. I do need to create a
website, mailing list and caldav for it, but for now questions and
ideas for presentations can be sent to m...@patrickmarchand.com or
@mathuin@bsd.network (mastodon)

Au plaisir



Re: Home NAS

2019-11-15 Thread Patrick Marchand

Hi,


I'll be playing around with DragonflyBSD Hammer2 (and multiple offsite 
backups) for a home NAS over the next few weeks. I'll probably do a 
presentation about the experience at the Montreal BSD user group 
afterwards. It does not require as many ressources as ZFS or BTRFS, but 
offers many similar features.


As for OpenBSD as a home NAS, I'm sure it would be fine if you're 
diligent about backups. You might also want to get a small UPS for it (I 
bought a refurbished APC for 80$), so frequent but short power 
interruptions do not require an FFS integrity check. (I do this for my 
router)


Pleasure



Re: Ergonomic USB wired mouse

2019-08-19 Thread Patrick Marchand
Hello,

On 08/19, Oliver Marugg wrote:
> I am preparing switching my desktop from another OS to OpenBSD. Is anyone
> using an Evoluent USB Wired Mouse (C/4 or 4 small) with OpenBSD? Or any
> other great ideas about an ergonomic mouse working with OpenBSD?

Most mouses should work, though I remember having problems with
mouses that have more than 3 buttons (The extra buttons didnt do
anything)

I'm using the contour unimouse right now and it works great.
Trackballs work as well.

Have a nice day



Re: New laptop recommendations

2018-06-19 Thread Patrick Marchand
You can get a pretty good refurbished 3th gen thinkpad x1 carbon under 900$.
I've baught two on ebay over the last year,



Re: Buying new laptop, looking for feedback

2018-05-15 Thread Patrick Marchand

I've been using a 3rd gen x1 carbon for half a year now and havent had any 
problems

OpenBSD 6.3-current (GENERIC.MP) #33: Mon May  7 18:59:05 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8261529600 (7878MB)
avail mem = 8003121152 (7632MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries)
bios0: vendor LENOVO version "N14ET42W (1.20 )" date 09/13/2017
bios0: LENOVO 20BTS0Y500
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.61 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 3 (EXP1)
acpiprt3 at acpi0: bus 4 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpiprt5 at acpi0: bus 10 (EXP6)
acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1
acpipwrres1 at acpi0: NVP3, resource for PEG_
acpipwrres2 at acpi0: NVP2, resource for PEG_
acpitz0 at acpi0: critical temperature is 128 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpicmos0 at acpi0
"LEN0071" at acpi0 not configured
"LEN0048" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "00HW003" serial   716 type LiP oem "SMP"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"INT340F" at acpi0 not configured
acpivideo0 at acpi0: VID_
acpivout at acpivideo0 not configured
acpivideo1 at acpi0: VID_
cpu0: Enhanced SpeedStep 2494 MHz: speeds: 2601, 2600, 2500, 2300, 2100, 2000, 
1800, 1700, 1500, 1400, 1200, 1100, 

Re: wsmouse mapping button clicks

2018-05-14 Thread Patrick Marchand
On 05/14, Ulf Brosziewski wrote:
> Hi Patrick,
> 
> thanks for the infos.  I'm afraid you're out of luck, it seems
> that this device would need vendor-/model-specific extensions
> in our HID-mouse driver.  It only announces two "regular" buttons,
> so our driver won't look for more (what xinput shows as buttons 4
> and 5 are mappings from "Z axis" values).  No kind of button
> mapping will help.  If it's a workaround for you, you might enable
> middle-button emulation in X.
> 
I was afraid of that. Well guess I'll have to return it then.

Has anybody tried a Contour Unicomp mouse? I'm guessing it should 
work fine and will probably be ideal for use with acme.

Thanks for the help Ulf.



Re: wsmouse mapping button clicks

2018-05-14 Thread Patrick Marchand
On 05/14, Ulf Brosziewski wrote:
> Would you mind to run
> $ xinput --test /dev/wsmouse
> in an X terminal, press each button once, grab the output,
> and post it here?
Output:

motion a[0]=1364 a[1]=907 
button press   4 
button release 4 
motion a[0]=1365 
motion a[0]=1367 
motion a[0]=1368 
motion a[0]=1370 
motion a[0]=1372 a[1]=906 
motion a[0]=1373 a[1]=905 
motion a[0]=1375 a[1]=904 
motion a[0]=1377 a[1]=903 
motion a[0]=1378 a[1]=902 
motion a[0]=1379 a[1]=901 
motion a[0]=1380 
motion a[0]=1381 a[1]=900 
motion a[0]=1382 
motion a[0]=1381 
motion a[0]=1380 
button press   5 
button release 5 
button press   5 
button release 5 
button press   5 
button release 5 
button press   1 
button release 1 
button press   3 
button release 3 

So button 1 the left click
Button 3 is the right click
Motion is moving the ball
Button 4 and 5 are the scroll function on the ball
Clicking on the upper two button of the mouse does not register any events.



wsmouse mapping button clicks

2018-05-13 Thread Patrick Marchand
I bought myself a Kensington Slimblade mouse the other day, 
it is a trackball mouse with 4 buttons and scrolling features. 
It mostly works out of the box, but openbsd seems to only detect 
two of the buttons, leaving me without a middle click. I'd like to find
a way to program the two other buttons to do as I wish, but am at a loss
on how to do it. I've read the man page for wsmouse and wsmoused, but I
havent been able to do anything useful.

Somebody on bsd.network suggested using synclient with the synaptics driver, 
but I wanted to try it with the default driver first.

 SCSI3 0/direct 
fixed naa.50025389
sd0: 244198MB, 512 bytes/sector, 500118192 sectors, thin
ehci0 at pci0 dev 29 function 0 "Intel 9 Series USB" rev 0x03: apic 2 int 23
usb1 at ehci0: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 
addr 1
pcib0 at pci0 dev 31 function 0 "Intel 9 Series LPC" rev 0x03
ichiic0 at pci0 dev 31 function 3 "Intel 9 Series SMBus" rev 0x03: apic 2 int 18
iic0 at ichiic0
pchtemp0 at pci0 dev 31 function 6 "Intel 9 Series Thermal" rev 0x03
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
wsmouse1 at pms0 mux 0
pms0: Synaptics clickpad, firmware 8.1, 0x1e2b1 0x943300
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
vmm0 at mainbus0: VMX/EPT
Unclaimed register detected before reading register 0x23a0
uhidev0 at uhub0 port 1 configuration 1 interface 0 "Dell Dell USB Keyboard" 
rev 1.10/3.06 addr 2
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub0 port 2 configuration 1 interface 0 "Kensington Kensington 
Slimblade Trackball" rev 1.10/1.09 addr 3
uhidev1: iclass 3/1
ums0 at uhidev1: 2 buttons, Z dir
wsmouse2 at ums0 mux 0
uvideo0 at uhub0 port 8 configuration 1 interface 0 "Chicony Electronics 
Co.,Ltd. Integrated Camera" rev 2.00/0.29 addr 4
video0 at uvideo0
uhub2 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 
2.00/0.03 addr 2
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (f799eb61a98c803a.a) swap on sd0b dump on sd0b
iwm0: hw rev 0x210, fw ver 16.242414.0, address 60:57:18:91:b7:16
error: [drm:pid9886:intel_pipe_update_start] *ERROR* Potential atomic update 
failure on pipe A
uid 1000 on /tmp: file system full
dist/dist-sandbox-dc80bf54/build/Basement/Terminal/Size_hsc_make(16645): W^X 
binary outside wxallowed mountpoint
syncing disks... done
rebooti
OpenBSD 6.3-current (GENERIC.MP) #33: Mon May  7 18:59:05 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8261529600 (7878MB)
avail mem = 8003108864 (7632MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries)
bios0: vendor LENOVO version "N14ET42W (1.20 )" date 09/13/2017
bios0: LENOVO 20BTS0Y500
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.63 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
cpu2: 

Re: Kakoune editor on openbsd

2018-04-16 Thread Patrick Marchand
> On 04/16, Stuart Henderson wrote:
> > On 2018-04-16, Patrick Marchand <m...@patrickmarchand.com> wrote:
> > So trying again I looked closer at what the function was doing and how
> > it was implemented for freebsd and dragonflybsd. The function
> > tries to find the executable path of kak, but the freebsd way of doing
> > it doesnt work because it doesnt seem like KERN_PROC_PATHNAME is defined
> > in openbsd? So whats the preferred way of doing this on openbsd?
> 
> Hardcode it.
If anybody wants to play with it, heres my tentative pull request
https://github.com/mawww/kakoune/pull/2005
 
Kakoune has at least one stable release, so I might make this my first
try at creating an openbsd package.



Kakoune editor on openbsd

2018-04-16 Thread Patrick Marchand
So I'd like to try the kakoune editor on openbsd 6.3-current. 

For now I've identified two files that stop me from compiling the project, 
The first one is the makefile, which requires gmake and has a os
specific command for finding ncursesw and the second one is the file.cc
file in the get_kak_binary_path function, where there is also os specific
preprocessing.

My naive fix was to copy paste the dragonflybsd entries and rename them
to openbsd and while it does allow the project to compile, it
understandably aborts when run.

So trying again I looked closer at what the function was doing and how
it was implemented for freebsd and dragonflybsd. The function
tries to find the executable path of kak, but the freebsd way of doing
it doesnt work because it doesnt seem like KERN_PROC_PATHNAME is defined
in openbsd? So whats the preferred way of doing this on openbsd?

https://github.com/mawww/kakoune/blob/master/src/file.cc
https://github.com/mawww/kakoune/tree/master/src

Thanks,
Patrick Marchand



Re: Compilations errors with plan9port on 2018/04/05 snapshot

2018-04-08 Thread Patrick Marchand
On 04/08, Gleydson Soares wrote:
> Hi Patrick,
> could you please test this diff?
> https://marc.info/?l=openbsd-ports=152160090624047=2

The diff worked, I was able to run plumber, factotum and acme without
any aborts. 

Thanks!



Re: Compilations errors with plan9port on 2018/04/05 snapshot

2018-04-08 Thread Patrick Marchand
On 04/08, Theo de Raadt wrote:
> At the moment snapshots contain the MAP_STACK diff.  Your program is
> setting up threads incorrectly (it has it's own thread library?),
> resulting in stacks not being mapped with MAP_STACK.  Stacks must be
> carefully setup now.  ktrace -di may expose the memory allocation which
> setup an address corresponding to a crash, basically a mmap with MAP_STACK
> will be missing.
So there is a mmap right before it crashes and it does not set
MAP_STACK, only MAP_PRIVATE|MAP_ANON. I dont exactly have the time to
investigate more today, but I'll look at it again later this week. In
the meantime I've joined the output of kdump.
 39430 ktrace   RET   ktrace 0
 39430 ktrace   CALL  execve(0x7f7c5630,0x7f7c5bb8,0x7f7c5bd0)
 39430 ktrace   NAMI  "/home/patrick/bin/9"
 39430 ktrace   RET   execve -1 errno 2 No such file or directory
 39430 ktrace   CALL  execve(0x7f7c5630,0x7f7c5bb8,0x7f7c5bd0)
 39430 ktrace   NAMI  "/bin/9"
 39430 ktrace   RET   execve -1 errno 2 No such file or directory
 39430 ktrace   CALL  execve(0x7f7c5630,0x7f7c5bb8,0x7f7c5bd0)
 39430 ktrace   NAMI  "/sbin/9"
 39430 ktrace   RET   execve -1 errno 2 No such file or directory
 39430 ktrace   CALL  execve(0x7f7c5630,0x7f7c5bb8,0x7f7c5bd0)
 39430 ktrace   NAMI  "/usr/bin/9"
 39430 ktrace   RET   execve -1 errno 2 No such file or directory
 39430 ktrace   CALL  execve(0x7f7c5630,0x7f7c5bb8,0x7f7c5bd0)
 39430 ktrace   NAMI  "/usr/sbin/9"
 39430 ktrace   RET   execve -1 errno 2 No such file or directory
 39430 ktrace   CALL  execve(0x7f7c5630,0x7f7c5bb8,0x7f7c5bd0)
 39430 ktrace   NAMI  "/usr/X11R6/bin/9"
 39430 ktrace   RET   execve -1 errno 2 No such file or directory
 39430 ktrace   CALL  execve(0x7f7c5630,0x7f7c5bb8,0x7f7c5bd0)
 39430 ktrace   NAMI  "/usr/local/bin/9"
 39430 ktrace   NAMI  "/bin/sh"
 39430 ktrace   ARGS  
[0] = "/bin/sh"
[1] = "/usr/local/bin/9"
[2] = "acme"
 39430 sh   RET   execve 0
 39430 sh   CALL  mprotect(0xf880fa832d0,0x1d20,0x1)
 39430 sh   RET   mprotect 0
 39430 sh   CALL  kbind(0,0,0)
 39430 sh   RET   kbind 0
 39430 sh   CALL  
mmap(0,0x40,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 17088257970176/0xf8aab8bd000
 39430 sh   CALL  getthrid()
 39430 sh   RET   getthrid 125773/0x1eb4d
 39430 sh   CALL  __set_tcb(0xf8aab8bd000)
 39430 sh   RET   __set_tcb 0
 39430 sh   CALL  
mmap(0,0x1000,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 17085717172224/0xf8a141a5000
 39430 sh   CALL  mprotect(0xf8a141a5000,0x1000,0x1)
 39430 sh   RET   mprotect 0
 39430 sh   CALL  pledge(0xf880f9731c2,0)
 39430 sh   STRU  promise="stdio rpath wpath cpath fattr flock getpw proc 
exec tty"
 39430 sh   RET   pledge 0
 39430 sh   CALL  readlink(0xf880f975f8e,0x7f7cd4a0,63)
 39430 sh   NAMI  "/etc/malloc.conf"
 39430 sh   RET   readlink -1 errno 2 No such file or directory
 39430 sh   CALL  issetugid()
 39430 sh   RET   issetugid 0
 39430 sh   CALL  getentropy(0x7f7cd430,40)
 39430 sh   RET   getentropy 0
 39430 sh   CALL  
mmap(0,0x450,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 17086025576448/0xf8a267c3000
 39430 sh   CALL  minherit(0xf8a267c3000,0x450,MAP_INHERIT_ZERO)
 39430 sh   RET   minherit 0
 39430 sh   CALL  mprotect(0xf880fa92000,0x1000,0x3)
 39430 sh   RET   mprotect 0
 39430 sh   CALL  
mmap(0,0x4000,0,0x1002,-1,0)
 39430 sh   RET   mmap 17088441876480/0xf8ab682
 39430 sh   CALL  mprotect(0xf8ab6821000,0x2000,0x3)
 39430 sh   RET   mprotect 0
 39430 sh   CALL  
mmap(0,0x1000,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 17089010298880/0xf8ad8637000
 39430 sh   CALL  mprotect(0xf880fa92000,0x1000,0x1)
 39430 sh   RET   mprotect 0
 39430 sh   CALL  
mmap(0,0x1000,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 17087969476608/0xf8a9a59c000
 39430 sh   CALL  
mmap(0,0x1000,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 17088927444992/0xf8ad3733000
 39430 sh   CALL  
mmap(0,0x1000,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 17087480500224/0xf8a7d349000
 39430 sh   CALL  
mmap(0,0x1000,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 17089152483328/0xf8ae0dd
 39430 sh   CALL  
mmap(0,0x1000,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 17086353305600/0xf8a3a04f000
 39430 sh   CALL  
mmap(0,0x1000,0x3,0x1002,-1,0)
 39430 sh   RET   mmap 

Re: Compilations errors with plan9port on 2018/04/05 snapshot

2018-04-08 Thread Patrick Marchand
On 04/08, Patrick Marchand wrote:
> Compilation succeeds on the april 8 snapshot

Though now I'm getting Abort Trap whenever I try to run the plumber or
acme. I was able to compile some programs with mk though, as I compiled
both $PLAN9/src/cmd/upas and $PLAN9/src/cmd/upas/nfs. I've joined the
dmesg of the current system.
OpenBSD 6.3-current (GENERIC.MP) #135: Thu Apr  5 12:31:23 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8261529600 (7878MB)
avail mem = 8004063232 (7633MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries)
bios0: vendor LENOVO version "N14ET42W (1.20 )" date 09/13/2017
bios0: LENOVO 20BTS0Y500
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.67 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
acpihpet0: recalibrated TSC frequency 2593995060 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 3 (EXP1)
acpiprt3 at acpi0: bus 4 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpiprt5 at acpi0: bus 10 (EXP6)
acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1
acpipwrres1 at acpi0: NVP3, resource for PEG_
acpipwrres2 at acpi0: NVP2, resource for PEG_
acpitz0 at acpi0: critical temperature is 128 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpicmos0 at acpi0
"LEN0071" at acpi0 not configured
"LEN0048" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "00HW003" serial   716 type LiP oem "SMP"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0

Re: Compilations errors with plan9port on 2018/04/05 snapshot

2018-04-08 Thread Patrick Marchand
Compilation succeeds on the april 8 snapshot



Re: Compilations errors with plan9port on 2018/04/05 snapshot

2018-04-06 Thread Patrick Marchand
On 04/05, Philip Guenther wrote:
> On Thu, Apr 5, 2018 at 9:50 PM, Philip Guenther <guent...@gmail.com> wrote:
> 
> > On Thu, Apr 5, 2018 at 7:53 PM, Patrick Marchand <m...@patrickmarchand.com
> > > wrote:
> >
> >> Output of compiling plan9port on amd64 with the april 5 snaphot
> >>
> > ...
> >
> >> ===>  Patching for plan9port-20180117
> >> Segmentation fault (core dumped)
> >> *** Warning in /usr/ports/plan9/plan9port: "uname -m" returned non-zero
> >>
> >
> > dmesg from this box, please.
> >
> 
> Also, does this segfault happen consistently at that same exact spot, or is
> it inconsistent?

It appears to be inconsistent, I've joined a file containing a few
failed runs and another with the dmesg.
OpenBSD 6.3-current (GENERIC.MP) #135: Thu Apr  5 12:31:23 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8261529600 (7878MB)
avail mem = 8004067328 (7633MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries)
bios0: vendor LENOVO version "N14ET42W (1.20 )" date 09/13/2017
bios0: LENOVO 20BTS0Y500
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.59 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
acpihpet0: recalibrated TSC frequency 2593996580 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.22 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.22 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.22 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 3 (EXP1)
acpiprt3 at acpi0: bus 4 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpiprt5 at acpi0: bus 10 (EXP6)
acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33

Compilations errors with plan9port on 2018/04/05 snapshot

2018-04-05 Thread Patrick Marchand
Output of compiling plan9port on amd64 with the april 5 snaphot

===> plan9port-20180117 depends on: bzip2-* -> bzip2-1.0.6p8
===>  Verifying specs:  X11 Xext c m pthread util fontconfig freetype z
===>  found X11.16.1 Xext.13.0 c.92.3 m.10.1 pthread.25.1 util.13.0
fontconfig.11.0 freetype.28.2 z.5.0
===>  Checking files for plan9port-20180117
>> Fetch
>> https://github.com/9fans/plan9port/archive/019be4481fee53a999ccb73c78e40df5f408b24e.tar.gz
>> Fetch http://pdos.lcs.mit.edu/~rsc/pgw.tar.bz2
ftp: SSL write error: name `pdos.lcs.mit.edu' not present in server
certificate
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/plan9port/pgw.tar.bz2
pgw.tar.bz2  100%
|***|
9184 KB00:11
>> Fetch http://pdos.lcs.mit.edu/~rsc/software/plan9/roget.tar.bz2
ftp: SSL write error: name `pdos.lcs.mit.edu' not present in server
certificate
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/plan9port/roget.tar.bz2
roget.tar.bz2 100%
|**|
471 KB00:01
>> Fetch http://pdos.lcs.mit.edu/~rsc/scat.tgz
ftp: SSL write error: name `pdos.lcs.mit.edu' not present in server
certificate
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/plan9port/scat.tgz
scat.tgz 100%
|***|
5024 KB00:09
>> (SHA256) plan9port/019be4481fee53a999ccb73c78e40df5f408b24e.tar.gz:
>> OK
>> (SHA256) plan9port/pgw.tar.bz2: OK
>> (SHA256) plan9port/roget.tar.bz2: OK
>> (SHA256) plan9port/scat.tgz: OK
===>  Extracting for plan9port-20180117
cd
/usr/obj/ports/plan9port-20180117/plan9port-019be4481fee53a999ccb73c78e40df5f408b24e/dict
&& tar xjf /usr/ports/distfiles/plan9port/pgw.tar.bz2
cd
/usr/obj/ports/plan9port-20180117/plan9port-019be4481fee53a999ccb73c78e40df5f408b24e/dict
&& tar xjf /usr/ports/distfiles/plan9port/roget.tar.bz2
cd
/usr/obj/ports/plan9port-20180117/plan9port-019be4481fee53a999ccb73c78e40df5f408b24e/sky
&& tar xzf /usr/ports/distfiles/plan9port/scat.tgz
===>  Patching for plan9port-20180117
Segmentation fault (core dumped)
*** Warning in /usr/ports/plan9/plan9port: "uname -m" returned non-zero
status (/usr/ports/infrastructure/mk/arch-defines.mk:12)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: 

Re: Building software that requires older libressl on snapshots

2018-03-21 Thread Patrick Marchand
> There is a patch on rust-openssl to force the build using the latest
> suppported version (see 
> lang/rust/patches/patch-src_vendor_openssl-sys_build_rs).
Applying the patch worked
 
> Running testsuite is usually a good method to check breakage.
And the test suite passed
> For me, rust FFI is a bit a shame: it is a *copy* of C headers, written
> and maintained in Rust language. It is good for crosscompilation (as
> Rust know how to build stuff without any C headers), but it is awful to
> maintain and keep up-to-date.
I think I recall work being done on that front? And as I'm writting this
I realize you're the own who started the git issue. Issue #2239 on the
rust github. (pasting in st is a bit bonkers right now, so I'm not copy
pasting the url)

Thanks for the help



Building software that requires older libressl on snapshots

2018-03-20 Thread Patrick Marchand
So I'm trying to build pijul (rust vcs based on patch theory) but it
requires rust-openssl, which only supports the latest release of
libressl (2.6). Is there a quick fix to build software that requires an
older libressl than what is currently used in snapshots? Or should I try
to patch the rust-openssl source code myself.



Re: minor too small - pkg_add

2018-03-20 Thread Patrick Marchand
> > Wait a few hours until the next packages, built against 45.0, hit
> > the mirrors.
Yep retrying today all the packages installed correctly!



Re: minor too small - pkg_add

2018-03-19 Thread Patrick Marchand
> You updated from a base snapshot that had libssl.so.44.8 to one that
> has 45.0, but skipped the intervening 44.9 one.  Unfortunately, the
> package snapshot had been built against 44.9.
> 
> > a similar issue with libm. Now I can get around the error by building
> > the packages in ports, but I was wondering if there was an easy fix.
> 
> Wait a few hours until the next packages, built against 45.0, hit
> the mirrors.
> 

Oh that makes a lot more sense, I'll check it out when I get back from
work. 
Thanks 



Re: minor too small - pkg_add

2018-03-19 Thread Patrick Marchand
> It seems you have to update your snapshot because it's too old. It was
> shipped with the lib version 44.8 and the current is now 44.9 from the
> output. That mean your snapshot is too old and the packages have been built
> against a more recent snapshot.
> 
> Regards
Hhmm I guess it's possible that the snapshot was updated at the same
time I was installing the last snapshot. I'll try updating again and
will report back.



minor too small - pkg_add

2018-03-19 Thread Patrick Marchand
Hello,
I updated to the latest snapshot yesterday and when I run 
pkg_add -Dsnap -u a bunch of pkg will not upgrade because it cant find
ssl.44.9

It does find 44.8 and 45 but not that specific version, last week I had
a similar issue with libm. Now I can get around the error by building
the packages in ports, but I was wondering if there was an easy fix.

Thanks,
Patrick



Re: Trying to build golang on 9th march snapshot

2018-03-12 Thread Patrick Marchand
> Apparently something to do with Go according to a message I received
> off-list after writing to the maintainer of syncthing(1) earlier today:

In that case I'll wait for a diff on the golang port to appear in the
mailing list.



Trying to build golang on 9th march snapshot

2018-03-12 Thread Patrick Marchand
Like it says on the tin, I tried building golang so I could get fzf but
I get the following compilation errors. I got help to build rustlang
last time, so maybe golang is just a small fix away? I didnt see any
mention of golang in the ports mailing list in the last few days.

I'm guessing the response is to just update to the latest snapshot and
try again? I'm still learning the rules here.
===>  Checking files for go-1.9.2
`/usr/ports/distfiles/go1.9.2.src.tar.gz' is up to date.
>> (SHA256) go1.9.2.src.tar.gz: OK
===> go-1.9.2 depends on: go-bootstrap-* - not found
===>  Verifying install for go-bootstrap-* in lang/go-bootstrap
===>  Building for go-bootstrap-1.4.20171003
# Building C bootstrap tool.
cmd/dist

# Building compilers and Go bootstrap tool for host, openbsd/amd64.
lib9
libbio
liblink
cmd/cc
cmd/gc
cmd/6l
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/6l/../ld/dwarf.c:1479:15: 
warning: implicit conversion from 'int' to 'char' changes value from 156 to 
-100 [-Wconstant-conversion]
block[i++] = DW_OP_call_frame_cfa;
   ~ ^~~~
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/6l/../ld/dwarf.c:1763:21: 
warning: implicit conversion from 'int' to 'char' changes value from 144 to 
-112 [-Wconstant-conversion]
cput(DW_CFA_offset + FAKERETURNCOLUMN);  // return address
~~~^~~
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/6l/../ld/lib.h:168:13: 
note: expanded from macro 'cput'
{ *cbp++ = c;\
 ~ ^
2 warnings generated.
/usr/obj/ports/go-bootstrap-1.4.20171003/go/pkg/obj/openbsd_amd64/liblink.a(list6.o):
 In function `Dconv':
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/liblink/list6.c:214: warning: 
strcat() is almost always misused, please use strlcat()
/var/tmp/go-cbuild-wwgAkE/dwarf.o: In function `defptrto':
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/6l/../ld/dwarf.c:1109: 
warning: strcpy() is almost always misused, please use strlcpy()
cmd/6a
/var/tmp/go-cbuild-wwgAkE/lex.o: In function `macinc':
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/6a/../cc/macbody:583: 
warning: strcat() is almost always misused, please use strlcat()
/var/tmp/go-cbuild-wwgAkE/lex.o: In function `assemble':
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/6a/lex.c:145: warning: 
strcpy() is almost always misused, please use strlcpy()
cmd/6c
/usr/obj/ports/go-bootstrap-1.4.20171003/go/pkg/obj/openbsd_amd64/libcc.a(lex.o):
 In function `Tconv':
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/cc/lex.c:1408: warning: 
strcat() is almost always misused, please use strlcat()
/usr/obj/ports/go-bootstrap-1.4.20171003/go/pkg/obj/openbsd_amd64/libcc.a(lex.o):
 In function `compile':
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/cc/lex.c:237: warning: 
strcpy() is almost always misused, please use strlcpy()
cmd/6g
/usr/obj/ports/go-bootstrap-1.4.20171003/go/pkg/obj/openbsd_amd64/libgc.a(lex.o):
 In function `importfile':
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/gc/lex.c:743: warning: 
strcat() is almost always misused, please use strlcat()
/var/tmp/go-cbuild-wwgAkE/gobj.o: In function `dgostringptr':
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src/cmd/6g/gobj.c:203: warning: 
strcpy() is almost always misused, please use strlcpy()
runtime
errors
sync/atomic
sync
io
unicode
unicode/utf8
unicode/utf16
bytes
math
strings
strconv
bufio
sort
container/heap
encoding/base64
syscall
time
os
reflect
fmt
encoding
encoding/json
flag
path/filepath
path
io/ioutil
log
regexp/syntax
regexp
go/token
go/scanner
go/ast
go/parser
os/exec
os/signal
net/url
text/template/parse
text/template
go/doc
go/build
cmd/go
./make.bash: line 162: 73101 Abort trap  (core dumped) 
"$GOTOOLDIR"/go_bootstrap clean -i std
*** Error 134 in /usr/ports/lang/go-bootstrap (Makefile:72 'do-build': @cd 
/usr/obj/ports/go-bootstrap-1.4.20171003/go/src &&  CC="cc"  CXX=...)
*** Error 1 in /usr/ports/lang/go-bootstrap 
(/usr/ports/infrastructure/mk/bsd.port.mk:2738 
'/usr/obj/ports/go-bootstrap-1.4.20171003/build-amd64/.build_done')
*** Error 1 in /usr/ports/lang/go-bootstrap 
(/usr/ports/infrastructure/mk/bsd.port.mk:1938 
'/usr/ports/packages/amd64/all/go-bootstrap-1.4.20171003.tgz')
*** Error 1 in /usr/ports/lang/go-bootstrap 
(/usr/ports/infrastructure/mk/bsd.port.mk:2440 '_internal-package')
*** Error 1 in /usr/ports/lang/go-bootstrap 
(/usr/ports/infrastructure/mk/bsd.port.mk:2419 'package')
*** Error 1 in /usr/ports/lang/go-bootstrap 
(/usr/ports/infrastructure/mk/bsd.port.mk:1956 
'/var/db/pkg/go-bootstrap-1.4.20171003/+CONTENTS')
*** Error 1 in /usr/ports/lang/go-bootstrap 
(/usr/ports/infrastructure/mk/bsd.port.mk:2419 'install')
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2073 
'/usr/obj/ports/go-1.9.2/.dep-lang-go-bootstrap')
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2508 
'/usr/obj/ports/go-1.9.2/.extract_done')
*** Error 1 in . 

Re: Fwd: Trying to build rust 1.24 on -current

2018-03-12 Thread Patrick Marchand
> Temporary hack to get it building until semarie can generate new bootstraps:
> 
> post-extract:
>   cp /usr/lib/libpthread.so.25.1 \
>   ${WRKDIR}/rustc-bootstrap-${MACHINE_ARCH}-1.24.0-20180213/lib/

Yep, that worked, thanks.



Fwd: Trying to build rust 1.24 on -current

2018-03-11 Thread Patrick Marchand
Sent this to ports, but maybe it's better for misc? Tell me if I'm
wrong.

- Forwarded message from math...@posteo.net -

> From: math...@posteo.net
> To: po...@openbsd.org
> Date: Sun, 11 Mar 2018 17:05:03 -0400
> Subject: Trying to build rust 1.24 on -current
>=20
> So I updated to -current yesterday and noticed that there was no binary
> package for rust available in snapshots. So I setup ports, pkg installed
> all of it's dependencies and then tried running make install.=20
>=20
> It error's out and I'm not sure I understand why. I attached the output
> as a .txt file.

> =3D=3D=3D>  Checking files for rust-1.24.0
> `/usr/ports/distfiles/rust/rustc-1.24.0-src.tar.gz' is up to date.
> `/usr/ports/distfiles/rust/rustc-bootstrap-amd64-1.24.0-20180213.tar.gz' =
is up to date.
> >> (SHA256) rust/rustc-1.24.0-src.tar.gz: OK
> >> (SHA256) rust/rustc-bootstrap-amd64-1.24.0-20180213.tar.gz: OK
> =3D=3D=3D> rust-1.24.0 depends on: cmake-* -> cmake-3.9.3
> =3D=3D=3D> rust-1.24.0 depends on: bash-* -> bash-4.4.19
> =3D=3D=3D> rust-1.24.0 depends on: llvm-* -> llvm-5.0.1p1
> =3D=3D=3D> rust-1.24.0 depends on: ninja-* -> ninja-1.8.2
> =3D=3D=3D> rust-1.24.0 depends on: python->=3D2.7,<2.8 -> python-2.7.14p0
> =3D=3D=3D> rust-1.24.0 depends on: gmake-* -> gmake-4.2.1
> =3D=3D=3D> rust-1.24.0 depends on: libtool-* -> libtool-2.4.2p0
> =3D=3D=3D> rust-1.24.0 depends on: libgit2-* -> libgit2-0.26.0p1
> =3D=3D=3D> rust-1.24.0 depends on: curl-* -> curl-7.58.0p0
> =3D=3D=3D> rust-1.24.0 depends on: libssh2-* -> libssh2-1.8.0
> =3D=3D=3D>  Verifying specs:  c++ c++abi pthread c crypto curl git2 m pth=
read ssh2 ssl z=20
> =3D=3D=3D>  found c++.1.0 c++abi.0.0 pthread.25.1 c.92.3 crypto.42.7 curl=
=2E25.14 git2.10.0 m.10.0 ssh2.8.0 ssl.44.8 z.5.0
> =3D=3D=3D>  Extracting for rust-1.24.0
> =3D=3D=3D>  Patching for rust-1.24.0
> =3D=3D=3D>   Applying OpenBSD patch patch-src_bootstrap_bin_rustc_rs
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --
> |$OpenBSD: patch-src_bootstrap_bin_rustc_rs,v 1.2 2018/02/23 16:38:16 lan=
dry Exp $
> |try to reduce memory usage on i386:
> | - small code size to optimize (more codegen-units)
> | - optimization level to 1 (instead of 2) to reduce the work in memory
> | - reduce memory use by retaining fewer names within compilation artifac=
ts
> |Index: src/bootstrap/bin/rustc.rs
> |--- src/bootstrap/bin/rustc.rs.orig
> |+++ src/bootstrap/bin/rustc.rs
> --
> Patching file src/bootstrap/bin/rustc.rs using Plan A...
> Hunk #1 succeeded at 179.
> done
> =3D=3D=3D>   Applying OpenBSD patch patch-src_bootstrap_builder_rs
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --
> |$OpenBSD: patch-src_bootstrap_builder_rs,v 1.2 2018/02/23 16:38:16 landr=
y Exp $
> |disable Bootstrap test as it requires network access.
> |pass RUSTC_ERROR_METADATA_DST as absolute path (8c9bf663d4a8074e4955d1ad=
3f85a3b82e946297).
> |Index: src/bootstrap/builder.rs
> |--- src/bootstrap/builder.rs.orig
> |+++ src/bootstrap/builder.rs
> --
> Patching file src/bootstrap/builder.rs using Plan A...
> Hunk #1 succeeded at 251.
> Hunk #2 succeeded at 484.
> done
> =3D=3D=3D>   Applying OpenBSD patch patch-src_bootstrap_check_rs
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --
> |$OpenBSD: patch-src_bootstrap_check_rs,v 1.1 2018/02/23 16:38:16 landry =
Exp $
> |pass RUSTC_ERROR_METADATA_DST as absolute path (8c9bf663d4a8074e4955d1ad=
3f85a3b82e946297).
> |Index: src/bootstrap/check.rs
> |--- src/bootstrap/check.rs.orig
> |+++ src/bootstrap/check.rs
> --
> Patching file src/bootstrap/check.rs using Plan A...
> Hunk #1 succeeded at 980.
> done
> =3D=3D=3D>   Applying OpenBSD patch patch-src_bootstrap_dist_rs
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --
> |$OpenBSD: patch-src_bootstrap_dist_rs,v 1.3 2018/02/23 16:38:16 landry E=
xp $
> |Stop in the middle of "Extended" step: we have generated tarballs for ru=
stc,
> |rust-std and cargo: it is enough and generating a combined tarball in me=
mory
> |requires too much RAM for i386
> |Index: src/bootstrap/dist.rs
> |--- src/bootstrap/dist.rs.orig
> |+++ src/bootstrap/dist.rs
> --
> Patching file src/bootstrap/dist.rs using Plan A...
> Hunk #1 succeeded at 1292.
> done
> =3D=3D=3D>   Applying OpenBSD patch patch-src_bootstrap_doc_rs
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --
> |$OpenBSD: patch-src_bootstrap_doc_rs,v 1.1 2018/02/23 16:38:16 landry Ex=
p $
> |pass RUSTC_ERROR_METADATA_DST as absolute path (8c9bf663d4a8074e4955d1ad=
3f85a3b82e946297).
> |Index: src/bootstrap/doc.rs
> |--- src/bootstrap/doc.rs.orig
> |+++ src/bootstrap/doc.rs
> --
> Patching file 

Re: Upgrading to current prep

2018-03-10 Thread Patrick Marchand
On Sat, Mar 10, 2018 at 07:22:43PM +, Otto Moerbeek wrote:
> On Sat, Mar 10, 2018 at 02:15:02PM -0500, math...@posteo.net wrote:
> 
> > > You would not be the first
> > > one to have written to a file in /dev instead of a device.
> > 
> > Thats exactly what happened, my /dev/sd1 is 943056 bytes large
> > I was trying to dd dragonflybsd to a usb stick earlier this week and messed 
> > up.
> > 
> > What exactly do I have to do to fix this?
> 
> just rm the file. /dev/sd1 is not a device name anyway,
> 
>   -Otto

cool, thanks!