[gentoo-user] Re: Something started muting the sound

[Ian Zimmerman]

On 2017-08-12 13:21, John Covici wrote:

> How about checking the various volumes rather than muting maybe some
> of them are 0 or rather some negative number or something?  Also, you
> might delete the asound.state and let the system start over.  Last
> resort, there is an alsa users mailing list.
> 
> One other thought, get pulse audio out of the way and see if alsa is
> working.

To clarify: it works for me (TM), I don't need a solution.  I am just
curious because I don't heed the warning and it still works.

My volumes are not the defaults, and they do get restored.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
Do obvious transformation on domain to reply privately _only_ on Usenet.

Re: [gentoo-user] Re: dev-python/whoosh fails to compile

[John Covici]

On Thu, 10 Aug 2017 16:37:57 -0400,
Ian Zimmerman wrote:
> 
> On 2017-08-09 08:31, Ian Zimmerman wrote:
> 
> > So, bug #627244 is relevant after all.
> > 
> > I don't have doc in make.conf, so it should just work for me [murmurs a
> > belief-neutral invocation/]
> 
> And it did work with no problems.
> 
> So John - your "doc" USE flag is almost certainly what ails you.

OK, thanks. Its now working, but I take your point.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

[gentoo-user] Re: Something started muting the sound

[Ian Zimmerman]

On 2017-08-12 17:31, Mick wrote:

> > My ALSA is built as modules, including the core (I'm guessing that
> > means snd.ko, right?).  I don't do anything particular to load them,
> > they're not listed in /etc/conf.d/modules.  Yet the mixer save and
> > restore via alsasound works.
> > 
> > Could it be that alsasound itself loads the modules on demand, and
> > the warning above is misleading?
> 
> Did you run alsactl init to see if the alsa modules are probed and
> loaded without errors?

They're listed in the output of lsmod, and sound playback works as
expected.  If there was an error neither would be the case, or am I
wrong about this?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
Do obvious transformation on domain to reply privately _only_ on Usenet.

Re: [gentoo-user] Re: Something started muting the sound

[John Covici]

