Post it. I ain't got no idea what the people are talking about.canci wrote: Also, my rc.conf is not a mess.
The DM looks different if you restart/reboot then if you simply start it?
Post it. I ain't got no idea what the people are talking about.canci wrote: Also, my rc.conf is not a mess.
Haha, I'm a bit anal about what "feeling" the theme gives me when the computer startsnadir wrote: The DM looks different if you restart/reboot then if you simply start it?
Also, rc.conf has the advantage of having almost everything start up and system related in 1 file
So if you would ever want to edit something it would be all in one file?Also, my rc.conf looks the same as any vanilla one, except for the actual variables which are changed.
Dosna seem hard to understand, my friend.Also, my rc.conf looks the same as any vanilla one, except for the actual variables which are changed.
A real example what a real user does on a regular basis would probably help more of us to understand what the advantage is (one which is worth to mention it at all).But that's of no relevance to someone who likes the default settings,
Bad luck, any idea as to what caused it?oOarthurOo wrote:I think the experiment is over. Just had a hard-lockup. Nothing worked. Couldn't switch terminals. Nada. I really thought this was the distro that might take me away from Debian, but it's like travelling; the more amazing things you see abroad, the more you appreciate how great you got it back home. Sigh... time to get out the usb and download the netinst.
canci wrote:Sounds to me like the Liquorix kernel
The only thing running was evolution. There's been some noise on the evo mailing lists about it segfaulting on F14, unfortunately there was nothing in any of the logs to suggest more conclusively what happened.cynwulf wrote:Bad luck, any idea as to what caused it?
You can even make it look prettier:nadir wrote:/etc/init.d/gdm stop
/etc/init.d/kdm start
Code: Select all
service gdm stop
service kdm start
I think that it won't be bad if somebody explain in plain language(bulgarian prefered ) what SPICE gives to normal desktop users compared to other virtualization technologies, and is it possible SPICE to become the "next NetworkManager". Plus if possible to say how turbo is the new turbo jpegSo what do you think about Fedora 14?
I have an i830 toshiba 1200-s212 lappy with 2 x 128MB PC133 sodimmArconsII wrote:Fedora was difficult to netinstall due to YUM's erratic behavior, but the fact that FULL (I mean everything working) kernel modesetting worked on my i830 mobile chipset means it gets both cookies and crackers.
I'll stick with Debian and back-ported Intel video drivers until it absolutely necessary however....
Was this the latest, F14? If so it may be partly due to the newer kernel (2.6.35 ?). I am having problems with an i830 chipset in my old laptop (running Sid), the 2.6.36 kernel from experimental makes it usable but performance is bad - but I need to update anyway as it's been nearly a week since I've tried. I don't think I'll install fedora on it though as it was hard enough to get debian on there with only floppy drive.ArconsII wrote:Fedora was difficult to netinstall due to YUM's erratic behavior, but the fact that FULL (I mean everything working) kernel modesetting worked on my i830 mobile chipset means it gets both cookies and crackers.
I'm pretty sure it was the newest (F14) version.cynwulf wrote:Was this the latest, F14? If so it may be partly due to the newer kernel (2.6.35 ?). I am having problems with an i830 chipset in my old laptop (running Sid), the 2.6.36 kernel from experimental makes it usable but performance is bad - but I need to update anyway as it's been nearly a week since I've tried. I don't think I'll install fedora on it though as it was hard enough to get debian on there with only floppy drive.ArconsII wrote:Fedora was difficult to netinstall due to YUM's erratic behavior, but the fact that FULL (I mean everything working) kernel modesetting worked on my i830 mobile chipset means it gets both cookies and crackers.