Linux Wizard

<<		Juillet			>>
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31
<<		2009			>>

FAQ/HOWTO
04/01/2006 : Comment utiliser urpmi --parallel
09/03/2005 : Comment installer plusieurs distributions
07/07/2004 : Introduction à Linux
07/07/2004 : Gestion des logiciels ( tar.gz, rpm et urpmi )
07/07/2004 : Comment installer le pilote NForce ?

Linux Wizard - Votre ressource Linux !!

Mandriva : My ideas for Mandriva 2010.0	17/06/2009 19:36:08
1 week ago, I submitted to http://ideas.mandriva.com/en/ my proposals/ideas for Mandriva 2010.0. In order to let people comment on them, I will post the list of my submissions. I was planning to add more, but unfortunately, I'm presently in holidays ( at La Baule ), and so don't have time to do this :-). So here are my proposals : UXA and KMS support in drakx11">UXA and KMS support in drakx11">UXA and KMS support in drakx11 : As Mandriva 2010.0 will support UXA ( for Intel graphics cards ) and eventually KMS, the goal is to allow to enable/disable them directly from drax11 UI. Add runlevel 3 boot menu entry in grub options menu : This would allow to boot Mandriva directly in text mode without having to edit the kernel options. UPnP support in drakfirewall/shorewall : UPnP support may be useful for the applications supporting UPnP and thus willing to open a port on the firewall. A whitelist of applications couldbe used to only allow some specific applications to do this. Combined with a mdsum binary verification ( can be done by rpm ), this would prevent most trojans/backdoors possibles issues. Full NFSv4 support in Mandriva tools : Presently mandriva tools can't cofnigure a NFSv4 server, and doesn't handle idmapd configuration, especially in auto-install mode. App Store like GUI or how to make store.mandriva.com being a software channel distribution : This is related to my previous article about this question : About Apple App Store like GUI for Linux. reduce urpm tools executables by merging urpmq with urpmf, and urpmi.removemedia with urpmi.addmedia : The goal is to use the number of urpm tools executable and have more coherent naming and options. Integrate Moblin components : As Mandriva is part of the Moblin project, I guess that Mandriva could proposed a Moblin version. Use tracker with Nepomuk support instead of Beagle : Tracker aims to support Nepomuk, so as Mandriva have been leading the Nepomuk development and integration on the KDE side, i found normal to use Tracker with Nepomuk support under Gnome instead of Beagle. Integrate grid/cloud computing components : Mandriva is involved in a grid-computing project ( Xtreem OS ), so it could be interesting to integrate some of its components in the standard distribution notably Xtreem FS. Better Nepomuk integration : the title said all :-) One click multimedia content sharing support : Presently with one click, a user can share a directory using CIFS or NFS protocol under Mandriva. Now the goal is to allow to do the same thing, but this time using UPnP-AV thus allowing Mandriva to be a media content provider. Flicker free boot : the title said it all. Since migration to splashy, we can see big flickering during the boot process, notably before X start. This si a regression compared to the bootsplash situation. Switch to Tomoyo Linux as Mandatory Access Control system : Tomoyo have been integrated in upstream kernel, Apparmor not : the choice is easy. easy iSCSI support ( GUI ) : This could be a very useful feature in grid/cloud computing, or allow to have low cost NAS for SOHO. Compcache support notably in kernel-netbook : This feature, really useful for netbook, allow to improved kernel perf under low memory systems. Move some Mandriva tools to github or Google Code : Why not ? ;-) Group support in consolehelper : This would allow to have more fine grained permissions for Mandriva tools access. I tried to be as exhaustive as possible, but many ideas are missing, but I'd rather wait for another release. From firsts comments and rumor, 2010.0 will be an exciting release :-)
4 comment (s)	FACORAT Fabrice

Mandriva : My ideas for Mandriva 2010.0

17/06/2009 19:36:08

1 week ago, I submitted to http://ideas.mandriva.com/en/ my proposals/ideas for Mandriva 2010.0. In order to let people comment on them, I will post the list of my submissions. I was planning to add more, but unfortunately, I'm presently in holidays ( at La Baule ), and so don't have time to do this :-). So here are my proposals :

UXA and KMS support in drakx11">UXA and KMS support in drakx11">UXA and KMS support in drakx11 : As Mandriva 2010.0 will support UXA ( for Intel graphics cards ) and eventually KMS, the goal is to allow to enable/disable them directly from drax11 UI.
Add runlevel 3 boot menu entry in grub options menu : This would allow to boot Mandriva directly in text mode without having to edit the kernel options.
UPnP support in drakfirewall/shorewall : UPnP support may be useful for the applications supporting UPnP and thus willing to open a port on the firewall. A whitelist of applications couldbe used to only allow some specific applications to do this. Combined with a mdsum binary verification ( can be done by rpm ), this would prevent most trojans/backdoors possibles issues.
Full NFSv4 support in Mandriva tools : Presently mandriva tools can't cofnigure a NFSv4 server, and doesn't handle idmapd configuration, especially in auto-install mode.
App Store like GUI or how to make store.mandriva.com being a software channel distribution : This is related to my previous article about this question : About Apple App Store like GUI for Linux.
reduce urpm tools executables by merging urpmq with urpmf, and urpmi.removemedia with urpmi.addmedia : The goal is to use the number of urpm tools executable and have more coherent naming and options.
Integrate Moblin components : As Mandriva is part of the Moblin project, I guess that Mandriva could proposed a Moblin version.
Use tracker with Nepomuk support instead of Beagle : Tracker aims to support Nepomuk, so as Mandriva have been leading the Nepomuk development and integration on the KDE side, i found normal to use Tracker with Nepomuk support under Gnome instead of Beagle.
Integrate grid/cloud computing components : Mandriva is involved in a grid-computing project ( Xtreem OS ), so it could be interesting to integrate some of its components in the standard distribution notably Xtreem FS.
Better Nepomuk integration : the title said all :-)
One click multimedia content sharing support : Presently with one click, a user can share a directory using CIFS or NFS protocol under Mandriva. Now the goal is to allow to do the same thing, but this time using UPnP-AV thus allowing Mandriva to be a media content provider.
Flicker free boot : the title said it all. Since migration to splashy, we can see big flickering during the boot process, notably before X start. This si a regression compared to the bootsplash situation.
Switch to Tomoyo Linux as Mandatory Access Control system : Tomoyo have been integrated in upstream kernel, Apparmor not : the choice is easy.
easy iSCSI support ( GUI ) : This could be a very useful feature in grid/cloud computing, or allow to have low cost NAS for SOHO.
Compcache support notably in kernel-netbook : This feature, really useful for netbook, allow to improved kernel perf under low memory systems.
Move some Mandriva tools to github or Google Code : Why not ? ;-)
Group support in consolehelper : This would allow to have more fine grained permissions for Mandriva tools access.

I tried to be as exhaustive as possible, but many ideas are missing, but I'd rather wait for another release. From firsts comments and rumor, 2010.0 will be an exciting release :-)

4 comment (s)

FACORAT Fabrice

