Re: Which is the public interface to use for ipfw when lagg(4)? [SOLVED]

[Unga]

Hi Mark

Thanks for the reply. It worked. It was lagg1.Unga


- Original Message -
> From: Mark Felder 
> To: freebsd-questions@freebsd.org
> Cc: 
> Sent: Tuesday, June 25, 2013 2:29 PM
> Subject: Re: Which is the public interface to use for ipfw when lagg(4)?
> 
> On Tue, Jun 25, 2013, at 7:13, Unga wrote:
>> 
>>  What is the interface should I use for the pif? Is it lagg1?
>> 
> 
> The interface you should use is the interface the IPs are on. It doesn't
> matter what kind of interface it is. In this case it looks like lagg1.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscr...@freebsd.org"
> 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Help finding sound driver

[Polytropon]

On Wed, 26 Jun 2013 11:45:10 +0700 (ICT), Olivier Nicole wrote:
> Azalia ADI1986A, 6 -Channel High-Definition Audio CODEC
> Support Jack-Sensing, Enumeration, Multi-streaming
> S/PDIF out on back I/O port
> Jack-Sensing & Enumeration 
> 
> Is there any change a driver exists for that audio chipset, for FreeBSD 9.1?

Probably snd_hda will work. A common solution is to try this first
(because of the "name matching"), and then load all drivers and
see which one is working. Check the kernel output messages and
also "cat /dev/sndstat" to confirm success.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Help finding sound driver

[Olivier Nicole]

Hello,

I have an old motherboard Asus P5L-MX that I want to use for an
application. It needs sound.

