Re: Advice sought on Portmaster -Faf and deleted ports

On Mon, Oct 14, 2013 at 9:48 PM, Scott Ballantyne wrote: > > Adam Vande More wrote: > > > > > It does seem like a bit > > > of over-kill to quit updating ALL ports because one is long > > > gone. Seems like it could do the others. > > > > > > > So it should continue on and potentially build 1000'

Re: Advice sought on Portmaster -Faf and deleted ports

On Mon 14 Oct 2013 Warren Block wrote: > On Mon, 14 Oct 2013, Scott Ballantyne wrote: > > > > > On Mon, 14 oct 2013, Warren Block wrote: > >> On Mon, 14 Oct 2013, Scott Ballantyne wrote: > >> > > > > Actually, the last time I updated my ports was when I installed 9.0, > > and I used the portmast

Re: Advice sought on Portmaster -Faf and deleted ports

Adam Vande More wrote: > > > It does seem like a bit > > of over-kill to quit updating ALL ports because one is long > > gone. Seems like it could do the others. > > > > So it should continue on and potentially build 1000's of ports with broken > linking and dependencies? Portupgrade will do th

Re: Advice sought on Portmaster -Faf and deleted ports

On Mon, 14 Oct 2013, Scott Ballantyne wrote: On Mon, 14 oct 2013, Warren Block wrote: On Mon, 14 Oct 2013, Scott Ballantyne wrote: What errors, exactly? Well, for example: portmaster -Faf it starts to fetch a bunch of files it finds a port which has been deleted, such as linux-base-fc4

Re: FreeBSD, Centos and ZFS

On Oct 12, 2013, at 10:56 AM, Mark Felder wrote: > On Sat, Oct 12, 2013, at 10:53, aurfalien wrote: >> Hi, >> >> I would like to first say that by no means is this a "hey, why is my Mac >> faster then my PC" kind of email. >> >> I'm really hoping its an LSI driver issue. >> > > It may very we

Re: Advice sought on Portmaster -Faf and deleted ports

On Mon, Oct 14, 2013 at 6:35 PM, Scott Ballantyne wrote: > > > I understand why portmaster quits that port. Because it has no choice. > It does seem like a bit > of over-kill to quit updating ALL ports because one is long > gone. Seems like it could do the others. > So it should continue on a

Re: Advice sought on Portmaster -Faf and deleted ports

On Mon, 14 oct 2013, Warren Block wrote: > On Mon, 14 Oct 2013, Scott Ballantyne wrote: > > >> > >> What errors, exactly? > > > > Well, for example: > > > > portmaster -Faf > > it starts to fetch a bunch of files > > it finds a port which has been deleted, such as > > linux-base-fc4 > > and it s

Re: Do I really have to install 80 packages?

On 10/13/13 17:38, Thomas Mueller wrote: On the question of playing Adobe Flash in FreeBSD, could one use the MS-Windows 32-bit version with (i386-)Wine? I plan to try that. Apparently that won't solve much. The primary issue now with watching flash movies is the drm - on linux it somehow uses

Re: SU+J Lost files after a power failure

On Oct 14, 2013, at 12:41 PM, RW wrote: > On Mon, 14 Oct 2013 11:48:18 -0700 Charles Swiger wrote: >> Yes. Without journalling, you'd normally perform the full >> timeconsuming fsck in the foreground. > > Journalling removes the need for the background fsck which only recovers > lost space. Th

Re: SU+J Lost files after a power failure

Hi-- On Oct 14, 2013, at 11:51 AM, Daniel Feenberg wrote: > This discussion skirts the critical issue - are files that are not open for > writing endangered? No description of the uses of journaling can be > considered informative if it doesn't address that explicitly. As a naive user > I have

Re: SU+J Lost files after a power failure

On 14.10.2013 20:43, Adam Vande More wrote: > On Mon, Oct 14, 2013 at 1:33 PM, CeDeROM > wrote: > > Thank you for explaining :-) So it looks that it would be sensible to > force filesystem check every n-th mount..? > > > Please explain the logic in which this he

Re: SU+J Lost files after a power failure

On 14.10.2013 18:47, Adam Vande More wrote: > There is no *warranty* as explicitly stated in > http://www.freebsd.org/copyright/freebsd-license.html > Aha, please don't play on words ;-). I think you understood I was speaking about the filesystem state not a lawyer issue.

Re: SU+J Lost files after a power failure

