LQWiki - User contributions [en]

Burning a CDROM from an ISO file

2004-03-06T15:11:11Z

Dud:

== Burning a CDROM from an ISO file ==

=== Burning a CDROM under kernel verion 2.4 or less ===

To burn a CDROM under kernel version 2.4 or less, make sure that you have the ide-scsi kernel module loaded at startup. This is most easily done by adding:

hdc=ide-scsi

to the kernel line of your boot loader ([[GRUB]] or [[LILO]]), if your CD writer is the secondary master in your IDE setup.

The cdrecord command for burning a CDROM is as follows:

cdrecord -v device=0,0,0 fs=64M speed=16 driveropts=burnproof NameOfISOFile

The command:

cdrecord --scanbus

will show you the SCSI devices you have, useful if you
have more than one and your CD burner is not at 0,0,0.

See section on 'cdrecord options' for explanation.

=== Burning a CDROM under kernel version 2.6 or later ===

To burn a CDROM under kernel version 2.6, you can just invoke the cdrecord command. Below is a sample cdrecord command with useful options set. See 'cdrecord options' for explanation.

cdrecord -v device=ATAPI:0,0,0 fs=64M speed=16 driveropts=burnproof NameOfISOFile

=== Options for the cdrecord command ===

* The '-v' option makes cdrecord more verbose, so you can see what is going on, and it will show progress as it writes the CD.

* The device option will tell cdrecord where to find your CD writer. You may need to adjust it if you have more than one CD drive. If you have a CD drive and a CD writer, the device line might become: 0,1,0.

* The 'fs' option indicates how large the buffer should be. 64 megabytes gives a nice large margin. Most computers have 256 MB or more anyways, so this is not a problem.

* Speed is fairly obvious. The cdrecord program will take the maxium speed between what you specified and what the cd-recordable is able to do (cdrecord will find this out from looking at the cd-recordable).

* Most newer CD writers have a buffer underrun protection feature, where the drive will stop or slow down if the data being fed to it is not fast enough. This feature can be enabled with the 'driveropts=burnproof' option (on all writers having such a feature, even if they might not call it 'burnproof').

* The last argument is the name of the isofile you downloaded or perhaps made with [[mkisofs]].

Burning a CDROM from an ISO file

2004-03-06T15:10:34Z

Dud: added mention of cdrecord --scanbus

== Burning a CDROM from an ISO file ==

=== Burning a CDROM under kernel verion 2.4 or less ===

To burn a CDROM under kernel version 2.4 or less, make sure that you have the ide-scsi kernel module loaded at startup. This is most easily done by adding:

hdc=ide-scsi

to the kernel line of your boot loader ([[GRUB]] or [[LILO]]), if your CD writer is the secondary master in your IDE setup.

The cdrecord command for burning a CDROM is as follows:

cdrecord -v device=0,0,0 fs=64M speed=16 driveropts=burnproof NameOfISOFile

cdrecord --scanbus will show you the SCSI devices you have, useful if you
have more than one and your CD burner is not at 0,0,0.

See section on 'cdrecord options' for explanation.

=== Burning a CDROM under kernel version 2.6 or later ===

To burn a CDROM under kernel version 2.6, you can just invoke the cdrecord command. Below is a sample cdrecord command with useful options set. See 'cdrecord options' for explanation.

cdrecord -v device=ATAPI:0,0,0 fs=64M speed=16 driveropts=burnproof NameOfISOFile

=== Options for the cdrecord command ===

* The '-v' option makes cdrecord more verbose, so you can see what is going on, and it will show progress as it writes the CD.

* The device option will tell cdrecord where to find your CD writer. You may need to adjust it if you have more than one CD drive. If you have a CD drive and a CD writer, the device line might become: 0,1,0.

* The 'fs' option indicates how large the buffer should be. 64 megabytes gives a nice large margin. Most computers have 256 MB or more anyways, so this is not a problem.

* Speed is fairly obvious. The cdrecord program will take the maxium speed between what you specified and what the cd-recordable is able to do (cdrecord will find this out from looking at the cd-recordable).