Asus documentation
(http://www.asus.com/Motherboards/P5LMX/#specifications) lists the
sound chipset as:

Azalia ADI1986A, 6 -Channel High-Definition Audio CODEC
Support Jack-Sensing, Enumeration, Multi-streaming
S/PDIF out on back I/O port
Jack-Sensing & Enumeration 

Is there any change a driver exists for that audio chipset, for FreeBSD 9.1?

TIA,

Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: http://www.freebsd.org/doc/en/books/handbook/serialconsole-set up.html

[Jungle Boogie]

Raspberry pi running headless with practically no services and usb to
serial connection is what I'm likely to use.

--
sip:jungleboo...@sip2sip.info
inum:  +883510009902611
On Jun 25, 2013 6:23 PM, "Warren Block"  wrote:

> On Tue, 25 Jun 2013, Mark Felder wrote:
>
>  On Tue, Jun 25, 2013, at 11:23, Stephen Burke wrote:
>>
>>> Does anyone know how I could push serial output to an IP port that I
>>> could SSH to?
>>>
>>>
>> You want something like a Portmaster or Lantronix device that will
>> provide serial consoles over SSH
>>
>> http://www.lantronix.com/**device-networking/external-**device-servers/
>>
>
> Or a small computer like a netbook running sshd with a USB to serial
> adapter and cu(1).
>
> If you had two systems located near each other in a data center, each
> could act as the SSH serial console terminal for the other.
> __**_
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions
> To unsubscribe, send any mail to "freebsd-questions-**
> unsubscr...@freebsd.org "
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Hello

[Mike Jeays]

On Wed, 26 Jun 2013 08:56:59 +1000
julius  wrote:

> Which BSD for a user desktop ??!.
> I all ready have Linux mint but I like to try again, in the past I have 
> use it but no luck in dual booting system with windows and I have try to 
> follow youtube BSD users that gave instructions on the BSD and no luck.
> Everybody that I watch in youtube for instruction it hasn't work even 
> loading the BSD on is own hasn't work.So which BSD for a user desktop??!
> Thank you
> -- 
> Best Wishes Julius
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

PC-BSD is a good place to start; it makes installation easy.

I prefer running Windows in a VM under VirtualBox to dual-booting. Switching
between the two is much faster, and you can make the host file system visible
to the guest with Samba.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Should I be able to use mergemaster with freebsd-update?

[Mike Brown]

On Tue, Jun 25, 2013, at 15:29, Eugene wrote:
> I do not quite understand. Is the freebsd-update upgrade process
> completely broken? 

IMHO it is partially broken; I'm not doing anything special. How broken it is 
depends on what's getting changed. Most of what the system is designed to do, 
it indeed does very well. It also overlaps some of the functionality of 
mergemaster in that it automatically merges as many files as it can, which is 
nice.

Where it is under-designed and under-implemented is in its rudimentary 
handling of un-mergeable files, and in its total lack of support for the 
regeneration of /etc/*.db files (like the, uh, rather important password 
database) and sendmail aliases - things that you would handle via mergemaster 
in an ordinary, source-based upgrade, but which you must now figure out how to 
do by hand, without any guidance, and they really don't make it easy for you.

When I upgraded from 8.1 to 8.3, I avoided the issue altogether by not really 
merging anything; when dumped into the empty text editor, I just loaded my old 
files and made no changes. In the Handbook, there's an assumption that people 
who do this will go back later and figure out what merges are needed, but the 
resources you need to do that don't exist; if you don't do the merge when 
prompted, you don't get a second chance. In fact, even if you do it when 
prompted, you need to get it right, or start the whole process over.

My upgrade to 8.3 worked out OK because I got lucky; freebsd-update hadn't 
fetched new, stock password database files. The unmergeable files were all 
text files, nothing requiring anything to be regenerated.

But this time around, for 8.3 to 8.4, I am trying to do everything I'm 
supposed to, actually merging when prompted. The fact that it's a *really* 
manual process is a pain, but as I mentioned, I found a way to at least run 
sdiff from another window, which made it a lot easier, although still more 
tedious than it should be.

The main problem this time is that I'm not so lucky with the password files, 
because for 8.4, freebsd-update has fetched new, stock .db files to put in 
/etc.  So, yes, I was able to merge master.passwd & passwd, but that's not 
very helpful since the .db files won't be in sync with them.

If allow my custom password database to be overwritten with these new, stock 
.db files, obviously that's bad. And because freebsd-update makes no special 
allowance for the .db files, it actually put a zero-byte file in the staging 
area instead of the real .db file (as if it were going to have me modify it 
with an editor). So if I proceed, my password database will actually be 
overwritten with an empty file, which I believe would be a disaster.


The solution, I feel, is to:

1. make freebsd-update recognize files that most likely need to be regenerated 
instead of replaced - /etc/*.db, at least, if not also any other binary file, 
and some of the things that would be generated by 'make' in /etc/mail. The 
user should be informed that these files need to be regenerated, if there's no 
way to just regenerate them automatically when their companion source files 
have been updated or merged.

2. make freebsd-update run mergemaster on the unmergeable text files, instead 
of dumping the user into an empty text editor for each one. For each file that 
can't be automatically merged, mergemaster will give the user the opportunity 
to choose whether to keep the old file, replace it with the new file, 
interactively merge them via sdiff, or do nothing. It is also smart enough to 
realize that when certain files are being touched, such as /etc/master.passwd, 
/etc/mail/aliases, etc. you'll need to run pwd_mkdb, cap_mkdb, services_mkdb, 
or newaliases...and it will run those for you (or remind you to do it). For 
this to work, mergemaster would need some tweaking to deal with 
freebsd-update's staging area, and to not duplicate any of the work that 
freebsd-update does.

I keep hoping that maybe there's some nuance of the process that I'm missing, 
and that all of this really is not a problem.. user error, or not reading the 
docs carefully enough, you know? But Mark Felder's comments seem to confirm 
that it's a real issue.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: http://www.freebsd.org/doc/en/books/handbook/serialconsole-set up.html

[Warren Block]

On Tue, 25 Jun 2013, Mark Felder wrote:


On Tue, Jun 25, 2013, at 11:23, Stephen Burke wrote:

Does anyone know how I could push serial output to an IP port that I
could SSH to?



You want something like a Portmaster or Lantronix device that will
provide serial consoles over SSH

http://www.lantronix.com/device-networking/external-device-servers/


Or a small computer like a netbook running sshd with a USB to serial 
adapter and cu(1).


If you had two systems located near each other in a data center, each 
could act as the SSH serial console terminal for the other.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Cannot Update Source Tree After Move To Subversion 1.8

[Tim Daneliuk]

On 06/24/2013 04:58 PM, Tim Daneliuk wrote:

On 06/24/2013 03:20 PM, Matthew Seaman wrote:

On 24/06/2013 20:28, Tim Daneliuk wrote:

After the update to svn 1.8, I did a new svn co of the FBSD 9-STABLE
source branch.  When I try to do an update to it, I see this now:

svn: E155005: Working copy not locked at /usr/scr
svn co svn://svn.freebsd.org/base/stable/9 /usr/src

/usr/src is a symlink to another directory in a separate filesystem,
but this historically worked, so I'm guess that is not the problem.

Ideas?



svn upgrade




Hm 

[root] ozzie ~>svn upgrade /usr/src
[root] ozzie ~>svn update /usr/src
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/usr1/src-9-STABLE' locked.
svn: E155004: '/usr1/src-9-STABLE' is already locked.
[root] ozzie ~>svn cleanup /usr/src
[root] ozzie ~>svn update /usr/src
Updating '/usr/src':
svn: E155005: No write-lock in '/usr/src/sys'
svn: E155005: Additional errors:
svn: E155005: Working copy not locked at '/usr/src'.





It seems that svn 1.8 does not like symlinks.  I have this:

   /usr/src -> /usr1/src-9-STABLE

I can do this fine:

  svn update /usr1/src-9-STABLE

But this causes svn to dump core:

  svn update /usr/src


At which point I have to do a cleanup to get the locks cleared out.


--

Tim Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Should I be able to use mergemaster with freebsd-update?

[Mark Felder]

On Tue, Jun 25, 2013, at 15:29, Eugene wrote:
> Hi all,
> 
> I do not quite understand. Is the freebsd-update upgrade process
> completely 
> broken? Or is it some special mode? Or was it broken recently?
> Because some time ago I have upgraded from 8.1 to 8.2 quite nicely, with 
> editor-based merging of config files, and was planning to upgrade to 8.4 
> soon (especially as 8.2 is already not compatible with some ports).
> 

It depends on how many changes happen between the releases. Have you
tried taking 7.x to 9.x before? You'll have to deal with that editor for
merging many, many files. Maybe nearly everything in /etc. It's quite
time consuming, whereas I can get mergemaster to auto-merge all of those
files and only show me the 5 that I've personally touched.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Hello

[julius]

Which BSD for a user desktop ??!.
I all ready have Linux mint but I like to try again, in the past I have 
use it but no luck in dual booting system with windows and I have try to 
follow youtube BSD users that gave instructions on the BSD and no luck.
Everybody that I watch in youtube for instruction it hasn't work even 
loading the BSD on is own hasn't work.So which BSD for a user desktop??!

Thank you
--
Best Wishes Julius
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Should I be able to use mergemaster with freebsd-update?

[Eugene]

Hi all,

I do not quite understand. Is the freebsd-update upgrade process completely 
broken? Or is it some special mode? Or was it broken recently?
Because some time ago I have upgraded from 8.1 to 8.2 quite nicely, with 
editor-based merging of config files, and was planning to upgrade to 8.4 
soon (especially as 8.2 is already not compatible with some ports).


Best wishes
Eugene

-Original Message- 
From: Mike Brown

Sent: Tuesday, June 25, 2013 12:14 PM
To: freebsd-questions@freebsd.org
Subject: Re: Should I be able to use mergemaster with freebsd-update?


I'm using freebsd-update to upgrade my system to the latest minor version
(from 8.3-RELEASE to 8.4-RELEASE).

I'm surprised that the merge handling system isn't more robust. When 
upgrading

the old way, from source, I was used to using mergemaster to handle any
merges that couldn't be done automatically.

But when using freebsd-update, it seems that any failed merges require 
that

you get dumped into an empty text editor for each file.
[...]


As I continue with this process, doing all the mergemaster tasks manually, 
I'm

finding that the situation is even worse than I first realized.

<> 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html

[pete wright]

On Jun 25, 2013 9:25 AM, "Stephen Burke"  wrote:
>
> Does anyone know how I could push serial output to an IP port that I
> could SSH to?
>

Sounds like you are looking for something like SOL (serial over LAN) which
can be setup with IPMI.  Google should help you find more info on setting
up IPMI.

-pete
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html

[Mark Felder]

On Tue, Jun 25, 2013, at 11:23, Stephen Burke wrote:
> Does anyone know how I could push serial output to an IP port that I
> could SSH to?
>

You want something like a Portmaster or Lantronix device that will
provide serial consoles over SSH

http://www.lantronix.com/device-networking/external-device-servers/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html

[Stephen Burke]

Does anyone know how I could push serial output to an IP port that I
could SSH to?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Your AdWord Position on Google

[AdWordPosition]

Hello,

 Let me introduce you to our new advertisement technology which
will bring your website on top of Google, Yahoo, Bing etc. without
Pay Per Click campaign.

 With our technology you will be only person or company who owes
exclusive rights on chosen keyword and once you get that keyword,
no one else can use it during whole year.

 In order to see our technology in action, you can try online demo on
our website in 3 easy steps:
 - Go to our website and click ONLINE DEMO button (green one);
 - Fill online demo form fields with your website www.freebsd.org and keyword;
 - Click View Online Demo button and see results.

 If you are interested in getting more information from us, you can send
us quote request with Get a Quote button or call us and our experts will
analyze your website and keywords and will provide you all needed
 information about our technology and details.

We await your response.

Best Regards,
AdWordPosition·com
5716 Corsa Avenue,
Westlake Village, CA 91362

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Failed to allocate receive buffer problem

[John Baldwin]

On Wednesday, June 12, 2013 3:06:26 am Alex Liptsin wrote:
> Hi.
> 
> I have a problem that when running a ping (or any other traffic) over IPoIB 
port,
> Traffic fails after some time.
> At destination server DMESG I see that errors:
> 
> Jun 11 14:42:11 h-qa-033 kernel: ib1: failed to allocate receive buffer 253
> Jun 11 14:42:12 h-qa-033 kernel: ib1: failed to allocate receive buffer 254
> Jun 11 14:42:13 h-qa-033 kernel: ib1: failed to allocate receive buffer 255
> Jun 11 14:42:14 h-qa-033 kernel: ib1: failed to allocate receive buffer 0
> Jun 11 14:42:15 h-qa-033 kernel: ib1: failed to allocate receive buffer 1
> Jun 11 14:42:16 h-qa-033 kernel: ib1: failed to allocate receive buffer 2
> Jun 11 14:42:17 h-qa-033 kernel: ib1: failed to allocate receive buffer 3
> Jun 11 14:42:18 h-qa-033 kernel: ib1: failed to allocate receive buffer 4
> Jun 11 14:42:19 h-qa-033 kernel: ib1: failed to allocate receive buffer 5
> Jun 11 14:42:20 h-qa-033 kernel: ib1: failed to allocate receive buffer 6
> Jun 11 14:42:21 h-qa-033 kernel: ib1: failed to allocate receive buffer 7
> 
> I work with FreeBSD 9.1.
> 
> Is it a bug or some configuration issues?

Do you see memory allocation errors in netstat -m?

Specifically this line:

0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters)

If so, it may be that the IPoIB layer has an mbuf leak.  The rest of netstat -
m might be useful here as you can see if any of the zones are full.

-- 
John Baldwin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Should I be able to use mergemaster with freebsd-update?

[Mark Felder]

On Tue, Jun 25, 2013, at 3:14, Mike Brown wrote:
> 
> Well, thanks for reading this far. I'm scared to death to reboot now,
> since my
> server is in another city, but we'll see how it goes.
> 

I always avoid freebsd-update when moving between releases simply
because of this atrocity.

If it requires we setup a stupid kickstarter to fund a developer to sit
down and rip into freebsd-update so it uses mergemaster I would be
incredibly thankful. I don't know how anyone can upgrade between FreeBSD
releases without an /etc/mergemaster.rc with the following settings:

AUTO_INSTALL='yes'
AUTO_UPGRADE='yes'
# keep our custom motd
IGNORE_FILES='/etc/motd'
# Do not display changes that only affect whitespace
DIFF_FLAG='-Bub'
FREEBSD_ID='yes'
DELETE_STALE_RC_FILES='yes'
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Which is the public interface to use for ipfw when lagg(4)?

[Mark Felder]

On Tue, Jun 25, 2013, at 7:13, Unga wrote:
> 
> What is the interface should I use for the pif? Is it lagg1?
> 

The interface you should use is the interface the IPs are on. It doesn't
matter what kind of interface it is. In this case it looks like lagg1.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Which is the public interface to use for ipfw when lagg(4)?

[Unga]

Hi all 

My server runs FreeBSD 9.0 (i386).

/etc/rc.conf shows:
#
cloned_interfaces="lagg0 lagg1"
#
ifconfig_em0="up"
ifconfig_em2="up"
ifconfig_lagg0="laggproto lacp laggport em0 laggport em2"
ipv4_addrs_lagg0="someIP/26"
#
ifconfig_em1="up"
ifconfig_em3="up"
ifconfig_lagg1="laggproto lacp laggport em1 laggport em3"
ipv4_addrs_lagg1="publicIP1/29 publicIP2/32"


The server is publicly accessed using publicIP1 and publicIP2.


In the ipfw rules:
cmd="ipfw -q add"
pif="???"

# Allow out ping
$cmd 00100 allow icmp from any to any out via $pif keep-state


What is the interface should I use for the pif? Is it lagg1?

Best regards
Unga
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: When to submit regression in a PR

[Aymeric Mansoux]

Hi,

Shane Ambler said :
> > My question therefore is: while I will mention these problems
> > upstream, should I also make the PR? Contact the port maintainer
> > directly? I understand it is not FreeBSD specific (same issue on
> > Debian Sid) however it really make the current port unusable for
> > those working on laptops and those needing to input characters only
> > reachable with the compose key.
> 
> I would. While the ports are handled separately from the base system
> they need to be maintained as well. If a version of a port has issues
> then an older version could stay in place.
> 
> The pr system is used for ports as well as the base system.

Mark Felder said :
> It's probably a good idea to open a PR and let the port maintainer
> know, but we really need to have upstream to fix it. FreeBSD
> discourages doing custom "development" in the ports tree, so even if
> you could whip up a patch to fix it we would prefer that it get
> committed upstream and the port updated to pull the new version rather
> than have the port committer include a custom patch with the port.

Thanks Shane and Mark. In fact, shortly after this mail a beginning of
fix as been committed, so it will eventually surface in FreeBSD as well.


Shane Ambler said: 
> Can't say I'm sure which key you refer to as compose - do you mean Alt
> or Ctrl? I have heard of the ctrl key being remapped to the caps lock
> for continuous use. You may also look into turning on sticky keys, it
> keeps a modifier key active without holding it down so that the next key
> pressed has the modifier included. see x11/xkbset

You can turn any key into a compose/multi key. Mine is mapped on the
Right Alt: 

setxkbmap -option compose:ralt 

It allows you to input characters such "é" or "ø" on keyboards where
such keys are missing. It works by making key combos or chords.

As for the stickiness of the key this is partly a problem linked to
the fix just committed. By default a compose key seems to work both as
sticky and non sticky to accommodate different writing styles/needs.
This is noticeable in any X applications that accept keyboard input,
from terminals to a browser. The last commit in upstream plan9port has
brought back the functionality of the compose key only as sticky. When a
key chord is done (non-sticky) the compose functionality is not working.

Anyway this discussion is not so relevant to this list anymore :)
Thanks again for advising on the PR issue! Very useful.

Best,
a.
--
http://su.kuri.mu

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Agevolazioni per le nuove imprese

[SEVERO]

Agevolazioni per le nuove aziende e per quelle esistenti da massimo 2 anni
Per informazioni clicca quì

Per non ricevere news clicca quì

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Should I be able to use mergemaster with freebsd-update?

[Mike Brown]

> I'm using freebsd-update to upgrade my system to the latest minor version
> (from 8.3-RELEASE to 8.4-RELEASE).
> 
> I'm surprised that the merge handling system isn't more robust. When 
> upgrading 
> the old way, from source, I was used to using mergemaster to handle any 
> merges that couldn't be done automatically.
> 
> But when using freebsd-update, it seems that any failed merges require that 
> you get dumped into an empty text editor for each file.
> [...]

As I continue with this process, doing all the mergemaster tasks manually, I'm 
finding that the situation is even worse than I first realized.


First, the relatively painless part. As I mentioned, after running 
'freebsd-update -r 8.4-RELEASE upgrade', I had to deal with the un-mergeable 
files.

Although mergemaster apparently isn't an option, its interactive merge 
function is really just a front-end for sdiff, so I found that I could 
replicate that part of its functionality by doing this in a separate window 
(-w 100 because I use a 100-column terminal):

cd /var/db/freebsd-update/merge/8.4-RELEASE
find -X . -type f | xargs -n 1 -o -I % sh -c '{ echo Now processing %. 
left=current, right=new, help="?"; sdiff -d -w 100 -o ../new/% ../old/% %; }'

This populated my 'new' directory with merged files, so that (in the first 
window) when I opened the text editor for each one, I only had to just give it 
a once-over and exit the editor.

Among the diffs in this 8.3 to 8.4 upgrade were changes to /etc/master.passwd 
and /etc/passwd, to add the 'auditdistd' and 'hast' users. As reported in 
March 2012 [1] in relation to 8.x to 9.x upgrades, this won't work as 
expected, because freebsd-update doesn't run pwd_mkdb after the master.passwd 
update.



Now the real hurt begins; in the 8.3 to 8.4 upgrade, it's even worse.

Once I saved all the files in the editor, I was prompted to approve a diff for 
each one. I had to answer "y" or the entire process aborts.

Among the changes I was asked to approve, besides visible diffs, were 
unspecified differences in /etc/pwd.db and /etc/spwd.db, the binary files that 
contain the password database.  There's no choice but to answer "y" and 
approve them, and I don't get any opportunity to rebuild them properly.

So apparently, freebsd-update wants to install new, stock password databases, 
which are out-of-sync with my customized, merged master.passwd & passwd files. 
(And because of the way the freebsd-update system works, what I actually 
approved were empty, 0-byte files, the result of the failed merges.)

What would happen if I just let it do this? Surely I wouldn't be able to log 
in, after the reboot, right?



After approving the files (again, I had no choice!), I was presented with 
lists of all the files that would be deleted, added, and modified. Sure 
enough, bad /etc/pwd.db and /etc/spwd.db files were in the list.

At this point, the merge folders were now gone; I no longer had the new 
master.passwd in a recognizable place. So I thought, OK, I'll run 
'freebsd-update install' and hope that the new files end up in /etc. Then I 
could just run 'pwd_mkdb -p /etc/master.passwd' to regenerate passwd, pwd.db 
and spwd.db before my reboot.

But the 'freebsd-update install' didn't put them there yet; I guess that 
doesn't happen till after the reboot. So they're still sitting in a staging 
folder, now gzipped and with obfuscated names, indexed in a separate file.

Averting this disaster-in-the-making is not at all straightforward:

cd /var/db/freebsd-update
mkdir -m 0700 /tmp/oldpwdfiles
zcat files/`grep '^/etc/master\.passwd' install.LYQAJQ/INDEX-NEW | cut -d \| -f 
7`.gz > /tmp/oldpwdfiles/master.passwd
zcat files/`grep '^/etc/passwd' install.LYQAJQ/INDEX-NEW | cut -d \| -f 7`.gz > 
/tmp/oldpwdfiles/passwd
zcat files/`grep '^/etc/pwd\.db' install.LYQAJQ/INDEX-NEW | cut -d \| -f 7`.gz 
> /tmp/oldpwdfiles/pwd.db
zcat files/`grep '^/etc/spwd\.db' install.LYQAJQ/INDEX-NEW | cut -d \| -f 7`.gz 
> /tmp/oldpwdfiles/spwd.db
mkdir -m 0700 /tmp/newpwdfiles
pwd_mkdb -d /tmp/newpwdfiles -p /tmp/oldpwdfiles/master.passwd
gzip /tmp/newpwdfiles/*
mv /tmp/newpwdfiles/master.passwd.gz files/`grep '^/etc/master\.passwd' 
install.LYQAJQ/INDEX-NEW | cut -d \| -f 7`.gz
mv /tmp/newpwdfiles/passwd.gz files/`grep '^/etc/passwd' 
install.LYQAJQ/INDEX-NEW | cut -d \| -f 7`.gz
mv /tmp/newpwdfiles/pwd.db.gz files/`grep '^/etc/pwd\.db' 
install.LYQAJQ/INDEX-NEW | cut -d \| -f 7`.gz
mv /tmp/newpwdfiles/spwd.db.gz files/`grep '^/etc/spwd\.db' 
install.LYQAJQ/INDEX-NEW | cut -d \| -f 7`.gz
rm -fr /tmp/oldpwdfiles /tmp/newpwdfiles


I'm really shocked that it came to this. Did I just overlook the 
"--no-surprises" option in freebsd-update?



And now, before I reboot, I have to figure out how to handle the changes that 
got made in /etc/mail ... ordinarily I'd run 'make all install restart' in 
there. Not an option till after reboot, though. At least it's not crucial for 
the reboot to work.

Again, this is something that mergemaster w

Re: freebsd-update percentage indicators - what are they, why are they so random?

[Mike Brown]

> Fetching 1 metadata files...  70.5%
> done.
>  70.5%
>  70.5%
>  74.2%
>  74.2%
>  81.7%
>  81.7%
>  70.5%

I think this is a result of having "-v" in my GZIP environment variable.
I always forget about my GZIP and BZIP2 variables. I should've known.
So, never mind about that.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"