kernel 2.6.12.3 compilation problem

glussier · 08-08-2005, 02:07 PM

And why would I want to run bash and vncviewer under windows?

If you think I'm not a slackware user, I have 3 computers running slackware 10.1 at home at more than 2 dozens at the office, which btw is my own company. I'm never tried to prove that slackware was not a good o/s and have nothing to prove you. Geez look at your processes there's not much in there taking that much resources from your computer.

rkrishna · 08-08-2005, 11:58 PM

ok friends

now everything is ok can i remove my source files from /usr/src after the kernel is installed??
will that cause any problem.
%actually there is no need to copy the source to /usr/src so why should i clean tht

gbonvehi · 08-09-2005, 12:37 AM

rkrishna you can remove the sources, but may be needed to compile some module, like nvidia or ati drivers.

rkrishna · 08-09-2005, 01:57 AM

now onwards i will compile sources from my home folder only

if i want to apply patches, i must keep tht source there isn't it??
now i have sources in /home/.../build/linu..2.6.12.3 and in /usr/src/ in /usr/src/lin 2.4 and 2.6 sources resides

in home tehre are lot of space around 60gb tht is nice to unload kernel sources to home

thnks for conformation

Bruce Hill · 08-09-2005, 02:57 AM

Do not remove your original kernel source from /usr/src and please
read my quote from Linus Torvalds in post #3.

rkrishna · 08-09-2005, 04:06 AM

forgot abt tht post now remember ok nice suggection

when will u posting or putting a web page "how t compile new 2.6... kernel efficently" include applying patches also
regards

Bruce Hill · 08-09-2005, 07:49 AM

There is some entropy that you can remove from previous compiles.

This is what you had when you installed Slackware:

Code:

mingdao@james:~$ ls -alh /usr/src/
total 1.0K
drwxr-xr-x   5 root root 160 2005-03-31 02:05 ./
drwxr-xr-x  18 root root 520 2004-10-11 07:55 ../
lrwxrwxrwx   1 root root  12 2005-03-31 02:05 linux -> linux-2.4.29/
drwxr-xr-x  15 root root 584 2005-01-21 03:41 linux-2.4.29/
drwxr-xr-x   7 root root 168 2003-10-29 14:08 rpm/
drwxr-xr-x   2 root root 176 2005-01-21 06:31 speakup-2.4.29/

Now I've compiled at least 10 kernel versions, and some more than
once since I installed Slackware, and haven't added anything to my
/usr/src/ directory.

If you didn't restore the linux -> linux-2.4.29/ symlink as I told you
earlier, you should do that.

You can safely get rid of rpm/ and speakup-2.4.29/ by issuing
"rm -rf /usr/src/rpm/"
"rm -rf /usr/src/speakup-2.4.29/"

Looking at "ls -al /usr/src/" from your earlier post you can also
"rm -rf /usr/src/linux-2.6.12.3"

Next let's look at your /boot/ directory. You only need the default kernel
and the one you're running, but may keep others if you want them. I am
not saying I do everything correctly, but here is what my /boot/ looks like:

Code:

mingdao@james:~/build$ ls -alh /boot/
total 16M
drwxr-xr-x   3 root root  808 2005-08-07 07:33 ./
drwxr-xr-x  22 root root  568 2005-08-08 08:22 ../
lrwxrwxrwx   1 root root   37 2005-03-31 02:03 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
lrwxrwxrwx   1 root root   25 2005-08-07 07:17 System.map -> /boot/System.map-2.6.12.4
-rw-r--r--   1 root root 795K 2005-05-30 21:43 System.map-2.6.11.11
-rw-r--r--   1 root root 802K 2005-04-09 17:38 System.map-2.6.11.6
-rw-r--r--   1 root root 829K 2005-06-19 08:56 System.map-2.6.12
-rw-r--r--   1 root root 796K 2005-07-22 18:23 System.map-2.6.12.1
-rw-r--r--   1 root root 785K 2005-07-05 19:32 System.map-2.6.12.2
-rw-r--r--   1 root root 730K 2005-08-07 05:35 System.map-2.6.12.3
-rw-r--r--   1 root root 730K 2005-08-07 07:17 System.map-2.6.12.4
-rw-r--r--   1 root root  512 2005-03-30 18:39 boot.0300
-rw-r--r--   1 root root  30K 2005-05-30 21:56 config-2.6.11.11
-rw-r--r--   1 root root  30K 2005-04-09 17:38 config-2.6.11.6
-rw-r--r--   1 root root 5.0K 2004-05-21 15:19 diag1.img
-rw-------   1 root root 138K 2005-08-07 07:33 map
-rw-r--r--   1 root root  11K 2005-08-07 07:28 slack.bmp
-rw-r--r--   1 root root 1.5M 2005-05-30 21:43 vmlinuz-2.6.11.11
-rw-r--r--   1 root root 1.5M 2005-04-09 17:38 vmlinuz-2.6.11.6
-rw-r--r--   1 root root 1.6M 2005-06-19 08:57 vmlinuz-2.6.12
-rw-r--r--   1 root root 1.5M 2005-07-22 18:24 vmlinuz-2.6.12.1
-rw-r--r--   1 root root 1.4M 2005-07-05 19:33 vmlinuz-2.6.12.2
-rw-r--r--   1 root root 1.4M 2005-08-07 05:35 vmlinuz-2.6.12.3
-rw-r--r--   1 root root 1.4M 2005-08-07 07:18 vmlinuz-2.6.12.4

I certainly don't need all those kernels, but I keep them anyway. The main
reason is when somebody says, "I'm running Slackware with kernel <blah>
and my <hardware> isn't recognized / doesn't work, etc. I can sometimes
boot into one of those old kernels and see what happens on my box. I am
not concerned about space, as this computer has a 60GB IDE drive and an
80GB SATA drive; and it's backed up to my server's 250GB SATA drive. So for
me to keep a few extra kernel images and module directories around isn't a
concern at this point. Also, whenever I read that something works for another
person in kernel-blah and it doesn't work as well in my present kernel, I can
go check.

That is my workstation, and I don't have a 2.4.x kernel because I nuked it
during a Slackware -current update and didn't bother restoring it because
I don't use 2.4.x on here anymore.

On my server, which I recently upgraded, there is only the default 2.4.29
and a custom 2.4.31 kernel:

Code:

mingdao@paul:/backup/ISO$ ls -alh /boot/               
total 4.9M
drwxr-xr-x   2 root root  504 2005-07-31 08:09 ./
drwxrwxr-x  19 root root  432 2005-08-06 18:47 ../
lrwxrwxrwx   1 root root   37 2005-07-30 03:07 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
lrwxrwxrwx   1 root root   23 2005-07-31 08:06 System.map -> /boot/System.map-2.4.31
-rw-r--r--   1 root root 572K 2005-07-31 07:54 System.map-2.4.31
-rw-r--r--   1 root root 594K 2005-01-21 12:24 System.map-ide-2.4.29
-rw-r--r--   1 root root  512 2005-07-30 06:08 boot.0300
-rw-r--r--   1 root root  512 2005-07-30 06:08 boot.0810
-rw-r--r--   1 root root 1.2M 2005-07-31 07:53 bzImage-2.4.31
lrwxrwxrwx   1 root root   19 2005-07-31 08:07 config -> /boot/config-2.4.31
-rw-r--r--   1 root root  24K 2005-07-31 07:54 config-2.4.31
-rw-r--r--   1 root root  41K 2005-01-21 12:24 config-ide-2.4.29
-rw-r--r--   1 root root 5.0K 2004-05-21 15:19 diag1.img
-rw-------   1 root root  39K 2005-07-31 08:09 map
-r--------   1 root root 1.3M 2005-07-30 03:23 vmlinuz
-rw-r--r--   1 root root 1.2M 2005-01-21 12:24 vmlinuz-ide-2.4.29

He boots and runs on bzImage-2.4.31, and I might add, there is not one
error message in his log after booting. I also run him without any modules
by preference. He has some hardware, such as IEEE 1394, which I haven't
configured by design.

As for module directories, you can issue and look at "ls -alh /lib/modules/"

Code:

mingdao@paul:/backup/ISO$ ls -alh /lib/modules/
total 5.0K
drwxr-xr-x  4 root root   96 2005-07-31 07:52 ./
drwxr-xr-x  4 root root 3.2K 2005-07-30 03:11 ../
drwxr-xr-x  4 root root  416 2005-01-21 12:47 2.4.29/
drwxr-xr-x  4 root root  416 2005-07-31 07:52 2.4.31/

That's where all the modules go when you compile a kernel. If you remember
that /lib/modules/2.6.12.3test/ directory you referenced earlier, I'll imagine it
is still there. You should also have a new /lib/modules/2.6.12.3/ that is from
your latest kernel. You can safely remove any that correspond to a kernel you
will not run by issuing, for instance:
"rm -rf /lib/modules/2.6.12.3test/"
NB: You must not remove a module directory for a kernel that you still use.

And for patching, Linus wrote instructions for that, too. From ./linux-2.6.12.3/README

Quote:

- You can also upgrade between 2.6.xx releases by patching. Patches are
distributed in the traditional gzip and the new bzip2 format. To
install by patching, get all the newer patch files, enter the
top level directory of the kernel source (linux-2.6.xx) and execute:

gzip -cd ../patch-2.6.xx.gz | patch -p1

or
bzip2 -dc ../patch-2.6.xx.bz2 | patch -p1

(repeat xx for all versions bigger than the version of your current
source tree, _in_order_) and you should be ok. You may want to remove
the backup files (xxx~ or xxx.orig), and make sure that there are no
failed patches (xxx# or xxx.rej). If there are, either you or me has
made a mistake.

Alternatively, the script patch-kernel can be used to automate this
process. It determines the current kernel version and applies any
patches found.

linux/scripts/patch-kernel linux

The first argument in the command above is the location of the
kernel source. Patches are applied from the current directory, but
an alternative directory can be specified as the second argument

I've never patched a kernel, so I'll make no other comments except to say
that the patch file should be placed in the same directory as the kernel
source that you're patching. For your present kernel I presume that it's
under /home somewhere named ./linux-2.6.12.3/

As for posting a Kernel Build HOW-TO, I'll do that later on my website so
that I don't have to be bothered with all the guys like glussier there who
want to disagree with me, but don't have any technical information or even
some data for discussion. As far as I'm concerned, the instructions by Linus
are good enough, and the other things we need to do are obtained from
sources on the internet. I'd just like to tie them all together, give some good
references, and leave it there.

I'm glad you got your kernel compiled, and hope you soon get your Slackware
OS configured and tweaked to your desire.

If you have any more questions about these things, post the output of "ls -al"
on the directory and we'll help.

BroX · 08-09-2005, 08:38 AM

Quote:

Originally posted by Chinaman
This may sound like drastic measures to you, but I would:
1) su - (switch user to root and root's environment)
2) cd /usr/src
3) rm linux
4) ln -s /usr/src/linux /usr/src/linux-2.4.29
5) print or at least save your 2.6.12.3 .config file to read, but not to use in your system
6) rm -rf linux-2.6.12.3
Then make a directory for building kernels, since it sounds like
you are ready to do that on your system. From /home/<username>
"mkdir /home/<username>/build/"
and then copy linux-2.6.12.3.tar.bz2 into that directory from
wherever it is now; then untar it by issuing as a normal user
"tar -xvjf linux-2.6.12.3.tar.bz2" then "cd linux-2.6.12.3" and
now we're ready to start fresh.

Chinaman,

after reading every so often about the "proper" way to compile kernels I decided to do it like that. Eventhough I never ran into problems with using the sources and link in /usr/src/. So from now on I compile in my home directory.

Question: I don't have the original 2.4.29 source in /usr/src/ anymore, but I still have the kernel and modules around. How/Should I restore the source to the original state? If I install the header files will that do?

I am now running 2.6.12.4, and /usr/src shows

Code:

bash-3.00$ ll /usr/src/
total 512
lrwxrwxrwx   1 root root  14 Jul 18 12:25 linux -> linux-2.6.12.3
drwxr-xr-x  18 root root 736 Aug  8 00:53 linux-2.6.12.3
bash-3.00$