On Sat, 12 Aug 2017 12:31:45 -0400,
Mick wrote:
> 
> [1  ]
> On Saturday 12 Aug 2017 09:05:10 Ian Zimmerman wrote:
> > On 2017-08-12 17:39, Alexander Kapshuk wrote:
> > > (5). Postinst message for alsa-utils:
> > > pkg_postinst() {
> > > if [[ -z ${REPLACING_VERSIONS} ]]; then
> > > elog
> > > elog "To take advantage of the init script, and automate the process of"
> > > elog "saving and restoring sound-card mixer levels you should"
> > > elog "add alsasound to the boot runlevel. You can do this as"
> > > elog "root like so:"
> > > elog "# rc-update add alsasound boot"
> > > ewarn
> > > ewarn "The ALSA core should be built into the kernel or loaded through
> > > other" ewarn "means. There is no longer any modular auto(un)loading in
> > > alsa-utils."
> > I don't get this last part.
> > 
> > My ALSA is built as modules, including the core (I'm guessing that means
> > snd.ko, right?).  I don't do anything particular to load them, they're
> > not listed in /etc/conf.d/modules.  Yet the mixer save and restore via
> > alsasound works.
> > 
> > Could it be that alsasound itself loads the modules on demand, and the
> > warning above is misleading?
> 
> Did you run alsactl init to see if the alsa modules are probed and loaded 
> without errors?


How about checking the various volumes rather than muting maybe some
of them are 0 or rather some negative number or something?  Also, you
might delete the asound.state and let the system start over.  Last
resort, there is an alsa users mailing list.

One other thought, get pulse audio out of the way and see if alsa is
working.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

Re: [gentoo-user] Re: Something started muting the sound

[Mick]

On Saturday 12 Aug 2017 09:05:10 Ian Zimmerman wrote:
> On 2017-08-12 17:39, Alexander Kapshuk wrote:
> > (5). Postinst message for alsa-utils:
> > pkg_postinst() {
> > if [[ -z ${REPLACING_VERSIONS} ]]; then
> > elog
> > elog "To take advantage of the init script, and automate the process of"
> > elog "saving and restoring sound-card mixer levels you should"
> > elog "add alsasound to the boot runlevel. You can do this as"
> > elog "root like so:"
> > elog "# rc-update add alsasound boot"
> > ewarn
> > ewarn "The ALSA core should be built into the kernel or loaded through
> > other" ewarn "means. There is no longer any modular auto(un)loading in
> > alsa-utils."
> I don't get this last part.
> 
> My ALSA is built as modules, including the core (I'm guessing that means
> snd.ko, right?).  I don't do anything particular to load them, they're
> not listed in /etc/conf.d/modules.  Yet the mixer save and restore via
> alsasound works.
> 
> Could it be that alsasound itself loads the modules on demand, and the
> warning above is misleading?

Did you run alsactl init to see if the alsa modules are probed and loaded 
without errors?
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: Something started muting the sound

[Ian Zimmerman]

On 2017-08-12 17:39, Alexander Kapshuk wrote:

> (5). Postinst message for alsa-utils:
> pkg_postinst() {
> if [[ -z ${REPLACING_VERSIONS} ]]; then
> elog
> elog "To take advantage of the init script, and automate the process of"
> elog "saving and restoring sound-card mixer levels you should"
> elog "add alsasound to the boot runlevel. You can do this as"
> elog "root like so:"
> elog "# rc-update add alsasound boot"
> ewarn
> ewarn "The ALSA core should be built into the kernel or loaded through other"
> ewarn "means. There is no longer any modular auto(un)loading in alsa-utils."

I don't get this last part.

My ALSA is built as modules, including the core (I'm guessing that means
snd.ko, right?).  I don't do anything particular to load them, they're
not listed in /etc/conf.d/modules.  Yet the mixer save and restore via
alsasound works.

Could it be that alsasound itself loads the modules on demand, and the
warning above is misleading?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
Do obvious transformation on domain to reply privately _only_ on Usenet.

Re: [gentoo-user] Re: Restart agetty after update @world?

[Neil Bothwick]

On Sat, 12 Aug 2017 16:30:34 +0300, Nikos Chantziaras wrote:

> > lsof | grep -w DEL | grep portage  
> 
> You should probably use app-admin/lib_users for this.

Or app-admin/needrestart, which also has an option to restart affected
services.


-- 
Neil Bothwick

Don't put all your hypes in one home page.


pgp3ZAM1ixOid.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Something started muting the sound

[Robin Atwood]

On Saturday 12 August 2017, Mick wrote:
> On Saturday 12 Aug 2017 20:49:48 Robin Atwood wrote:
> Which device does alsamixer or pulseaudio show as being active?  I found on
> some PCs that HDMI is now set as the default audio device and I had to
> change the configuration to make analogue sound devices active again.

Mick, thanks for the suggestion but alsamixer still shows: 
Card: HDA Intel MID  │
Chip: Conexant CX20585

and is in fact the only device.

Robin
-- 
--
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
 from "Mandalay" by Rudyard Kipling
--









-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [gentoo-user] Re: Restart agetty after update @world?

[Matthias Hanft]

Nikos Chantziaras wrote:
>>
>> lsof | grep -w DEL | grep portage
> 
> You should probably use app-admin/lib_users for this.

Thank you, I didn't know this.  Looks good (and found mysql
in addition to my "lsof" command).

-Matt

Re: [gentoo-user] Restart agetty after update @world?

[Matthias Hanft]

Dale wrote:
> 
> Correct.  I should have mentioned that in my post but assumed it would
> be known.  Anytime agetty is killed, it just pops back up.  I suspect it
> doesn't stay dead for even a second.  Sort of like those zombie movies. 

Looks good.  I used "pkill agetty", and now it looks like

root 16153 1  0 17:01 tty6 00:00:00 /sbin/agetty 38400 tty6 linux
root 16155 1  0 17:01 tty1 00:00:00 /sbin/agetty 38400 tty1 linux
root 16156 1  0 17:01 tty2 00:00:00 /sbin/agetty 38400 tty2 linux
root 16157 1  0 17:01 tty3 00:00:00 /sbin/agetty 38400 tty3 linux
root 16158 1  0 17:01 tty4 00:00:00 /sbin/agetty 38400 tty4 linux
root 16159 1  0 17:01 tty5 00:00:00 /sbin/agetty 38400 tty5 linux

and lsof... (or lib_users) doesn't show anything any more.  Thank you!

-Matt

Re: [gentoo-user] Something started muting the sound

[Alexander Kapshuk]

On Sat, Aug 12, 2017 at 4:49 PM, Robin Atwood  wrote:
> I have a Thinkpad T410 where, after I installed Gentoo on it, everything
> "just worked (TM)". The sound is via the bog-standard Intel chips on the
> mobo and uses the hda_intel drivers. I didn't use the TP for a long time,
> just periodically updating Gentoo, but when I eventually did try to use it
> the sound was muted. This means I shut down the X server to remove
> complications from the desktop and from the console aplay doesn't produce
> any sound. Everything looks normal, driver modules loaded, alsamixer shows
> the usual output, channels all active. I booted to a windows partition and
> the sound works, so the hardware is OK. The very weird thing is if I put the
> TP to sleep with acpitool and wake it up again, the sound works for about 60
> seconds and then dies. There is nothing in the message log at all when this
> happens. I upgraded the kernel but that didn't help.
>
>
>
> This problem has been dragging on for some years and I am contemplating a
> complete re-install from scratch. But before I do that does anyone have any
> idea what I could try?
>
>
>
> TIA
>
> Robin
>
>
>
> --
>
> --
>
> Robin Atwood.
>
>
>
> "Ship me somewheres east of Suez, where the best is like the worst,
>
> Where there ain't no Ten Commandments an' a man can raise a thirst"
>
> from "Mandalay" by Rudyard Kipling
>
> --
>
>

What's the output of these command lines?
(1). lspci -vnn | sed '/Audio/,/driver/!d'

(2). grep -Ei '^[^#]*(snd|hda)' linux/.config

(3). rc-update show | grep alsa

(4). grep HDA /var/log/dmesg

(5). Postinst message for alsa-utils:
pkg_postinst() {
if [[ -z ${REPLACING_VERSIONS} ]]; then
elog
elog "To take advantage of the init script, and automate the process of"
elog "saving and restoring sound-card mixer levels you should"
elog "add alsasound to the boot runlevel. You can do this as"
elog "root like so:"
elog "# rc-update add alsasound boot"
ewarn
ewarn "The ALSA core should be built into the kernel or loaded through other"
ewarn "means. There is no longer any modular auto(un)loading in alsa-utils."
fi
}

(6). Also, if you check out the Gentoo wiki article on how to set up ALSA.
See if there's anything you might've overlooked when setting it up:
https://wiki.gentoo.org/wiki/ALSA

Re: [gentoo-user] Something started muting the sound

[Mick]

On Saturday 12 Aug 2017 20:49:48 Robin Atwood wrote:
> I have a Thinkpad T410 where, after I installed Gentoo on it, everything
> "just worked (TM)". The sound is via the bog-standard Intel chips on the
> mobo and uses the hda_intel drivers. I didn't use the TP for a long time,
> just periodically updating Gentoo, but when I eventually did try to use it
> the sound was muted. This means I shut down the X server to remove
> complications from the desktop and from the console aplay doesn't produce
> any sound. Everything looks normal, driver modules loaded, alsamixer shows
> the usual output, channels all active. I booted to a windows partition and
> the sound works, so the hardware is OK. The very weird thing is if I put
> the TP to sleep with acpitool and wake it up again, the sound works for
> about 60 seconds and then dies. There is nothing in the message log at all
> when this happens. I upgraded the kernel but that didn't help.
> 
> This problem has been dragging on for some years and I am contemplating a
> complete re-install from scratch. But before I do that does anyone have any
> idea what I could try?
> 
> TIA
> Robin

Which device does alsamixer or pulseaudio show as being active?  I found on 
some PCs that HDMI is now set as the default audio device and I had to change 
the configuration to make analogue sound devices active again.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Something started muting the sound

[Robin Atwood]

I have a Thinkpad T410 where, after I installed Gentoo on it, everything "just 
worked (TM)". The sound is via the bog-standard Intel chips on the mobo and 
uses the hda_intel drivers. I didn't use the TP for a long time, just 
periodically updating Gentoo, but when I eventually did try to use it the 
sound was muted. This means I shut down the X server to remove complications 
from the desktop and from the console aplay doesn't produce any sound. 
Everything looks normal, driver modules loaded, alsamixer shows the usual 
output, channels all active. I booted to a windows partition and the sound 
works, so the hardware is OK. The very weird thing is if I put the TP to sleep 
with acpitool and wake it up again, the sound works for about 60 seconds and 
then dies. There is nothing in the message log at all when this happens. I 
upgraded the kernel but that didn't help.

This problem has been dragging on for some years and I am contemplating a 
complete re-install from scratch. But before I do that does anyone have any 
idea what I could try?

TIA
Robin

-- 
--
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
 from "Mandalay" by Rudyard Kipling
--









-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [gentoo-user] Restart agetty after update @world?

[John Covici]

On Sat, 12 Aug 2017 07:51:46 -0400,
Rich Freeman wrote:
> 
> On Sat, Aug 12, 2017 at 4:22 AM, Matthias Hanft  wrote:
> > Dale wrote:
> >>
> >> I do it this way.
> >> pkill agetty
> >> Simple, quick and easy to remember.  One could script it I guess???
> >
> > I'm pretty sure this would work, but is there something which would
> > start them again?  As far as I understand, these are the processes
> > that provide console login - correct?  Normally, I log in using ssh
> > via network, but I would be a little upset if I couldn't log in at
> > the console any more...
> >
> 
> Agetty is started by init, so it will be restarted if it dies.
> sysvinit does all of about 3 things in total, and this is one of them.

Would not you have to do this for each device, so maybe killall agetty
or some such?

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

[gentoo-user] Re: Restart agetty after update @world?

[Nikos Chantziaras]

On 12/08/17 10:35, Matthias Hanft wrote:

Hi,

for weekly updates, I'm using the usual update commands, such as

emerge -NDuv @world
emerge -c
revdep-rebuild -i

In order to find out which services are still using old versions
of updated programs/libraries, I add

lsof | grep -w DEL | grep portage


You should probably use app-admin/lib_users for this.

Re: [gentoo-user] Restart agetty after update @world?

[Dale]

Rich Freeman wrote:
> On Sat, Aug 12, 2017 at 4:22 AM, Matthias Hanft  wrote:
>> Dale wrote:
>>> I do it this way.
>>> pkill agetty
>>> Simple, quick and easy to remember.  One could script it I guess???
>> I'm pretty sure this would work, but is there something which would
>> start them again?  As far as I understand, these are the processes
>> that provide console login - correct?  Normally, I log in using ssh
>> via network, but I would be a little upset if I couldn't log in at
>> the console any more...
>>
> Agetty is started by init, so it will be restarted if it dies.
> sysvinit does all of about 3 things in total, and this is one of them.
>

Correct.  I should have mentioned that in my post but assumed it would
be known.  Anytime agetty is killed, it just pops back up.  I suspect it
doesn't stay dead for even a second.  Sort of like those zombie movies. 
lol 

Dale

:-)  :-) 

Re: [gentoo-user] Restart agetty after update @world?

[Rich Freeman]

On Sat, Aug 12, 2017 at 4:22 AM, Matthias Hanft  wrote:
> Dale wrote:
>>
>> I do it this way.
>> pkill agetty
>> Simple, quick and easy to remember.  One could script it I guess???
>
> I'm pretty sure this would work, but is there something which would
> start them again?  As far as I understand, these are the processes
> that provide console login - correct?  Normally, I log in using ssh
> via network, but I would be a little upset if I couldn't log in at
> the console any more...
>

Agetty is started by init, so it will be restarted if it dies.
sysvinit does all of about 3 things in total, and this is one of them.

-- 
Rich

Re: [gentoo-user] Restart agetty after update @world?

[Matthias Hanft]

Dale wrote:
> 
> I do it this way.
> pkill agetty
> Simple, quick and easy to remember.  One could script it I guess??? 

I'm pretty sure this would work, but is there something which would
start them again?  As far as I understand, these are the processes
that provide console login - correct?  Normally, I log in using ssh
via network, but I would be a little upset if I couldn't log in at
the console any more...

-Matt

Re: [gentoo-user] Restart agetty after update @world?

[Rich Freeman]

On Sat, Aug 12, 2017 at 3:35 AM, Matthias Hanft  wrote:
>
> But now, there's agetty left, and I don't know how to restart this
> service (without reboot):
>

