tlaro...@polynum.com writes:
>> Another question is if your disk is following the specifications
>>
>
> It's a not used disk but not new that I'm using as a guinea pig because
> I don't trust it. It was in a Iomega enclosure with an ARM board, that I
> bought several years ago (because I
"J. Lewis Muir" writes:
> Thank you for your reply! That makes sense. I guess my problem is
> that I'm not sure where some of these remote file systems "fit." In
> one case, I have a web app that needs read access to the log file of a
> server process running on another machine. The web app
On 07/25, Johnny Billquist wrote:
> For your question, the answer is essentially "where it fits".
>
> If you, for example have the netbsd source tree available over NFS, the
> reasonable place to mount it would be under /usr/src
> If you have user home directories over NFS, /home might be a good
For your question, the answer is essentially "where it fits".
If you, for example have the netbsd source tree available over NFS, the
reasonable place to mount it would be under /usr/src
If you have user home directories over NFS, /home might be a good place.
It does not make sense to have a
Hi, all!
I'm wondering, what's the best location for a client machine to
permanently mount NFS remote file systems?
I was thinking
/mnt/
or maybe (but I'm less convinced that encoding the type of the remote
file system in the path is a good idea):
/mnt/nfs/
However, in hier(7)
On Thu, Jul 25, 2019 at 07:14:32PM -, Michael van Elst wrote:
> tlaro...@polynum.com writes:
>
> >But I have heard the disk writing after the filesystem was unmounted and
> >the prompt back. Several seconds after, even one minute or a bit more...
>
> unmounting flushes caches, so all writes
tlaro...@polynum.com writes:
>But I have heard the disk writing after the filesystem was unmounted and
>the prompt back. Several seconds after, even one minute or a bit more...
unmounting flushes caches, so all writes will be done when umount
returns.
>This was with the USB connection.
>With
On Thu, Jul 25, 2019 at 06:20:19PM -, Michael van Elst wrote:
> tlaro...@polynum.com writes:
>
> >2) Is there a way to query the status of the disk in order to give a hint
> >to the user about if it's safe or not to unplug the external device?
>
> It is safe to unplug the device when you
tlaro...@polynum.com writes:
>2) Is there a way to query the status of the disk in order to give a hint
>to the user about if it's safe or not to unplug the external device?
It is safe to unplug the device when you have unmounted the filesystem.
--
--
Michael
Hello,
On Thu, Jul 25, 2019 at 12:04:52PM -0400, Greg Troxel wrote:
> tlaro...@polynum.com writes:
>
> > It's then clear that writes are differed (the write cache is not
> > settable with dkctl(8)) and that the disk gets a lot in its cache
> > memory and writing only after.
>
> Does it write
They both point to 1 sector or 64 block. Also, you must have booting
partition end
lined up too, so it never can be bigger than 2Gb.
I mean 2Tb, but this statement is anyway wrong. However - I have all
booting wedges less than MBR partition, but never succeeded if boot
wedge was bigger than
I installed /boot, ran installboot and gpt biosboot. Here is fdisk
output for the disk:
What flags installboot was used with?
installboot -o console=com0,speed=115200 /dev/rdk2
/usr/mdec/bootxx_ffsv2
Did you installed MBR ever? I always do that separately.
Here is the result:
# dkctl
wrote:
> I guess it's on a i386/amd64 arch? Because, if my memory is right,
> there is the need of the "\x55\xAA" in the two last bytes of the
> first 512b block (the signature) for the BIOS.
Yes, this is amd64. The magic number is there, indeed:
# dd if=/dev/rwd2d bs=512 count=1|hexdump
tlaro...@polynum.com writes:
> It's then clear that writes are differed (the write cache is not
> settable with dkctl(8)) and that the disk gets a lot in its cache
> memory and writing only after.
Does it write things within a few seconds?
> 2) Is there a way to query the status of the disk in
On Thu, Jul 25, 2019 at 05:46:31PM +0200, Emmanuel Dreyfus wrote:
> Martin Husemann wrote:
>
> > You may want to use rwd2d instead of rdk2
>
> What is the rationale? I expect that to destroy the GPT.
There are various architectures that write the boot record to the disk,
not the NetBSD root
On Thu, Jul 25, 2019 at 04:20:59PM +0200, Emmanuel Dreyfus wrote:
> Hello
>
> I try to boot NetBSD/Xen from a GPT, with little success.
>
> I understand NetBSD EFI bootstrap does not support multiboot, so I
> should use BIOS boot.
>
> I installed /boot, ran installboot and gpt biosboot. Here is
If the subject line isn't clear, I hope the explanations will be:
Context: I'm testing an ARM Soc (Olimex Lime2 based on Allwinner A20
and earmv7hf proc) and the board has a SATA port and is able to power
a 2.5" HDD but not a 3.5" one.
I have then to connect an external disk (3.5" HDD) with its
Martin Husemann wrote:
> You may want to use rwd2d instead of rdk2
What is the rationale? I expect that to destroy the GPT.
# installboot -o console=com0,speed=115200 /dev/rwd2d
/usr/mdec/bootxx_ffsv2
And indeed:
# gpt show wd2
start size index contents
0
On Thu, Jul 25, 2019 at 05:20:12PM +0200, Emmanuel Dreyfus wrote:
> Dima Veselov wrote:
>
> > > I installed /boot, ran installboot and gpt biosboot. Here is fdisk
> > > output for the disk:
> >
> > What flags installboot was used with?
>
> installboot -o console=com0,speed=115200 /dev/rdk2
>
Dima Veselov wrote:
> > I installed /boot, ran installboot and gpt biosboot. Here is fdisk
> > output for the disk:
>
> What flags installboot was used with?
installboot -o console=com0,speed=115200 /dev/rdk2
/usr/mdec/bootxx_ffsv2
Here is the result:
# dkctl wd2 listwedges
/dev/rwd2d: 3
I understand NetBSD EFI bootstrap does not support multiboot, so I
should use BIOS boot.
I installed /boot, ran installboot and gpt biosboot. Here is fdisk
output for the disk:
What flags installboot was used with?
Partition table:
0: GPT Protective MBR (sysid 238)
start 1, size
Hello
I try to boot NetBSD/Xen from a GPT, with little success.
I understand NetBSD EFI bootstrap does not support multiboot, so I
should use BIOS boot.
I installed /boot, ran installboot and gpt biosboot. Here is fdisk
output for the disk:
Partition table:
0: GPT Protective MBR (sysid 238)
I would re-open the PR.
christos
> On Jul 23, 2019, at 11:47 PM, Dima Veselov wrote:
>
> Hello, Christos,
>
> I see there is no comments on filed port-amd64/53687 assuming
> the task is not that easy. Is there any glue to fix that temporary?
>
> 27.10.2018 3:47, Christos Zoulas пишет:
>> In
On Jul 11, 2019, at 8:43 PM, Brett Lymn wrote:
On Thu, Jul 11, 2019 at 07:31:22PM -0400, Dan LaBell wrote:
I can't believe that trash is still on the internet, personally.
OK, personal opinion and then launching into a ad hominem attack
with no
technical argument. That was not
24 matches
Mail list logo
