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
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 Lo
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
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
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?
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 p
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
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
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 d
Thanks @bryanharris and @bruno
Thanks guys, I will check out the links.
/jl
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.
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-*
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 c
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
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 re
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 late
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 mig
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
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
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
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.
> >
>
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
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 wind
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 k
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
25 matches
Mail list logo