Linux : Why starting a KDE application with just su failed ?	05/06/2009 01:00:49
Several times users where surprised by the new behavior of KDE 4 applications. Indeed, as the super-user mode for the applications doesn't not work currently, they often have to open a terminal, and use su to start the application as another, notably root. However when just using su instead of su -, this will failed. Why ? The explication is very simple. First it should be noted that su means Substitute User, and not Super User. Indeed su allow to switch to whatever user you want and not just to the root user. However if no user is specified, then it will used the root user. This is logic because in a Unix/linux system, there's only one user which will normally always exist and with the same name : root. Now that this point is clarified, it should be noted that you have 2 ways to switch to another user : the light way and the heavy way. Now let's try to explain the differences between each ways : the light way : to use the light, just use the su. This will change the user, but the full environments variables of the user will not be execute, and notably, many environment variable will be inherited from the previous user. Another interesting behavior is the fact that you will stayed in the current directory. Here is an example when I will switch from the admin user to the invite user : [admin@info1 ~]$ whoami admin [admin@info1 ~]$ pwd /home/techmodis/admin [admin@info1 ~]$ env \| grep -E 'BUS\|USER' KONSOLE_DBUS_SERVICE=:1.48 USER=admin KONSOLE_DBUS_SESSION=/Sessions/4 DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-FWmPVm44Lx,guid=7e2ee933b5ed99e499368d4d4a28f64b [admin@info1 ~]$ su invite Password: [invite@info1 admin]$ pwd /home/techmodis/admin [invite@info1 admin]$ env \| grep -E 'BUS\|USER' KONSOLE_DBUS_SERVICE=:1.48 USER=invite KONSOLE_DBUS_SESSION=/Sessions/4 DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-FWmPVm44Lx,guid=7e2ee933b5ed99e499368d4d4a28f64b [invite@info1 admin]$ whoami invite As you may noticed, I'm still in the in /home/techmodis/admin directory, and thus even when I switched to the invite user. Please noticed also the $DBUS_SESSION_BUS_ADDRESS environment variable. This variable tell to all applications willing to use DBUS where they can contact the DBUS server. If the variable is not defined, then they will start a new one, but if the variable is defined, then they will try to connect to the DBUS server and failed if they can't. As normally a user is not allowed to connect to another user DBUS session, you can guess that if an application started as invite try to connect to the DBUS session of the admin user, it will failed. Please read dbus-launch manpage for further details. Now If I try to start for example dolphin, it will failed as it won't be able to connect to DBUS because it will not have the right to connect to the admin user DBUS server : [invite@info1 admin]$ dolphin (1985)/: KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." (1984)/: KUniqueApplication: Pipe closed unexpectedly. The heavy way : to use the heavy way, you just need to add the - switch to su. By using this switch, you will make su load the environment variables of the new user. Let's see an example : [admin@info1 ~]$ whoami admin [admin@info1 ~]$ pwd /home/techmodis/admin [admin@info1 ~]$ su - invite Password: [invite@info1 ~]$ pwd /home/techmodis/invite [invite@info1 ~]$ env \| grep -E 'BUS\|USER' USER=invite [invite@info1 ~]$ whoami invite As you can see, when switching to another user, the new current working directory will be the new user home directory. Please note also that the $DBUS_SESSION_BUS_ADDRESS variable is not defined. This means that when an application will try to contact DBUS, as the variable is not defined, it will auto-start a new DBUS session. So this time, Dolphin will be able to start successfully : [invite@info1 ~]$ dolphin dolphin(2499)/kio (KDirWatch) KDirWatchPrivate::KDirWatchPrivate: Available methods: ("Stat", "FAM", INotify") dolphin(2499)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/home/techmodis/invite/.local/share //user-places.xbel" for "" ["KDirWatch-1"] dolphin(2499)/kio (bookmarks) KBookmarkManager::KBookmarkManager: starting KDirWatch for "/home /techmodis/invite/.local/share//user-places.xbel" dolphin(2499)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp /kdecache-invite/ksycoca4" dolphin(2499)/kio (KDirListerCache) KDirListerCache::listDir: Listing directory: KUrl("trash:/") "/usr/bin/dolphin(2499)" Error in thread 3048703696 : "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files" "/usr/bin/dolphin(2499)" Error in thread 3048703696 : "QLocalSocket::connectToServer: Invalid name" dolphin(2499) ::GlobalModelContainer::init: Failed to connect to Nepomuk server via local socket "/home/techmodis/invite/.kde4/share/apps/nepomuk/socket" dolphin(2499)/kio (KDirListerCache) KDirListerCache::listDir: Reloading directory: KUrl("file:///home/techmodis/invite") .... All of this explains why starting a KDE application with just "su" will not work. From dbus-launch manpage, it seems that one way to solve this is to add at the end of the variable the keyword autolaunch: : You can however include autolaunch in an explicit session bus address as a fallback, for example DBUS_SESSION_BUS_ADDRESS="something:,autolaunch:" - in that case if the first address doesn't work, processes will autolaunch. (The bus address variable contains a comma-separated list of addresses to try.). So if you know the application/script which is setting the value of$DBUS_SESSION_BUS_ADDRESS, then you can modify it to make it add autolaunch automatically at the end. I do hope that this explanation will allow people to understand why they need to do some supplementary steps to start their KDE4 applications. The behavior of su is normal and exists since years on the different Unix systems. For further informations, please consult the su manpage. Note : Please note that whereas PolicyKit support will allow to do administrative task in KDE Control Center ( KDM configuration for example ), this will not solve the issue which consists to run a KDE4 application under another user name. The usage of "su -" will still be required, and kdesu/kdesudo will eventually need to be ported to KDE 4 to allow to do it without using the CLI.
1 comment (s)	FACORAT Fabrice

Linux : Why starting a KDE application with just su failed ?

05/06/2009 01:00:49

Several times users where surprised by the new behavior of KDE 4 applications. Indeed, as the super-user mode for the applications doesn't not work currently, they often have to open a terminal, and use su to start the application as another, notably root. However when just using su instead of su -, this will failed. Why ? The explication is very simple.

First it should be noted that su means Substitute User, and not Super User. Indeed su allow to switch to whatever user you want and not just to the root user. However if no user is specified, then it will used the root user. This is logic because in a Unix/linux system, there's only one user which will normally always exist and with the same name : root. Now that this point is clarified, it should be noted that you have 2 ways to switch to another user : the light way and the heavy way. Now let's try to explain the differences between each ways :

the light way : to use the light, just use the su. This will change the user, but the full environments variables of the user will not be execute, and notably, many environment variable will be inherited from the previous user. Another interesting behavior is the fact that you will stayed in the current directory. Here is an example when I will switch from the admin user to the invite user :
```
[admin@info1 ~]$ whoami
admin

[admin@info1 ~]$ pwd
/home/techmodis/admin

[admin@info1 ~]$ env | grep -E 'BUS|USER'
KONSOLE_DBUS_SERVICE=:1.48
USER=admin
KONSOLE_DBUS_SESSION=/Sessions/4
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-FWmPVm44Lx,guid=7e2ee933b5ed99e499368d4d4a28f64b

[admin@info1 ~]$ su invite
Password:

[invite@info1 admin]$ pwd
/home/techmodis/admin

[invite@info1 admin]$ env | grep -E 'BUS|USER'
KONSOLE_DBUS_SERVICE=:1.48
USER=invite
KONSOLE_DBUS_SESSION=/Sessions/4
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-FWmPVm44Lx,guid=7e2ee933b5ed99e499368d4d4a28f64b

[invite@info1 admin]$ whoami
invite
```
As you may noticed, I'm still in the in /home/techmodis/admin directory, and thus even when I switched to the invite user. Please noticed also the $DBUS_SESSION_BUS_ADDRESS environment variable. This variable tell to all applications willing to use DBUS where they can contact the DBUS server. If the variable is not defined, then they will start a new one, but if the variable is defined, then they will try to connect to the DBUS server and failed if they can't. As normally a user is not allowed to connect to another user DBUS session, you can guess that if an application started as invite try to connect to the DBUS session of the admin user, it will failed. Please read dbus-launch manpage for further details. Now If I try to start for example dolphin, it will failed as it won't be able to connect to DBUS because it will not have the right to connect to the admin user DBUS server :
```
[invite@info1 admin]$ dolphin
(1985)/: KUniqueApplication: Cannot find the D-Bus session server:  "Did not receive
 a reply. Possible causes include: the remote application did not send a reply, the message bus security policy
 blocked the reply, the reply timeout expired, or the network connection was broken."

(1984)/: KUniqueApplication: Pipe closed unexpectedly.
```

