ranger

If the machine you are installing from has linux on it already, use the kernel ( isolinux/alt0/vmlinuz) as a kernel in your bootloader, with the file isolinux/alt0/all.rdz as the initrd, and you should be able to boot into the installer as if you had booted the CD. Note that you need to add an append line as well, similar to that in the default entry in isolinux/isolinux.cfg If the machine does not have linux installed, but has PXE support, you can use that to load the same kernel and initrd. There are some more hints on this on the cooker wiki ....

I have the driver working fine, I will try and provide dkms packages ...

You should also just try booting with the 'pci=noapic' boot option.

ipw2100 works out-the-box on 10.1, but if you're not using the commercial/Club versions, you just need to get the firmware files from http://ipw2100.sf.net

Uh, you really need to give more information here. What do you mean by "entirely Windows network"? Does that mean you have a Windows NT4 domain with clients joined to it, or a Windows 2000/3/Active Directory domain? Or, is it just a workgroup of Win9x machines? With WinXP home? With WinXP Pro? Samba can do this under any of these conditions, but to be able to help you configure it, we need to know this ... Otherwise, you can: # urpmi samba-server ksambaplugin and use ksambaplugin to configure samba.

Which one?

Please check if unix extensions are enabled on the samba server. If they are, you may want to try turning them off, otherwise you need an updated samba package which allows smbmount to disable unix extensions (this is an upstream bug). I will upload packages shortly to 10.0 community that have the patch needed to disable unix extensions. I am not sure why Knoppix works - maybe they have an old version of smbfs which doesn't know anything about unix extensions ...

qgis crashed for me under 10.0, but it works on cooker/10.1, and it is now in contrib (version 0.4). The problem on 10.0 was that an updated gdal was needed to build grass57, which changed the minor number of the library, but not that of the rpm, and resulted in file conflicts. Updating gdal would require rebuilding all other apps that require gdal. I didn't want to push this to community contrib, but thac did rebuild the packages on 10.0. 10.1/cooker currently has grass-5.0.3, gras53-5.3.0, and grass57-5.7.0 though. Grass isn't only text based, there is the tck/tk gui ... Anyway, AFAIK, we're the only distro with all 3 (grass, grass53, grass57), as we were also the first with grass (5.0.x).

The problem with the keyboards on these machines is not affected by the distribution, it is a hardware/BIOS issue. Our company has about 20 of these machines, those with the earlier models had problems on every distribution they tried (Fedora, RHEL, Gentoo, Mandrake). BIOS updates help. I am happy with my NX7010 running Mandrake, getting the wireless working on 10.0 was not difficult (I had it running in May IIRC), but it is much easier on 10.1 (beta1), you just need to put the firmware file in /usr/lib/hotplug/firmware (you have to create the directory still at present).

Firstly, the easiest solution to your problem is to setup a network urpmi source for main. Use http://plf.zarb.org/~nanardon/ , and if you are on low bandwidth, choose to use synthesis hdlists (since you already have hdlists for the stuff you have on the 2 CDs. Secondly, Mandrakesoft does not hide the fact that Standard Edition is not suitable (on it's own) for development work, but it's not going to advertise that there is no gcc on the page showing the features (just as any other company isn't going to tell you the missing features of a certain model). Just go and compare these two pages: http://www.mandrakesoft.com/products/91/standard http://www.mandrakesoft.com/products/91/powerpack Finally, if you *just* want to give Mandrakesoft some money (and you can also get all the "commercial" software you get on Standard from them), join the MandrakeClub instead. -You get the CDs sooner (if you dowload/burn or buy from a cheaper online vendor) -You get all the same (and more) benefits) -Mandrakesoft gets more of the money (since they don't have to pay shipping, printing, stamping costs) -Everyone wins

Well, that's your problem. You need an IP masquerading rule, and Mandrake uses shorewall for this. So, if you turn the firewall on, you should have your internet connection sharing working. If you need to access the box the ICS is on, you can (until you get the hang of shorewall rules) turn the policy for masq->fw and fw->masq to accept by editing /etc/shorewall/policy and restarting shorewall.

Internal users may be able to hack your firewall more easily. If you trust them, then that's probably OK. If someone does hack your box from the outside, they can now get into your network (so you may want to rather turn the policy for fw->masq back to deny, and add a rule in /etc/shorewall/rules allowing only connections to high ports on your network, but you may also need ports 137-139 for samba ..). It's always safer to restrict connections as much as possible, going both into and out of a firewall, but unless you have the extra machines, a firewall that is pretty tight from the outside should be enough to make you a less attractive target to hack ...

You probably changed your hostname, and didn't log out and back in, so X didn't know who it should allow connections from. I tested it on 9.1 with XFree86-4.3 (not that I think X version makes a difference) with no problems.

Mandrake Control Center->Network & Internet->Drakconnect->Wizard->Expert mode, and it will allow you to set your various hostnames, set them all, and it should work. Otherwise take a look in /etc/sysconfig/network, and ensure HOSTNAME is set. Samba by default uses your hostname as your netbios name, so it's usually not necessary to change it.

# urpmi cyrus-imapd You do have to manually create accounts, but read the docs that are provided (including the one specific to the Mandrake package) and you should come right.

Mandrake's default config has everything set right, any user should be able to access their home directory as a share with their username. Please, consider carefully before suggesting SWAT to newbies, ksambaplugin in contrib is a better tool, and if you *must* have remote use, either ssh+vi or webmin instead. Not totally, samba has support for the unix extensions, which allows more of the features NFS allows (ie creating symlinks, named pipes etc), but we need the CIFS filesystem in the kernel to use it from the client side. The "more secure" isn't always totally accurate BTW ... especially if you do this: You shouldn't suggest to anyone to use no_root_squash without at least warning them that they have now given any user who can get root priveleges on any machine in your subnet rights to do what they like with everyone else's files you have shared on your NFS server. ie, if someone boots knoppix up on one of your machines, they can get to any files on /home on your server! So, don't unnecessarily use no_root_squash, there's a good reason why root_squash is the default.

KDE Control Center->Local Network Browsing->Windows Shares, fill in "Default Username", "Default Password", "Default Workgroup" is really only necessary if you are connecting to machines that members of a Windows domain. Or, if you type in the address bar of Konqueror: smb://user@server/ Then you should get a username/password prompt. Mandrake Control Center doesn't have support for authenticating before listing the shares on the server.

1)What version of samba are you running? At various points in samba-2.2.x, improvements have been made, so it's usually best to use the latest version. Of course, there are RPMS of the latest release for most recent Mandrake releases available on the samba FTP mirrors. 2)Are you connecting to the printer (when you print) as a user with printer admin rights or not? There were issues with this at one stage (non-printer-admin users would work fine). 3)This has been working for us since 2.2.2 or so, but we mostly have win2k clients (though I think the winxp clients also worked fine). 4)What printer/driver is it?

There unfortunately is very little documentation available on setting up XDMCP, but here goes: 1)You want XDMCP enabled on a display manager on the machine you want to connect to. 2)You may have to restart the display manager for changes to take effect (maybe not with gdm) 3)xdm, gdm and kdm (including mdkkdm) all support XDMCP, but it's easiest to configure with gdm (run the config tool and check the "enable XDMCP" box on the last tab). For kdm/mdkkdm, you can enable XDMCP by editing /usr/share/config/kdm/kdmrc, in the Xdmcp section, change "Enable=false" to "Enable=true" and restart kdm if necessary. If there are firewalls running on either the client or the server, or anything in between, you may have to disable for testing, and add extra rules for normal use (hint: ports 177 and 6000-6010)

This is very outdated, and very insecure, don't follow anything you read here ... Cygwin X works great, try the -rootless or -fullscreen options: XWin -query <IP> -rootless or XWin -fullscreen & ssh host gdm etc etc.

No, it's not normal. It seems like your hostname resolution isn't working. Are you actually using NFS? If not, turn it off.

Well, Mandrake can't enable ACPI by default, since many machines die if you try ACPI on them. If you had to do anything besides enabling ACPI on reasonable hardware (Compaq laptops are known to give problems, and in some cases you must recompile the kernel with a custom dsdt table etc etc), then you may want to post the details here and/or in Mandrake bugzilla so someone can look at fixing it.

It may be easier to share from the Windows side, but if not 1)Ensure that you have a unix account with the same name as he uses in Windows 2)Add a Samba password to that account that matches the password he uses to log into windows. The easiest way is with ksambaplugin, but on the console may be quicker: # smbpasswd -a username 3)Give his username ownership of the directory 4)Ensure the share is set as writeable (read-only is the default) Connect!

A better solution is to set the user's samba password. If you have installed ksambaplugin, this is very easy. In KDE Control Center, use Network->Samba Configuration->Administrator Mode->Users. Click on a user on the right, and hit the arrow pointing to the left, and enter the password they use in Windows. The benefits of this are that everything will work from windows without problems (you need a reg hack to use clear-text passwords from recent versions of windows).

Could you be more specific? Only some versions of windows support ipp ... for the rest you need samba (which isn't difficult to setup, but you would need to open ports 137-139).