Re: How to copy n bytes from stdin to stdout?
Tomasz Rola wrote:
> On Sun, Jun 24, 2018 at 10:53:37PM -0400, Steve Litt wrote:
> > On Thu, 21 Jun 2018 00:56:04 +0200
> > Tomasz Rola wrote:
> >
> [...]
> > > Craps. I have consulted OpenBSD's manpage for dd and there is no
> > > mention of iflag. So this will not work on OpenBSD. I will have to
> > > rethink this, sorry.
> > >
> >
> > Untested...
> >
> > int main(int argc, char* argv[]){
> > long l = atod(argv[1]);
> > while(l--){
> > if (c = getc(STDIN) != EOF)
> > putc(c, STDOUT);
> > else
> > break;
> > }
> > return 0;
> > }
> >
> > I haven't tested it so it might not be exactly right, and of course
> > error handling would need to be added, but you know what I mean. IIRC
> > getc() and putc() are very well buffered so it will be fast. In my
> > youth I wrote similar functions using low level read() and write() and
> > doing my own buffering, and those things were *really* fast, but I
> > think that's overkill in this century.
> >
> > As far as finding command line tools that do it, if that's becoming
> > hard to do, why not just write a 10 line program?
>
> Actually, I have written few such programs to satiate my own curiosity
> - I was dragged away from computer and in the meantime, others joined
> thread and even wrote nice buffered version of solution in C. I pitted
> this solution against my programs (in C, with fgetc/fputc and Common
> Lisp, with read-sequence/write-sequence) and head-c.c was many times
> faster (about hundred or more times) than my programs.
>
> I am not sure if there is performance difference between fgetc/fputc
> and getc/putc. Man says getc are macros around fgetc. Might be worth
> checking, but I guess no difference.
>
> My curiosity also "wanted" to know how much of performance hit was to
> be expected when writing best to my knowledge optimised Common Lisp vs
> simplistic C - they were similar in performance, with CL compiled by
> SBCL and few times slower, and head-c.c had beaten them both by many
> lengths. I am a bit surprised that in CL, performance was about the
> same, whether reading one byte or many at once. Perhaps I will find a
> way to speed it up some more.
>
> As of finding command line tools, I had working script in about an
> hour (and buggy one in few minutes). Buggy, because "dd | dd" is bad
> idea, and after finding better options for using dd in my script -
> which worked, but under Linux - I had also found out they would not
> work in OpenBSD.
>
> So, I consider it a worthy lesson for myself. Next time, I might just
> fire up Emacs and write a script in CL (mostly, because this is what
> is comfy for me nowadays, and I will not object against having compiled
> script for free). Or something similar, or maybe even do it in C, why
> not.
>
> BTW, the version of nread.sh (improved options) was on par with
> head-c.c, so writing a script with right things inside is very good
> choice, too. If the script actually works :-) .
>
> While the speed is not big problem for input of about 1 megabyte, it
> becomes a problem when gigabytes are copied.
Wow.
Re: how to know the progressive state of dd
Todd C. Miller wrote: > As someone else mentioned you would use pkill on OpenBSD. > > However, you will also need to use SIGINFO, not SIGUSR1, to get > dd's status. BSD systems have traditionally used SIGINFO for this > purpose. Linux lacks SIGINFO so there is no consistent signal for > this kind of a thing there. Hah, it goes beyond that. Sending SIGUSR1 to a random process kills it. What a hoot
Re: how to know the progressive state of dd
Tuyosi T wrote: > hi all . > > on Linux > > dd-progress.bat < > --- > while true > do > date > killall -USR1 dd > echo > echo > sleep 30 > done > > but killall is not possibele on OpenBSD . > --- > regards true. doesn't work for me on windows either
Re: how to know the progressive state of dd
As someone else mentioned you would use pkill on OpenBSD. However, you will also need to use SIGINFO, not SIGUSR1, to get dd's status. BSD systems have traditionally used SIGINFO for this purpose. Linux lacks SIGINFO so there is no consistent signal for this kind of a thing there. - todd
Re: How to copy n bytes from stdin to stdout?
On Sun, Jun 24, 2018 at 10:53:37PM -0400, Steve Litt wrote:
> On Thu, 21 Jun 2018 00:56:04 +0200
> Tomasz Rola wrote:
>
[...]
> > Craps. I have consulted OpenBSD's manpage for dd and there is no
> > mention of iflag. So this will not work on OpenBSD. I will have to
> > rethink this, sorry.
> >
>
> Untested...
>
> int main(int argc, char* argv[]){
> long l = atod(argv[1]);
> while(l--){
> if (c = getc(STDIN) != EOF)
> putc(c, STDOUT);
> else
> break;
> }
> return 0;
> }
>
> I haven't tested it so it might not be exactly right, and of course
> error handling would need to be added, but you know what I mean. IIRC
> getc() and putc() are very well buffered so it will be fast. In my
> youth I wrote similar functions using low level read() and write() and
> doing my own buffering, and those things were *really* fast, but I
> think that's overkill in this century.
>
> As far as finding command line tools that do it, if that's becoming
> hard to do, why not just write a 10 line program?
Actually, I have written few such programs to satiate my own curiosity
- I was dragged away from computer and in the meantime, others joined
thread and even wrote nice buffered version of solution in C. I pitted
this solution against my programs (in C, with fgetc/fputc and Common
Lisp, with read-sequence/write-sequence) and head-c.c was many times
faster (about hundred or more times) than my programs.
I am not sure if there is performance difference between fgetc/fputc
and getc/putc. Man says getc are macros around fgetc. Might be worth
checking, but I guess no difference.
My curiosity also "wanted" to know how much of performance hit was to
be expected when writing best to my knowledge optimised Common Lisp vs
simplistic C - they were similar in performance, with CL compiled by
SBCL and few times slower, and head-c.c had beaten them both by many
lengths. I am a bit surprised that in CL, performance was about the
same, whether reading one byte or many at once. Perhaps I will find a
way to speed it up some more.
As of finding command line tools, I had working script in about an
hour (and buggy one in few minutes). Buggy, because "dd | dd" is bad
idea, and after finding better options for using dd in my script -
which worked, but under Linux - I had also found out they would not
work in OpenBSD.
So, I consider it a worthy lesson for myself. Next time, I might just
fire up Emacs and write a script in CL (mostly, because this is what
is comfy for me nowadays, and I will not object against having compiled
script for free). Or something similar, or maybe even do it in C, why
not.
BTW, the version of nread.sh (improved options) was on par with
head-c.c, so writing a script with right things inside is very good
choice, too. If the script actually works :-) .
While the speed is not big problem for input of about 1 megabyte, it
becomes a problem when gigabytes are copied.
--
Regards,
Tomasz Rola
--
** A C programmer asked whether computer had Buddha's nature. **
** As the answer, master did "rm -rif" on the programmer's home**
** directory. And then the C programmer became enlightened... **
** **
** Tomasz Rola mailto:tomasz_r...@bigfoot.com **
Re: how to know the progressive state of dd
I do not understand what are you trying to achieve, but instead of killall you may use pkill(1) On Tue, Jun 26, 2018 at 1:33 AM, Tuyosi T wrote: > hi all . > > on Linux > > dd-progress.bat < > --- > while true > do > date > killall -USR1 dd > echo > echo > sleep 30 > done > > but killall is not possibele on OpenBSD . > --- > regards >
how to know the progressive state of dd
hi all . on Linux dd-progress.bat < --- while true do date killall -USR1 dd echo echo sleep 30 done but killall is not possibele on OpenBSD . --- regards
Re: New laptop recommendations
I am just researching this as well and have settled on the Dell laptops because they come pre-configured with Ubuntu and therefore I assume they will be opensource friendly. I have short listed:1. Dell Precision 7520 ($1502)2. Dell Precision 7720 ($1412)3. Dell Precision 3520 ($1352) Prices are based on my hardware choices so ymmv. With kind regards,Robert On Tuesday, 19 June 2018, 12:39:03 CEST, Rupert Gallagher wrote: I'm done with my 10 years old 1200EUR MacBookPro. It served me well, every day, but is now falling apart, finally. I would buy a new one if only Steve Jobs would be alive and keeping Apple inspired. The new models are meticulously designed to make you suffer: expensive, slow cpu, soldered ram, soldered disk, small disk, bad keyboard keys, wifi only, must pay extra for standard connectors. I have 1500EUR for a new laptop. What would you buy with it?
Re: KDE-apps okular, kmahjongg
Quoting Stefan Wollny : Hi there, I run amd64-current with the latest public snapshots: $ dmesg | grep Open OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 < Full dmesg at the end > Although I try to follow reading src-changes and topics on misc@ as close as possible I might have missed something lately. Until a few days ago okular and kmahjongg came up without a comment. Now I cannot start them (havn't tried other KDE apps) $ okular okular(68871)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'okular' crashing... KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/local/libexec/drkonqi directly drkonqi(78427)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) ~ $ kmahjongg kmahjongg(43798)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'kmahjongg' crashing... KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/local/libexec/drkonqi directly drkonqi(34562)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) What did I miss / what am I doing wrong here? In /etc/rc.conf.local I have: pkg_scripts=freshclam clamd messagebus avahi_daemon cupsd smartd cups_browsed (cups isn't working for a looong time but that should be a different thread) Anyone got a clue what might be wrong with my system or what knob to turn? Or is this just a temporary annnoyance that ought to go away in a short time? TIA. Best, STEFAN OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16420831232 (15660MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.34 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,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, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.85 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
KDE-apps okular, kmahjongg
Hi there, I run amd64-current with the latest public snapshots: $ dmesg | grep Open OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 < Full dmesg at the end > Although I try to follow reading src-changes and topics on misc@ as close as possible I might have missed something lately. Until a few days ago okular and kmahjongg came up without a comment. Now I cannot start them (havn't tried other KDE apps) $ okular okular(68871)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'okular' crashing... KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/local/libexec/drkonqi directly drkonqi(78427)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) ~ $ kmahjongg kmahjongg(43798)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'kmahjongg' crashing... KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/local/libexec/drkonqi directly drkonqi(34562)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) What did I miss / what am I doing wrong here? In /etc/rc.conf.local I have: pkg_scripts=freshclam clamd messagebus avahi_daemon cupsd smartd cups_browsed (cups isn't working for a looong time but that should be a different thread) Anyone got a clue what might be wrong with my system or what knob to turn? Or is this just a temporary annnoyance that ought to go away in a short time? TIA. Best, STEFAN OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16420831232 (15660MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.34 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,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, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.85 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 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,S
Re: httpd chroot outbound
Thanks for the help guys, I was linking, not copying resolv.conf Fixed. Thanks again. Elias. 2018-06-25 13:59 GMT-03:00 Scott Vanderbilt : > On 6/25/2018 9:37 AM, Elias M. Mariani wrote: > >> Does anybody knows what is needed to allow php to retrieve files while >> under httpd chrooted ? >> I recall the need of /etc/resolv.conf on the jail but that didn't work. > > > Also: http://php.net/manual/en/install.unix.openbsd.php
Re: httpd chroot outbound
On 6/25/2018 9:37 AM, Elias M. Mariani wrote: Does anybody knows what is needed to allow php to retrieve files while under httpd chrooted ? I recall the need of /etc/resolv.conf on the jail but that didn't work. Also: http://php.net/manual/en/install.unix.openbsd.php
Re: httpd chroot outbound
what are you trying to do ? if you want to make a file visible to the webserver just copy the file into the chrooted folder ie from cp /path-to-file/var/www/path-to-file if you want to make some files in a directory accessible to the web service (be careful with this (naturally) ) you can create a symlink in the manner as suggested in the following thread http://openbsd-archive.7691.n7.nabble.com/httpd-chroot-security-and-user-homepage-td299565.html I hope this helps On 25 June 2018 at 17:37, Elias M. Mariani wrote: > Hi. > Does anybody knows what is needed to allow php to retrieve files while > under httpd chrooted ? > I recall the need of /etc/resolv.conf on the jail but that didn't work. > > Cheers. > Elias. > -- Kindest regards, Tom Smyth Mobile: +353 87 6193172 The information contained in this E-mail is intended only for the confidential use of the named recipient. If the reader of this message is not the intended recipient or the person responsible for delivering it to the recipient, you are hereby notified that you have received this communication in error and that any review, dissemination or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately by telephone at the number above and erase the message You are requested to carry out your own virus check before opening any attachment.
Re: httpd chroot outbound
On 6/25/2018 9:37 AM, Elias M. Mariani wrote: Does anybody knows what is needed to allow php to retrieve files while under httpd chrooted ? I recall the need of /etc/resolv.conf on the jail but that didn't work. See /usr/local/share/doc/pkg-readmes/php-*
httpd chroot outbound
Hi. Does anybody knows what is needed to allow php to retrieve files while under httpd chrooted ? I recall the need of /etc/resolv.conf on the jail but that didn't work. Cheers. Elias.
Re: Partitioning recommendations for 6.3?
Thanks @bryanharris and @bruno Thanks guys, I will check out the links. /jl
Re: Partitioning recommendations for 6.3?
The webserver is called httpd (not the apache one). I like this book but some people don't need the extra help of a book (I do). https://www.michaelwlucas.com/tools/relayd On Mon, Jun 25, 2018 at 11:49 AM John Long wrote: > On Mon, 2018-06-25 at 10:15 -0500, Vijay Sankar wrote: > > Here is my df -h output -- Just as an FYI I was testing some > > workarounds for the samba virusfilter issue and then made some > > mistakes that screwed up KDE etc. So decided to build it from > > scratch > > and have about 5000 packages built right now with the following > > disk > > usage. > > > > $ df -h > > Filesystem SizeUsed Avail Capacity Mounted on > > /dev/sd0a 1005M102M852M11%/ > > /dev/sd0l 3.9G1.8G2.0G48%/builds > > /dev/sd0k 127G1.3G119G 1%/home > > /dev/sd0d 3.9G7.2M3.7G 0%/tmp > > /dev/sd0f 5.9G1.9G3.8G33%/usr > > /dev/sd0g 2.0G185M1.7G10%/usr/X11R6 > > /dev/sd0h 19.7G9.4G9.3G50%/usr/local > > /dev/sd0j 5.9G3.3G2.3G59%/usr/obj > > /dev/sd0i 2.0G990M929M52%/usr/src > > /dev/sd0e 31.5G 57.9M 29.9G 0%/var > > /dev/sd0m 243G 83.7G147G36%/usr/ports > > Thanks, this is good info. > > I am trying to find out about /usr/xenocara if it is still needed and > also whether it's still recommended to build from source and track > -stable or whether syspatch does away with that. > > What is the recommended http server these days? I remember the > transition from apache to nginx. What's the conventional wisdom? > > My plan for this box is sftp, http, and minidlna server. > > Thank you, > > /jl > > -- So the HP guy comes up to me and he says, 'If you say nasty things like that to vendors you're not going to get anything'. I said 'no, in eight years of saying nothing, we've got nothing, and I'm going to start saying nasty things, in the hope that some of these vendors will start giving me money so I'll shut up'. -Theo De Raadt
Re: Partitioning recommendations for 6.3?
On 25.06.2018 14:17, John Long wrote: Been a while and don't have my other OpenBSD boxes accessible. What are the recommended partitions and appropriate sizes for people who want to track stable and possibly build the whole ports tree? Thanks, /jl Check the detailed explanation given by Ingo Schwarze: https://marc.info/?l=openbsd-misc&m=149890809430366&w=2 Cheers, Bruno
Re: Partitioning recommendations for 6.3?
On Mon, 2018-06-25 at 10:15 -0500, Vijay Sankar wrote: > Here is my df -h output -- Just as an FYI I was testing some > workarounds for the samba virusfilter issue and then made some > mistakes that screwed up KDE etc. So decided to build it from > scratch > and have about 5000 packages built right now with the following > disk > usage. > > $ df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/sd0a 1005M102M852M11%/ > /dev/sd0l 3.9G1.8G2.0G48%/builds > /dev/sd0k 127G1.3G119G 1%/home > /dev/sd0d 3.9G7.2M3.7G 0%/tmp > /dev/sd0f 5.9G1.9G3.8G33%/usr > /dev/sd0g 2.0G185M1.7G10%/usr/X11R6 > /dev/sd0h 19.7G9.4G9.3G50%/usr/local > /dev/sd0j 5.9G3.3G2.3G59%/usr/obj > /dev/sd0i 2.0G990M929M52%/usr/src > /dev/sd0e 31.5G 57.9M 29.9G 0%/var > /dev/sd0m 243G 83.7G147G36%/usr/ports Thanks, this is good info. I am trying to find out about /usr/xenocara if it is still needed and also whether it's still recommended to build from source and track -stable or whether syspatch does away with that. What is the recommended http server these days? I remember the transition from apache to nginx. What's the conventional wisdom? My plan for this box is sftp, http, and minidlna server. Thank you, /jl
Re: Partitioning recommendations for 6.3?
Quoting John Long : On Mon, 2018-06-25 at 09:25 -0500, Vijay Sankar wrote: Quoting John Long : > Been a while and don't have my other OpenBSD boxes accessible. > > What are the recommended partitions and appropriate sizes for > people > who want to track stable and possibly build the whole ports tree? > > Thanks, > > /jl However, for the past year or so, I have had to increase the size of /usr to 6G and /usr/local to 20G to build all the packages. I can't remember now.. ports go under /usr/local, correct? What goes in /usr that would require 6G? Thanks, /jl Here is my df -h output -- Just as an FYI I was testing some workarounds for the samba virusfilter issue and then made some mistakes that screwed up KDE etc. So decided to build it from scratch and have about 5000 packages built right now with the following disk usage. $ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/sd0a 1005M102M852M11%/ /dev/sd0l 3.9G1.8G2.0G48%/builds /dev/sd0k 127G1.3G119G 1%/home /dev/sd0d 3.9G7.2M3.7G 0%/tmp /dev/sd0f 5.9G1.9G3.8G33%/usr /dev/sd0g 2.0G185M1.7G10%/usr/X11R6 /dev/sd0h 19.7G9.4G9.3G50%/usr/local /dev/sd0j 5.9G3.3G2.3G59%/usr/obj /dev/sd0i 2.0G990M929M52%/usr/src /dev/sd0e 31.5G 57.9M 29.9G 0%/var /dev/sd0m 243G 83.7G147G36%/usr/ports Reason why I had to increase /usr from the default 2G to 6G was because I tend to build -current or -stable in addition to packages and the additional files in /usr/share/relink went above the 2G size. As a result I increased /usr partition to 6G. Re. /usr/local, I used to be able to just run dpb (before 6.1) and get almost all the packages built without having to do any manual checks. So no packages were added to /usr/local earlier. But I may be missing something because nowadays I am able to only build around 2700 packages if I run dpb blindly. I then have to do a make package manually for critical items like cmake and others. I found out the hard way that if I clean stuff up, some packages such as window managers don't build for me. So I leave /usr/local as is which resulted in me having to increase the size of /usr/local. Also, for some packages such as webkit, I end up having to do a make clean all and then make package. I may be doing something wrong so none of the above is a recommendation. Vijay Sankar, M.Eng., P.Eng. ForeTell Technologies Limited vsan...@foretell.ca
Re: Partitioning recommendations for 6.3?
On Mon, 2018-06-25 at 09:25 -0500, Vijay Sankar wrote: > Quoting John Long : > > > Been a while and don't have my other OpenBSD boxes accessible. > > > > What are the recommended partitions and appropriate sizes for > > people > > who want to track stable and possibly build the whole ports tree? > > > > Thanks, > > > > /jl > > However, for the past year or so, I have had to increase the size of > /usr to 6G and /usr/local to 20G to build all the packages. I can't remember now.. ports go under /usr/local, correct? What goes in /usr that would require 6G? Thanks, /jl
Re: Partitioning recommendations for 6.3?
On Mon, 2018-06-25 at 17:16 +0300, IL Ka wrote: > Do you want to really build all ports or just fetch skeletons and > build some of them? Not sure, but I don't want to rule out building them all for a couple or reasons. I have a new box which is probably fast enough to make it worthwhile to build packages for some slower boxes I have. Second thing is rebuilding the system from source and then building all the ports is a good stability test. Bottom line is probably that I would rather plan to have the space available and not need it then to need it and not have it. Seems like in the past this was a problem for me. > For skeletons, automatic layout is good enough, but I recommend to > increase /usr/src a little and decrease /home. > Make sure you have ~ 5GB for /usr/src/ and /usr/obj. > Thanks, this helps. The automatic layout didn't include /usr/xenocara There used to be a recommendation in the past to have that as a separate filesystem. How large should it be? Is there any reason to track -stable anymore or has syspatch done away with the need for that? Seems to me, after trying to install OpenBSD on a new box, a lot of the helpful in the FAQ is totally AWOL now and I find it hard to get all the info together. /jl > > > > > On Mon, Jun 25, 2018 at 3:17 PM, John Long wrote: > > Been a while and don't have my other OpenBSD boxes accessible. > > > > What are the recommended partitions and appropriate sizes for > > people > > who want to track stable and possibly build the whole ports tree? > > > > Thanks, > > > > /jl > > > >
Re: Partitioning recommendations for 6.3?
Quoting John Long : Been a while and don't have my other OpenBSD boxes accessible. What are the recommended partitions and appropriate sizes for people who want to track stable and possibly build the whole ports tree? Thanks, /jl Hi, Hopefully more knowledgeable people may give us better advice. The default installation and partition sizes worked great for me till 6.1 and I was able to build and test changes to kernel and also test ports etc without making any changes. However, for the past year or so, I have had to increase the size of /usr to 6G and /usr/local to 20G to build all the packages. HTH, Vijay Vijay Sankar, M.Eng., P.Eng. ForeTell Technologies Limited vsan...@foretell.ca
Re: Partitioning recommendations for 6.3?
Do you want to really build all ports or just fetch skeletons and build some of them? For skeletons, automatic layout is good enough, but I recommend to increase /usr/src a little and decrease /home. Make sure you have ~ 5GB for /usr/src/ and /usr/obj. On Mon, Jun 25, 2018 at 3:17 PM, John Long wrote: > Been a while and don't have my other OpenBSD boxes accessible. > > What are the recommended partitions and appropriate sizes for people > who want to track stable and possibly build the whole ports tree? > > Thanks, > > /jl > >
Partitioning recommendations for 6.3?
Been a while and don't have my other OpenBSD boxes accessible. What are the recommended partitions and appropriate sizes for people who want to track stable and possibly build the whole ports tree? Thanks, /jl
