/lib/modules/(stock2.6.21kernel)# du -s
60804 .
/lib/modules/(my2.6.21kernel)# du -s
538292 .
That's a 785% increase in space consumed by my modules over stock modules.
Does that happen for anyone building their own Factory kernel? Can a more
normal space consumption be made to happen by a mere mortal kernel building
novice like myself?
What I did was:
1-apply the patch from http://bugzilla.kernel.org/show_bug.cgi?id=7513
2-zcat /proc/config.gz > .config
3-make menuconfig to add smbfs and change the CONFIG_LOCALVERSION
4-make
5-make modules_install
6-INSTALL_PATH=/boot make install
7-fix the resulting broken /boot/grub/menu.lst
--
"Therefore, if anyone is in Christ, he is a new creation; the
old has gone, the new has come!" 2 Corinthians 5:17 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://mrmazda.no-ip.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Users tend to ask about AIGLX quite a bit. Why do we not have this
enabled by default, where possible? Xgl is nice and a lot of people
prefer it (including myself), but a lot of people prefer using AIGLX
too. Having it enabled by default where possible of course also
provides the possibility of switching between compiz/kwin/metacity
easier too.
If not setting it up by default, perhaps we could consider having a
script similar to gnome-xgl-switch for setting it up a little more
easily for users.
Any thoughts?
Regards,
--
Francis Giannaros http://francis.giannaros.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
FYI: Current freetype in FACTORY is broken, use the version from Alpha4
instead of updating,
Andreas
--
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Acrobat Reader 8 is out, but on openSUSE NON OSS repo I see only version
7. Does it mean that acroread package will not be updated for 10.3
final?
Thanks!
--
Igor Jagec
Friday I determined that 4096 was an inappropriate blocksize for my
non-libata hda19 Factory / partition. I booted 10.1 from hda7 and did a cp
-a on that partition to another partition, reformatted to the 1024
blocksize, then did cp -a back to it. I then tried to mount and chroot to it
in order to run grub-install. Grub-install failed due to the non-existent
target device. Copying the hda19 device file from the 10.1 / and trying
again didn't help. I tried to do a rescue installation, but both rescue
modes apparently failed for a similar or the same reason. Is it possible in
Factory to do a rescue? If so, how?
--
"Therefore, if anyone is in Christ, he is a new creation; the
old has gone, the new has come!" 2 Corinthians 5:17 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://mrmazda.no-ip.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
I've added a new idea to idea.opensuse.org
| Move YaST tutorials from forgeftp.novell.com to openSUSE WIKI |
http://idea.opensuse.org/content/ideas/move-yast-tutorials-from-forgeftp.no…
We are currently working on implementing features and that's why the
documentation is a bit loosing at the end of the queue. On the other
hand, moving those YaST tutorials can:
* Help you to gain a respect from openSUSE community as well as from
YaST developers :) ;)
* Help you to understand YaST a lot more
Additionally, this is not only about moving some texts somewhere else,
you are expected to bring new ideas, new tutorials, you can realize your
dreams :)))
* * * * *
More about idea.opensuse.org:
It's a web/page for sharing ideas how to improve (openSUSE) Linux and
also implementing those ideas.
Maybe you are good designer but can't write in any programming language.
Maybe you can just write in Perl or C++ and you are really good at it :)
... idea.opensuse.org is the best way to go!
File an idea there or pick already filed one.
* * * * *
Thanks in advance
Bye
Lukas
PS: YaST developers and their (development-related) help can be found
also on IRC at irc.freenode.net, channel #yast
--
Lukas Ocilka, YaST Developer (xn--luk-gla45d)
-----------------------------------------------------------------
SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic
On Fri, 2007-11-23 at 17:27 +0100, Will Stephenson wrote:
> On Friday 23 November 2007, Rodrigo Moya said:
> > So, first, I would like people to test the packages we've built, and
> > second, what needs to be done to put this into the distro for 11.0? Are
> > KDE people aware and happy of the change?
>
> I'm aware of it affecting gnome, but at the moment I see it as GNOME replacing
> esd. Does it have a wider impact on the distro that I'm not aware of?
>
> I'm not aware of anyone writing a PA backend for Phonon yet.
>
PulseAudio replaces esd, true, but it offers many new features, not
present in arts AFAIK, that, I think, could benefit KDE also. If there
are no plans in upstream KDE, I guess we'd keep it as a GNOME thing
only, although we are going to patch some non-GNOME apps, like jack, so
I guess it would be good to be using the same sound server everywhere.
--
Rodrigo Moya <rodrigo(a)novell.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
The GNOME team set up a wiki page for 11.0 ideas. One of the requests is
for accessibility options to be available in the YaST installer, in
particular:
* Screen magnifier - shows a magnified version of the portion of the
screen you're pointing at.
* Screen reader - reads the labels and input text out loud.
* Braille output - provides tactile display of labels and input text via
a special device.
In GNOME, we use Orca to accomplish this, together with the at-spi
infrastructure. It is a Python app. I don't know what Qt/KDE uses, but I
imagine something similar.
So I have some questions for the YaST/installer guys:
* What accessibility technologies are available in the installer today,
and how are they configured?
* If we're missing accessibility functionality, how feasible would it be
to implement it for 11.0?
* Given that the installer is a Qt app, what technologies could we use?
Also see
http://en.opensuse.org/GNOME/Ideas/11.0#Accessibility
--
Hans Petter
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
I've just implemented a new feature of the YaST 'Progress' module:
| Icons shown during the progress run |
I hope you find it useful and that we get more icons to the UI to make
it brighter, cooler, and ... ;)
See this article with screen-shots:
http://en.opensuse.org/YaST/Development/Progress_With_Icons
(This feature is available in yast2-2.16.16 and later)
Bye
Lukas
PS: It's currently implemented by replacing images with another ones but
it would be better if there was a native Qt/GTK support for making
images gray-scaled (initial state) and then make them colored again
(active). Would it be possible? Thanks.
--
Lukas Ocilka, YaST Developer (xn--luk-gla45d)
-----------------------------------------------------------------
SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic
Hi,
A new article about installing openSUSE 10.3 on MiniLaptop Fikar FJ has
been just finished:
http://en.opensuse.org/Installation_on_Chocolate_Laptop
It can possibly help others when debugging installation on similar piece
of hardware.
Bye
Lukas
--
Lukas Ocilka, YaST Developer (xn--luk-gla45d)
-----------------------------------------------------------------
SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic
