Permalink
Browse files

Forgot to add a few files to the initial commit

  • Loading branch information...
1 parent 6bd4c15 commit b018fcf57c859528d212a7b0225141683abf4f22 @cb400f committed Jul 30, 2016
Showing with 270 additions and 0 deletions.
  1. +133 −0 windows.php
  2. +63 −0 wlan.php
  3. +74 −0 yast.php
View
@@ -0,0 +1,133 @@
+<?php include 'header.php'; ?>
+<title>12. MS Windows Interoperability - Using openSUSE With Windows Network, Documents and Running MS Windows Applications</title>
+<?php include 'header2.php'; ?>
+<?php include 'menu.php'; ?>
+
+<div class="os1">12. MS Windows Interoperability</div>
+The PC world is dominated by Microsoft, and they're not exactly known for making interoperability easy. Despite this, it's possible to interoperate fairly seamlessly in most cases. This chapter addresses the most common issues.<br /><br />
+
+
+<div class="os2">12.1 Office Documents</div>
+LibreOffice defaults to the Open Document Format (*.odt, *.ods, *.odp, etc.) which is an open standard. This format is partially supported by Microsoft Office >= 2007 Service Pack 2. Or you can suggest to your MS Windows and Mac OSX using contacts to install LibreOffice, as it's freely available for those platforms too.<br /><br />
+
+LibreOffice can also read and write the Microsoft Office formats (*.doc, *.xls,*.ppt, *.docx, *.xlsx, *.pptx etc.) quite well - as well as a wide range of other formats.<br /><br />
+
+<div class="tip">
+<table>
+<tbody>
+<tr>
+<td><img src="images/pics/tip.png" alt="tip" /></td>
+<td>If you come across Microsoft documents that LibreOffice doesn't render well, consider trying if you have better luck with the Calligra suite.</td>
+</tr>
+</tbody>
+</table>
+</div><br />
+
+
+<div class="os3">12.1.1 Fonts</div>
+The free Liberation Fonts provide metrically identical fonts for the most commonly used Microsoft fonts, and are installed by default. Install the package <b>fetchmsttfonts</b> if you need the most common Microsoft fonts.<br /><br />
+
+
+<div class="os2">12.2 Windows Network</div>
+For sharing resources on a local network with MS Windows machines the Samba service is used.<br /><br />
+
+
+<div class="os3">12.2.1 Accessing Shares</div>
+No configuration is needed to access files shared by others. Simply:
+<div class="sti">Launch the Dolphin file manager => Click the location bar or press Ctrl+L for an editable location bar => Enter 'smb://[ip-address]'</div><br />
+
+<center><a href="images/screenshots/smb-dolph.png" rel="thumbnail"><img src="images/screenshots/smb-dolphb.png" alt="smb-dolphin" class="pic" /></a></center><br />
+
+If you don't know the IP-address of the share, you can <i>browse</i> the local network by simply entering <i>smb:/</i> in the Dolphin location bar. However, this will only work if you configure the firewall first.<br />
+<div class="sti">Go to YaST =&gt; Security and Users =&gt; Firewall =&gt; Allowed Services =&gt; Select "Samba Client" and "Netbios Server" in the "Service to allow" combobox and add them</div><br />
+
+<center><a href="images/screenshots/firewall-samba.png" rel="thumbnail"><img src="images/screenshots/firewall-sambab.png" alt="firewall-samba" class="pic" /></a></center><br />
+
+
+<div class="os3">12.2.2 Sharing Your Files</div>
+To share <i>your</i> files with MS Windows users, Mac OSX users or other GNU/Linux users on the local network you must configure the Samba Server (make sure the packages <i>yast2-samba-server</i> and <i>samba</i> are installed). You only need to perform the first three steps the first time you want share a folder.<br /><br />
+
+
+<b>1) </b><br />
+Open the YaST Samba Server module.
+<div class="sti">YaST =&gt; Network Services =&gt; Samba Server</div><br />
+
+
+<center><a href="images/screenshots/samba-server.png" rel="thumbnail"><img src="images/screenshots/samba-serverb.png" alt="samba" class="pic" /></a></center><br />
+
+
+<b>2) </b><br />
+In the tab <i>Start-Up</i> select whether to autostart the Samba service during boot and whether to open the firewall ports required.<br /><br />
+
+<b>3) </b><br />
+Go to the <i>Shares</i> tab, check the options <i>Allow Users to Share Their Directories</i> and <i>Allow Guest Access</i>. In the <i>Identity</i> tab you can configure your workgroup and share name.<br /><br />
+
+<b>4) </b><br />
+Add shares by clicking the "Add" button and specifying the directories you want to share.</i><br /><br />
+
+
+<div class="os2">12.3 Running MS Windows Applications</div>
+High quality, native GNU/Linux applications exist for almost any purpose, but it's possible that you're dependent on a MS Windows-only application for some job. These are your options in such a case.<br /><br />
+
+
+<div class="obs">
+<table>
+<tbody>
+<tr>
+<td><img src="images/pics/obs.png" alt="obs" /></td>
+<td>You should only run non-native applications as a last resort. Apps work better in their native environment.</td>
+</tr>
+</tbody>
+</table>
+</div><br />
+
+
+
+<div class="os3">12.3.1 Wine</div>
+Wine (Wine Is Not an Emulator) is an application that enables you to run many MS Windows applications, you can install wine with YaST or zypper.
+
+Wine is a command line application, the syntax is:
+<div class="cl">wine /path/to/setup.exe</div><br />
+
+<div class="tip">
+<table>
+<tbody>
+<tr>
+<td><img src="images/pics/tip.png" alt="tip" /></td>
+<td>The package <a href="http://sourceforge.net/projects/q4wine/" target="_blank">q4wine</a> provides a graphical interface for some features of Wine.</td>
+</tr>
+</tbody>
+</table>
+</div><br />
+
+The Wine project keeps a database for sharing experiences of running applications, see:<br />
+<a href="http://appdb.winehq.org/appbrowse.php" target="_blank">http://appdb.winehq.org/appbrowse.php</a><br /><br />
+
+
+
+
+<div class="os3">12.3.2 CrossOver</div>
+CrossOver is not gratis. It's specialised in running a select few of the major MS Windows applications - mostly office related.<br />
+<a href="http://www.codeweavers.com/products/cxlinux/" target="_blank">http://www.codeweavers.com/products/cxlinux/</a><br /><br />
+
+
+<div class="os3">12.3.3 Dual Boot</div>
+As mentioned in the <i>Installation</i> chapter, it's relatively simple to run GNU/Linux and MS Windows on the same computer. If your only need a few applications that you rarely use, maybe it's worth it to reboot into MS Windows now and then, when you need to use these particular apps.<br /><br />
+
+When you install a dual boot system, your MS Windows disks/partitions should be mounted under <i>/windows/C/</i>, <i>/windows/D/</i> etc. If not, you can assign mountpoints (folders in which the drives should be mounted) with YaST => System => Partitioner. By default partitions formatted with the NTFS file system will be read-only. To make them writable for the normal user you have to edit the respective entries in <i>/etc/fstab</i> and replace <i>fmask=113,dmask=002</i> with <i>umask=0002</i>.<br /><br />
+
+
+<div class="os3">12.3.4 Virtualisation</div>
+It's possible to run MS Windows on top of GNU/Linux inside a <i>virtual machine</i>, using software such as VirtualBox, KVM, Xen or VMware. This is somewhat advanced, and requires some computer power.<br /><br />
+
+
+<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
+ <tbody>
+ <tr>
+ <td style="width: 50%;"><div style="text-align: center;"><a href="repositories.php"><img class="pic" style="width: 32px; height: 32px;" alt="prev" src="images/pics/prev.png" /></a></div></td>
+ <td style="width: 50%;"><div style="text-align: center;"><a href="codecs.php"><img class="pic" style="width: 32px; height: 32px;" alt="next" src="images/pics/next.png" /></a></div></td>
+ </tr>
+</tbody>
+</table>
+
+<?php include 'footer.php'; ?>
View
@@ -0,0 +1,63 @@
+<?php include 'header.php'; ?>
+<title>16. Wireless Driver Installation - Making Your Broadcom, Ralink etc. Wifi/Wlan Work</title>
+<?php include 'header2.php'; ?>
+<?php include 'menu.php'; ?>
+
+<div class="os1">16. Wifi Driver Installation</div>
+Most of the time wifi will just work out of the box. In these cases you'll be able to configure your wireless card using the NetworkManagement widget which you should find running in your system tray.<br /><br />
+
+
+<center><a href="images/screenshots/pnm.png" rel="thumbnail"><img src="images/screenshots/pnmb.png" alt="Plasmoid NetworkManagement" class="pic" /></a></center><br />
+
+
+<div class="os2">16.1 Find Out Which Chipset</div>
+If your wireless card isn't supported out of the box, chances are you can make it work fairly easily.<br /><br />
+
+The first step is running this command to find out which chipset is on the card. The chipset is what matters, the make and model of the device is basically of no importance.
+<div class="clroot">hwinfo --wlan --short</div><br />
+
+
+<center><a href="images/screenshots/hwinfo.png" rel="thumbnail"><img src="images/screenshots/hwinfob.png" alt="lspci" class="pic" /></a></center><br />
+
+Now that you know which chipset is on your card, you can start figuring out what is required to make the chipset work in openSUSE - usually you'll just need to install a driver and/or some firmware.<br /><br />
+
+
+<div class="os2">16.2 Recent Broadcom Chipset</div>
+The Linux kernel comes with the <a href="http://linuxwireless.org/en/users/Drivers/brcm80211" target="_blank">brcm80211 driver</a> by default. This driver supports <b>bcm4313, bcm43224, bcm43224, bcm43225, bcm4329, bcm4330, bcm4334, bcm43241, bcm43235 (>= rev 3), bcm43236 (>= rev 3), bcm43238 (>= rev 3), bcm43143, bcm43242</b>.<br /><br />
+
+If you experience problems with the above driver, and you have one of the following chipsets: <b>bcm4312, bcm4313, bcm4321, bcm4322, bcm43224, bcm43225, bcm43227, bcm43228</b>, you may want to try installing the proprietary <a href="http://www.broadcom.com/support/802.11/linux_sta.php" target="_blank">broadcom-wl driver</a> (package: <i>broadcom-wl</i>) available in the Packman software repository.<br /><br />
+
+<div class="os2">16.3 Older Broadcom Chipset</div>
+If you have an older Broadcom chip <a href="http://linuxwireless.org/en/users/Drivers/b43#Supported_chip_types" target="_blank">supported by the, free, reverse-engineered b43 driver</a>, i.e.: <b>bcm4303, bcm4306, bcm4309, bcm4311, bcm4318</b>, you only need to install the firmware. This is automated by simply running this command and rebooting afterwards (make sure the package <i>b43-fwcutter</i> is installed and that you are online while running the command):
+<div class="clroot">install_bcm43xx_firmware</div><br />
+
+
+<div class="os2">16.4 Atheros Chipset</div>
+Atheros are working with the Linux-kernel developers towards providing support for all their wireless chipsets in the mainline Linux-kernel, via the <a href="http://linuxwireless.org/en/users/Drivers/ath5k#supported_chips" target="_blank">ath5k</a> and <a href="http://linuxwireless.org/en/users/Drivers/ath9k#supported_chipsets" target="_blank">ath9k</a> drivers, so most atheros cards should just work.<br /><br />
+
+
+<div class="os2">16.5 Intel Chipset</div>
+Intel are cooperating quite well with the Linux-kernel developers and all Intel wifi chips should just work.<br /><br />
+
+<!--
+<div class="os2">16.6 Other Chipsets</div>
+If your chipset manufacturer is not mentioned above, search the web for <i>opensuse [your chipset]</i> and you're likely to find information on how to get it working.<br /><br />
+
+There's a software repository with drivers for e.g. Ralink and Realtek wireless chips. You can add it with this command:
+<div class="clroot">zypper addrepo -f http://download.opensuse.org/repositories/driver:/wireless/openSUSE_12.3 wireless</div><br />
+-->
+
+
+
+
+
+<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
+ <tbody>
+ <tr>
+ <td style="width: 50%;"><div style="text-align: center;"><a href="3d.php"><img class="pic" style="width: 32px; height: 32px;" alt="prev" src="images/pics/prev.png" /></a></div></td>
+ <td style="width: 50%;"><div style="text-align: center;"><a href="help.php"><img class="pic" style="width: 32px; height: 32px;" alt="next" src="images/pics/next.png" /></a></div></td>
+ </tr>
+</tbody>
+</table>
+
+<?php include 'footer.php'; ?>
View
@@ -0,0 +1,74 @@
+<?php include 'header.php'; ?>
+<title>9. Administrator Settings (YaST) - Introduction to the YaST Setup Tool</title>
+<?php include 'header2.php'; ?>
+<?php include 'menu.php'; ?>
+
+<div class="os1"><a name="yast" class="os1">9. Administrator Settings (YaST)</a></div>
+YaST (Yet another Setup Tool) is the central tool for system administration. You find YaST in the launch menu in the System category.<br /><br />
+
+
+
+<center><a href="images/screenshots/yast-controlcenter.png" rel="thumbnail"><img src="images/screenshots/yast-controlcenterb.png" alt="yast" class="pic" /></a></center><br />
+
+<b>Default YaST modules</b><br />
+In YaST you can perform almost any system task, with powerful graphical modules, e.g.:
+<ul>
+<li>Install and remove software (see next chapter)</li>
+<li>Set up your printer</li>
+<li>Configure the firewall</li>
+<li>Enable and disable system services</li>
+<li>Configure network sharing (samba)</li>
+<li>Format and partition your drives</li>
+<li>Enable NTP daemon</li>
+<li>And much, much more...</li>
+</ul>
+
+
+<b>Additional YaST modules</b><br />
+A lot more YaST modules are available than the ones included in the default installation (read about installing packages in the next chapter). Some notable modules not installed by default are:
+
+<ul>
+<li>Apache web server (package: yast2-http-server)</li>
+<li>SSH daemon (package: yast2-sshd)</li>
+<li>FTP server (package: yast2-ftp-server)</li>
+<li>NFS server (package: yast2-nfs-server)</li>
+<li>And many more...</li>
+</ul>
+
+<div class="tip">
+<table>
+<tbody>
+<tr>
+<td><img src="images/pics/tip.png" alt="tip" /></td>
+<td>You don't have to use YaST if you don't want to. You can achieve the same things and more using command line tools and manually editing configuration files.</td>
+</tr>
+</tbody>
+</table>
+</div><br />
+
+
+<div class="os2">9.1 YaST in the Terminal</div>
+The YaST modules can also be used in a terminal (ncurses mode) - this is very useful for servers with no graphical environment running, for remote access via SSH, or in case your graphical environment fails.<br /><br />
+
+Simply run <i>yast</i> as root in a terminal.<br />
+
+<div class="clroot">yast</div><br />
+
+
+<center><a href="images/screenshots/yast-ncurses.png" rel="thumbnail"><img src="images/screenshots/yast-ncursesb.png" alt="yast-ncurses" class="pic" /></a></center><br />
+
+
+Navigate using arrow keys, Enter and Alt+[highlighted letters] (e.g. Alt+Q to quit).<br /><br />
+
+
+
+<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
+ <tbody>
+ <tr>
+ <td style="width: 50%;"><div style="text-align: center;"><a href="command.php"><img class="pic" style="width: 32px; height: 32px;" alt="prev" src="images/pics/prev.png" /></a></div></td>
+ <td style="width: 50%;"><div style="text-align: center;"><a href="installpackage.php"><img class="pic" style="width: 32px; height: 32px;" alt="next" src="images/pics/next.png" /></a></div></td>
+ </tr>
+</tbody>
+</table>
+
+<?php include 'footer.php'; ?>

0 comments on commit b018fcf

Please sign in to comment.