Is there a reason to replace it with the earlier 2.4.29 or should it be 2.6.*???

Cheers, Leon.

keefaz · 08-09-2005, 08:46 AM

If you want you could rm /usr/src/linux ; rm -r /usr/src/linux-2.6.12.3
and install kernel-source pkg

Chinaman, I consider I use slackware 10.2 since the new slackpkg
mirrors file points to pub/slackware/slackware-10.2/

Bruce Hill · 08-09-2005, 09:19 AM

Quote:

Originally posted by keefaz
Chinaman, I consider I use slackware 10.2 since the new slackpkg
mirrors file points to pub/slackware/slackware-10.2/

I'm not familiar with that mirror. I believe this is the Official Slackware ftp server
ftp://ftp.slackware.com/pub/slackware/

rkrishna · 08-10-2005, 01:53 PM

here is the cdrecord scanbus
bash-3.00# cdrecord -scanbus
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.12.3
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
****************
but i could write it by right clicking the iso and write to cd

from gnome i could put the folder to burn:/// so some problem
*******************
i will all add append to lilo and check it later %i thought for 2.6 there is no need for scsi emulation

scsci emulation--i hope i had enabled it
#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set

#
# SCSI low-level drivers
#
CONFIG_BLK_DEV_3W_XXXX_RAID=m
# CONFIG_SCSI_3W_9XXX is not set
CONFIG_SCSI_7000FASST=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AHA152X=m
CONFIG_SCSI_AHA1542=m
# CONFIG_SCSI_AHA1740 is not set
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_PROBE_EISA_VL is not set
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_ENABLE_RD_STRM is not set
CONFIG_AIC79XX_DEBUG_ENABLE=y
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_DPT_I2O is not set
CONFIG_SCSI_IN2000=m
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_AHCI=m
CONFIG_SCSI_SATA_SVW=m
CONFIG_SCSI_ATA_PIIX=m
# CONFIG_SCSI_SATA_NV is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
CONFIG_SCSI_IPS=m
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

Bruce Hill · 08-10-2005, 05:41 PM

Yes, forget about SCSI emulation for 2.6.x.x. It uses device
names, such as /dev/hdc for your burners. You have what
you need > CONFIG_BLK_DEV_IDECD=y