The heavy way : to use the heavy way, you just need to add the - switch to su. By using this switch, you will make su load the environment variables of the new user. Let's see an example :

[admin@info1 ~]$ whoami
admin

[admin@info1 ~]$ pwd
/home/techmodis/admin

[admin@info1 ~]$ su - invite
Password:

[invite@info1 ~]$ pwd
/home/techmodis/invite

[invite@info1 ~]$ env | grep -E 'BUS|USER'
USER=invite

[invite@info1 ~]$ whoami
invite

As you can see, when switching to another user, the new current working directory will be the new user home directory. Please note also that the $DBUS_SESSION_BUS_ADDRESS variable is not defined. This means that when an application will try to contact DBUS, as the variable is not defined, it will auto-start a new DBUS session. So this time, Dolphin will be able to start successfully :

[invite@info1 ~]$ dolphin
dolphin(2499)/kio (KDirWatch) KDirWatchPrivate::KDirWatchPrivate: Available methods:  ("Stat", "FAM", 
INotify")
dolphin(2499)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/home/techmodis/invite/.local/share
//user-places.xbel" for "" ["KDirWatch-1"]
dolphin(2499)/kio (bookmarks) KBookmarkManager::KBookmarkManager: starting KDirWatch for  "/home
/techmodis/invite/.local/share//user-places.xbel"
dolphin(2499)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from  "/var/tmp
/kdecache-invite/ksycoca4"
dolphin(2499)/kio (KDirListerCache) KDirListerCache::listDir: Listing directory: KUrl("trash:/")
"/usr/bin/dolphin(2499)" Error in thread 3048703696 : "org.freedesktop.DBus.Error.ServiceUnknown - The 
name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files"
"/usr/bin/dolphin(2499)" Error in thread 3048703696 : "QLocalSocket::connectToServer: Invalid name"
dolphin(2499) ::GlobalModelContainer::init: Failed to connect to Nepomuk server via local socket 
"/home/techmodis/invite/.kde4/share/apps/nepomuk/socket"
dolphin(2499)/kio (KDirListerCache) KDirListerCache::listDir: Reloading directory: KUrl("file:///home/techmodis/invite")
....

All of this explains why starting a KDE application with just "su" will not work. From dbus-launch manpage, it seems that one way to solve this is to add at the end of the variable the keyword autolaunch: : You can however include autolaunch in an explicit session bus address as a fallback, for example DBUS_SESSION_BUS_ADDRESS="something:,autolaunch:" - in that case if the first address doesn't work, processes will autolaunch. (The bus address variable contains a comma-separated list of addresses to try.). So if you know the application/script which is setting the value of$DBUS_SESSION_BUS_ADDRESS, then you can modify it to make it add autolaunch automatically at the end.

I do hope that this explanation will allow people to understand why they need to do some supplementary steps to start their KDE4 applications. The behavior of su is normal and exists since years on the different Unix systems. For further informations, please consult the su manpage.

Note : Please note that whereas PolicyKit support will allow to do administrative task in KDE Control Center ( KDM configuration for example ), this will not solve the issue which consists to run a KDE4 application under another user name. The usage of "su -" will still be required, and kdesu/kdesudo will eventually need to be ported to KDE 4 to allow to do it without using the CLI.

1 comment (s)

FACORAT Fabrice

Mandriva : Community ideas proposal for Mandriva 2010.0	03/06/2009 11:23:38
Some days ago, Anne Nicolas announced on Cooker ML the availability of a dedicated site to allow the community to propose ideas and wanted features for the next Mandriva release : http://ideas.mandriva.com/. Proposals can be sorted by environment, release, and version. People can add comments to the proposal or vote for it. Presently more than 56 ideas have been proposed. For the 2010.0 release, proposal should be submitted for cooker release. So don't hesitate to participate, you just need to create a Mandriva account : the registration is free. Mandriva Ideas site : http://ideas.mandriva.com/
0 comment (s)	FACORAT Fabrice

Mandriva : Community ideas proposal for Mandriva 2010.0

03/06/2009 11:23:38

Some days ago, Anne Nicolas announced on Cooker ML the availability of a dedicated site to allow the community to propose ideas and wanted features for the next Mandriva release : http://ideas.mandriva.com/. Proposals can be sorted by environment, release, and version. People can add comments to the proposal or vote for it. Presently more than 56 ideas have been proposed. For the 2010.0 release, proposal should be submitted for cooker release. So don't hesitate to participate, you just need to create a Mandriva account : the registration is free.
Mandriva Ideas site : http://ideas.mandriva.com/

0 comment (s)

FACORAT Fabrice

Linux : Listing initrd content with lsinitrd	27/05/2009 19:52:41
The initrd used by most distribution to boot a Linux OS is most of the time a black magic box for most people. Today i've learn a new command from Andrey Borzenkov on the Cooker ML : lsinitrd. This command, from the nash package, allow to list the content of the initrd. For example to list the content of the default initrd used to boot your system, just do the following command as root : lsinitrd /boot/initrd.img. With lsinitrd, [root@info1 /boot/initrd.img: =================== -rwx------ 1 root drwx------ 3 root drwx------ 4 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root drwx------ 7 root drwx------ 2 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root drwx------ 5 root drwx------ 2 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root drwx------ 2 root -rw-r--r-- 1 root -rw-r--r-- 1 root drwx------ 2 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root drwx------ 2 root -rw-r--r-- 1 root drwx------ 2 root -rw-r--r-- 1 root drwx------ 2 root -rw-r--r-- 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root drwx------ 2 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root drwx------ 2 root drwx------ 2 root drwx------ 2 root drwx------ 2 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root drwx------ 3 root brw------- 1 root crw------- 1 root lrwxrwxrwx 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root brw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root drwx------ 2 root crw------- 1 root crw------- 1 root crw------- 1 root crw------- 1 root drwx------ 2 root drwx------ 5 root drwx------ 2 root drwx------ 2 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root drwx------ 3 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root -rwxr-xr-x 1 root drwx------ 3 root drwx------ 2 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw------- 1 root -rw-r--r-- 1 root -rw------- 1 root -rw------- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw------- 1 root -rw-r--r-- 1 root -rw------- 1 root -rw------- 1 root -rw-r--r-- 1 root -rw------- 1 root -rw------- 1 root -rw------- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw------- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw------- 1 root -rw------- 1 root -rw------- 1 root -rw------- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root -rwxr-xr-x 1 root drwx------ 2 root lrwxrwxrwx 1 root drwxr-xr-x 2 root -rw-r--r-- 1 root drwxr-xr-x 8 root drwxr-xr-x 2 root -rw-r--r-- 1 root -rw-r--r-- 1 root drwxr-xr-x 4 root drwxr-xr-x 8 root -rw-r--r-- 4 root =================== #!/bin/nash mount -t proc /proc /proc setquiet echo Mounting proc filesystem echo Mounting sysfs filesystem mount -t sysfs /sys /sys echo Creating /dev mount -o mode=0755 -t tmpfs /dev /dev mkdir /dev/pts mount -t devpts mkdir /dev/shm mkdir /dev/mapper echo Creating mknod /dev/null c 1 3 mknod /dev/zero c 1 5 mknod /dev/systty c 4 0 mknod /dev/tty c 5 0 mknod /dev/console c 5 1 mknod /dev/ptmx c 5 2 mknod /dev/fb c 29 0 mknod /dev/fb0 c 29 0 mknod /dev/tty0 c 4 0 mknod /dev/tty1 c 4 1 mknod /dev/tty2 c 4 2 mknod /dev/tty3 c 4 3 mknod /dev/tty4 c 4 4 mknod /dev/tty5 c 4 5 mknod /dev/tty6 c 4 6 mknod /dev/tty7 c 4 7 mknod /dev/tty8 c 4 8 mknod /dev/tty9 c 4 9 mknod /dev/tty10 c 4 10 mknod /dev/tty11 c 4 11 mknod /dev/tty12 c 4 12 mknod /dev/ttyS0 c 4 64 mknod /dev/ttyS1 c 4 65 mknod /dev/ttyS2 c 4 66 mknod /dev/ttyS3 c 4 67 daemonize plymouth --show-splash echo Starting splash. nash-if-splash splashy_chvt 8 nash-if-splash splashy boot echo Setting up hotplug. hotplug echo Creating mkblkdevs echo "Loading ext3 module" modprobe -q ext3 echo "Loading modprobe -q crc-t10dif echo "Loading scsi_mod module" modprobe -q scsi_mod echo "Loading sd_mod module" modprobe -q sd_mod echo "Loading libata module" modprobe -q libata echo "Loading sata_nv module" modprobe -q sata_nv echo "Loading pata_acpi module" modprobe -q pata_acpi echo "Loading ide-core module" modprobe -q ide-core echo "Loading ide-disk module" modprobe -q ide-disk echo "Loading ide-pci-generic module" modprobe -q ide-pci-generic echo "Loading ata_generic module" modprobe -q ata_generic echo "Loading pata_amd module" modprobe -q pata_amd echo "Loading ide_generic module" modprobe -q ide_generic echo waiting waitdev --timeout=60000000 mkblkdevs nash-resume echo Creating root device. mkrootdev echo Mounting root filesystem. mount /sysroot echo Setting up other filesystems. setuproot loadpolicy plymouth --newroot=/sysroot echo Switching nash-if-splash switchroot echo Booting has failed. nash-if-splash splashy_update exit nash-if-splash splashy_chvt 1 sleep -1 init =================== you will be able to see the list of modules included and thus loaded at boot, or the commands executed. This is especially useful for people needed specific modules not include automatically in the initrd by mkinitrd : they will be able to check if the right modules are icluded, or the right commands used. On a Mandriva cooker system using ext3 on standard partitions ( no LVM, no software RAID, no encryption ), this give the following output : boot]# lsinitrd /boot/initrd.img ===================================================== root 2461 May 27 16:12 init root 0 May 27 16:12 usr root 0 May 27 16:12 usr/lib root 801164 May 11 08:59 usr/lib/libglib-2.0.so.0.2100.0 root 137824 Dec 18 13:49 usr/lib/libjpeg.so.62.0.0 root 13956 Apr 7 23:11 usr/lib/libbdevid.so.6.0.63 root 27 May 27 16:12 usr/lib/libpng12.so.0 -> /usr/lib/libpng12.so.0.36.0 root 87560 Feb 20 13:31 usr/lib/libelf-0.140.so root 32 May 27 16:12 usr/lib/libglib-2.0.so.0 -> /usr/lib/libglib-2.0.so.0.2100.0 root 21940 Apr 18 09:50 usr/lib/libsplashy.so.1.0.0 root 106308 Apr 7 23:11 usr/lib/libnash.so.6.0.63 root 31 May 27 16:12 usr/lib/libsplashycnf.so.1 -> /usr/lib/libsplashycnf.so.1.0.0 root 534584 Mar 12 17:25 usr/lib/libfreetype.so.6.3.20 root 31 May 27 16:12 usr/lib/libfusion-1.2.so.0 -> /usr/lib/libfusion-1.2.so.0.7.0 root 25 May 27 16:12 usr/lib/liblzo2.so.2 -> /usr/lib/liblzo2.so.2.0.0 root 0 May 27 16:12 usr/lib/directfb-1.2-0 root 0 May 27 16:12 usr/lib/directfb-1.2-0/gfxdrivers root 21948 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_i810.so root 38332 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_mach64.so root 112284 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_nvidia.so root 17820 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_ati128.so root 21848 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_savage.so root 13640 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_sis315.so root 42620 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_cle266.so root 46412 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_nsc.so root 129008 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_radeon.so root 51028 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_unichrome.so root 22112 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_cyber5k.so root 13728 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_neomagic.so root 17852 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_i830.so root 13592 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_tdfx.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/interfaces root 0 May 27 16:12 usr/lib/directfb-1.2-0/interfaces/IDirectFBFont root 13716 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBFont/libidirectfbfont_ft2.so root 9564 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBFont/libidirectfbfont_dgiff.so root 26892 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBFont/libidirectfbfont_default.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/interfaces/IDirectFBVideoProvider root 17816 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBVideoProvider/libidirectfbvideoprovider_v4l.so root 17776 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBVideoProvider/libidirectfbvideoprovider_gif.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider root 13632 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider/libidirectfbimageprovider_gif.so root 13688 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider/libidirectfbimageprovider_png.so root 13676 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider/libidirectfbimageprovider_jpeg.so root 9532 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider/libidirectfbimageprovider_dfiff.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/wm root 38520 Mar 25 19:53 usr/lib/directfb-1.2-0/wm/libdirectfbwm_default.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/systems root 51152 Mar 25 19:53 usr/lib/directfb-1.2-0/systems/libdirectfb_fbdev.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/inputdrivers root 13700 Mar 25 19:53 usr/lib/directfb-1.2-0/inputdrivers/libdirectfb_keyboard.so root 173904 May 8 08:16 usr/lib/libpng12.so.0.36.0 root 38412 Mar 25 19:53 usr/lib/libfusion-1.2.so.0.7.0 root 24 May 27 16:12 usr/lib/libelf.so.1 -> /usr/lib/libelf-0.140.so root 140648 Dec 21 17:40 usr/lib/liblzo2.so.2.0.0 root 529020 Mar 25 19:53 usr/lib/libdirectfb-1.2.so.0.7.0 root 31 May 27 16:12 usr/lib/libdirect-1.2.so.0 -> /usr/lib/libdirect-1.2.so.0.7.0 root 33 May 27 16:12 usr/lib/libdirectfb-1.2.so.0 -> /usr/lib/libdirectfb-1.2.so.0.7.0 root 26 May 27 16:12 usr/lib/libjpeg.so.62 -> /usr/lib/libjpeg.so.62.0.0 root 30 May 27 16:12 usr/lib/libfreetype.so.6 -> /usr/lib/libfreetype.so.6.3.20 root 31 May 27 16:12 usr/lib/libparted-1.8.so.8 -> /usr/lib/libparted-1.8.so.8.0.0 root 28 May 27 16:12 usr/lib/libsplashy.so.1 -> /usr/lib/libsplashy.so.1.0.0 root 9576 Apr 18 09:50 usr/lib/libsplashycnf.so.1.0.0 root 430348 Feb 26 16:49 usr/lib/libparted-1.8.so.8.0.0 root 0 May 27 16:12 usr/lib/suspend root 31292 Mar 27 12:59 usr/lib/suspend/resume root 88232 Mar 25 19:53 usr/lib/libdirect-1.2.so.0.7.0 root 0 May 27 16:12 sys root 0 May 27 16:12 proc root 0 May 27 16:12 firmware root 0 May 27 16:12 bin root 85008 Apr 7 23:11 bin/nash root 13 May 27 16:12 bin/splashy_chvt -> /sbin/splashy root 30748 Feb 5 15:53 bin/modprobe root 5496 Apr 18 09:50 bin/splashy_update root 23 May 27 16:12 bin/resume -> /usr/lib/suspend/resume root 18368 Apr 18 09:50 bin/splashy root 9832 Feb 5 15:53 bin/rmmod root 0 May 27 16:12 dev root 1, 1 May 27 16:12 dev/ram1 root 1, 3 May 27 16:12 dev/null root 4 May 27 16:12 dev/ram -> ram1 root 4, 67 May 27 16:12 dev/ttyS3 root 4, 9 May 27 16:12 dev/tty9 root 4, 6 May 27 16:12 dev/tty6 root 4, 2 May 27 16:12 dev/tty2 root 4, 7 May 27 16:12 dev/tty7 root 5, 1 May 27 16:12 dev/console root 4, 0 May 27 16:12 dev/tty0 root 4, 8 May 27 16:12 dev/tty8 root 4, 11 May 27 16:12 dev/tty11 root 1, 5 May 27 16:12 dev/zero root 1, 0 May 27 16:12 dev/ram0 root 4, 12 May 27 16:12 dev/tty12 root 4, 5 May 27 16:12 dev/tty5 root 4, 64 May 27 16:12 dev/ttyS0 root 4, 1 May 27 16:12 dev/tty1 root 5, 0 May 27 16:12 dev/tty root 4, 66 May 27 16:12 dev/ttyS2 root 4, 65 May 27 16:12 dev/ttyS1 root 5, 2 May 27 16:12 dev/ptmx root 0 May 27 16:12 dev/mapper root 4, 3 May 27 16:12 dev/tty3 root 4, 4 May 27 16:12 dev/tty4 root 4, 0 May 27 16:12 dev/systty root 4, 10 May 27 16:12 dev/tty10 root 0 May 27 16:12 mnt root 0 May 27 16:12 etc root 0 May 27 16:12 etc/blkid root 0 May 27 16:12 etc/ld.so.conf.d root 114 Apr 14 23:00 etc/ld.so.conf.d/standard.conf root 14 Mar 28 15:03 etc/ld.so.conf.d/libarts1.conf root 1817 Mar 27 12:58 etc/suspend.conf root 2207 May 27 16:12 etc/ld.so.cache root 33 Apr 6 21:21 etc/ld.so.conf root 0 May 27 16:12 lib root 19 May 27 16:12 lib/libuuid.so.1 -> /lib/libuuid.so.1.2 root 22 May 27 16:12 lib/libsysfs.so.2 -> /lib/libsysfs.so.2.0.1 root 71380 Apr 6 21:22 lib/libresolv-2.9.so root 9680 Apr 6 21:22 lib/libdl-2.9.so root 16 May 27 16:12 lib/libm.so.6 -> /lib/libm-2.9.so root 149336 Apr 6 21:22 lib/libm-2.9.so root 18 May 27 16:12 lib/libz.so.1 -> /lib/libz.so.1.2.3 root 202056 Jan 15 16:43 lib/libpcre.so.0.0.1 root 21 May 27 16:12 lib/libpcre.so.0 -> /lib/libpcre.so.0.0.1 root 21 May 27 16:12 lib/libpopt.so.0 -> /lib/libpopt.so.0.0.0 root 17960 Feb 9 19:01 lib/libuuid.so.1.2 root 46612 Dec 22 16:43 lib/libsysfs.so.2.0.1 root 44932 Feb 9 19:01 lib/libblkid.so.1.0 root 117752 May 19 12:51 lib/libgcc_s-4.4.0.so.1 root 24 May 27 16:12 lib/libgcc_s.so.1 -> /lib/libgcc_s-4.4.0.so.1 root 20 May 27 16:12 lib/libblkid.so.1 -> /lib/libblkid.so.1.0 root 78152 Dec 16 18:45 lib/libz.so.1.2.3 root 25 May 27 16:12 lib/libmodprobe.so.0 -> /lib/libmodprobe.so.0.0.0 root 21 May 27 16:12 lib/libresolv.so.2 -> /lib/libresolv-2.9.so root 602619 Apr 6 21:15 lib/ld-2.9.so root 90656 Aug 6 2008 lib/libdevmapper.so.1.02 root 22 May 27 16:12 lib/libpthread.so.0 -> /lib/libpthread-2.9.so root 26092 Feb 5 15:53 lib/libmodprobe.so.0.0.0 root 111636 Apr 6 21:21 lib/libpthread-2.9.so root 1376436 Apr 6 21:22 lib/libc-2.9.so root 0 May 27 16:12 lib/modules root 0 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb root 80458 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/scsi_mod.ko.gz root 19356 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/sd_mod.ko.gz root 3941 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.alias.bin root 13270 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/sata_nv.ko.gz root 757 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.dep.bin root 22168 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.symbols.bin root 90624 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/libata.ko.gz root 2790 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/pata_acpi.ko.gz root 43 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.seriomap root 28161 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/jbd.ko.gz root 73 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.ieee1394map root 17149 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.symbols root 1886 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ide-generic.ko.gz root 5741 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.pcimap root 74 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.ofmap root 442 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.dep root 75829 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ext3.ko.gz root 3031 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ata_generic.ko.gz root 4038 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.alias root 1592 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/crc-t10dif.ko.gz root 14930 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ide-gd_mod.ko.gz root 2332 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ide-pci-generic.ko.gz root 189 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.usbmap root 69 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.ccwmap root 81 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.isapnpmap root 141 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.inputmap root 5350 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/pata_amd.ko.gz root 59037 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ide-core.ko.gz root 17 May 27 16:12 lib/libdl.so.2 -> /lib/libdl-2.9.so root 16 May 27 16:12 lib/libc.so.6 -> /lib/libc-2.9.so root 14 May 27 16:12 lib/ld-linux.so.2 -> /lib/ld-2.9.so root 30736 Oct 19 2008 lib/libpopt.so.0.0.0 root 0 May 27 16:12 sysroot root 3 May 27 16:12 sbin -> bin root 0 Apr 21 11:18 etc/splashy root 567 May 27 16:12 etc/splashy/config.xml root 0 Apr 18 09:49 etc/splashy/themes root 0 Apr 23 16:42 etc/splashy/themes/Mandriva-Powerpack-800x600 root 79193 Apr 23 15:19 etc/splashy/themes/Mandriva-Powerpack-800x600/suspend.jpg root 3454 Apr 23 15:19 etc/splashy/themes/Mandriva-Powerpack-800x600/theme.xml root 0 Apr 18 09:49 usr/share/splashy root 0 Apr 18 09:49 usr/share/splashy/themes root 158823 Apr 23 15:19 etc/splashy/themes/Mandriva-Powerpack-800x600/background.jpg ===================================================== -o gid=5,mode=620 /dev/pts /dev/pts initial device nodes --ignore-missing /bin/plymouthd block device nodes. crc-t10dif module" for root device UUID=8141d62a-0254-4405-be04-40b0dcb52cd1 to appear (timeout 1min) --rootdev UUID=8141d62a-0254-4405-be04-40b0dcb52cd1 -t ext3 -o relatime,defaults,data=writeback,ro UUID=8141d62a-0254-4405-be04-40b0dcb52cd1 to new root and running init. splashy_update "chroot /sysroot" =====================================================
2 comment (s)	FACORAT Fabrice

Linux : Listing initrd content with lsinitrd

27/05/2009 19:52:41

The initrd used by most distribution to boot a Linux OS is most of the time a black magic box for most people. Today i've learn a new command from Andrey Borzenkov on the Cooker ML : lsinitrd. This command, from the nash package, allow to list the content of the initrd. For example to list the content of the default initrd used to boot your system, just do the following command as root :
lsinitrd /boot/initrd.img.

With lsinitrd,

 [root@info1 /boot/initrd.img: =================== -rwx------   1 root drwx------   3 root drwx------   4 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root drwx------   7 root drwx------   2 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root drwx------   5 root drwx------   2 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root drwx------   2 root -rw-r--r--   1 root -rw-r--r--   1 root drwx------   2 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root drwx------   2 root -rw-r--r--   1 root drwx------   2 root -rw-r--r--   1 root drwx------   2 root -rw-r--r--   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root drwx------   2 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root drwx------   2 root drwx------   2 root drwx------   2 root drwx------   2 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root drwx------   3 root brw-------   1 root crw-------   1 root lrwxrwxrwx   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root brw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root drwx------   2 root crw-------   1 root crw-------   1 root crw-------   1 root crw-------   1 root drwx------   2 root drwx------   5 root drwx------   2 root drwx------   2 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root drwx------   3 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root -rwxr-xr-x   1 root drwx------   3 root drwx------   2 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-------   1 root -rw-r--r--   1 root -rw-------   1 root -rw-------   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-------   1 root -rw-r--r--   1 root -rw-------   1 root -rw-------   1 root -rw-r--r--   1 root -rw-------   1 root -rw-------   1 root -rw-------   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-------   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-r--r--   1 root -rw-------   1 root -rw-------   1 root -rw-------   1 root -rw-------   1 root -rw-r--r--   1 root -rw-r--r--   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root lrwxrwxrwx   1 root -rwxr-xr-x   1 root drwx------   2 root lrwxrwxrwx   1 root drwxr-xr-x   2 root -rw-r--r--   1 root drwxr-xr-x   8 root drwxr-xr-x   2 root -rw-r--r--   1 root -rw-r--r--   1 root drwxr-xr-x   4 root drwxr-xr-x   8 root -rw-r--r--   4 root =================== #!/bin/nash

mount -t proc /proc /proc setquiet echo Mounting proc filesystem echo Mounting sysfs filesystem mount -t sysfs /sys /sys echo Creating /dev mount -o mode=0755 -t tmpfs /dev /dev mkdir /dev/pts mount -t devpts mkdir /dev/shm mkdir /dev/mapper echo Creating mknod /dev/null c 1 3 mknod /dev/zero c 1 5 mknod /dev/systty c 4 0 mknod /dev/tty c 5 0 mknod /dev/console c 5 1 mknod /dev/ptmx c 5 2 mknod /dev/fb c 29 0 mknod /dev/fb0 c 29 0 mknod /dev/tty0 c 4 0 mknod /dev/tty1 c 4 1 mknod /dev/tty2 c 4 2 mknod /dev/tty3 c 4 3 mknod /dev/tty4 c 4 4 mknod /dev/tty5 c 4 5 mknod /dev/tty6 c 4 6 mknod /dev/tty7 c 4 7 mknod /dev/tty8 c 4 8 mknod /dev/tty9 c 4 9 mknod /dev/tty10 c 4 10 mknod /dev/tty11 c 4 11 mknod /dev/tty12 c 4 12 mknod /dev/ttyS0 c 4 64 mknod /dev/ttyS1 c 4 65 mknod /dev/ttyS2 c 4 66 mknod /dev/ttyS3 c 4 67 daemonize plymouth --show-splash echo Starting splash. nash-if-splash splashy_chvt 8 nash-if-splash splashy boot echo Setting up hotplug. hotplug echo Creating mkblkdevs echo "Loading ext3 module" modprobe -q ext3 echo "Loading modprobe -q crc-t10dif echo "Loading scsi_mod module" modprobe -q scsi_mod echo "Loading sd_mod module" modprobe -q sd_mod echo "Loading libata module" modprobe -q libata echo "Loading sata_nv module" modprobe -q sata_nv echo "Loading pata_acpi module" modprobe -q pata_acpi echo "Loading ide-core module" modprobe -q ide-core echo "Loading ide-disk module" modprobe -q ide-disk echo "Loading ide-pci-generic module" modprobe -q ide-pci-generic echo "Loading ata_generic module" modprobe -q ata_generic echo "Loading pata_amd module" modprobe -q pata_amd echo "Loading ide_generic module" modprobe -q ide_generic echo waiting waitdev --timeout=60000000 mkblkdevs nash-resume echo Creating root device. mkrootdev echo Mounting root filesystem. mount /sysroot echo Setting up other filesystems. setuproot loadpolicy plymouth --newroot=/sysroot echo Switching nash-if-splash switchroot echo Booting has failed. nash-if-splash splashy_update exit nash-if-splash splashy_chvt 1 sleep -1 init ===================

you will be able to see the list of modules included and thus loaded at boot, or the commands executed. This is especially useful for people needed specific modules not include automatically in the initrd by mkinitrd : they will be able to check if the right modules are icluded, or the right commands used. On a Mandriva cooker system using ext3 on standard partitions ( no LVM, no software RAID, no encryption ), this give the following output :
boot]# lsinitrd /boot/initrd.img ===================================================== root 2461 May 27 16:12 init root 0 May 27 16:12 usr root 0 May 27 16:12 usr/lib root 801164 May 11 08:59 usr/lib/libglib-2.0.so.0.2100.0 root 137824 Dec 18 13:49 usr/lib/libjpeg.so.62.0.0 root 13956 Apr 7 23:11 usr/lib/libbdevid.so.6.0.63 root 27 May 27 16:12 usr/lib/libpng12.so.0 -> /usr/lib/libpng12.so.0.36.0 root 87560 Feb 20 13:31 usr/lib/libelf-0.140.so root 32 May 27 16:12 usr/lib/libglib-2.0.so.0 -> /usr/lib/libglib-2.0.so.0.2100.0 root 21940 Apr 18 09:50 usr/lib/libsplashy.so.1.0.0 root 106308 Apr 7 23:11 usr/lib/libnash.so.6.0.63 root 31 May 27 16:12 usr/lib/libsplashycnf.so.1 -> /usr/lib/libsplashycnf.so.1.0.0 root 534584 Mar 12 17:25 usr/lib/libfreetype.so.6.3.20 root 31 May 27 16:12 usr/lib/libfusion-1.2.so.0 -> /usr/lib/libfusion-1.2.so.0.7.0 root 25 May 27 16:12 usr/lib/liblzo2.so.2 -> /usr/lib/liblzo2.so.2.0.0 root 0 May 27 16:12 usr/lib/directfb-1.2-0 root 0 May 27 16:12 usr/lib/directfb-1.2-0/gfxdrivers root 21948 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_i810.so root 38332 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_mach64.so root 112284 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_nvidia.so root 17820 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_ati128.so root 21848 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_savage.so root 13640 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_sis315.so root 42620 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_cle266.so root 46412 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_nsc.so root 129008 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_radeon.so root 51028 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_unichrome.so root 22112 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_cyber5k.so root 13728 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_neomagic.so root 17852 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_i830.so root 13592 Mar 25 19:53 usr/lib/directfb-1.2-0/gfxdrivers/libdirectfb_tdfx.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/interfaces root 0 May 27 16:12 usr/lib/directfb-1.2-0/interfaces/IDirectFBFont root 13716 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBFont/libidirectfbfont_ft2.so root 9564 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBFont/libidirectfbfont_dgiff.so root 26892 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBFont/libidirectfbfont_default.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/interfaces/IDirectFBVideoProvider root 17816 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBVideoProvider/libidirectfbvideoprovider_v4l.so root 17776 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBVideoProvider/libidirectfbvideoprovider_gif.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider root 13632 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider/libidirectfbimageprovider_gif.so root 13688 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider/libidirectfbimageprovider_png.so root 13676 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider/libidirectfbimageprovider_jpeg.so root 9532 Mar 25 19:53 usr/lib/directfb-1.2-0/interfaces/IDirectFBImageProvider/libidirectfbimageprovider_dfiff.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/wm root 38520 Mar 25 19:53 usr/lib/directfb-1.2-0/wm/libdirectfbwm_default.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/systems root 51152 Mar 25 19:53 usr/lib/directfb-1.2-0/systems/libdirectfb_fbdev.so root 0 May 27 16:12 usr/lib/directfb-1.2-0/inputdrivers root 13700 Mar 25 19:53 usr/lib/directfb-1.2-0/inputdrivers/libdirectfb_keyboard.so root 173904 May 8 08:16 usr/lib/libpng12.so.0.36.0 root 38412 Mar 25 19:53 usr/lib/libfusion-1.2.so.0.7.0 root 24 May 27 16:12 usr/lib/libelf.so.1 -> /usr/lib/libelf-0.140.so root 140648 Dec 21 17:40 usr/lib/liblzo2.so.2.0.0 root 529020 Mar 25 19:53 usr/lib/libdirectfb-1.2.so.0.7.0 root 31 May 27 16:12 usr/lib/libdirect-1.2.so.0 -> /usr/lib/libdirect-1.2.so.0.7.0 root 33 May 27 16:12 usr/lib/libdirectfb-1.2.so.0 -> /usr/lib/libdirectfb-1.2.so.0.7.0 root 26 May 27 16:12 usr/lib/libjpeg.so.62 -> /usr/lib/libjpeg.so.62.0.0 root 30 May 27 16:12 usr/lib/libfreetype.so.6 -> /usr/lib/libfreetype.so.6.3.20 root 31 May 27 16:12 usr/lib/libparted-1.8.so.8 -> /usr/lib/libparted-1.8.so.8.0.0 root 28 May 27 16:12 usr/lib/libsplashy.so.1 -> /usr/lib/libsplashy.so.1.0.0 root 9576 Apr 18 09:50 usr/lib/libsplashycnf.so.1.0.0 root 430348 Feb 26 16:49 usr/lib/libparted-1.8.so.8.0.0 root 0 May 27 16:12 usr/lib/suspend root 31292 Mar 27 12:59 usr/lib/suspend/resume root 88232 Mar 25 19:53 usr/lib/libdirect-1.2.so.0.7.0 root 0 May 27 16:12 sys root 0 May 27 16:12 proc root 0 May 27 16:12 firmware root 0 May 27 16:12 bin root 85008 Apr 7 23:11 bin/nash root 13 May 27 16:12 bin/splashy_chvt -> /sbin/splashy root 30748 Feb 5 15:53 bin/modprobe root 5496 Apr 18 09:50 bin/splashy_update root 23 May 27 16:12 bin/resume -> /usr/lib/suspend/resume root 18368 Apr 18 09:50 bin/splashy root 9832 Feb 5 15:53 bin/rmmod root 0 May 27 16:12 dev root 1, 1 May 27 16:12 dev/ram1 root 1, 3 May 27 16:12 dev/null root 4 May 27 16:12 dev/ram -> ram1 root 4, 67 May 27 16:12 dev/ttyS3 root 4, 9 May 27 16:12 dev/tty9 root 4, 6 May 27 16:12 dev/tty6 root 4, 2 May 27 16:12 dev/tty2 root 4, 7 May 27 16:12 dev/tty7 root 5, 1 May 27 16:12 dev/console root 4, 0 May 27 16:12 dev/tty0 root 4, 8 May 27 16:12 dev/tty8 root 4, 11 May 27 16:12 dev/tty11 root 1, 5 May 27 16:12 dev/zero root 1, 0 May 27 16:12 dev/ram0 root 4, 12 May 27 16:12 dev/tty12 root 4, 5 May 27 16:12 dev/tty5 root 4, 64 May 27 16:12 dev/ttyS0 root 4, 1 May 27 16:12 dev/tty1 root 5, 0 May 27 16:12 dev/tty root 4, 66 May 27 16:12 dev/ttyS2 root 4, 65 May 27 16:12 dev/ttyS1 root 5, 2 May 27 16:12 dev/ptmx root 0 May 27 16:12 dev/mapper root 4, 3 May 27 16:12 dev/tty3 root 4, 4 May 27 16:12 dev/tty4 root 4, 0 May 27 16:12 dev/systty root 4, 10 May 27 16:12 dev/tty10 root 0 May 27 16:12 mnt root 0 May 27 16:12 etc root 0 May 27 16:12 etc/blkid root 0 May 27 16:12 etc/ld.so.conf.d root 114 Apr 14 23:00 etc/ld.so.conf.d/standard.conf root 14 Mar 28 15:03 etc/ld.so.conf.d/libarts1.conf root 1817 Mar 27 12:58 etc/suspend.conf root 2207 May 27 16:12 etc/ld.so.cache root 33 Apr 6 21:21 etc/ld.so.conf root 0 May 27 16:12 lib root 19 May 27 16:12 lib/libuuid.so.1 -> /lib/libuuid.so.1.2 root 22 May 27 16:12 lib/libsysfs.so.2 -> /lib/libsysfs.so.2.0.1 root 71380 Apr 6 21:22 lib/libresolv-2.9.so root 9680 Apr 6 21:22 lib/libdl-2.9.so root 16 May 27 16:12 lib/libm.so.6 -> /lib/libm-2.9.so root 149336 Apr 6 21:22 lib/libm-2.9.so root 18 May 27 16:12 lib/libz.so.1 -> /lib/libz.so.1.2.3 root 202056 Jan 15 16:43 lib/libpcre.so.0.0.1 root 21 May 27 16:12 lib/libpcre.so.0 -> /lib/libpcre.so.0.0.1 root 21 May 27 16:12 lib/libpopt.so.0 -> /lib/libpopt.so.0.0.0 root 17960 Feb 9 19:01 lib/libuuid.so.1.2 root 46612 Dec 22 16:43 lib/libsysfs.so.2.0.1 root 44932 Feb 9 19:01 lib/libblkid.so.1.0 root 117752 May 19 12:51 lib/libgcc_s-4.4.0.so.1 root 24 May 27 16:12 lib/libgcc_s.so.1 -> /lib/libgcc_s-4.4.0.so.1 root 20 May 27 16:12 lib/libblkid.so.1 -> /lib/libblkid.so.1.0 root 78152 Dec 16 18:45 lib/libz.so.1.2.3 root 25 May 27 16:12 lib/libmodprobe.so.0 -> /lib/libmodprobe.so.0.0.0 root 21 May 27 16:12 lib/libresolv.so.2 -> /lib/libresolv-2.9.so root 602619 Apr 6 21:15 lib/ld-2.9.so root 90656 Aug 6 2008 lib/libdevmapper.so.1.02 root 22 May 27 16:12 lib/libpthread.so.0 -> /lib/libpthread-2.9.so root 26092 Feb 5 15:53 lib/libmodprobe.so.0.0.0 root 111636 Apr 6 21:21 lib/libpthread-2.9.so root 1376436 Apr 6 21:22 lib/libc-2.9.so root 0 May 27 16:12 lib/modules root 0 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb root 80458 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/scsi_mod.ko.gz root 19356 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/sd_mod.ko.gz root 3941 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.alias.bin root 13270 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/sata_nv.ko.gz root 757 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.dep.bin root 22168 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.symbols.bin root 90624 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/libata.ko.gz root 2790 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/pata_acpi.ko.gz root 43 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.seriomap root 28161 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/jbd.ko.gz root 73 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.ieee1394map root 17149 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.symbols root 1886 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ide-generic.ko.gz root 5741 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.pcimap root 74 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.ofmap root 442 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.dep root 75829 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ext3.ko.gz root 3031 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ata_generic.ko.gz root 4038 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.alias root 1592 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/crc-t10dif.ko.gz root 14930 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ide-gd_mod.ko.gz root 2332 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ide-pci-generic.ko.gz root 189 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.usbmap root 69 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.ccwmap root 81 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.isapnpmap root 141 May 27 16:12 lib/modules/2.6.30-desktop-0.rc7.1mnb/modules.inputmap root 5350 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/pata_amd.ko.gz root 59037 May 26 03:16 lib/modules/2.6.30-desktop-0.rc7.1mnb/ide-core.ko.gz root 17 May 27 16:12 lib/libdl.so.2 -> /lib/libdl-2.9.so root 16 May 27 16:12 lib/libc.so.6 -> /lib/libc-2.9.so root 14 May 27 16:12 lib/ld-linux.so.2 -> /lib/ld-2.9.so root 30736 Oct 19 2008 lib/libpopt.so.0.0.0 root 0 May 27 16:12 sysroot root 3 May 27 16:12 sbin -> bin root 0 Apr 21 11:18 etc/splashy root 567 May 27 16:12 etc/splashy/config.xml root 0 Apr 18 09:49 etc/splashy/themes root 0 Apr 23 16:42 etc/splashy/themes/Mandriva-Powerpack-800x600 root 79193 Apr 23 15:19 etc/splashy/themes/Mandriva-Powerpack-800x600/suspend.jpg root 3454 Apr 23 15:19 etc/splashy/themes/Mandriva-Powerpack-800x600/theme.xml root 0 Apr 18 09:49 usr/share/splashy root 0 Apr 18 09:49 usr/share/splashy/themes root 158823 Apr 23 15:19 etc/splashy/themes/Mandriva-Powerpack-800x600/background.jpg ===================================================== -o gid=5,mode=620 /dev/pts /dev/pts initial device nodes --ignore-missing /bin/plymouthd block device nodes. crc-t10dif module" for root device UUID=8141d62a-0254-4405-be04-40b0dcb52cd1 to appear (timeout 1min) --rootdev UUID=8141d62a-0254-4405-be04-40b0dcb52cd1 -t ext3 -o relatime,defaults,data=writeback,ro UUID=8141d62a-0254-4405-be04-40b0dcb52cd1 to new root and running init. splashy_update "chroot /sysroot" =====================================================

2 comment (s)

FACORAT Fabrice

Linux : Rant of the day : crappy new Gnome pulseaudio mixer	14/05/2009 00:59:18
I was just willing to make a gracious rant, so here it is : new gnome mixer based on pulseaudio is so crap that I can't believe they dare to release this and put it in a stable gnome release ! Sorry Colin, sorry pulseaudio dev ( Lennart ), but your new mixer is just utterly broken. Reinout van Schouwen or Adam already talk about it, but I will take the time to talk about this again, because I'm in trouble to fix 64 workstations running GNOME 2.26 on Mandriva 2009.1. Indeed, this week end, I've upgrade all the workstation at my call center to Mandriva 2009.1 Spring. The upgrade using Mandriva autoinstaller feature was smooth and easy : it was a pleasure. Now comes the hard part ... It seems that by default the Front control is muted, so you end up with no sound. You must admit that a call center without sounds, notably for the supervisor who need to listen to the call records, it's a very bad thing. So what can I do ? Pulseaudio mixer don't let adjust the volume for each of the sound card elements. So I end up installing gnome-alsamixer package or using aumix to fix the volume control. Unfortunately, at each reboot/logout, pulseaudio seems to reset the settings back, and so I end up without sound. As the gnome-volume-control applet is no longer shipped, I have really a problem. So dear lazy web, how can I fix this on the pulseaudio front ? Now I'm just willing to give an advice to pulseaudio dev : I do agree when you want to simplify user life by providing more simpler UI. However you should also never forget that the rule one size fit all doesn't exists. So you need to provide a way for users to provide customs settings. By the way, If no others OS like Windows or even more Mac OS X provide a so simplified UI for the volume control, there's must have a reason. This was my useless rant of the day, but you may understand that this piss me off as now I have 64 angry users who have to manually restore the volume control each time.
3 comment (s)	FACORAT Fabrice

Linux : Rant of the day : crappy new Gnome pulseaudio mixer

14/05/2009 00:59:18

I was just willing to make a gracious rant, so here it is : new gnome mixer based on pulseaudio is so crap that I can't believe they dare to release this and put it in a stable gnome release ! Sorry Colin, sorry pulseaudio dev ( Lennart ), but your new mixer is just utterly broken. Reinout van Schouwen or Adam already talk about it, but I will take the time to talk about this again, because I'm in trouble to fix 64 workstations running GNOME 2.26 on Mandriva 2009.1. Indeed, this week end, I've upgrade all the workstation at my call center to Mandriva 2009.1 Spring. The upgrade using Mandriva autoinstaller feature was smooth and easy : it was a pleasure. Now comes the hard part ... It seems that by default the Front control is muted, so you end up with no sound. You must admit that a call center without sounds, notably for the supervisor who need to listen to the call records, it's a very bad thing. So what can I do ? Pulseaudio mixer don't let adjust the volume for each of the sound card elements. So I end up installing gnome-alsamixer package or using aumix to fix the volume control. Unfortunately, at each reboot/logout, pulseaudio seems to reset the settings back, and so I end up without sound. As the gnome-volume-control applet is no longer shipped, I have really a problem. So dear lazy web, how can I fix this on the pulseaudio front ?

Now I'm just willing to give an advice to pulseaudio dev : I do agree when you want to simplify user life by providing more simpler UI. However you should also never forget that the rule one size fit all doesn't exists. So you need to provide a way for users to provide customs settings. By the way, If no others OS like Windows or even more Mac OS X provide a so simplified UI for the volume control, there's must have a reason.

This was my useless rant of the day, but you may understand that this piss me off as now I have 64 angry users who have to manually restore the volume control each time.

3 comment (s)

FACORAT Fabrice

Blog

HOWTO

FAQ

Recherche