* Most newer CD writers have a buffer underrun protection feature, where the drive will stop or slow down if the data being fed to it is not fast enough. This feature can be enabled with the 'driveropts=burnproof' option (on all writers having such a feature, even if they might not call it 'burnproof').

* The last argument is the name of the isofile you downloaded or perhaps made with [[mkisofs]].

Networking

2004-03-06T05:00:43Z

Dud:

Networking computers is often easier than people think. This section is dedicated to helping with basic network and network application setup.

* [[Networking basics]] - Setting up your first network can be tricky. Here are some tips that can help.
**[[Network Addressing]]
**[[Set up modem|Setting up your modem]]
**[[Set up DSL|Setting up broadband]]
***[[Set up PPoE|Setting up broadband using PPoE]]
* [[Advanced Networking]] - Networking for the more adventurous.
* [[Wireless networking]] - Setting up your linux box to access a wireless network.
* [[Web server]]s - Looking to set up a webserver? Take a look here.
* [[Samba]] - Information on sharing files and printers between linux and Windows machines.
* [[Remote Desktop Connection]] - Connect to other computers with vnc, ssh, telnet.
* [[Netatalk]] - Information on sharing files and printers between linux and Macintosh machines.

User:Dud

2004-03-06T00:11:44Z

Dud: initial content.

I'm a professional programmer, work mostly in Perl and C.
I'm interested in contributing all those nuggets that I had to search
Google Groups for in order to get stuff working.

LQWiki:Section suggestions

2004-03-06T00:10:10Z

Dud: added attribution, comment about digital camera suggestion

Please post any ideas you have for new sections below.

How about a Hardware topic. I have an xmodmap for my labtec keyboard and instructions how to bind a keyboard's special keys but no topic under which to post them.
[[User:koody]]

----

Some section for kernel questions "how to get suspend to disk work", "whats needed to get irda working", "how do I get pictures out of my digital camera" might be interesting. <-- perhaps this should be in a FAQ or something,
use of a digital camera is not really a kernel question.

[[User:pavel]]

Also: how to get ps2 mouse running in 2.6 kernel

Also: how to get swap working again in 2.6 kernel

[[User:dud]]
----

how about "in the court room". issues such as OS software legalities, SCO v. Linux, OS v. *, licensing, etc, but strictly based on a legal view.

[[User:danZenie|danZenie]]
----
How about a section on "Storage configuration". I can contribute material on Linux Software RAID, LVM, and possibly material comparing the various supported file systems.

[[User:Texastwister|Texastwister]] 14:07, Mar 3, 2004 (EST)

----
Perhaps a section on the best way to install gnome from scratch, with a list of dependency etc would be very useful (to me it would have been anyway). Unfortunately I do not have the expertise/time to do this. Anyone who takes up the buck will have my support.

[[User:Geniarse|generic_genus]] 03:33, Mar 2, 2004 (EST)
----

I would love to see a section for "ex-windows power users". For people who know what has to be done and how to do it in windows, but not yet how it is done in Linux. This would 'tasks equivalent' list partner to the software equivalent list available at http://linuxshop.ru/linuxbegin/win-lin-soft-en/table.shtml

The key advantage of a task equivlent list would be ex-windows people would be able to search on key words which they already know to find the linux method of performing the task. Quite a lot of the time I have taken to learn linux was taken up by just finding which keyword to seach on. One complication I've identified so far - we'll need instructions for the CLI, KDE & Gnome, but it would probably complicate things too much to support all the oher desktops etc out there...

An example of a few items to get started:

===================== 
Set File Associations 
=====================

In Windows 
Explorer | Tools | Folder Options | File Types

In Linux 
Configuration | KDE | Components | File Associations

Gnome instructions go here...

===================== 
Clear Browser History 
=====================

Windows IE

Internet Explorer | Tools | Internet Options | General Tab | Clear History

Linux

KDE 
The history is stored in ~/.kde/share/apps/konqueror/konq_history
To Clear Go Konqueror | Setting Configure Conqueror | History Sidebar (9th item down on left side panel) | Clear History

================== 
Kill a crashed App 
==================