To find your drive, if you don't already know the controller:
mingdao@paul:/backup$ dmesg | grep -i dvd
hdc: ASUS CD-S520/A, ATAPI CD/DVD-ROM drive
(Even if it's just a CD-ROM, it will still find it with 'dvd'.)

No need for "append=ide-scsi <blah>" in 2.6.x.x. Actually, you
don't need it for kernel 2.4.27 > iirc.

And I don't know how this works "but i could write it by right
clicking the iso and write to cd" Maybe because I use Fluxbox
and read files in xterm, and there is nothing to right-click.

Here are some commands I use from a terminal. Things work
more efficiently when you don't use a GUI interface, and you
are saved from those 'mouse fests' ... click, click, click, click

Code:

dd if=/dev/hdc of=namethecd.iso
To burn an image of a CD to the hd

cdrecord -v -eject driveropts=burnfree dev=/dev/hdc /path/to/file.iso
To make a CD from the iso image

gzip < /dev/cdrom > cdrom.iso.gz
save copy of data cdrom

mkisofs -r dir | gzip > cdrom.iso.gz
create cdrom image from directory

mount -oloop cdrom.iso /mnt/dir
mount the cdrom image at /mnt/dir (for viewing/editing)

gzip -dc cdrom.iso.gz | cdrecord dev=/dev/cdrom -
burn cdrom image (use 'dmesg | grep -i dvd' to confirm dev)

cdparanoia -B
rip audio tracks from CD to .wav files in current dir

for i in *.wav; do lame "$i" "`basename "$i" .wav`".mp3; done
To convert .wav to .mp3

make audio CD from all wavs in current dir
cdrecord dev=/dev/cdrom -audio *.wav

oggenc --tracknum='track' track.cdda.wav -o 'track.ogg'
make ogg file from wav file

/usr/bin/growisofs -dvd-compat -Z /dev/hdb=/path/to/file.iso
To burn an iso to DVD

cdrdao copy --device /dev/hdb --source-device /dev/hdc
To copy a CD from one drive to another (good for VCDs)

I've been wanting to ask you ... what does the percent sign % in
your posts mean?

rkrishna · 08-11-2005, 06:24 AM

when in nutilus i could right click the iso and write to cd yseterday i tried by pasting files to burn: /// folder and writting both worked.. i will check waht is the problem

Quote:

I've been wanting to ask you ... what does the percent sign % in your posts mean?

actually in tex language % means comment that line, what ever coming after %is a comment, tex wont take that. this is similar to # in linux things but % can be inserted whereever u want.
so the things i wrote after %will b for reader and it is not comming in the questions

, actually write it like this usually and i thought u people also take tht in the way i do

bash-3.00$ dmesg |grep -i dvd
hda: HL-DT-ST RW/DVD GCC-4481B, ATAPI CD/DVD-ROM drive
hda: ATAPI 48X DVD-ROM CD-R/RW drive, 2048kB Cache

bash-3.00$ cdrecord -scanbus
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schil ling
cdrecord: Warning: Running on Linux-2.6.12.3
cdrecord: There are unsettled issues with Linux-2.5 and newer. %<---- what is this
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris .
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open S CSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

i ussually write using cdrecord, i just ran cdrecord -scanbus to check what device does teh 2.6.12.3 kernel took

ok i will trY diffrent things and check, If it works i will tell bse i could write it using some othre methods

thank u for the short listing of commands, cd writer
*************
if we enable things in kernel, does it means that we are installing drivers for the same
eg. for usb to work i must enable it in the kernel, similarly for others

hi friend i will b engaged in a seminar conducted by us, in our dept so will not b available continuesly for 3-4 days

Bruce Hill · 08-11-2005, 04:48 PM

Do you mean TeX? I'm still clueless. Only languages I know with
any proficiency are English and Chinese...not a programmer.

You don't need to use that cdrecord -scanbus with 2.6.x.x because
you're using device names now. That's why I had you grep dmesg
for the location of your drive. So we see that your burner is:
hda: HL-DT-ST RW/DVD GCC-4481B, ATAPI CD/DVD-ROM drive

To burn that iso image to disc, just issue:
"cdrecord -v -eject driveropts=burnfree dev=/dev/hda /path/to/file.iso"
and you'll be surprised how quickly you have it without one single
mouse click. ;) And no screens to redraw with all those GUI images.

Quote:

cdrecord: There are unsettled issues with Linux-2.5 and newer. %<---- what is this

That is because the author of cdrecord, Jörg Schilling, refused to change
with Linus Torvalds and the Linux kernel guys. So Linus and Jens Axbode
patched the cdrecord app. It appears that Jörg Schilling is more interested
in Solaris, and the commercial apps he wrote. It's just like Micro$loth FUD,
so don't let it worry you. The issues are resolved by Linus.

Quote:

if we enable things in kernel, does it means that we are installing drivers for the same
eg. for usb to work i must enable it in the kernel, similarly for others

Yes, and they can either be built in (Y) or modules (M) for them to work.

Hope you have a great seminar!

rkrishna · 08-15-2005, 10:38 AM

Quote:

Do you mean TeX? I'm still clueles

s LateX a typestting thing i think it was originally tex, and 4 unix . but very powerfull, since i am in physics i need to type many equations, for publishing our work we need to present the things as tex files, it is like linux 4 winblogs as tex 4 word.

Quote:

You don't need to use that cdrecord -scanbus with 2.6.x.x because
you're using device names now.

nice i was searching 4 the device, now ok
it need only dev=/dev/hda instead of number, very fine

that means you cant use xcdroast in 2.6.12* hi hi but i was using cdrecord only so tht i could let the cdwriting in background. virtual terminal...

seminar was very good and i didnt even got time to look LQ and check my mails
#there was a nice professor and i had given him a copy of SlaX live cd..

i was prepearing a note from this thread about compiling kernel and the burning tricks

******@*********
thank u for the borthday wishes,

now only i saw it in inbox sorry, but it was a surprise
******!!!!!!!!!!!!!!!!
will b back soon with another threads

regards