This is because these are run directly by init and not by openrc,
unlike all the other daemons on the system.  As others pointed out you
can just kill these directly.

Under systemd agetty is run as a service just like everything else and
you can restart it the same way that you'd restart apache.  There
isn't really any equivalent to inittab in systemd other than one or
two similar global settings.

Arguably it might be nicer to treat them more like a normal service
under openrc, now that it can restart crashed services.  I'm not sure
how reliable this feature is (I haven't run openrc in a while now),
and you would need it to be reliable for agetty since most people like
having a console.  Traditionally agetty has been run by init for a
long time though, so there might be some reluctance to make this
change.  Offhand I'm not sure if there are any other issues with
making it a service in openrc.

Fun fact: sysvinit is essentially a poor man's service manager.  You
could stick anything in inittab and init will start it, and restart it
if it dies.  There is just no control over things like dependencies
and sequencing, and you have to watch out because if you have init run
some bash script, which launches a process that forks, and your script
terminates, then init will re-launch it possibly giving you a fork
bomb at boot.  Things like this are why more full-featured service
managers were created.  Even these tend to fall in generations, with
openrc being a lot more modern than what most distros were using
before upstart/runit/systemd came along.

-- 
Rich

Re: [gentoo-user] Restart agetty after update @world?

[Dale]

Matthias Hanft wrote:
> Hi,
>
> for weekly updates, I'm using the usual update commands, such as
>
> emerge -NDuv @world
> emerge -c
> revdep-rebuild -i
>
> In order to find out which services are still using old versions
> of updated programs/libraries, I add
>
> lsof | grep -w DEL | grep portage
>
> and /etc/init.d/XXX restart for those services.
>
> But now, there's agetty left, and I don't know how to restart this
> service (without reboot):
>
> [...]
> agetty 3438root  DEL   REG8,4   
> 30199325219 
> /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libnss_files-2.23.so
> agetty 3438root  DEL   REG8,4   
> 30199325229 
> /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libnss_nis-2.23.so
> agetty 3438root  DEL   REG8,4   
> 30199325233 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libnsl-2.23.so
> agetty 3438root  DEL   REG8,4   
> 30199325236 
> /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libnss_compat-2.23.so
> agetty 3438root  DEL   REG8,4   
> 30199325238 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libc-2.23.so
> agetty 3438root  DEL   REG8,4   
> 30199325230 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/ld-2.23.so
> [...]
>
> There is a /etc/init.d/agetty service, but it's stopped anyway.
> I already found some discussions in the net which stated that
> "init q" should do the job, but this doesn't work here (just
> nothing happens).
>
> Is there a way to restart agetty and finally drop those old
> libraries?
>
> Thanks,
>
> -Matt
>
>

