On 8 September 1998, Tony Nugent <[EMAIL PROTECTED]> wrote:
> On Tue Sep 08 1998, Chaiya Intasoie wrote:
>
> > I am trying to make slakware35 cd. But I have some problem as
> > follow;
>
> Oh my, please don't. Don't give linux a bad name. Don't spread
> around a brain-dead linux distribution. Give away RedHat or Debian
> instead, even SuSe.
>
> [Please, no "distribution wars". This is my humble opinion, and in
> my humble opinion this is a well-informed opinion - I'm speaking from
> 5 years experience with linux, and there are many reasons why I say
> this.]
IMHO, Slackware is better than RedHat, and I'm speaking from an
equally vast experience --- 5 years with Linux, and 15 years with other
Unix systems. So what? The initial poster didn't ask what to put on
his CD, but how to write it. If you don't want a "distribution war"
then you might start by not posting statements whose only possible
effect is to open a piss contest.
> > 1. I have HP CDR which connect to my LPT1 port (printer port). I
> > can use it with my windows95/98 machine because it has some software
> > came with when I purchased.
> > *** My question: How can I use this CDR with Linux (slakware35)
>
> Read the CDROM-HOWTO. It's unusual to have a CDR on the LPT port, but
> I'd be suprised if linux didn't have a driver for it and if the howto
> doesn't mention it.
Well, in my experience things might be a bit more involved. I had
to make an EIDE HP CDR work with Linux some time ago, and it wasn't that
obvious.
Personally, I'd recommend creating the "image" of the CD with
mkisofs on Linux (see CD-Writing-HOWTO for the details), then writing
_that_ on the CD from Windows (the soft that came with the drive
should know how to do that). But if you insist on doing it entirely
from Linux, you'll have to make Linux see your drive. First, you'll
need a kernel from the 2.1 series --- the 2.0 ones don't have the
"vendor-specific extensions" needed by HP writers. Then you have
to compile it with CONFIG_BLK_DEV_IDESCSI "SCSI emulation support",
CONFIG_CHR_DEV_SG "SCSI generic support" and CONFIG_BLK_DEV_SR_VENDOR
"Enable vendor-specific extensions (for SCSI CDROM)" options. You
should also answer 'N' to CONFIG_BLK_DEV_IDECD "Include IDE/ATAPI CDROM
support", or SCSI emulation would be ignored (this is described to some
extent in CD-Writing-HOWTO, but you might need to get a bit creative in
order to apply that to your particular situation :-)). This was enough
for me for an EIDE CDR, but for a parallel port one you'll probably also
need CONFIG_PARIDE "Parallel port IDE device support", then you'll have
to experiment with the various high-level parallel drivers. My first
shot would be to try the CONFIG_PARIDE_PCD "Parallel port ATAPI CD-ROMs"
option (and then access it through /dev/pcd0, or something like that ---
you might also need to create that first with mknod). Of course, YMMV.
On a side note, if you're not running a 2.1 kernel already, beware
that switching from 2.0 to 2.1 kernels involves upgrading a few other
packages too. If you never did it before, that task might be a PITA
by itself. Read the various READMEs and HOWTOs and make sure you have
everything you need before starting to compile the new kernel.
Of course, once you can "see" the CDR from Linux (f.i. if you can
open the door of the drive with "cdwrite --eject ...", as described in
CD-Writing-HOWTO), you can use cdrecord (or whatever) to actually start
writing CDs.
[...]
> > -- I ftp all Slakware35 tree from my server with ws-ftp95 which
> > has no problem with all long filename at all.
> > -- I tried to create file like "my.first.file.txt" in windows98
> > (fat32) and it allowed.
> > *** But When I tried to write slakware Linux file like
> > autoconfig.tar.gz the software did not allow me to do that at
> > all. How can I solve this problem? I know it's the Easy CD creater
> > problem.
>
> That's a standard limitation of the iso9660 filesystem. To get around
> it, use the long names option with mkisofs (linux). And I have never
> seen any use for the RockRidge extentions (except to create those
> ugly and virtually useless TRANS.TBL files). Also enable the Joliet
> extentions.
FYI, using RockRidge extensions _is_ the standard way to write
long names on CDs under Unix. The TRANS.TBL files are there just for
reference for systems which can't read RockRidge records, they are not
really needed for reading the long names on Linux (and they are no
longer created by default by newer versions of mkisofs).
Joliet is used for writing long names in Windows world, and it has
some limitations compared to RockRidge (f.i. files don't have owners).
Linux can read both formats, most Unices can only read RockRidge CDs,
while, as you might expect, Windows can only read Joliet CDs. Also the
standard mkisofs (at least version 1.11.2 I have here) can't create
images in Joliet format --- you need a patch for that.
FWIW, here's the incantation I'm using with mkisofs, to create
RockRidge images:
mkisofs -a -L -R -o <image_file> <source_dir>
(and it won't put TRANS.TBL files all over the place).
> If you don't know what I'm talking about here, then you are really in
> over your head. To get up and running, have a good long read of the
> CD-Writing-HOWTO.
[...]
Oh yes, I definitely second this.
Regards,
Liviu
--
Dr. Liviu Daia e-mail: [EMAIL PROTECTED]
Institute of Mathematics web page: http://www.imar.ro/~daia
of the Romanian Academy PGP key: finger [EMAIL PROTECTED]