In Windows
Ctrl-Alt-Delete

In Linux
Ctrl-Esc bring up a task list, and allows the user to select and kill a process.

Ctrl=Alt-Esc invokes XKill, which changes the cursor to Skull & Crossbones - and allows the user to kill a program by positioning the cursor over the crashed program and clicking to kill it.

----

I apologize for editing your comments (which I definitely don't think should be done as a general rule) but all I did was remove the excessive equal signs and put breaks in where your text indicated you wanted them. No need for pages that would be broken on anything but 1600x1200 or higher.

Quote: 
In Windows 
Explorer | Tools | Folder Options | File Types

In Linux 
Configuration | KDE | Components | File Associations

Impossible, really. That's not how Linux works. You don't 'set file associations in Linux'. Setting that varies from KDE to Gnome to non-IDEs and from file manager to file manager. You set file associations in midnight commander and gentoo and emelfm and and and. If you set file associations at all. bash has no file associations. But something like that could be very useful - it's a good idea. It'd just have to be carefully done and require a lot of qualifying - lots of ifs, ands, and buts. 'There's more than one way to do it' and Linux isn't so much about following a rote set of steps. Even './configure, make, make install' is excessive simplification.

BTW, it's customary to separate and sign comments.

[[User:Digiot|Digiot]] 06:50, Mar 1, 2004 (EST)

----

How about a section on hardware. A place to let other know about what will work or not work. I have been playing with an old Zaurus that I got off ebay aand could have used a couple of pointers on the little things that go with it. I learned at least one thing not to do!

pben

:http://www.linuxquestions.org/hcl/index.php
:[[User:Jeremy|Jeremy]] 18:21, Mar 3, 2004 (EST)
----

Remember, you can sign your name with 4 tildes on an empty line like below:

<nowiki>~~~~</nowiki>

[[User:Skyline|Skyline]] 22:29, Mar 2, 2004 (EST)

----

I'd like to see a section on Hardware Installation that then branched out into things like configuring ALSA or OSS for soundcards or SANE for scanners. Things like that would be helpful, IMHO.

Oh, and it might be nice to block ads from Microsoft.com in the google ads. There's one now advertising "Get The Facts". I personally could do without seeing that. I'm trying to avoid high-blood pressure.

[[User:Flickerfly|Flickerfly]] 09:27, Mar 5, 2004 (EST)

I would like a section on hardware issues (ie: FuBar DVD writer works with Kernal 2.6.XX and up.

[[User:Kenng|Kenng]] 18:08, Mar 5, 2004 (EST)

I agree, it would be nice to have hardware, possible sorted by both type and brand. The hardest thing I have had to do with linux was getting it to work with my hardware (installing ALSA, Nvidia, Logitech drivers). Because wikis can become so expansive it could become a great 1 stop resource, with very specific instructions and up to date links to the drivers
[[User:Platinum1|Platinum1]] 15:28, Mar 5, 2004 (PST)

Hardware, definitely [[User:Damas|Damas]]

----
"Installing Linux" seems to be conspicuously absent. I think that would be one of the first things a novice would look for. I imagine the topic would branch off into specific instructions for each of the various distros.

[[User:Alanyst|Alanyst]] 18:49, Mar 5, 2004 (EST)

LQWiki:Section suggestions

2004-03-06T00:07:28Z

Dud: added more kernel suggestions

Please post any ideas you have for new sections below.

How about a Hardware topic. I have an xmodmap for my labtec keyboard and instructions how to bind a keyboard's special keys but no topic under which to post them.
[[User:koody]]

----

Some section for kernel questions "how to get suspend to disk work", "whats needed to get irda working", "how do I get pictures out of my digital camera" might be interesting.

[[User:pavel]]

Also: how to get ps2 mouse running in 2.6 kernel

Also: how to get swap working again in 2.6 kernel

----

how about "in the court room". issues such as OS software legalities, SCO v. Linux, OS v. *, licensing, etc, but strictly based on a legal view.

[[User:danZenie|danZenie]]
----
How about a section on "Storage configuration". I can contribute material on Linux Software RAID, LVM, and possibly material comparing the various supported file systems.

[[User:Texastwister|Texastwister]] 14:07, Mar 3, 2004 (EST)

----
Perhaps a section on the best way to install gnome from scratch, with a list of dependency etc would be very useful (to me it would have been anyway). Unfortunately I do not have the expertise/time to do this. Anyone who takes up the buck will have my support.

[[User:Geniarse|generic_genus]] 03:33, Mar 2, 2004 (EST)
----

I would love to see a section for "ex-windows power users". For people who know what has to be done and how to do it in windows, but not yet how it is done in Linux. This would 'tasks equivalent' list partner to the software equivalent list available at http://linuxshop.ru/linuxbegin/win-lin-soft-en/table.shtml

The key advantage of a task equivlent list would be ex-windows people would be able to search on key words which they already know to find the linux method of performing the task. Quite a lot of the time I have taken to learn linux was taken up by just finding which keyword to seach on. One complication I've identified so far - we'll need instructions for the CLI, KDE & Gnome, but it would probably complicate things too much to support all the oher desktops etc out there...

An example of a few items to get started:

===================== 
Set File Associations 
=====================

In Windows 
Explorer | Tools | Folder Options | File Types

In Linux 
Configuration | KDE | Components | File Associations

Gnome instructions go here...

===================== 
Clear Browser History 
=====================

Windows IE

Internet Explorer | Tools | Internet Options | General Tab | Clear History

Linux

KDE 
The history is stored in ~/.kde/share/apps/konqueror/konq_history
To Clear Go Konqueror | Setting Configure Conqueror | History Sidebar (9th item down on left side panel) | Clear History

================== 
Kill a crashed App 
==================

In Windows
Ctrl-Alt-Delete

In Linux
Ctrl-Esc bring up a task list, and allows the user to select and kill a process.

Ctrl=Alt-Esc invokes XKill, which changes the cursor to Skull & Crossbones - and allows the user to kill a program by positioning the cursor over the crashed program and clicking to kill it.

----

I apologize for editing your comments (which I definitely don't think should be done as a general rule) but all I did was remove the excessive equal signs and put breaks in where your text indicated you wanted them. No need for pages that would be broken on anything but 1600x1200 or higher.

Quote: 
In Windows 
Explorer | Tools | Folder Options | File Types

In Linux 
Configuration | KDE | Components | File Associations

Impossible, really. That's not how Linux works. You don't 'set file associations in Linux'. Setting that varies from KDE to Gnome to non-IDEs and from file manager to file manager. You set file associations in midnight commander and gentoo and emelfm and and and. If you set file associations at all. bash has no file associations. But something like that could be very useful - it's a good idea. It'd just have to be carefully done and require a lot of qualifying - lots of ifs, ands, and buts. 'There's more than one way to do it' and Linux isn't so much about following a rote set of steps. Even './configure, make, make install' is excessive simplification.

BTW, it's customary to separate and sign comments.

[[User:Digiot|Digiot]] 06:50, Mar 1, 2004 (EST)

----

How about a section on hardware. A place to let other know about what will work or not work. I have been playing with an old Zaurus that I got off ebay aand could have used a couple of pointers on the little things that go with it. I learned at least one thing not to do!

pben

:http://www.linuxquestions.org/hcl/index.php
:[[User:Jeremy|Jeremy]] 18:21, Mar 3, 2004 (EST)
----

Remember, you can sign your name with 4 tildes on an empty line like below:

<nowiki>~~~~</nowiki>

[[User:Skyline|Skyline]] 22:29, Mar 2, 2004 (EST)

----

I'd like to see a section on Hardware Installation that then branched out into things like configuring ALSA or OSS for soundcards or SANE for scanners. Things like that would be helpful, IMHO.

Oh, and it might be nice to block ads from Microsoft.com in the google ads. There's one now advertising "Get The Facts". I personally could do without seeing that. I'm trying to avoid high-blood pressure.

[[User:Flickerfly|Flickerfly]] 09:27, Mar 5, 2004 (EST)

I would like a section on hardware issues (ie: FuBar DVD writer works with Kernal 2.6.XX and up.

[[User:Kenng|Kenng]] 18:08, Mar 5, 2004 (EST)

I agree, it would be nice to have hardware, possible sorted by both type and brand. The hardest thing I have had to do with linux was getting it to work with my hardware (installing ALSA, Nvidia, Logitech drivers). Because wikis can become so expansive it could become a great 1 stop resource, with very specific instructions and up to date links to the drivers
[[User:Platinum1|Platinum1]] 15:28, Mar 5, 2004 (PST)

Hardware, definitely [[User:Damas|Damas]]

----
"Installing Linux" seems to be conspicuously absent. I think that would be one of the first things a novice would look for. I imagine the topic would branch off into specific instructions for each of the various distros.

[[User:Alanyst|Alanyst]] 18:49, Mar 5, 2004 (EST)

LQWiki:Section suggestions

2004-03-06T00:06:35Z

Dud:

Please post any ideas you have for new sections below.

How about a Hardware topic. I have an xmodmap for my labtec keyboard and instructions how to bind a keyboard's special keys but no topic under which to post them.
[[User:koody]]

----

Some section for kernel questions "how to get suspend to disk work", "whats needed to get irda working", "how do I get pictures out of my digital camera" might be interesting.

[[User:pavel]]

Also: how to get ps2 mouse running in 2.6 kernel
how to get swap working again in 2.6 kernel

----

how about "in the court room". issues such as OS software legalities, SCO v. Linux, OS v. *, licensing, etc, but strictly based on a legal view.

[[User:danZenie|danZenie]]
----
How about a section on "Storage configuration". I can contribute material on Linux Software RAID, LVM, and possibly material comparing the various supported file systems.

[[User:Texastwister|Texastwister]] 14:07, Mar 3, 2004 (EST)

----
Perhaps a section on the best way to install gnome from scratch, with a list of dependency etc would be very useful (to me it would have been anyway). Unfortunately I do not have the expertise/time to do this. Anyone who takes up the buck will have my support.

[[User:Geniarse|generic_genus]] 03:33, Mar 2, 2004 (EST)
----

I would love to see a section for "ex-windows power users". For people who know what has to be done and how to do it in windows, but not yet how it is done in Linux. This would 'tasks equivalent' list partner to the software equivalent list available at http://linuxshop.ru/linuxbegin/win-lin-soft-en/table.shtml

The key advantage of a task equivlent list would be ex-windows people would be able to search on key words which they already know to find the linux method of performing the task. Quite a lot of the time I have taken to learn linux was taken up by just finding which keyword to seach on. One complication I've identified so far - we'll need instructions for the CLI, KDE & Gnome, but it would probably complicate things too much to support all the oher desktops etc out there...

An example of a few items to get started:

===================== 
Set File Associations 
=====================

In Windows 
Explorer | Tools | Folder Options | File Types

In Linux 
Configuration | KDE | Components | File Associations

Gnome instructions go here...

===================== 
Clear Browser History 
=====================

Windows IE

Internet Explorer | Tools | Internet Options | General Tab | Clear History

Linux

KDE 
The history is stored in ~/.kde/share/apps/konqueror/konq_history
To Clear Go Konqueror | Setting Configure Conqueror | History Sidebar (9th item down on left side panel) | Clear History

================== 
Kill a crashed App 
==================

In Windows
Ctrl-Alt-Delete

In Linux
Ctrl-Esc bring up a task list, and allows the user to select and kill a process.

Ctrl=Alt-Esc invokes XKill, which changes the cursor to Skull & Crossbones - and allows the user to kill a program by positioning the cursor over the crashed program and clicking to kill it.

----

I apologize for editing your comments (which I definitely don't think should be done as a general rule) but all I did was remove the excessive equal signs and put breaks in where your text indicated you wanted them. No need for pages that would be broken on anything but 1600x1200 or higher.

Quote: 
In Windows 
Explorer | Tools | Folder Options | File Types

In Linux 
Configuration | KDE | Components | File Associations

Impossible, really. That's not how Linux works. You don't 'set file associations in Linux'. Setting that varies from KDE to Gnome to non-IDEs and from file manager to file manager. You set file associations in midnight commander and gentoo and emelfm and and and. If you set file associations at all. bash has no file associations. But something like that could be very useful - it's a good idea. It'd just have to be carefully done and require a lot of qualifying - lots of ifs, ands, and buts. 'There's more than one way to do it' and Linux isn't so much about following a rote set of steps. Even './configure, make, make install' is excessive simplification.

BTW, it's customary to separate and sign comments.

[[User:Digiot|Digiot]] 06:50, Mar 1, 2004 (EST)

----

How about a section on hardware. A place to let other know about what will work or not work. I have been playing with an old Zaurus that I got off ebay aand could have used a couple of pointers on the little things that go with it. I learned at least one thing not to do!

pben

:http://www.linuxquestions.org/hcl/index.php
:[[User:Jeremy|Jeremy]] 18:21, Mar 3, 2004 (EST)
----

Remember, you can sign your name with 4 tildes on an empty line like below:

<nowiki>~~~~</nowiki>

[[User:Skyline|Skyline]] 22:29, Mar 2, 2004 (EST)

----

I'd like to see a section on Hardware Installation that then branched out into things like configuring ALSA or OSS for soundcards or SANE for scanners. Things like that would be helpful, IMHO.

Oh, and it might be nice to block ads from Microsoft.com in the google ads. There's one now advertising "Get The Facts". I personally could do without seeing that. I'm trying to avoid high-blood pressure.

[[User:Flickerfly|Flickerfly]] 09:27, Mar 5, 2004 (EST)

I would like a section on hardware issues (ie: FuBar DVD writer works with Kernal 2.6.XX and up.

[[User:Kenng|Kenng]] 18:08, Mar 5, 2004 (EST)

I agree, it would be nice to have hardware, possible sorted by both type and brand. The hardest thing I have had to do with linux was getting it to work with my hardware (installing ALSA, Nvidia, Logitech drivers). Because wikis can become so expansive it could become a great 1 stop resource, with very specific instructions and up to date links to the drivers
[[User:Platinum1|Platinum1]] 15:28, Mar 5, 2004 (PST)

Hardware, definitely [[User:Damas|Damas]]

----
"Installing Linux" seems to be conspicuously absent. I think that would be one of the first things a novice would look for. I imagine the topic would branch off into specific instructions for each of the various distros.

[[User:Alanyst|Alanyst]] 18:49, Mar 5, 2004 (EST)

Flash Player(s)

2004-03-06T00:03:32Z

Dud:

A Flash Player is a program that displays animations available in [[Flash Format]] (typically file names end with the letters .swf ). These programs run under [[X-Windows]] and are typically run as [[Browser Helper Applications]].

INSTALLATION NOTE: If you have Depth < 16 in your XF86Config-4,
then all the flash player plugins will crash and burn when you load
a page containing flash. (True for Konqueror and Mozilla).

Flash Player(s)

2004-03-06T00:03:15Z

Dud:

A Flash Player is a program that displays animations available in [[Flash Format]] (typically file names end with the letters .swf ). These programs run under [[X-Windows]] and are typically run as [[Browser Helper Applications]].
pl
INSTALLATION NOTE: If you have Depth < 16 in your XF86Config-4,
then all the flash player plugins will crash and burn when you load
a page containing flash. (True for Konqueror and Mozilla).

Plugins

2004-03-06T00:02:15Z

Dud:

[[Flash Player(s)]], [[mplayer-plugin]]

Web browser

2004-03-06T00:01:16Z

Dud:

[[plugins]], [[Flash Player(s)]]

Flash Player(s)

2004-03-05T23:51:23Z

Dud: Added warning about installing flashplayer.

INSTALLATION NOTE: If you have DisplayDepth < 16 in your XF86Config-4,
then all the flash player plugins will crash and burn when you load
a page containing flash. (True for Konqueror and Mozilla).

Web browser

2004-03-05T23:49:56Z

Dud: Added Flash Player(s)

[[Mozilla]], [[Firefox]], [[Opera]], [[Konqueror]], [[Flash Player(s)]]