Re: 10.4 release - is the binary update corrupt?

On 08/10/2017 11:27, Dr. Nikolaus Klepp wrote: > Hi! > > My notes suggest for this case: > > pkg clean # cleans /var/cache/pkg/ > rm -rf /var/cache/pkg/* # just remove it all > pkg update -f # forces update of repository catalog > rm

10.4 release - is the binary update corrupt?

Hi, I’m having trouble upgrading a 10.3 machine to 10.4: looks like something is corrupt: Fetching metadata signature for 10.4-RELEASE from update4.freebsd.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata

Re: 10.4 release - is the binary update corrupt?

Hi! My notes suggest for this case: pkg clean # cleans /var/cache/pkg/ rm -rf /var/cache/pkg/* # just remove it all pkg update -f # forces update of repository catalog rm /var/db/pkg/repo-*.sqlite# removes all remote repository catalogs pkg

Re: console-only freebsd

On Sat, Oct 07, 2017 at 04:43:08PM +0200, Polytropon wrote: > On Sat, 7 Oct 2017 15:20:19 +0100, tech-lists wrote: > > what program or port would one use to view a gif or jpg file? > > Additional thought: > > With vt, default text modes are typically much bigger than > the traditional 80x25 of

dd: vm_fault: pager read error

Here is a report of a repeatable unrecoverable problem. 11.0 release amd64 r306420 kern.geom.debugflags=0 (unmodified) # dd if=/dev/zero of=/dev/ada0s1 seek=2048 count=1 bs=1m 1+0 records in 1+0 records out 1048576 bytes transferred # reboot # The same goes for any other uncached access to

Re: dd: vm_fault: pager read error

09.10.2017 1:23, grarpamp пишет: > Here is a report of a repeatable unrecoverable problem. > > 11.0 release amd64 r306420 > > kern.geom.debugflags=0 (unmodified) > > # dd if=/dev/zero of=/dev/ada0s1 seek=2048 count=1 bs=1m > 1+0 records in > 1+0 records out > 1048576 bytes transferred > > #

Re: 10.4 release - is the binary update corrupt?

> On 8 Oct 2017, at 12:04, Matthew Seaman wrote: > >> Am Sonntag, 8. Oktober 2017 schrieb Dr Josef Karthauser: >>> Hi, >>> >>> I’m having trouble upgrading a 10.3 machine to 10.4: looks like something >>> is corrupt: >>> >>> Fetching metadata signature for 10.4-RELEASE

automount usb msdosfs no partition table

Hello world :-) I need to configure automount for a testing machine. It seems to work fine, except for two issues: 1. Mount point does not disappear after device disappears, what makes things harder to script when device is gone. automount -c does not remove the mountpoint, only restarting the