On 14.10.2013 20:08, RW wrote: > On Mon, 14 Oct 2013 18:34:36 +0200 > David Demelier wrote: > >> On 14.10.2013 14:39, RW wrote: > >>> If you are having problems with data integrity you might try >>> gjournal or zfs instead. >> >> Why? SU+J is enabled by default. Isn't the purpose of a journaled f

Re: Advice sought on Portmaster -Faf and deleted ports

On Mon, 14 Oct 2013, Scott Ballantyne wrote: I'm following the recipe at the end of man portmaster for deleting and reinstalling all my ports, which I have done many times in the past. This time, I am getting errors on the portmaster -Faf step involving deleted ports, and I'm not sure how to dea

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013 11:48:18 -0700 Charles Swiger wrote: > fsck_y_enable="YES" One of the most annoying things about SU+J is that fsck asks if you want to use the journal. So fsck -y wont do a proper check unless the journal replay fails. ___ freebsd-q

Re: SU+J Lost files after a power failure

Charles Swiger wrote: [snip] > Yes. Without journalling, you'd normally perform the full timeconsuming > fsck > in the foreground. With journalling, it should be able to do a journal > replay to restore the filesystem to an OK state, but sometimes that > doesn't restore consistency, in which c

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013 11:48:18 -0700 Charles Swiger wrote: > Yes. Without journalling, you'd normally perform the full > timeconsuming fsck in the foreground. Journalling removes the need for the background fsck which only recovers lost space. > With journalling, it should be > able to do a j

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013, Bruce Cran wrote: On 10/14/2013 6:16 PM, CeDeROM wrote: Isn't there Journal to prevent and reverse such damage? Unlike other journaling filesystems, UFS+J only protects the metadata, not the data itself - i.e. I think it ensures you won't have to run a manual fsck, bu

NFS locks rpcbind port = 0 failed? - try #2

This is a continuation of "9.1 VM nfs3 & locks over VPN" - trying a different angle maybe it'll jostle someones memory. I now have a FreeBSD 9.2 VM at an offsite hosting company.  hostname nl101vpn OpenVPN is installed on it, routed not bridged mode. I have multiple OSs installed on local network

Re: SU+J Lost files after a power failure

Thank you all for good hints! This will come handy! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-

Re: SU+J Lost files after a power failure

On Oct 14, 2013, at 11:33 AM, CeDeROM wrote: > On Mon, Oct 14, 2013 at 7:54 PM, Bruce Cran wrote: >> On 10/14/2013 6:16 PM, CeDeROM wrote: >>> Isn't there Journal to prevent and reverse such damage? >> >> Unlike other journaling filesystems, UFS+J only protects the metadata, not >> the data itse

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 1:43 PM, Adam Vande More wrote: > > > mount -o sync > should be mount sync -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 1:33 PM, CeDeROM wrote: > Thank you for explaining :-) So it looks that it would be sensible to > force filesystem check every n-th mount..? Please explain the logic in which this helps anything. > Or to do a filesystem check > after crash..? Already standard behavio

Re: SU+J Lost files after a power failure

On 10/14/2013 7:33 PM, CeDeROM wrote: Thank you for explaining :-) So it looks that it would be sensible to force filesystem check every n-th mount..? Or to do a filesystem check after crash..? Are there any flags like that to mark filesystem unclean and to force fsck after n-th mount? That would

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 7:54 PM, Bruce Cran wrote: > On 10/14/2013 6:16 PM, CeDeROM wrote: >> Isn't there Journal to prevent and reverse such damage? > > Unlike other journaling filesystems, UFS+J only protects the metadata, not > the data itself - i.e. I think it ensures you won't have to run a m

Re: Advice sought on Portmaster -Faf and deleted ports

> > > Hi, > > > > I'm following the recipe at the end of man portmaster for deleting and > > reinstalling all my ports, which I have done many times in the > > past. This time, I am getting errors on the portmaster -Faf step > > involving deleted ports, and I'm not sure how to deal with this > > e

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013 18:34:36 +0200 David Demelier wrote: > On 14.10.2013 14:39, RW wrote: > > If you are having problems with data integrity you might try > > gjournal or zfs instead. > > Why? SU+J is enabled by default. Isn't the purpose of a journaled file > system to ensure that any bad shutd

Re: SU+J Lost files after a power failure

On 10/14/2013 6:16 PM, CeDeROM wrote: Isn't there Journal to prevent and reverse such damage? Unlike other journaling filesystems, UFS+J only protects the metadata, not the data itself - i.e. I think it ensures you won't have to run a manual fsck, but just like plain old UFS files may be trun

Re: FreeBSD, Centos and ZFS

On Oct 12, 2013, at 10:56 AM, Mark Felder wrote: > On Sat, Oct 12, 2013, at 10:53, aurfalien wrote: >> Hi, >> >> I would like to first say that by no means is this a "hey, why is my Mac >> faster then my PC" kind of email. >> >> I'm really hoping its an LSI driver issue. >> > > It may very we

Re: Tuning /etc/sysctl.conf

Hi Steve, I use it as a paticular desktop PC. Well, if you need more details about it, please, let me know. What do you think about current tuning? Thanks --CJPM 2013/10/14 Carlos Jacobo Puga Medina > Mmm... just a correction in /etc/sysctl.conf, it seems that by mistake > I've copied a websi

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 7:09 PM, Brad Mettee wrote: > On 10/14/2013 12:50 PM, CeDeROM wrote: >> Then why random files gets damaged as well even they are not >> accessed/written on power loss? :-) > > Random files can be affected because the sectors of the hard disk containing > the directory entri

Re: SU+J Lost files after a power failure

On 10/14/2013 12:50 PM, CeDeROM wrote: On Mon, Oct 14, 2013 at 6:47 PM, Adam Vande More wrote: On Mon, Oct 14, 2013 at 11:34 AM, David Demelier wrote: Why? SU+J is enabled by default. Isn't the purpose of a journaled file system to ensure that any bad shutdown will protect data? As already st

Re: Tuning /etc/sysctl.conf

On Mon, 14 Oct 2013 18:35:49 +0200 Carlos Jacobo Puga Medina wrote: > Hi people, > > I'm very interested to tuning /etc/sysctl.conf according to the > specifications of my PC. As a general rule it is more appropriate to think of tuning in terms of the workload you intend to apply to you

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 6:56 PM, Adam Vande More wrote: > On Mon, Oct 14, 2013 at 11:50 AM, CeDeROM wrote: >> Then why random files gets damaged as well even they are not >> accessed/written on power loss? :-) > Prove they weren't. Hmm, maybe /etc/pwd.db as David mentioned? This is updated on pa

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 11:50 AM, CeDeROM wrote: > > Then why random files gets damaged as well even they are not > accessed/written on power loss? :-) > Prove they weren't. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lis

Re: Tuning /etc/sysctl.conf

Mmm... just a correction in /etc/sysctl.conf, it seems that by mistake I've copied a website link into the file. Sorry, it was a copy-paste error :) % cat /etc/sysctl.conf # $FreeBSD: release/9.2.0/etc/sysctl.conf 112200 2003-03-13 18:43:50Z mux $ # # This file is read when going to multi-user an

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 6:47 PM, Adam Vande More wrote: > On Mon, Oct 14, 2013 at 11:34 AM, David Demelier > wrote: >> >> Why? SU+J is enabled by default. Isn't the purpose of a journaled file >> system to ensure that any bad shutdown will protect data? > > As already stated, those measures are to

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 11:34 AM, David Demelier wrote: > > Why? SU+J is enabled by default. Isn't the purpose of a journaled file > system to ensure that any bad shutdown will protect data? > As already stated, those measures are to preserve fs integrity eg meta data is in sync. It doesn't ensu

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 6:34 PM, David Demelier wrote: > Why? SU+J is enabled by default. Isn't the purpose of a journaled file > system to ensure that any bad shutdown will protect data? > > On GNU/Linux, on Windows you will not require anything else to recover > your data. > > I don't want to tw

Tuning /etc/sysctl.conf

Hi people, I'm very interested to tuning /etc/sysctl.conf according to the specifications of my PC. I've been reading some guides [1], tutorials [2-3], Q&A [4] and the FreeBSD Handbook's related section 12.12 Tuning with sysctl(8), but I think it's much more convenient if I contrast it with other

Re: SU+J Lost files after a power failure

On 14.10.2013 14:39, RW wrote: > On Mon, 14 Oct 2013 05:02:22 -0400 > Michael Powell wrote: > >> David Demelier wrote: >> >>> Hello there, >>> >>> I'm writing because after a power failure I was unable to log in on >>> my FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly >>> but some f

Re: Reinstall without reformat

The brutal and brute-force approach can work - better if you boot from a USB stick, of course. You can untar base.tzx and kernel.tzx in your /, with filesystems mounted. As Polytropon says, do a backup of what you'll want afterwards. This approach will leave a lot of cruft (old versions of shared

Re: Reinstall without reformat