I do it this way.

pkill agetty

Simple, quick and easy to remember.  One could script it I guess??? 

Dale

:-)  :-) 

Re: [gentoo-user] Restart agetty after update @world?

[Adam Carter]

Logout and login again?

Re: [gentoo-user] Restart agetty after update @world?

[Ian Bloss]

Running kill on the current pids?

On Sat, Aug 12, 2017, 12:36 AM Matthias Hanft  wrote:

> Hi,
>
> for weekly updates, I'm using the usual update commands, such as
>
> emerge -NDuv @world
> emerge -c
> revdep-rebuild -i
>
> In order to find out which services are still using old versions
> of updated programs/libraries, I add
>
> lsof | grep -w DEL | grep portage
>
> and /etc/init.d/XXX restart for those services.
>
> But now, there's agetty left, and I don't know how to restart this
> service (without reboot):
>
> [...]
> agetty 3438root  DEL   REG8,4
>  30199325219 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/
> libnss_files-2.23.so
> agetty 3438root  DEL   REG8,4
>  30199325229 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/
> libnss_nis-2.23.so
> agetty 3438root  DEL   REG8,4
>  30199325233 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/
> libnsl-2.23.so
> agetty 3438root  DEL   REG8,4
>  30199325236 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/
> libnss_compat-2.23.so
> agetty 3438root  DEL   REG8,4
>  30199325238 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/
> libc-2.23.so
> agetty 3438root  DEL   REG8,4
>  30199325230 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/
> ld-2.23.so
> [...]
>
> There is a /etc/init.d/agetty service, but it's stopped anyway.
> I already found some discussions in the net which stated that
> "init q" should do the job, but this doesn't work here (just
> nothing happens).
>
> Is there a way to restart agetty and finally drop those old
> libraries?
>
> Thanks,
>
> -Matt
>
>

[gentoo-user] Restart agetty after update @world?

[Matthias Hanft]

Hi,

for weekly updates, I'm using the usual update commands, such as

emerge -NDuv @world
emerge -c
revdep-rebuild -i

In order to find out which services are still using old versions
of updated programs/libraries, I add

lsof | grep -w DEL | grep portage

and /etc/init.d/XXX restart for those services.

But now, there's agetty left, and I don't know how to restart this
service (without reboot):

[...]
agetty 3438root  DEL   REG8,4   
30199325219 
/var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libnss_files-2.23.so
agetty 3438root  DEL   REG8,4   
30199325229 
/var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libnss_nis-2.23.so
agetty 3438root  DEL   REG8,4   
30199325233 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libnsl-2.23.so
agetty 3438root  DEL   REG8,4   
30199325236 
/var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libnss_compat-2.23.so
agetty 3438root  DEL   REG8,4   
30199325238 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/libc-2.23.so
agetty 3438root  DEL   REG8,4   
30199325230 /var/tmp/portage/sys-libs/glibc-2.23-r4/image/lib64/ld-2.23.so
[...]

There is a /etc/init.d/agetty service, but it's stopped anyway.
I already found some discussions in the net which stated that
"init q" should do the job, but this doesn't work here (just
nothing happens).

Is there a way to restart agetty and finally drop those old
libraries?

Thanks,

-Matt