On Fri, May 9, 2025 at 9:56 AM Janne Johansson wrote:
> Same goes for if you
> must place /home/_sysupgrade somewhere else for space reasons, make
> sure the softlink is relative and it will keep on working during
> upgrades also.
Thanks for this -- I had been making it work with 'sysupgrade -b
/
upposed to recognize the message "No space
left on device" as a rendering of the error number ENOSPC documented
in the errno(2) manual page, described like this:
28 ENOSPC No space left on device. A write(2) to an ordinary file,
the creation of a directory or symbolic lin
On 2025-05-09 12:53, Janne Johansson wrote:
> I had that with systems where /var/www is a symlink into
> another (small) slice/partition like "/".
Thanks. I had /var/www symlinked to /home/www, and that
was, for some reason, enough to cause the trouble. I removed
the symlink and the upgrade w
> > I had that with systems where /var/www is a symlink into
> > another (small) slice/partition like "/".
>
> Thanks. I had /var/www symlinked to /home/www, and that
> was, for some reason, enough to cause the trouble. I removed
> the symlink and the upgrade went fine. What is not understood,
> ho
Am 09.05.2025 12:17 schrieb rsyk...@disroot.org:
What is not understood,
however, is the fact that the symlink went *not* to a small partition;
my /home was
/dev/sd0k 295G227G 53.8G81%/home
Might happen that /home is not mounted in that moment?
Try to unmount it and see if/w
On 2025-05-09 11:02, Philipp Buehler wrote:
Am 09.05.2025 10:29 schrieb rsyk...@disroot.org:
The complain is about / , which, upon reboot, seems to be rd0a,
something I do not really understand what that is.
Can anybody tell me what is probably going wrong?
I had that with systems where /
Am 09.05.2025 10:29 schrieb rsyk...@disroot.org:
The complain is about / , which, upon reboot, seems to be rd0a,
something I do not really understand what that is.
Can anybody tell me what is probably going wrong?
I had that with systems where /var/www is a symlink into
another (small) slice/
Dear list,
upon running sysupgrade, after the reboot I it seems
as if I run out of space on /
/: write failed, file system is full
tar: Failed write to file ./var/www/bin/bgpctl: No space left on the
device
but before the attempt I see:
odin:~$ df -h
Filesystem SizeUsed Avail
nisp1953:
> Will OpenBSD get a new file system sometime in the future?
The responses so far have been a bit too smart-alecky, so here's a
better one: Nobody in the project is working on a new file system
at this time. So there likely won't be one in the forseeable future.
--
Chr
On Wed, 2025-03-05 at 12:13 -0700, nisp1953 wrote:
> Will OpenBSD get a new file system sometime in the future?
Most of the time when you ask if XYZ would ever come at some point
(even outside of OpenBSD) you can't really get a timed response because
as many opensource projects you need p
Claudio Jeker writes:
> On Thu, Mar 06, 2025 at 11:25:52AM -, Stuart Henderson wrote:
>> On 2025-03-05, nisp1953 wrote:
>> >
>> > Will OpenBSD get a new file system sometime in the future?
>>
>> Magic crystal ball is cloudy.
>
> My crystal ball
On Thu, Mar 6, 2025 at 10:37 PM Stuart Henderson
wrote:
>
> On 2025-03-05, nisp1953 wrote:
> >
> > Will OpenBSD get a new file system sometime in the future?
>
> Magic crystal ball is cloudy.
>
*shakes 8 ball* "Ask again later"
--
Aaron Mason - Program
> On Mar 6, 2025, at 7:20 AM, Claudio Jeker wrote:
>
> On Thu, Mar 06, 2025 at 11:25:52AM -, Stuart Henderson wrote:
>> On 2025-03-05, nisp1953 wrote:
>>>
>>> Will OpenBSD get a new file system sometime in the future?
>>
>> Magic crystal
On Thu, Mar 06, 2025 at 11:25:52AM -, Stuart Henderson wrote:
> On 2025-03-05, nisp1953 wrote:
> >
> > Will OpenBSD get a new file system sometime in the future?
>
> Magic crystal ball is cloudy.
My crystal ball answered with "Computer says no"
--
:wq Claudio
Stuart Henderson :
> On 2025-03-05, nisp1953 wrote:
>>
>> Will OpenBSD get a new file system sometime in the future?
>
> Magic crystal ball is cloudy.
I would go for Gemini..
On 2025-03-05, nisp1953 wrote:
>
> Will OpenBSD get a new file system sometime in the future?
Magic crystal ball is cloudy.
--
Please keep replies on the mailing list.
Will OpenBSD get a new file system sometime in the future?
I read Ted Unangst’s article on ZFS and Tedu basically says it’s too
complicated. Do the developers have have a replacement in mind?
https://flak.tedunangst.com/post/ZFS-on-OpenBSD
Peter Hessler writes:
> On 2024 Dec 10 (Tue) at 21:10:51 +0200 (+0200), Divan Santana wrote:
>
> :mount 3b3840fcdf524721.c /data
>
> you've basically guaranteed corruption of your disk. the 'c' partition
> the entire disk, including all metadata.
>
> You'll want to create another partition with
ipt rc(8) during automatic reboot. If
>> > no
>> > file systems are specified, fsck reads the file fstab(5) to determine
>> > which file systems to check and in what order. Only partitions in
>> > fstab
>> > that are mounted “rw” or “ro” and
t; It is normally used in the script rc(8) during automatic reboot. If no
> > file systems are specified, fsck reads the file fstab(5) to determine
> > which file systems to check and in what order. Only partitions in
> > fstab
> > that are mounte
r. Only partitions in fstab
> that are mounted “rw” or “ro” and that have non-zero pass numbers are
> checked. File systems with pass number 1 (normally just the root file
> system) are checked one at a time.
OK, good point. But if there is a file system listed in fstab
Otto Moerbeek writes:
> On Tue, Dec 10, 2024 at 09:10:51PM +0200, Divan Santana wrote:
>
>> Greetings and happy December :)
>>
>> I have a 3.5TB ffs mounted at /data which is specified in fstab.
>>
>> When there is a power outage this file system corrupts
On Wed, Dec 11, 2024 at 02:24:16PM +0100, Peter Hessler wrote:
> On 2024 Dec 10 (Tue) at 21:10:51 +0200 (+0200), Divan Santana wrote:
>
> :mount 3b3840fcdf524721.c /data
>
> you've basically guaranteed corruption of your disk. the 'c' partition
> the entire disk, including all metadata.
>
> Yo
On 2024 Dec 10 (Tue) at 21:10:51 +0200 (+0200), Divan Santana wrote:
:mount 3b3840fcdf524721.c /data
you've basically guaranteed corruption of your disk. the 'c' partition
the entire disk, including all metadata.
You'll want to create another partition with size * in a or d to have a
good time.
On Tue, Dec 10, 2024 at 09:10:51PM +0200, Divan Santana wrote:
> Greetings and happy December :)
>
> I have a 3.5TB ffs mounted at /data which is specified in fstab.
>
> When there is a power outage this file system corrupts (I'll install
> another UPS shortly).
>
&g
On 2024-12-10, Divan Santana wrote:
> Greetings and happy December :)
>
> I have a 3.5TB ffs mounted at /data which is specified in fstab.
>
> When there is a power outage this file system corrupts (I'll install
> another UPS shortly).
>
> Is it possible to fsck_ffs
tab
that are mounted “rw” or “ro” and that have non-zero pass numbers are
checked. File systems with pass number 1 (normally just the root file
system) are checked one at a time.
--
wbr, Kirill
Greetings and happy December :)
I have a 3.5TB ffs mounted at /data which is specified in fstab.
When there is a power outage this file system corrupts (I'll install
another UPS shortly).
Is it possible to fsck_ffs a 3.5TB file system from the boot rescue
environment?
When I've tr
On Thu, Apr 25, 2024 at 07:26:41AM +0200, Peter J. Philipp wrote:
> On Thu, Apr 25, 2024 at 12:45:29AM -0300, Gustavo Rios wrote:
> > Hi folks!
> >
> > What is the maximum file size in OpenBSD ?
> >
> > Thanks a lot.
> >
> > --
> > The lion and the tiger may be more powerful, but the wolves do
On Thu, Apr 25, 2024 at 12:45:29AM -0300, Gustavo Rios wrote:
> Hi folks!
>
> What is the maximum file size in OpenBSD ?
>
> Thanks a lot.
>
> --
> The lion and the tiger may be more powerful, but the wolves do not perform
> in the circus
There is this comment in /usr/include/ufs/ffs/fs.h:
/*
Hi folks!
What is the maximum file size in OpenBSD ?
Thanks a lot.
--
The lion and the tiger may be more powerful, but the wolves do not perform
in the circus
> Packages should be installing into /usr/local which should be a separate
> partition from /usr. I know, in the last install I had something around 300
> packages installed and after trying to install qemu the partition ran out of
> space. I could try to install the system again since I have no
On 2023-04-15, Nick Holland wrote:
> Partition your system. And / should be as small as you can sanely
> get away with. That isn't to say it should be super-tiny. But
> if you have 1GB to spare, it is probably too big.
I disagree on that, around 1GB to spare on / seems pretty comfortable
unles
> If you had an appropriate sized root partition, perhaps 1G (default),I was
>using the default partitioning before but I had to reinstall the system
>because kf that: I couldn't install packages because /usr partition was full
>after a week of usage. I'm new to OpenBSD and I'm still learning h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 15 Apr 2023 12:49:47 -0400
Nick Holland wrote:
> if you have 1GB to spare, it is probably too big. I did learn to
> regret a 200MB root because OpenBSD grew a lot over around ten
I learned to regret setting / to under 1 mb once upon a tim
On 4/15/23 10:14, Lorenzo Torres wrote:
Hello, I've run the dd command to wipe the data of an SD card:dd
if=/dev/zero of=/dev/rsdb1c bs=1MAfter quite some time it crashed
^^ bzzzt. game over.
saying that the / filesystem is full and even after a reboot the same
happe
On Sat, Apr 15, 2023 at 04:14:08PM +0200, Lorenzo Torres wrote:
> Hello, I've run the dd command to wipe the data of an SD card:dd if=/dev/zero
> of=/dev/rsdb1c bs=1MAfter quite some time it crashed saying that the /
> filesystem is full and even after a reboot the same happens. Now I can't even
Am 15.04.2023 um 16:14 schrieb Lorenzo Torres:
Hello, I've run the dd command to wipe the data of an SD card:dd if=/dev/zero
of=/dev/rsdb1c bs=1MAfter quite some time it crashed saying that the /
filesystem is full and even after a reboot the same happens. Now I can't even
run xorg because the
Thanks, that was the issue, I'll pay more attention in the future.Lorenzo
Torres (https://sagittarius-a.org)
On Sat, Apr 15, 2023, at 9:14 AM, Lorenzo Torres wrote:
> Hello, I've run the dd command to wipe the data of an SD card:dd
> if=/dev/zero of=/dev/rsdb1c bs=1MAfter quite some time it crashed
> saying that the / filesystem is full and even after a reboot the same
> happens. Now I can't even run x
Hello, I've run the dd command to wipe the data of an SD card:dd if=/dev/zero
of=/dev/rsdb1c bs=1MAfter quite some time it crashed saying that the /
filesystem is full and even after a reboot the same happens. Now I can't even
run xorg because the fs is full. Any idea on why this happened? I hav
On 7/14/22 12:09 PM, Zé Loff wrote:
On Thu, Jul 14, 2022 at 09:44:20AM +0200, Brian Durant wrote:
The browser issue has returned. An open dialog window to upload a file or to
open a file cannot find the downloads directory and it is impossible to
access by using "recents" or "computer" in the op
On Thu, Jul 14, 2022 at 09:44:20AM +0200, Brian Durant wrote:
> The browser issue has returned. An open dialog window to upload a file or to
> open a file cannot find the downloads directory and it is impossible to
> access by using "recents" or "computer" in the open dialog window. Not sure
> what
The browser issue has returned. An open dialog window to upload a file
or to open a file cannot find the downloads directory and it is
impossible to access by using "recents" or "computer" in the open dialog
window. Not sure what is going on, but it sure is irritating.
being unable to
access the file system using the "open" dialog. The dialog appears,
but no files or directories appear regardless of path. Things
function normally however, with both Midori and Thunderbird. I assume
that Firefox and Chromium are experiencing a permissions issue, but
what cau
have said, Midori and Thunderbird don't have this issue
because neither of them use unveil. It would be really cool if one day
at least Thunderbird did.
Courtney
On 7/10/22 23:46, Brian Durant wrote:
I have a problem with both Firefox and Chromium being unable to access
the file system
Actually, there is one major difference between the two systems that I
had forgotten about. While both use the Calm window manager, the system
that is experiencing problems with the browser file dialogs, uses
PCManFM...
On 7/11/22 17:53, Stuart Henderson wrote:
> I guess your locate database was last generated when firefox was
> installed but chromium was not
>
>> Wondering if something else is at play here...
> grep unveil /usr/local/share/doc/pkg-readmes/*
>
> ls /etc/*/*unveil*
$ grep unveil /usr/local/share
> ... how to rectify it is beyond my capabilities as a new OpenBSD user.
First of all, there is nothing to rectify. All was done to act like
this and to serve a specific purpose. Much work and developers'
efforts were poured into this, again with a specific great purpose (
hint: security related).
On 2022-07-11, Brian Durant wrote:
> On 7/11/22 15:25, Stuart Henderson wrote:
>> On 2022-07-11, Björn Gohla wrote:
>>>
>>> Brian Durant writes:
>>>
>>>> I have a problem with both Firefox and Chromium being unable to access
>>>> the
On 7/11/22 15:25, Stuart Henderson wrote:
> On 2022-07-11, Björn Gohla wrote:
>>
>> Brian Durant writes:
>>
>>> I have a problem with both Firefox and Chromium being unable to access
>>> the file system using the "open" dialog. The dialo
On 2022-07-11, Björn Gohla wrote:
>
> Brian Durant writes:
>
>> I have a problem with both Firefox and Chromium being unable to access
>> the file system using the "open" dialog. The dialog appears, but no
>> files or directories appear regardless of path. Th
On 7/11/22 14:40, Björn Gohla wrote:
>
> Brian Durant writes:
>
>> I have a problem with both Firefox and Chromium being unable to access
>> the file system using the "open" dialog. The dialog appears, but no
>> files or directories appea
Brian Durant writes:
> I have a problem with both Firefox and Chromium being unable to access
> the file system using the "open" dialog. The dialog appears, but no
> files or directories appear regardless of path. Things function
[...]
This sounds like an unveil(2) issue
On 2022-07-11, Brian Durant wrote:
> I have a problem with both Firefox and Chromium being unable to access
> the file system using the "open" dialog. The dialog appears, but no
> files or directories appear regardless of path. Things function normally
> however
Perhaps you run them in sandbox mode ?
Kind regards
Wim
Brian Durant schreef op 11 juli 2022 08:46:21
CEST:
>I have a problem with both Firefox and Chromium being unable to access the
>file system using the "open" dialog. The dialog appears, but no files or
>directories a
I have a problem with both Firefox and Chromium being unable to access
the file system using the "open" dialog. The dialog appears, but no
files or directories appear regardless of path. Things function normally
however, with both Midori and Thunderbird. I assume that Firefox and
Ch
Per Google, most likely there's a symlink loop in the source.
See mkdirat(2) (it refers to ELOOP).
See also errno(2), which has: 31 EMLINK Too many links
It also has
62 ELOOP Too many levels of symbolic links
Your message has the text from EMLINK, but mkdirat only mentions ELOOP.
That's not
Michael Lowery Wilson writes:
> Greetings,
>
> My attempts at creating a local mirror of Project Gutenberg's ebooks
> under OpenBSD 6.9 using openrsync following official instructions:
> https://www.gutenberg.org/help/mirroring.html have been unsuccessful.
>
> Specifically I am using:
>
> openrs
On 2021-06-07, Michael Lowery Wilson wrote:
> Greetings,
>
> My attempts at creating a local mirror of Project Gutenberg's ebooks under
> OpenBSD 6.9 using openrsync following official instructions:
> https://www.gutenberg.org/help/mirroring.html have been unsuccessful.
>
> Specifically I am usi
Greetings,
My attempts at creating a local mirror of Project Gutenberg's ebooks under
OpenBSD 6.9 using openrsync following official instructions:
https://www.gutenberg.org/help/mirroring.html have been unsuccessful.
Specifically I am using:
openrsync -av --del aleph.gutenberg.org::gutenberg
Hey, I read that message about Freeradius not being able to access /dev/null in
a setup where /dev is mounted on an mfs -based filesystem.I'm running similar
setup (for years now) - OpenBSD on a USB stick. EVERYTHING is mounted
read-only, except /var, /tmp, /dev and /jails, which are mfs - based
And if the FS is mounted rw, do you have the issue ?
Best Regards,
Strahil Nikolov
На 11 юли 2020 г. 10:22:53 GMT+03:00, Vertigo Altair
написа:
> Hello Again,
>I followed Stuart's recommendations,
>
>in fstab, / has read-write permissions;
>also, I mounted /dev as ramdisk, ( I executed "MAKED
On 2020/07/11 10:22, Vertigo Altair wrote:
> Hello Again,
> I followed Stuart's recommendations,
>
> in fstab, / has read-write permissions;
> also, I mounted /dev as ramdisk, ( I executed "MAKEDEV all" in /dev_src
> directory for once)
>
> vertigo# cat /etc/fstab
> 5e045fec2af2ab03.b none sw
Hello Again,
I followed Stuart's recommendations,
in fstab, / has read-write permissions;
also, I mounted /dev as ramdisk, ( I executed "MAKEDEV all" in /dev_src
directory for once)
vertigo# cat /etc/fstab
5e045fec2af2ab03.b none swap sw
5e045fec2af2ab03.a / ffs rw 1 1
5e045fec2af2ab03.e /my
On 6/27/20 10:57 AM, Stuart Henderson wrote:
On 2020-06-26, Marko Cupać wrote:
On 2020-06-24, Aaron Mason wrote:
Auto filesystem repair is bad juju.
On 2020-06-25 11:17, Stuart Henderson wrote:
Nonsense. For many, the possible downsides of automatically running
fsck -y are much less a prob
On 2020-06-26, Marko Cupać wrote:
>>> On 2020-06-24, Aaron Mason wrote:
>>> Auto filesystem repair is bad juju.
>
>> On 2020-06-25 11:17, Stuart Henderson wrote:
>> Nonsense. For many, the possible downsides of automatically running
>> fsck -y are much less a problem than the downsides of *not* r
On 2020-06-24, Aaron Mason wrote:
Auto filesystem repair is bad juju.
On 2020-06-25 11:17, Stuart Henderson wrote:
Nonsense. For many, the possible downsides of automatically running
fsck -y are much less a problem than the downsides of *not* running it.
Some time ago I wrote here on misc@ a
x27;fsck -y' if an
> >> +# automatic file system check fails with exit code 8.
>
> I have quite a few machines patched like this.
>
> On 2020-06-24, Aaron Mason wrote:
> > Auto filesystem repair is bad juju.
>
> Nonsense. For many, the possible downsides o
> On Mon, Jun 22, 2020 at 4:24 PM Mogens Jensen
> wrote:
>> +# NOTE: The do_fsck() function has been patched to run 'fsck -y' if an
>> +# automatic file system check fails with exit code 8.
I have quite a few machines patched like this.
On 2020-06-24, Aaron Mas
On Wednesday, June 24, 2020 10:58 PM, Aaron Mason
wrote:
> Auto filesystem repair is bad juju.
Indeed, but an unbootable network appliance thousands of miles away,
is much much worse.
Regards,
Mogens Jensen
file: /cvs/src/etc/rc,v
> retrieving revision 1.536
> diff -u -p -u -p -r1.536 rc
> --- src/etc/rc 1 Apr 2019 11:39:46 - 1.536
> +++ src/etc/rc 20 Aug 2019 22:47:49 -
> @@ -1,5 +1,8 @@
> # $OpenBSD: rc,v 1.536 2019/04/01 11:39:46 tedu Exp $
>
> +# NOTE:
19/04/01 11:39:46 tedu Exp $
+# NOTE: The do_fsck() function has been patched to run 'fsck -y' if an
+# automatic file system check fails with exit code 8.
+
# System startup script run by init on autoboot or after single-user.
# Output and error are redirected to console by init, a
On 2020-06-13 12:56, Todd C. Miller wrote:
> On Sat, 13 Jun 2020 12:12:05 -0400, Nick Holland wrote:
>
>> On 2020-06-11 12:07, Strahil Nikolov wrote:
>> > I always thought that 'sync' mount option is enough to avoid
>> > corruption of the FS. Am I just "fooling" myself ?
>>
>> As "sync" is the
In Linux, the kernel can force flushing the disk cache (which also can be
disabled ) via fsync() call . That feature is called 'write barrier'. As
I'm not a developer, I never read that portion of the source of openBSD , so I
got no idea if similar logic can be used in openBSD.
Does 'soft
, I want to use readonly file system.
I know there are some projects like "resflash", but I want to do that
manually.
...
On startup following errors comming from /etc/rc; I think errors about
/etc/motd are not so important, but are the errors coming from
/etc/tty*
can cause any prob
On Sat, 13 Jun 2020 12:12:05 -0400, Nick Holland wrote:
> On 2020-06-11 12:07, Strahil Nikolov wrote:
> > I always thought that 'sync' mount option is enough to avoid
> > corruption of the FS. Am I just "fooling" myself ?
>
> As "sync" is the default...yes, I think you are.
Actually, by defaul
eded writes.
* Faster disks -- How about a small SSD? They spend less
time writing, and often have enough on-board capacitance to
complete writes after a power interruption.
* experiment with softdeps. Supposedly, it helps keep the
/FILE SYSTEM/ consistent. My experience is it tends to
truncate fi
On 2020-06-11 23:47, Dirk Coetzee wrote:
> I always thought that 'sync' mount option is enough to avoid corruption of
the FS.
> Am I just "fooling" myself ?
> I guess it boils down to a matter of preference and business requirements.
>
> "slow writes" vs "no writes".
It's a good point, per
I guess it boils down to a matter of preference and business requirements.
"slow writes" vs "no writes".
-Original Message-
From: Strahil Nikolov
Sent: Friday, 12 June 2020 12:08 AM
To: Dirk Coetzee ; Joe Barnett ;
Vertigo Altair
Cc: Misc
Subject: Re: OpenBSD Rea
om: owner-m...@openbsd.org On Behalf Of Joe
>Barnett
>Sent: Wednesday, 10 June 2020 8:02 AM
>To: Vertigo Altair
>Cc: Misc
>Subject: Re: OpenBSD Readonly File System
>
>On 2020-06-09 00:59, Vertigo Altair wrote:
>> Hi Misc,
>> I have a firewall device and I'm using
:02 AM
To: Vertigo Altair
Cc: Misc
Subject: Re: OpenBSD Readonly File System
On 2020-06-09 00:59, Vertigo Altair wrote:
> Hi Misc,
> I have a firewall device and I'm using OpenBSD on it. There is an
> electricity problem where the device runs. Therefore, I have to run
> the
, I want to use readonly file system.
I know there are some projects like "resflash", but I want to do that
manually.
I have hacked and slashed my way to this kind of configuration for my
firewall/gateway and a few other machines -- and with what appears to be
good results. Please
On Tue, 9 Jun 2020 at 08:59, Vertigo Altair wrote:
>
> Hi Misc,
> I have a firewall device and I'm using OpenBSD on it. There is an
> electricity problem where the device runs. Therefore, I have to run the
> "fsck -y" command regularly at startup due to the electricity problem.
Isn't it just easi
; overcome this, I want to use readonly file system.
> I know there are some projects like "resflash", but I want to do that
> manually.
The usual way to handle / is to have it RW during boot and remount
it (mount -ur /) in rc.local.
Use a ramdisk (MFS) for /dev. Create a direct
Hi Misc,
I have a firewall device and I'm using OpenBSD on it. There is an
electricity problem where the device runs. Therefore, I have to run the
"fsck -y" command regularly at startup due to the electricity problem. To
overcome this, I want to use readonly file system.
I know
oas or su camped out on the amd vols.
>>
>>I've tesed a lot of ways, but I just did an upgrade to -current and
>>immediately "looked" at the amd mount, so even my backup scripts
>>haven't run.
>>
>>Plus -- as a control, /v/2 has absolutely nothing o
uot;looked" at the amd mount, so even my backup scripts
>haven't run.
>
>Plus -- as a control, /v/2 has absolutely nothing on it, and it
>behaves the same way. Not that something couldn't camp out on the
>empty file system, but not much reason for something to do so.
behaves the same way. Not that something couldn't camp out on the
empty file system, but not much reason for something to do so.
Thanks for looking!
Nick.
> —
> Antoine
>
>> On 13 Jan 2020, at 06:01, Nick Holland wrote:
>>
>> Hiya.
>>
>> I'
959760 0%/usr/local
> /dev/sd2g 4136828 64920 3865068 2%/var
> amd:36583 0 0 0 100%/v
>
> $ ls /v/1/
> [...expected output from files and directories on that file system...]
>
> $ df
> Filesystem 1K-blocks
/dev/sd2g 4136828 64920 3865068 2%/var
amd:365830 0 0 100%/v
$ ls /v/1/
[...expected output from files and directories on that file system...]
$ df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/sd2a 505838 83602
Hi Chris,
i just committed the patch shown below;
thanks for bringing up the point.
Yours,
Ingo
CVSROOT:/cvs
Module name:src
Changes by: schwa...@cvs.openbsd.org2019/12/05 17:14:08
Modified files:
lib/libc/sys : unveil.2
Log message:
Explicitly say that *
Hi,
i like the tweak; OK to commit?
While it is reasonable to expect this behaviour without the "zero
or more", i see how the misunderstanding "one or more" can arise:
In many situations, to grant no permissions on a given path, it is
sufficient to not mention it in unveil(2) at all, so it may no
On Wed, 4 Dec 2019, at 18:07, Theo de Raadt wrote:
> I think it is implied, if no permissions are listed.
Perhaps and it may be due my inexperience with C interfaces that I didn't
think to try it.
I think your wording would have been enough for me to twig so I've made
the patch for that instances
Chris Rawnsley wrote:
> On Wed, 4 Dec 2019, at 14:08, Theo de Raadt wrote:
> > unveil("/", "");
> > unveil(NULL, NULL);
>
> Thank you. I didn't realise that was possible.
>
> I tried to write an update to the man page for unveil(2). Is this
> accurate? Should I send it along to tech@?
>
> Inde
On Wed, 4 Dec 2019, at 14:08, Theo de Raadt wrote:
> unveil("/", "");
> unveil(NULL, NULL);
Thank you. I didn't realise that was possible.
I tried to write an update to the man page for unveil(2). Is this
accurate? Should I send it along to tech@?
Index: lib/libc/sys/unveil.2
===
Chris Rawnsley wrote:
> I applied unveil next. This went much more smoothly allowing only the
> few files required for the programme to function. However, I've realised
> since that I only need to access a few files at initialisation and then
> I can shut off all access t
plied unveil next. This went much more smoothly allowing only the
few files required for the programme to function. However, I've realised
since that I only need to access a few files at initialisation and then
I can shut off all access to the file system.
>From the man page on unveil
Let me guess, that /bsd link was another "security" idea from that
mercury chloride .org?
On 2018-02-21, Nicolas Schmidt wrote:
> Thanks Tim, that was right on the money! Indeed my „/bsd“ was a symbolic
> link, pointing to „/bsd.mp“. Because the target path of the symlink was
> absolute, when it tried to write the new kernel to „./mnt/bsd“ it of course
> pointed to the ramdisk.
>
>
1 - 100 of 315 matches
Mail list logo
