wilcal

Thanks John. Same for me, I just let it ride. I looked into Bugzilla and couldn't find anything. Just let it alone for now. Good to know someone else has seen the same thing.

The following are errors I get during install of Cooker 0.5 Has anyone else here encountered the same errors? zenity-2.10.1-1mdk.i586 zip-2.31-1mdk.i586 yelp-2.10.0-4mdk.i586 The message is: "There was an error installing packages:" "Go on anyway? then reference to the above. I type Y and the installation contines on to success.

Is this what you are talking about: ftp://mandrake.contactel.cz/Mandrakelinux...i586/media/main apache-mod_auth_external-2.0.54_2.2.9-3mdk.i586.rpm

Sure. Your can set up users all you want. But if you create a public_html directory that cannot be accessed outside that users account. Logged in as the user you can open the files using Mozilla/Firefox. The test page does work and you can change that to whatever you want. Apache is running. I think they have to think of a scheme in MCC to first allow the Users to set this up and still maintain the security they are looking for. FWIW back in the bad ole days of Mandrake 9.2 that version defaulted to allowing proxy which meant pretty quickly your webserver got used by every spammer that could find you.

Thanks..The Mandriva Bugzilla team has acknowledged the fault and assigned it. I would expect that the next release should be a lot easier to let users have their own webpages function. I agree with you that you can get into the code and tweek things to work but that goes entirely against the concept that Mandriva should be an easy to install and set up OS. And that includes all it's functions. Even the webserver. What used to be an automatically working funtion now requires a code tweek to make it work. And MCC is broken when asked to set the function to working. Lets see what happens on the next release. I am just getting started with underestanding how Bugzilla works and this was my first post there. All seems fair and responsive. Thanks for the help

This "Bug" has been officially acknowledged, and assigned, in the Cooker Bugzilla. Visit: http://qa.mandriva.com/show_bug.cgi?id=18775 for it's status.

I found this: http://rpm.pbone.net/index.php3/stat/4/idp...S.i586.rpm.html and will try it this weekend to see if it works on cooker. I doubt it.

Lots of warts still in 2006 (cooker). I would give it until probably Apr/May 2006 before I would switch over from Mandriva 2005 LE which is turning out to be one of the most stable and reliable OS's around.

As it turns out the public_html user directory is turned off in cooker by default and you do have to "turn it on" by installing the "mod_userdir" module. I am not an Apache expert so how do you "install the mod_userdir module". Is it an RPM? Or just that it is part of the Apache code and the text that you recommeded above installs it. thanks

I suggest staying away from Lilo/Grub to dual boot anything. Get up to speed on: Ranish Partition Manager http://www.ranish.com/part/ You can have as many as 30 seperate and discreet OS's on a single hard disk. Typically I set up 10GB partitions.

During installation make sure you set the Security Level to "Normal". http://shots.osdir.com/slideshows/slidesho...ase=334&slide=5 Allowing it the default "High" will close off the Apache webserver to the WAN.

This will be a really interesting question for me also. I suggest that "really good" video editors really don't exist on Linux at this time. Unfortunately. "Really Good" to me would suggest that you are looking to produce something professional or nearly professional. Way out of the home movie arena. Two editors come to mind. Adobe Premiere Pro is an excellent video editor and very popular. If you are looking to produce something "Really Good" in the under 10 minute range then Pro is the only way to go. Many of the commercials that you see on local television are produced using Premiere Pro. http://www.adobe.com/products/premiere/main.html I have used Premiere for about 5 years now and find that there is only one other product that is better. And that is....... Avid Xpress http://www.avid.com This is the platform of choice for professionals both Hollywood and TV. It's the most common platform taught in schools. This is a _VERY_ (did I underline very) powerful video editor and creation tool. If you go to a movie, watch a TV program or view a DVD you are probably looking at a presentation created in Avid. Both of these platforms suffer from the fact that they are Microsoft XP specific. Even using the latest updated version of Pro on the latest updated Windows XP you still get the occasional freeze and crash. Avid offers a custom entry level system for about $6000 that I am sure is better. That system uses Windows XP. "Really Good" can translate into $53,245++ including software and hardware in this application in this tool.

Yes, sure does. Just confirming that it happens is fine. I'm sure it will all be corrected by the time 06 goes official. 2006 0.3 installed Gnome but never turned it on because they were waiting for the newer version. There were also some RPM install errors.

