Re: [Mageia-dev] Preparing Alpha 1 isos of Mageia2
On Sat, Dec 3, 2011 at 8:06 AM, Kamil Rytarowski wrote: > W dniu 23.11.2011 22:30, Philippe Makowski pisze: > >> Pascal Terjan a écrit : >> >>> On Wed, Nov 23, 2011 at 15:34, philippe makowski >>> wrote: 2011/11/23 Funda Wang: > > The problem is, why we are shipping a dead package? Dead ? https://bitbucket.org/troorl/pino3/ not sure it is dead >>> It is dead as in "build errors reported 1 year ago have not been fixed >> >> Ok dead or nearly, no package maintainer, certainly alternatives (I don't >> know) so we can drop it >> >> > pino is moved to obsoletes in our svn > > Please remove it from mirrors Done now!
[Mageia-dev] New Kernel doesn't boot on virtualbox
New Kernel doesn't boot on virtualbox because of modprob error. This may already be know otherwise I can provide details -- Thomas
Re: [Mageia-dev] Enable kernel log timestamps?
On Sat, 03 Dec 2011 20:26:24 +0200, Thomas Backlund wrote about Re: [Mageia-dev] Enable kernel log timestamps?: >I'm not sure I like to enable it by default as it also makes it a pain >to compare 2 dmesgs as you cant do a simple diff anymore. Not that painful, sending the dmesg and dmesg.old through |cut... Ciao, =Dick Gevers=
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release courier-authlib-0.63.0-9.mga2
On 03/12/11 10:21, Barry Jackson wrote: On 03/12/11 08:37, Jani Välimaa wrote: 2011/12/3 Barry Jackson: On 28/11/11 14:39, Guillaume Rousse wrote: Le 28/11/2011 14:46, Mageia Team a écrit : barjac 0.63.0-9.mga2: + Revision: 173752 - Added ldconfig in %post and %postun This is supposed to be done automatically by file triggers... Yes - I was only reading something about that yesterday, however after installation of courier-authlib prior to the addition of ldconfig in %post and %postun, courier-imap would not build as it could not find a lib installed by courier-authlib. Can't reproduce your "bug" with up-to-date Cauldron chroots. Tried both i586 and x86_64. Removed %post and %postun scripts, rebuild courier-authlib and build courier-imap with new courier-authlib and all went just fine. Very strange. This was also confirmed by shlomif who hit the same errors prior to the addition of ldconfig. Maybe something else fixed this in the meantime. I will re-test in a new clean fully updated installation. I agree. I have tested several times. I have removed the scripts in courier-authlib in svn and bumped the release of courier-authlib and courier-imap, to force it to re-build as a final check. I wish I knew what fixed this issue. Thanks, Barry
Re: [Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.
Le samedi 3 décembre 2011 00:06:31, Anssi Hannula a écrit : > BTW, shouldn't we regenerate initrds when installing radeon-firmware for > the first time? Yes : I had this problem testing Alpha1 DVD on a RV100 hardware. - no firmware installed as nonfree repo is not enabled - no X after install (I should have tested in the installer?) - installed radeon firmware, reboot, still no X - updated initrd, then it works
Re: [Mageia-dev] Enable kernel log timestamps?
03.12.2011 20:26, Thomas Backlund skrev: 03.12.2011 18:22, Anssi Hannula skrev: Hi! I propose to we configure our kernel to emit timestamps in kernel messages. + This allows quickly seeing the timing of kernel messages when using the "dmesg" command. + Allows to quickly see which msgs come from kernel when other processes (like systemd) inject messages there. + Others are doing it AFAIK. - Causes longer log lines I'm not sure I like to enable it by default as it also makes it a pain to compare 2 dmesgs as you cant do a simple diff anymore. Whats more, it can be enabled dynamically when really needed by adding "printk.time=1" to the kernel command line. I used to have it enabled in kernel-tmb during (sigh, pressed send by mistake) I used to have it enabled in kernel-tmb during some debugging, but disabled it again when I remembered it can be enabled dynamically. -- Thomas
Re: [Mageia-dev] Enable kernel log timestamps?
03.12.2011 18:22, Anssi Hannula skrev: Hi! I propose to we configure our kernel to emit timestamps in kernel messages. + This allows quickly seeing the timing of kernel messages when using the "dmesg" command. + Allows to quickly see which msgs come from kernel when other processes (like systemd) inject messages there. + Others are doing it AFAIK. - Causes longer log lines I'm not sure I like to enable it by default as it also makes it a pain to compare 2 dmesgs as you cant do a simple diff anymore. Whats more, it can be enabled dynamically when really needed by adding "printk.time=1" to the kernel command line. I used to have it enabled in kernel-tmb during
Re: [Mageia-dev] Enable kernel log timestamps?
On 03/12/11 16:41, Dick Gevers wrote: On Sat, 03 Dec 2011 18:22:26 +0200, Anssi Hannula wrote about [Mageia-dev] Enable kernel log timestamps?: Hi! I propose to we configure our kernel to emit timestamps in kernel messages. Please! Like (some) tmb kernels did/do. Tks+ =Dick Gevers= This is a good idea +1
Re: [Mageia-dev] Enable kernel log timestamps?
On Sat, 03 Dec 2011 18:22:26 +0200, Anssi Hannula wrote about [Mageia-dev] Enable kernel log timestamps?: >Hi! > >I propose to we configure our kernel to emit timestamps in kernel messages. Please! Like (some) tmb kernels did/do. Tks+ =Dick Gevers=
[Mageia-dev] Enable kernel log timestamps?
Hi! I propose to we configure our kernel to emit timestamps in kernel messages. + This allows quickly seeing the timing of kernel messages when using the "dmesg" command. + Allows to quickly see which msgs come from kernel when other processes (like systemd) inject messages there. + Others are doing it AFAIK. - Causes longer log lines Patch attached. -- Anssi Hannula Index: configs/x86_64.config === --- configs/x86_64.config (revision 175581) +++ configs/x86_64.config (working copy) @@ -5215,7 +5215,7 @@ # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y -# CONFIG_PRINTK_TIME is not set +CONFIG_PRINTK_TIME=y CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4 CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_ENABLE_MUST_CHECK=y Index: configs/arm.config === --- configs/arm.config (revision 175581) +++ configs/arm.config (working copy) @@ -3967,7 +3967,7 @@ # # Kernel hacking # -# CONFIG_PRINTK_TIME is not set +CONFIG_PRINTK_TIME=y CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4 CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_ENABLE_MUST_CHECK=y Index: configs/i386.config === --- configs/i386.config (revision 175581) +++ configs/i386.config (working copy) @@ -5567,7 +5567,7 @@ # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y -# CONFIG_PRINTK_TIME is not set +CONFIG_PRINTK_TIME=y CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4 CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_ENABLE_MUST_CHECK=y
Re: [Mageia-dev] Dolphin toolbar default settings in mga2 alpha
On 2 December 2011 22:42, Barry Jackson wrote: > On 02/12/11 16:41, Balcaen John wrote: >> >> Le vendredi 2 décembre 2011 14:56:45 Barry Jackson a écrit : >>> >>> Anyone else find the default settings in Dolphin after a clean Alpha1 >>> installation utterly useless? >>> It's not even possible to easily navigate a file system without UP and >>> BACK buttons. >>> For new users I think the toolbar should have all the regularly needed >>> buttons in place "out of the box". >>> I tried to figure out where these are stored and in which package, but >>> after half an hour I gave up :\ >> >> If i'm not wrong there's some changes regarding dolphin's configuration, >> it was >> already reported to me last week. >> >> I'll be able to work again on kde's configuration soon (i was quite buzy) >> > > Good that's excellent. > > May I suggest a basic default toolbar? > > HOME,BACK,FORWARDS,UP,RELOAD,FIND,SPLIT,Show Hidden Files I would add PREVIEW to that list. > > I see no reason to add anything that is in the context menu. > > Also:- > May I suggest that the icon view is NOT the default and that the details > view be made default. I really can't imagine that anyone who uses dolphin > for anything serious would use the icon view, as long filenames get > truncated. It gets quite tedious changing it for both root and normal user > on each fresh installation. Also, having details view, can we enable the little drop down arrows by default too. For icon mode, changing from 2 lines for the filename to 1 would be nice too. > > Just my 2 cents ;) > > Barry Addig the information panal back would be good as well. I may have got a little carried away here...
Re: [Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.
On 03.12.2011 08:05, Thomas Backlund wrote: > Anssi Hannula skrev 3.12.2011 01:06: >> On 03.12.2011 00:18, Thomas Backlund wrote: >>> Anssi Hannula skrev 2.12.2011 23:17: Patch attached. I guess this would remain as a Mageia specific patch as the wanted behavior is dependant on how the distribution handles driver switching etc... >>> >>> Speaking of driver switching... >>> >>> Is it possible to detect missing radeon firmware in initrd in early >>> boot, and then switch to loading radeon with modeset=0 ? >> >> Seems doable (if a bit hacky), but unfortunately new radeon cards (at >> least cayman/northern islands) do not work without KMS at all (while >> slightly older cards like Evergreen mostly work but without any kind of >> 2d/3d acceleration). >> > > Yeah, I started thinking about those too after my post... > >> This also means that X server will fail to start since it doesn't >> fallback to autodetection (and therefore vesa) when the card is >> explicitely listed in xorg.conf. >> >> Not quite sure what is the best way forward. >> > > Hm, so we would need a split in detection for nonkms capable cards > and the rest... > > or take the easy way out and boot everyone on vesa until radeon firmware > is available... Does loading of radeon modesetting kernel driver without firmware break the boot completely, or does it just make X.org server fail to start? >> BTW, shouldn't we regenerate initrds when installing radeon-firmware for >> the first time? >> > > Yeah, I've been thinking the same, but haven't gotten around to doing it > yet. > > and what about nvidia* and fglrx, should they do the same ? Well, currently we always include the KMS drivers in initrd, and when nvidia* or fglrx is enabled we simply add nokmsboot (mga/mdv specific) kernel parameter to avoid initrd rebuild. > and for a dkms related issue, I've also been thinking we whould > trigger dkms rebuild on kernel install to save time on next bootup. That would seem reasonable, it would just be a matter of [ -x /usr/sbin/dkms_autoinstaller ] && \ /usr/sbin/dkms_autoinstaller start %kernelver || : in kernel %post AFAICS... -- Anssi Hannula
Re: [Mageia-dev] Replacing mysql with mariadb
Update: I built a test package of ZoneMinder git master against MariaDB. This version supports my mjpeg USB webcam, so I have been able to test the full functionality. No problems :)
Re: [Mageia-dev] Help on a particular spec pkg (perl)
YES! Thanks :) -Original Message- From: Funda Wang Sender: mageia-dev-boun...@mageia.org Date: Sat, 3 Dec 2011 21:05:35 To: Mageia development mailing-list Reply-To: Mageia development mailing-list Subject: Re: [Mageia-dev] Help on a particular spec pkg (perl) make: *** No rule to make target `/usr/lib/perl5/5.14.2/x86_64-linux-thread-multi/CORE/EXTERN.h', needed by `Tools.o'. Stop. You should add perl-devel into buildRequires. 2011/12/3 Sandro CAZZANIGA : > Hi there! > > I've made a complicated perl pkg today (instead of sepc file that's very > simple). I've got a build error and I'm mailing here for help :) > > In PJ, the spec file and the error here: > http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20111203113946.kharec.valstar.31298/log/perl-Search-Tools-0.650.0-1.mga2/build.0.20111203114002.log > > Maybe a missing BR? Thanks :)
Re: [Mageia-dev] Help on a particular spec pkg (perl)
make: *** No rule to make target `/usr/lib/perl5/5.14.2/x86_64-linux-thread-multi/CORE/EXTERN.h', needed by `Tools.o'. Stop. You should add perl-devel into buildRequires. 2011/12/3 Sandro CAZZANIGA : > Hi there! > > I've made a complicated perl pkg today (instead of sepc file that's very > simple). I've got a build error and I'm mailing here for help :) > > In PJ, the spec file and the error here: > http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20111203113946.kharec.valstar.31298/log/perl-Search-Tools-0.650.0-1.mga2/build.0.20111203114002.log > > Maybe a missing BR? Thanks :)
[Mageia-dev] Help on a particular spec pkg (perl)
Hi there!
I've made a complicated perl pkg today (instead of sepc file that's very
simple). I've got a build error and I'm mailing here for help :)
In PJ, the spec file and the error here:
http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20111203113946.kharec.valstar.31298/log/perl-Search-Tools-0.650.0-1.mga2/build.0.20111203114002.log
Maybe a missing BR? Thanks :)
%define upstream_nameSearch-Tools
%define upstream_version 0.65
Name: perl-%{upstream_name}
Version:%perl_convert_version %{upstream_version}
Release:%mkrel 1
Summary:High-performance tools for building search applications
License:GPL+ or Artistic
Group: Development/Perl
Url:http://search.cpan.org/dist/%{upstream_name}
Source0:http://cpan.metacpan.org/authors/id/K/KA/KARMAN/%{upstream_name}-%{upstream_version}.tar.gz
BuildRequires: perl(Data::Dump)
BuildRequires: perl(Encode)
BuildRequires: perl(Encoding::FixLatin)
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(File::Slurp)
BuildRequires: perl(Rose::ObjectX::CAF)
BuildRequires: perl(Search::Query)
BuildRequires: perl(Test::More)
BuildArch: noarch
%description
This distribution is a set of utilities for building search applications. Rather than adhering to a particular search application or framework, the goal of Search::Tools is to provide general-purpose methods for common search application features. Think of Search::Tools like a toolbox rather than a hammer.
%prep
%setup -q -n %{upstream_name}-%{upstream_version}
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
%make
%check
%make test
%install
%makeinstall_std
%files
%doc META.yml Changes README MANIFEST
/usr/src/debug/*
%{_libdir}/debug/.build-id/*
%{_libdir}/debug/*
%{_mandir}/man3/*
%perl_vendorlib/*
Re: [Mageia-dev] Unable to boot into kernel-3.1.3
'Twas brillig, and Colin Guthrie at 02/12/11 12:15 did gyre and gimble: > 'Twas brillig, and Kira at 02/12/11 11:24 did gyre and gimble: >> 在 Fri, 02 Dec 2011 18:44:32 +0800, Colin Guthrie >> 寫道: >>> Actually I didn't really need it in the end, I should have spotted the >>> problem without it, but it did make me go through the motions. >>> >>> It was a simple variable name typo. >>> >>> I've submitted a new version, please wait for dracut-013-5.mga2 and >>> regenerate, test, yada, yada, and let me know how you get on. >>> >>> Col >>> >> No, it didn't work. > > Well it kinda worked - at least it's actually trying to mount /usr now! > >> Error message: device node not found >> >> dracut Warning: e2fsck returned with 16 >> dracut Warning: *** An error occurred during the file system check. >> dracut Warning: *** Dropping yo to a shell: the system will try >> dracut Warning: *** to mount the filesystem(s), when you leave the shell > > > OK, so according to man e2fsck exit code 16 is "Usage or syntax error" > > I think this is due to using UUID=. > > I'll work on a fix for the next round of testing :D OK, hopefully 013-6.mga2 will work for you! Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.
'Twas brillig, and Anssi Hannula at 02/12/11 21:17 did gyre and gimble: > On 02.12.2011 15:57, Anssi Hannula wrote: >> On 02.12.2011 13:28, Colin Guthrie wrote: >>> Hi, >>> >>> Just a suggestion! Should we move wholesale to dracut? >>> >>> It's very easy to hack on, and Harald Hoyer has been very helpful and >>> has merged some of the patches we carried locally (which I mostly copied >>> from Mandriva). Not sure why they were not upstreamed before. >>> >>> There are still a couple patches we carry locally (soon to be less when >>> Harald pushes his git repo and I rebase), but they are pretty trivial, >>> understandable and easily maintainable (mostly they will be stylistic >>> tweaks and naming variations - i.e. very minor). >>> >>> Modprobe rules are included even in the initrd so tweaks there follow >>> through. >>> >>> I'm not necessarily against keeping mkinitrd, but I think we should take >>> the time from now until the beta phase to obsolte mkinitrd and force >>> everyone to use dracut in order to see if there are any issues and then >>> make the call before next beta or rc. >> >> +1 >> >> One thing that doesn't work with dracut yet is that it only includes the >> KMS drivers into initramfs if they are loaded at the time of initramfs >> creation, causing unoptimal boot screen when a) initramfs created by the >> installer (I guess), and when b) user has switched a driver non-kms -> kms. >> >> This can probably be solved by some patching of >> modules.d/50plymouth/module-setup.sh, but I haven't looked at it closely >> yet. > > Patch attached. I guess this would remain as a Mageia specific patch as > the wanted behavior is dependant on how the distribution handles driver > switching etc... > > Shall I apply it? I just updated dracut with another patch, so I included this one too. I know there is ongoing discussions about firmwares etc. but I think this patch still stands alone. I'll discuss with Harald if there is a way to upstream this in a semi generic way. If not, we just carry it as a local patch. Thanks Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release courier-authlib-0.63.0-9.mga2
On 03/12/11 08:37, Jani Välimaa wrote: 2011/12/3 Barry Jackson: On 28/11/11 14:39, Guillaume Rousse wrote: Le 28/11/2011 14:46, Mageia Team a écrit : barjac 0.63.0-9.mga2: + Revision: 173752 - Added ldconfig in %post and %postun This is supposed to be done automatically by file triggers... Yes - I was only reading something about that yesterday, however after installation of courier-authlib prior to the addition of ldconfig in %post and %postun, courier-imap would not build as it could not find a lib installed by courier-authlib. Can't reproduce your "bug" with up-to-date Cauldron chroots. Tried both i586 and x86_64. Removed %post and %postun scripts, rebuild courier-authlib and build courier-imap with new courier-authlib and all went just fine. Very strange. This was also confirmed by shlomif who hit the same errors prior to the addition of ldconfig. Maybe something else fixed this in the meantime. I will re-test in a new clean fully updated installation.
Re: [Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.
'Twas brillig, and David W. Hodgins at 03/12/11 09:21 did gyre and gimble:
> On Sat, 03 Dec 2011 01:05:31 -0500, Thomas Backlund wrote:
>
> Fyi. On one of my cauldron installs, I have /usr in a lvm
> logical volume. In order to get this to be bootable, I
> modified /etc/dracut.conf to have
> add_drivers+="dm_mod dm_crypt"
> and
> install_items+=(/bin/grep /lib/libpcre.so.0.0.1 /lib/libpcre.so.0
> /lib/libdevmapper-event.so.1.02 /lib/libdevmapper.so.1.02
> /lib/libreadline.so.6 /lib/libncurses.so.5 /sbin/lvm
> /lib/modules/3.1.4-server-1.mga2/kernel/drivers/md/dm-crypt.ko.gz
> /lib/modules/3.1.4-server-1.mga2/kernel/drivers/md/dm-mod.ko.gz
> /sbin/dmsetup /sbin/lsmod )
>
> I modified /usr/share/dracut/modules.d/98usrmount/mount-usr.sh to have ...
> #!/bin/sh
> # -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*-
> # ex: ts=8 sw=4 sts=4 et filetype=sh
>
> type info >/dev/null 2>&1 || . /lib/dracut-lib.sh
> type fsck_single >/dev/null 2>&1 || . /lib/fs-lib.sh
>
> mount_usr()
> {
> local _dev _mp _fs _opts _rest _fs_found _ret _mount_point
> if ! __fgrep "device-mapper" /proc/devices >/dev/null 2>&1 ; then
>modprobe dm-mod >/dev/null 2>&1
> fi
> /sbin/lvm vgchange -a y --sysinit
> fsck_mount()
> (
> # check, if we have to mount the filesystem
> _fs_found=""
> while read _dev _mp _fs _opts _rest; do
> if [ "$_mp" = "/$_mount_point" ]; then
> echo "$_dev $NEWROOT/$_mp $_fs ${_opts} $_rest"
> _fs_found="1"
> break
> fi
> done < "$NEWROOT/etc/fstab" >> /etc/fstab
> if [ "x$_fs_found" != "x" ]; then
> # we have to mount it
> fsck_single "$_dev" "$_fs"
> _ret=$?
> echo $_ret >/run/initramfs/$_mount_point-fsck
> if [ $_ret -ne 255 ]; then
> info "Mounting /$_mount_point"
> mount "$NEWROOT/$_mount_point" 2>&1 | vinfo
> fi
> fi
> )
> _mount_point="usr"; fsck_mount
> _mount_point="var"; fsck_mount
> _mount_point="var/mnt"; fsck_mount
> _mount_point="opt"; fsck_mount
> _mount_point="tmp"; fsck_mount
> _mount_point="home"; fsck_mount
> }
>
> mount_usr
>
> I initially only had the /usr being mounted, but found that when it
> got around to trying to mount the next lv, it would report that the
> mount timed out due to a dependency failure, but with no indication
> of why. I ended up modifying the script to mount all of my lvm
> partitions, in the initramfs, to get it to work.
Cheers Dave. I'll speak to Harald to see how best to handle this in a
more official way.
Col
--
Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/
Day Job:
Tribalogic Limited http://www.tribalogic.net/
Open Source:
Mageia Contributor http://www.mageia.org/
PulseAudio Hacker http://www.pulseaudio.org/
Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release shorewall-4.4.23.1-2.mga2
On Sat, 3 Dec 2011 01:07:15 +0100 (CET), Mageia Team wrote about [changelog] [RPM] cauldron core/release shorewall-4.4.23.1-2.mga2: >blino 4.4.23.1-2.mga2: >+ Revision: 175272 >- do not try to add LAST LINE comments anymore in config files: Cher Olivier, Shorewall6 (and maybe shorewall) leaves 'LAST LINE' lines in some config files: at least in params. HTH Best regards, =Dick Gevers=
Re: [Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.
On Sat, 03 Dec 2011 01:05:31 -0500, Thomas Backlund wrote:
Fyi. On one of my cauldron installs, I have /usr in a lvm
logical volume. In order to get this to be bootable, I
modified /etc/dracut.conf to have
add_drivers+="dm_mod dm_crypt"
and
install_items+=(/bin/grep /lib/libpcre.so.0.0.1 /lib/libpcre.so.0
/lib/libdevmapper-event.so.1.02 /lib/libdevmapper.so.1.02 /lib/libreadline.so.6
/lib/libncurses.so.5 /sbin/lvm
/lib/modules/3.1.4-server-1.mga2/kernel/drivers/md/dm-crypt.ko.gz
/lib/modules/3.1.4-server-1.mga2/kernel/drivers/md/dm-mod.ko.gz /sbin/dmsetup
/sbin/lsmod )
I modified /usr/share/dracut/modules.d/98usrmount/mount-usr.sh to have ...
#!/bin/sh
# -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*-
# ex: ts=8 sw=4 sts=4 et filetype=sh
type info >/dev/null 2>&1 || . /lib/dracut-lib.sh
type fsck_single >/dev/null 2>&1 || . /lib/fs-lib.sh
mount_usr()
{
local _dev _mp _fs _opts _rest _fs_found _ret _mount_point
if ! __fgrep "device-mapper" /proc/devices >/dev/null 2>&1 ; then
modprobe dm-mod >/dev/null 2>&1
fi
/sbin/lvm vgchange -a y --sysinit
fsck_mount()
(
# check, if we have to mount the filesystem
_fs_found=""
while read _dev _mp _fs _opts _rest; do
if [ "$_mp" = "/$_mount_point" ]; then
echo "$_dev $NEWROOT/$_mp $_fs ${_opts} $_rest"
_fs_found="1"
break
fi
done < "$NEWROOT/etc/fstab" >> /etc/fstab
if [ "x$_fs_found" != "x" ]; then
# we have to mount it
fsck_single "$_dev" "$_fs"
_ret=$?
echo $_ret >/run/initramfs/$_mount_point-fsck
if [ $_ret -ne 255 ]; then
info "Mounting /$_mount_point"
mount "$NEWROOT/$_mount_point" 2>&1 | vinfo
fi
fi
)
_mount_point="usr"; fsck_mount
_mount_point="var"; fsck_mount
_mount_point="var/mnt"; fsck_mount
_mount_point="opt"; fsck_mount
_mount_point="tmp"; fsck_mount
_mount_point="home"; fsck_mount
}
mount_usr
I initially only had the /usr being mounted, but found that when it
got around to trying to mount the next lv, it would report that the
mount timed out due to a dependency failure, but with no indication
of why. I ended up modifying the script to mount all of my lvm
partitions, in the initramfs, to get it to work.
Regards, Dave Hodgins
Re: [Mageia-dev] Pino
2011/12/3 Sebastian : > Pino may be dead or dieing, but it is still a very popular client for > Identi.ca. I find it a very good client, as a result I strongly believe > > that it should definitely stay in the repos for Mageia 2. > > If Pino is no longer made I think it would be good for many distros > to > still provide it in their repos for at least another year > > Also looking at things from a user point of view, I think that many > > computer users don't mind using old software that is no longer > maintained as long as they can still use it for it's intended > purpose. I think that for myself and > many other people that use Identi.ca Pino is an example of this. > > Unfortunately at the moment though in my install of Mageia 2 Alpha 1 with > the latest updates, I can't install Pino using RPMdrake, because: > > Sorry, the following package cannot be selected: > > - pino-0.2.11-1.mga1.i586 (due to unsatisfied libnotify.so.1) > The problem in this case is: pino isn't working anymore with the newer libraries included in Mageia. It can't be built against those libraries and with no upstream to fix that, one of our packagers would have to take over the de facto development. Also there are alternatives in the repo, aren't there? > As for other clients that could be provided in the repos there's Gwibber and > Hotot and so on. gwibber is in the repos, about others I don't know. I don't use that stuff. But you can always file a rpm request on our bugzilla. Oliver
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release courier-authlib-0.63.0-9.mga2
2011/12/3 Barry Jackson : > On 28/11/11 14:39, Guillaume Rousse wrote: >> >> Le 28/11/2011 14:46, Mageia Team a écrit : >>> >>> barjac 0.63.0-9.mga2: >>> + Revision: 173752 >>> - Added ldconfig in %post and %postun >> >> This is supposed to be done automatically by file triggers... >> > Yes - I was only reading something about that yesterday, however after > installation of courier-authlib prior to the addition of ldconfig in %post > and %postun, courier-imap would not build as it could not find a lib > installed by courier-authlib. Can't reproduce your "bug" with up-to-date Cauldron chroots. Tried both i586 and x86_64. Removed %post and %postun scripts, rebuild courier-authlib and build courier-imap with new courier-authlib and all went just fine.
[Mageia-dev] Pino
On 03/12/11 07:06, Kamil Rytarowski wrote: W dniu 23.11.2011 22:30, Philippe Makowski pisze: Pascal Terjan a écrit : On Wed, Nov 23, 2011 at 15:34, philippe makowski wrote: 2011/11/23 Funda Wang: The problem is, why we are shipping a dead package? Dead ? https://bitbucket.org/troorl/pino3/ not sure it is dead It is dead as in "build errors reported 1 year ago have not been fixed Ok dead or nearly, no package maintainer, certainly alternatives (I don't know) so we can drop it pino is moved to obsoletes in our svn Please remove it from mirrors Pino may be dead or dieing, but it is still a very popular client for Identi.ca. I find it a very good client, as a result I strongly believe that it should definitely stay in the repos for Mageia 2. If Pino is no longer made I think it would be good for many distros to still provide it in their repos for at least another year Also looking at things from a user point of view, I think that many computer users don't mind using old software that is no longer maintained as long as they can still use it for it's intended purpose. I think that for myself and many other people that use Identi.ca Pino is an example of this. Unfortunately at the moment though in my install of Mageia 2 Alpha 1 with the latest updates, I can't install Pino using RPMdrake, because: Sorry, the following package cannot be selected: - pino-0.2.11-1.mga1.i586 (due to unsatisfied libnotify.so.1) As for other clients that could be provided in the repos there's Gwibber and Hotot and so on. P.S This is my first email to this mailing list or any Mageia mailing list, and I think any mailing list in general.