On Mon, 14 Oct 2013 07:51:15 -0600 (MDT), Warren Block wrote: > It is possible to mount filesystems manually from the shell and have > bsdinstall continue with the install without formatting them. It's been > a while since I tried that, and I don't recall the exact details. > bsdinstall(8) sugg

Re: firefox: after update -> version 23: can not swap tabs

On Mon, 14 Oct 2013, O. Hartmann wrote: FF is in my case 24, too: pkg info firefox firefox-24.0,1 Have you done updating the ports regarding 20130929 in /usr/ports/UPDATING? I did on all boxes and on all boxes I did the tab-stickyness is present. Firefox 24 allows tab moves for me on both

Re: Reinstall without reformat

On Mon, 14 Oct 2013, Polytropon wrote: On Sun, 13 Oct 2013 23:01:02 -0600 (MDT), Warren Block wrote: On Mon, 14 Oct 2013, Polytropon wrote: On Sun, 13 Oct 2013 13:24:30 -0400, Kenta Suzumoto wrote: Hi all. Is it possible to install FreeBSD without formatting the disk? Yes. The installer su

vBSDcon: October 25 - 27. 2013 in Herndon, VA

Just a friendly reminder vBSDcon is less than 2 weeks away from October 25 – 27, 2013 in Herndon, VA. Online registrations are open for 9 more days and will close on October 23, 2013. On-site registrations will be available throughout the entirety of vBSDcon. Attendees may register for vBSDco

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013 05:02:22 -0400 Michael Powell wrote: > David Demelier wrote: > > > Hello there, > > > > I'm writing because after a power failure I was unable to log in on > > my FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly > > but some files disappeared, including /etc/pwd.

DEFAULT_VERSIONS=

Has the "DEFAULT_VERSIONS=" been extended to include ports other than python=2.7 python2=2.7 python3=3.3 perl5=5.18 ruby=2.0 tcltk=8.6 as presently shown in UPDATING? Are their plans to extend it to ports like db6, mysql56\*, etcetera? -- Jerry ♔ Disclaimer: off-list followups get on-list replie

Re: SU+J Lost files after a power failure

Michael Powell wrote: [snip] > The other box is my first foray into the land of GPT, along with SU+J. It > was sitting at the 'couldn't mount... Press return for /bin/sh' line. > There was an error indicating that replaying one or more journals had > failed. I was able to successfully fsck all the

Re: Authorisation Errors on 9.2

On 14/10/2013 06:37, Beeblebrox wrote: Hi, I Inadvertently posted the gnome-keyring bit. That's almost standard error message on FreeBSD-Gnome. The relevant bit for the error is in fact: slim: gkr-pam: no password is available for user However, the user cannot login on a tty without providing a p

Re: SU+J Lost files after a power failure

David Demelier wrote: > Hello there, > > I'm writing because after a power failure I was unable to log in on my > FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some > files disappeared, including /etc/pwd.db. Thus I was unable to log in. > > I've been able to regenerate the p

Re: firefox: after update -> version 23: can not swap tabs

El día Monday, October 14, 2013 a las 10:23:49AM +0200, O. Hartmann escribió: > > I have a 10-CURRENT r255948 from October 1st, with all ports from head > > too, rev. r328930. > > > > FF is version 24.0 in the r328930 ports and the tabs can be moved fine > > with drag and drop. > > > > HIH > >

Re: firefox: after update -> version 23: can not swap tabs

On Mon, 14 Oct 2013 09:50:48 +0200 Matthias Apitz wrote: > El día Monday, October 14, 2013 a las 08:54:56AM +0200, O. Hartmann > escribió: > > > > > After the last major update of www/firefox to version 23 firefox > > rejects of moving/swapping the tabs. They are static now. I do not > > know

Re: Reinstall without reformat

On Mon, Oct 14, 2013 at 1:21 AM, Polytropon wrote: > On Sun, 13 Oct 2013 23:01:02 -0600 (MDT), Warren Block wrote: > > On Mon, 14 Oct 2013, Polytropon wrote: > > > > > On Sun, 13 Oct 2013 13:24:30 -0400, Kenta Suzumoto wrote: > > >> Hi all. Is it possible to install FreeBSD without formatting the

Re: firefox: after update -> version 23: can not swap tabs

El día Monday, October 14, 2013 a las 08:54:56AM +0200, O. Hartmann escribió: > > After the last major update of www/firefox to version 23 firefox > rejects of moving/swapping the tabs. They are static now. I do not > know whether this has to do with the "great pixman update", because > coincide