A quick question here about the lastest beta release of 2006, the Apache webserver. All previous versions of Mandrake/Mandriva have a default page with loads of information about Apache. That has now been simplified down to a blank page except for the words: It Works! Ok fine, It works and the latest RPM for Webmin (1.220) installs just fine and it tells me that Apache is running. But Creating a public_html directory in a users root is not reachable. Example /home/testuser/public.html/index.html In a browser http://127.0.0.1/ gets you the It works page but http://127.0.0.1/~testuser/ gets you nothing even though it exists anyone else run into this? This process in 2005 LE runs just fine without having to manage anything. Thanks

Last night I updated my two Mandriva LE 2005 boxes. One box is my crash test dummy (everything gets tried here first) the other is my production on line webserver at: http://66.159.200.93 There was a little wrinkle in the update I have not run into before. If you opt'd to install Apache on a new install the webserver defaults to on. Simply create users and add a public_html directory in the User space. Create your index.html page and your off and running. After last nights updates it appears that the server gets turned off by default. So you need to turn the Apache server back on. I use webmin to do that.

I picked'em all Intel, P4 530J 3.0 GHz, 800MHz FSB, 1MB L2, LGA 775 GigaByte GA-8I915G Pro" i915G Marvel Yukon 88E8001 Gigabit LAN Intel High Def Audio, Azalia (C-Media 9880) Intel Graphics Media Accelerator 900 (on Intel 915) Kingston 1G(512MBx2) DDR400 PC-3200 Ranish Partition Manager http://www.ranish.com/part/ Maxtor 80GB SATA (one partition) -------------------------------------- Mandriva LE 2005 Maxtor 120GB SATA (eleven partitions) -------------------------------------------- Mandriva LE 2005 (20GB) Mandriva 2006.3 (10GB) Mandriva 2006.4 (10GB) Ubuntu 5.10 (10GB) Elive .3 (10GB) empty (10GB) empty (10GB) empty (10GB) empty (10GB) empty (10GB) Maxtor 160GB SATA (one partition) ---------------------------------------- Windows XP SP2, mostly dormant or for compatibility testing KingWin HD SATA Rack/Tray subsystem Sony CD/DVD-RW DW-D26A I use Mandrake 10.1 at work on an 800Mhz VIA platform Mandriva LE 2005 is my OS of choice :D

cron activity is normal Folder: /etc/cron.d /etc/cron.hourly /etc/cron.daily /etc/cron.weekly /etc/cron.monthly all have script files in them that execute at a specific time. I have created additional script files in these folders to do regular house keeping such as backup of specific directories. Once a week on Sunday morning, 4:20AM, a script file kicks off that takes about 15 minutes to complete. The hard drive sounds like a washing machine. And because my webserver is about a meter from my feet when I am in bed there are times it wakes me up. Install and use webmin to understand, review and modify your cron file schedule.

Ref: http://www.ranish.com/part/ I spent some considerable time last evening going through the installation process of part243.exe. I was finally able to document as best I could on the process of creating what is called the Boot Manager Partition. Below is the process I followed. Do note that I was not interested in any other OS other then Linux. The intent was to create 10 discrete and independent partitions on a 120GB Drive. Read this process several times end to end before doing it for yourself. Your computer may react differently then mine. Here's my process: 1) Create a bootable floppy using Windows XP 2) Copy to that disk all the files found on part243.zip 3) Remove XP drive and replace with a completely zero'd out 120GB SATA Maxtor drive. Use www.killdisk.com to zero the drive. I use removable rack mounted drives in the computer under test. 4) Warm boot the system, primary boot device floppy, secondary boot CD-ROM, third is the HD. 5) Execute part243.exe ( A: part243 (cr) ) (cr) = return 6) When part is running move highlighted section to the Master Boot Record (MBR) then (cr) 7) The highlighted section will move to the MBR frame first line MBR Executable Code change to Boot Manager using the space bar 8) Down arrow to Boot Interface Type. Space Bar to Text 25x80 9) Down arrow to Checking for Virus: Space bar to no 10) Boot Prompt Time: clear and fill in 10 seconds 11) Default Boot Choice: left at not set 12) (cr) back to Master Boot Record. A line will appear instructing "ins(ert) to create Boot Manager Partition" 13) key insert 14) down arrow though file system type to Boot Manager (cr) to select. The Boot Manager partition will now be placed in the table on the screen. Move to the Boot Manager line and modify the Starting Cyl Head Sect number such that you define a Partition all the way at the end of the disk. There will be quite an amount of trial and error with error messages until you get a satisfactory partition size. Especially finding a combination that is fully at the end of the disk with no unused space after it. Also you will likely find that the Boot Partition size is hard to keep below the many megabytes size. The smallest workable size I was able to create was 7MB on a 120GB drive. 15)After finishing creating the Boot Partition Part will ask if you want to save, I selected later. 16) Then positioning the highlighted section between the Master Boot Record and the Boot Manager Partitions I keyed insert and created a single Linux partition of 20GB. Then created a second of 10GB. 17) At this point you can designate both of these partitions as "Primary" and the 20GB as 1 and bootable. Number them 1 and 2. I fiddled with the locations of these partitions such that the 20GB partition was at the far end of the disk and the 10GB partition just in front of it. The reason for this is below. 18) It is at this point I keyed F2 to install the Ranish Partition in the MBR and the Boot Manager Partition. 19) Leaving the bootable floppy in the drive I then keyed esc and forced the system back to the A: prompt. 20) Remove the floppy and warm boot the system. 21) The system rebooted and displayed the Boot Manager text box in the upper right side of the terminal. Three partitions were offered for Boot one of which was the Boot Manager. There are disappearing dots indicating that within 10 seconds the active primary will boot in 10 seconds. If you let things time out at this point, and nothing is installed in the primary partition, what you get on the screen is unpredictable gibberish. 22) During the count down process if you key "0", the number key zero, you will be taken directly to part243 that is now installed in the Boot Mananger partition. At that point you can create additional partitions up to 30. I created 10. 9 10GB and one 20GB. Remember there is the one additional partition, the Boot Manager partition. The numbering system is a little confusing so trail and error is the best teacher. Keep pencil and paper close at hand. 23) Installing OS's. I have found that filling in partitions from the furthest out partition in works best. The single 20GB last partition is where I installed Mandriva LE 2005. That is the working partition for this 120GB drive. In there are the ISO's (image files) for all the other Linux OS's that I keep stored in the other partitions on this drive. The 9th partition contains Mandriva 2006 Beta 3. The 8th Ubuntu and so on and so forth. 24) Installation of an OS can be tricky. Some of them are very smart ( Mandriva 2005/2006 ) some of them want to walk all over your MBR and first sectors of your drive. Or insist on installing into the first partition. Let'm do it. 25) The postions and sizes of the partitions on this drive (120Gb) will never change. So booting from floppy again to the A: prompt I keyed the following A: part243 -p > part120.txt that created a text file part120.txt on the floppy that tells me the beginning and ending and file system for all the partitions on this drive. And this is my printable table for restoring things back after a misbehaving OS stomps all over the MBR and first sectors of the drive. Because the needed drive partitions are loaded from the end first OS load is not likely to effect them. 26) As you edit the partitions using Part243 you will find that you can only make active 4 at a time 1 -> 4. You can have 30 partitions but only 4 at once active and only one auto bootable. This is a good thing as some OS's get really confused when they see multiple drives (partitions). I found myself designation only one active partition at a time. The number 1 was assigned to one of the partitions and that partition designated bootable even before I installed an OS's to it. That made things a lot simpler during the install process. Mandriva 2005/2006 flat out thought that the other 100GB of drive space was "unused". And that is exactly what I wanted it to think. Don't touch whatever you do. (end procedure) I am sure I will find more interesting things to do with the Ranish Partition Manager. If you are only intending on having no more the 4 bootable partitions then you need only install the MBR from floppy. No Boot Manager Partition need be created. But, if you want to change something you will have to boot from floppy again. Not all that of a problem but in my case I would have an associated floppy with a specific set of removable drives. No big deal. On boot the Boot Manager Text Box will appear in the upper right hand quandrant of your computer screen. If you have designated a auto boot partition at the end of the time out that partition will boot. If you key either the up or down arrow the timeout will cease and you can up down arrow through the various partitions, active or not, and a (cr) will select and boot that partition. Remember keep that paper and pencil close as lots of partitions and OS's can get pretty confusing and fun to play with. I hate having to use Windows XP to create a bootable floppy but there are alternatives at http://www.bootdisk.com/

2006 beta 3 has a very different KDE facia then 2005. I get the feel that it's a little quicker too. It's all kinda like the 3nd trimester. The baby ain't born yet but it's get'n close and look'n good. A comment. Mandriva has done an outstanding job to make the install pretty easy to use. I would say that for the novice user comparing Win XP SP2 vs 2005 LE and 2006 beta, Mandy is much easier to install, use and navigate around in. As always if you are trying to dual/triple or more boot a single HD then things get pretty tricky. Kernel is 2.6.12-10mdk Could the real market challange to Redmond WA come from Paris, France? Could be.

partial success For some reason either I don't understand the interaction between Lilo and how LE 2005/2006 interact and/or how they create partitions. The point of this exercise was the ability to create, on a single drive lets say a Maxtor 120GB, discreet and independent partitions not related to, interacting with, dependent upon or even recognizing the existence of the other partitions. I wanted the ability to create partitions, install various Linux distros, erase the partition completely, reuse erased partitions and create/re-size new or existing partions. I suspect the tools available within Mandriva 2005/2006 may not be capable of all of that. I dabbled with the Ranish Disk Partitioner some months ago so I went back to that. http://www.ranish.com/part/ More dabbling and I was successful in installing the Ranish Disk Partitioner as MBR. It's pretty easy to just set up a number of independent unrelated Linux partitions with this utility. The boot screen from Lilos pretty graphics to the Ranish "hd1>" thing is pretty stark but after a few installs it became pretty obvious that Ranish created the environment I was looking for. I have no use for M$ OS's so that's not even being considered. Additionally, I was able to use: http://www.killdisk.com on any one of the partitions created by Ranish to independently wipe clean to all "0"s any of the partitions created by Ranish without disturbing the other partitions or the MBR. So now a 120GB Maxtor drive can become effectively up to 30 discrete and separately bootable drives just like they were 30 different hard disks.

If your set on one ot those then the DG632 RJ-45 (big telephone connection) should go into one of these: http://www.netgear.com/products/details/FS605.php The Mandriva LE 2005 should be set up to connect to the LAN "DHCP" (automatic)

DSL (Damn Small Linux) is kinda fun to tinker with http://www.damnsmalllinux.org/

uname -a tells me that regardless if I tell lilo to boot with 2005(sda1) or 2005(sda7) it still uses Linux 2.6.11-6 the Kernal for LE 2005. 05 /boot/vmlinuz-2.6.11-6mdksmp (sda1) 06 /boot/vmlinuz-2.6.12-10mdksmp (sda7) even with the following code in lilo.conf: image=/boot/vmlinuz-2.6.12-10mdksmp label="LE_2006" root=/dev/sda7 initrd=/boot/initrd-smp.img append="acpi=ht resume=/dev/sda7 splash=silent" vga=788 read-only sda1 (/), sda5 (swap), sda6 (/home), sda7 (/), sda8 (swap), sda9 (/home) which is in fact correct. I'm beginning to suspect that there is something in 2006 beta3 that prevents dual booting from working. Remember if I clean the disk off completely (killdisk) and insall only 2005 beta3 it installs just fine and runs just fine although there are large parts not in it yet (Gnome). I tried all kinds of different ways to dual boot install but no go. FWIW the visuals on beta3 are VERY different then LE 2005 so if anyone has an extra system, or in my case swappable hard drives, give it a look. Thanks again for the hints

I changed the lilo.conf to be the below then ran /sbin/lilo. Then immediately got the response no such file /boot/vmlinuz-2.6.12-10mdksmp So for some reason that I do not understand the system cannot see sda7 as a seperate partition. In fact this may be a wrinkle of 2006 beta. Anyway tonight I will run uname -a when 2006 beta3 is running and actually see if it's running the 11 or 12 kernal. I suspect it's running the 11 kernal on the 12 apps. FWIW the test computer uses a removable hard drive system and one of those removable drives has a perfectly running LE 2005 system on it. When I get frustrated goofing around with this stuff I just plug in the good system and watch a DVD or something. It's all great fun. Thanks for the hints. # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file default="LE_2005" boot=/dev/sda map=/boot/map keytable=/boot/us.klt prompt nowarn timeout=200 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="LE_2005" root=/dev/sda1 initrd=/boot/initrd.img append="acpi=ht resume=/dev/sda5 splash=silent" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/sda1 initrd=/boot/initrd.img append="acpi=ht resume=/dev/sda5" read-only image=/boot/vmlinuz label="failsafe" root=/dev/sda1 initrd=/boot/initrd.img append="failsafe acpi=ht resume=/dev/sda5 devfs=nomount" read-only image=/boot/vmlinuz-2.6.12-10mdksmp label="LE_2006" root=/dev/sda7 initrd=/boot/initrd-smp.img append="acpi=ht resume=/dev/sda7 splash=silent" vga=788 read-only