swiftgri...@gmail.com said:
> Let's say I've got a machine with a boatload of RAM and I have an
> application which wants extremely fast writes, but doesn't really care that
> much about data integrity, and this case, nor do I. Having the system come
> back in the same state after rebooting is
Sounds like you want a tmpfs, possibly union mounted over the
"stable" filesystem, with "rsync" being your :sync" command.
kre
Sounds like you're looking for a combo of overlay mounts on top of tmpfs
- the flush to disk you'd have to manage manually but I've done this
with some success in the past and I do seem to recall it being discussed
to provide pseudo read-write over a read-only medium such as a CDROM
I know NetBSD supports RAM disks. I also know it uses them for
installation, but I'm not sure if they are overlays on top of the static
disk images or if they get loaded/populated with the image after the
system boots. The effect is the same, either way. You end up with a
writable file
> I have a scenario where I have several NetBSD systems which were just
> upgraded to SSDs. I forgot to turn on discard (TRIM) support on the drives
> when I first put them in.
I don’t think that’s a big deal. For the record, I have run my SSD without TRIM
on NetBSD for a long while now. In
Gerard Lally writes:
> If I want separate / swap and /home, I presume I should delete raid1a
> and create raid1a, raid1b and raid1e instead (by clicking on its
> parent raid1 and selecting "Edit BSD partitions")?
Separately from how to use sysinst for this (which I've
On Tue, 8 Mar 2016, Andrew Cagney wrote:
One got ya! They can be slow to come online and may not be ready if
you're trying to use or mount it during boot.
This is especially slow for some reason on WD drives with SES. I have a
2TB WD USB3 drive for backups that has this issue. It's fine
On Tue, 8 Mar 2016, Benny Siegert wrote:
I don?t think that?s a big deal. For the record, I have run my SSD
without TRIM on NetBSD for a long while now. In fact, your email taught
me about the ?discard? option :?
Well, I have also on other systems. I've also read that some SSDs don't
On 8 March 2016 at 11:13, herbert langhans wrote:
> Hi List,
> you sure know these little external USB-harddisks, often used for laptops
> or basic backups. Like WD-Passport and Seagate Expansion and whatever
> they name them.
>
> They come FAT formatted, right? Has anyone
Most of these that I've used work just fine. You end up mounting them
as /dev/sdXe and use mount_msdos. /dev/sdXe is just a made up
disklabel that the machine makes to temporarily deal with it.
Some come formatted with ExFAT now which is not compatible with
NetBSD, and
From: Travis Paul [160308 18:36]
> They come FAT formatted, right? Has anyone of you tried to
> reformat them for NetBSD? I guess its not a big thing, but I wonder if I
> can buy any brand (need it for portable server backup and need GID/UID)
or
> there
Andy Ruhl writes:
> On Tue, Mar 8, 2016 at 9:13 AM, herbert langhans wrote:
>> Hi List,
>> you sure know these little external USB-harddisks, often used for laptops
>> or basic backups. Like WD-Passport and Seagate Expansion and whatever
>> they name
On Tue, Mar 8, 2016 at 9:13 AM, herbert langhans wrote:
> Hi List,
> you sure know these little external USB-harddisks, often used for laptops
> or basic backups. Like WD-Passport and Seagate Expansion and whatever
> they name them.
>
> They come FAT formatted, right? Has
Hi List,
you sure know these little external USB-harddisks, often used for laptops
or basic backups. Like WD-Passport and Seagate Expansion and whatever
they name them.
They come FAT formatted, right? Has anyone of you tried to
reformat them for NetBSD? I guess its not a big thing, but I wonder
On Mar 8, 2:26pm, fr...@phoenix.owl.de (Frank Wille) wrote:
-- Subject: Re: Simple IPSEC client with certificate - phase 1 time out
| http://www.netbsd.org/docs/network/ipsec/
| In section "Configuring IPsec kernel".
|
| It also mentions IPSEC_ESP, which was removed together with IPSEC_NAT_T
|
Greg Troxel wrote:
> It seems to me that if a kernel with "option IPSEC" and w/o swcrypto
> doesn't work, then perhaps it should fail to config, or log an error at
> runtime. (Perhaps swcrypto isn't required, and it's just that there
> must be some crypto provider.)
As far as I understand
Frank Wille writes:
> BTW, my problem with setkey on macppc was caused by the missing swcrypto
> pseudo device in the kernel.
>
> Our IPsec FAQ should mention that you need that, besides "option IPSEC". I
> know that amd64, i386 and sparc64 have these enabled by default
On Mar 8, 12:14pm, fr...@phoenix.owl.de (Frank Wille) wrote:
-- Subject: Re: Simple IPSEC client with certificate - phase 1 time out
| Christos Zoulas wrote:
|
| >>| > If your server is behind NAT, I think that got broken at some point.
| >>|
| >>| Oh no! :(
| >>
| >>Yes, it is almost
18 matches
Mail list logo