Linux-Misc Digest #426, Volume #24               Wed, 10 May 00 13:13:02 EDT

Contents:
  Re: CD-RW weirdness ([EMAIL PROTECTED])
  Re: GNOME/Enlightenment strangeness with certain applications... (Richard)
  problem when registering a misc driver ("Stéphane RICHOUX")
  disk mirroring --- system image ("shahzad bhatti")
  Re: German Govt says Microsoft a security risk (JEDIDIAH)
  Re: Newbie need help on configuring eth0 (Leonard Evens)
  Re: "From" in elm and mutt (Jim Marshall)
  Re: samba printing (Patrick O'Neil)
  Re: SCSI devices and SMP kernels (Pierre Vigneras)
  Re: samba printing (Patrick O'Neil)
  Re: LILO 1024 cyl thing (Rick Hoffman)
  Re: Damn samba (Bob Hauck)
  Uses for a CD Tower under Linux (Kerry Cox)
  Re: Can I use DiskImage to back up linux. (Thaddeus L. Olczyk)

----------------------------------------------------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux.mandrake
Subject: Re: CD-RW weirdness
Date: Wed, 10 May 2000 15:04:10 GMT

In article <[EMAIL PROTECTED]>,> use /dev/sr0
for /dev/hdc (or your first cd-ROM or RW)
> use /dev/sr1 for /dev/hdd(or your second     ""           "" )

Okay:
# mount /dev/sr0 /mnt/cdrom2
mount: the kernel does not recognize /dev/sr0 as a block device
       (maybe `insmod driver'?)

I guess I'm missing something really basing here on how to associate
/dev files with the appropriate modules.

-Jonathan


Sent via Deja.com http://www.deja.com/
Before you buy.

------------------------------

Subject: Re: GNOME/Enlightenment strangeness with certain applications...
From: Richard <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x
Date: Wed, 10 May 2000 08:17:45 -0700

I've noticed a similar behavior when opening the Enlightenment
help window. The first time it is started it shows up with the
title bar barely showing at the bottom of the screen (most of
window is off-screen). The second time it is started, the window
shows up at the top-left corner of the screen. The third time it
shows up in the middle of the screen.

* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!


------------------------------

From: "Stéphane RICHOUX" <[EMAIL PROTECTED]>
Subject: problem when registering a misc driver
Date: Wed, 10 May 2000 17:32:37 +0200

Hello,

   I am writing my first linux driver. It is a driver for a touch panel.
Let's call it toto.
  I test it using the insmod facility : insmod toto.o.
     I am calling function "misc_register" from init_module. The result
is successfull (0)
the module appears in /proc/modules but I was expecting to see a
/dev/toto , but nothing happen.
Do I miss something ?

Stephane


------------------------------

From: "shahzad bhatti" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,comp.os.linux.setup,comp.os.linux.hardware
Subject: disk mirroring --- system image
Date: Wed, 10 May 2000 10:48:07 -0500

Hi,
 I am swapping my disk drive on my linux redhat system. I want to copy
entire image of my system to new disk drive. I currently have two
partitions, first is swap and second is system
and user area. Can someone suggest best way to do this?
(I have about 3Gig space filled with system and user area)
Thanks in advance.
- Shahzad Bhatti



------------------------------

From: [EMAIL PROTECTED] (JEDIDIAH)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: German Govt says Microsoft a security risk
Date: Wed, 10 May 2000 15:54:50 GMT

On Wed, 10 May 2000 08:06:15 -0700, Salvador Peralta <[EMAIL PROTECTED]> 
wrote:
>Unfortunately, the article had nothing to do with m$ being a security
>risk from the software standpoint and everything to do with m$
>incorporating some of scientology's philosophies into their corporate
>model.  The german government has already given us enough intolerance
>for the next 2 centuries, IMHO.  Let's not applaud them for giving us

        ...as if they are fundementally much different than other 
        governments that send stormtroopes into cult monasteries...

        Scientology is quite distinct in several ways from any other
        entity that claims to be a religion.
        
        The abuse of courts and IP law would be the obvious parallels
        with Microsoft.


>more.
>
>Charlie Ebert wrote:
>> 
>> HEY!  WAY TO GO GERMANY!
>> 
>> They are a security risk and they should be delt with!
>> 
>> I know.
>> 
>> Charlie
>> 

-- 

    In what language does 'open' mean 'execute the evil contents of'    |||
    a document?      --Les Mikesell                                    / | \
    
                                      Need sane PPP docs? Try penguin.lvcm.com.

------------------------------

From: Leonard Evens <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.setup
Subject: Re: Newbie need help on configuring eth0
Date: Wed, 10 May 2000 10:47:22 -0500

Damon wrote:
> 
> Thanks Leonard, i think i solve the problem. I took out the network card and
> put it in another slot. Abit BP6 mobo is sure a weird mobo.
> 
> Thanks again.
> 
> Regards
> Damon
> 
> Leonard Evens wrote:
> 
> > Damon wrote:
> > >
> > > Hi, sorry to post this but i would appreciate if anyone got any idea how
> > > to resolve this.
> > >
> > > I found out that my PC ( Abit BP6 with Gentus Linux (similar to RH6.1) )
> > > uses irq 11 for both mass storage controllers and the Network
> > > Controller. I believe that there might be a conflict. My network card is
> > > using the RTL8139A chipset and i believe this is supported.
> > >
> > > Does anyone know how to resolve conflicting irq? The funniest thing is
> > > that previously when i install RH6.1 on my Abit BP6 using the "linux
> > > ide2=0x????,0x????" as the boot parameters, it worked! Using the
> > > RTL8139A drivers, if i recall correctly. I switch to Gentus because i
> > > got sick of lack of ATA66 support in RH6.1 and having to go through hell
> > > to get RH6.1 installed.
> > >
> > > Thank you.
> > >
> > > Regards
> > > Damon
> >
> > The interrupt for the network card is unlikely to be set
> > by hardware.   Linux should choose compatible interrupts.
> > For example, my (SCSI) system uses interrupt 9 for the
> > network card and interrupt 11 for the scsi adapter.
> >
> > Try
> > more /proc/interrupts
> >
> > --
> >
> > Leonard Evens      [EMAIL PROTECTED]      847-491-5537
> > Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208

I believe that some machines tie the interrupt to the slot;
I vaguley remember encountering that.   IF so, mvoing the card
to another slot might resolve a problem.
-- 

Leonard Evens      [EMAIL PROTECTED]      847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208

------------------------------

From: [EMAIL PROTECTED] (Jim Marshall)
Crossposted-To: comp.os.linux.networking,comp.os.linux.setup,alt.os.linux
Subject: Re: "From" in elm and mutt
Date: Wed, 10 May 2000 09:56:48 -0700
Reply-To: [EMAIL PROTECTED]

On Wed, 10 May 2000 15:16:40 +0200, Quentin PHILIPPE 
<[EMAIL PROTECTED]> wrote:
>Hello,
>
>I have a problem with elm and mutt: If I send an email with them, the
>answer address is [EMAIL PROTECTED] (easynet is my provider, and
>quentin my user under linux). And it should be as underneath:
>[EMAIL PROTECTED]
>
>What do I have to change in my .muttrc?
>
>Thank you.
>-- 
>Quentin PHILIPPE
>[EMAIL PROTECTED]

Try puttin these lines in:

my_hdr From: Quentin Phillippe <[EMAIL PROTECTED]>
my_hdr Reply-To: [EMAIL PROTECTED]

These are for your .muttrc. Not sure about Elm. Hope this helps.
-- 
Slackware 7.0 Linux
  9:53am  up 1 day, 10:15,  6 users,  load average: 0.00, 0.00, 0.00

------------------------------

From: Patrick O'Neil <[EMAIL PROTECTED]>
Subject: Re: samba printing
Date: Wed, 10 May 2000 10:48:40 -0600

Patrick O'Neil wrote:
> 
> I am running Mandrake 7.0 with samba-2.0.6-4.  I have been
> trying to make samba printing work but have NEVER been able
> with Mandrake.  I have tried setting up the shared printers

OK, what I need is for someone with a WORKING samba printing
setup (as a client) to PLEASE post the ownership, user and group, 
for the files in the appropriate /var/spool/lpd/lp* directory.

When I created a samba printer as lp on Mandrake using linuxconf, it
created:
---/var/spool/lpd/lp---

-rwxr-xr-x   1 root     root          10532 May  9 12:57 filter*
-rw-r--r--   1 root     root            188 May  9 12:57 general.cfg
-rw-r--r--   1 root     root             37 May 10 10:41 lock
-rw-r--r--   1 root     root            347 May  9 12:57 postscript.cfg
-rw-rw-r--   1 root     root             25 May 10 10:41 status
-rw-r--r--   1 root     root            146 May  9 12:57 textonly.cfg

I question the ownerships and the group membership on these files.
What are they supposed to be?

I cannot print to samba printers on Mandrake 7.0.  Never have been
able to.  I get no error messages, not a thing appears in any log
anywhere.  

patrick

------------------------------

From: Pierre Vigneras <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: SCSI devices and SMP kernels
Date: Wed, 10 May 2000 20:45:44 +0200

This is a multi-part message in MIME format.
==============29767BDE1F121D5D89E7772B
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Thanks very much for your help, really :-).

Nevertheless, i really don't understand something : 
my version of Lilo is :

[root@moucheron /root]# lilo -V
LILO version 21
[root@moucheron /root]# 

Is there a more recent version ?

Moreover, the lilo doc talked about this 1024 cylinders limits :

[root@moucheron /root]# cd /usr/doc/lilo-0.21/doc/
[root@moucheron doc]# cat user.tex 

[...]

\subsubsection{BIOS restrictions}
\label{broken}

Nowadays, an increasing number of systems is equipped with comparably
large
disks or even with multiple disks. At the time the disk interface of the
standard PC BIOS has been designed (about 16 years ago), such
configurations
were apparently considered to be too unlikely to be worth supporting.

The most common BIOS restrictions that affect \LILO\ are the limitation
to
two hard disks and the inability to access more than 1024 cylinders per
disk. \LILO\ can detect both conditions, but in order to work around the
underlying problems, manual intervention is necessary.

The drive limit does not exist in every BIOS. Some modern motherboards
and disk controllers are equipped with a BIOS that supports more
(typically
four) disk drives. When attempting to access the third, fourth, etc.
drive,
\LILO\ prints a warning message but continues. Unless the BIOS really
supports more than two drives, the system will \emphasize{not} be able
to
boot in that case.\footnote{However, if only ``unimportant'' parts of
the
system are located on the ``high'' drives, some functionality may be
available.}

The cylinder limit is a very common problem with IDE disks. There, the
number of cylinders may already exceed 1024 if the drive has a capacity
of more than 504 MB. Many SCSI driver BIOSes present the disk geometry
in a way that makes the limit occur near 1 GB. Modern disk controllers
may even push the limit up to about 8 GB. All cylinders beyond the
1024th are inaccessible for the BIOS. \LILO\ detects this problem and
aborts the installation (unless the \craw{linear} option is used, see
section \ref{cfgglo}).

Note that large partitions that only partially extend into the
``forbidden
zone'' are still in jeopardy even if they appear to work at first,
because
the file system does not know about the restrictions and may allocate
disk space from the area beyond the 1024th cylinder when installing new
kernels. \LILO\ therefore prints a warning message but continues as long
as no imminent danger exists.

[...]

Lilo should output a warning message. But, as you can see below, it's
not the case.

Supposing Lilo don't really see the problem and don't print a warning,
how can i see where the data block allocated to store my new kernel
image file is (in terms of cylinders...) ?

Is there a command for it (like stat...) ?

One other (stupid ?) question :

Can i remove some files in /boot/ so copying a new kernel image in
/boot/ will allocate the blocks in the good regions (below the 1024
bound) to store it ?

I can't see a solution to my problem, with my configuration(see below). 

Please help !

Eric wrote:
> 
> The bootmap may be correct, but since the bios cannot see any discspace
> beyond cylinder 1024,(or lilo since it uses the bios info) you may have
> bad luck. All depends on the actual physical location of your kernel
> image, so a previous image may have booted (out of pure luck being
> allocated below cylinder 1024) but your new kernel isn't located on such
> a place.
> BTW. You can get the new lilo from the web which doesn't suffer from
> this limit.
> 
> Eric
> 
> Pierre Vigneras wrote:
> >
> > You're right :
> >
> > [root@moucheron /boot]# sfdisk -l /dev/sda
> >
> > Disk /dev/sda: 8715 cylinders, 64 heads, 32 sectors/track
> > Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from
> > 0
> >
> >    Device Boot Start     End   #cyls   #blocks   Id  System
> > /dev/sda1          0+    512     513-   525296   82  Linux swap
> > /dev/sda2        513    4513    4001   4097024   83  Linux
> > /dev/sda3       4514    8714    4201   4301824    c  Win95 FAT32 (LBA)
> > /dev/sda4          0       -       0         0    0  Empty
> > [root@moucheron /boot]#
> >
> > But, why can i boot with a ramdisk and not with my new kernel ?
> >
> > Can anyone answer to questions about the /boot/* files (see below...) ?
> >
> > Eric wrote:
> > >
> > > Just to make sure: you didn't make the partition where the kernel
> > > resides (possibly in /boot) too large so it crosses the 1024th cylinder?
> > >
> > > Eric
> > >
> > > Pierre Vigneras wrote:
> > > >
> > > > Johan Kullstam wrote:
> > > > >
> > > > > Eric <[EMAIL PROTECTED]> writes:
> > > > >
> > > > > > Henrique Seganfredo wrote:
> > > > > > >
> > > > > > > Anybody here knows about the behaviour of SMP kernels with SCSI drivers?
> > > > > > >
> > > > > > > I am trying to set up a right out of the box RPM package with a SMP
> > > > > > > kernel (the same version non SMP is already running)...when I boot, I
> > > > > > > get "kernel panic" cause the root fs (on sda1) could not be mounted due
> > > > > > > a problem loading the aic7xxx.o module....no, its not a version issue or
> > > > > > > something like that....
> > > > > > >
> > > > > > > ...some dudes told me that I can't use some SCSI drivers with SMP
> > > > > > > kernels...is that a fact?
> > > > > > >
> > > > > > you can't have scsi support as a module if you want to boot from a scsi
> > > > > > disc
> > > > > > it must be compiled into your kernel
> > > > >
> > > > > this is not quite true.  you can put the scsi module on an initial
> > > > > ramdisk (initrd).  this is what most distributions do because
> > > > > compiling every possible scsi driver into their kernel would be a bit
> > > > > much.
> > > > >
> > > > > however, i agree that it is a damned good recommendation.  if you can
> > > > > compile yourself a kernel, by all means build the scsi driver into it.
> > > >
> > > > That's what i did, but i got a
> > > > "kernel panic" too : "unable to mount on /dev/sda2".
> > > >
> > > > I did compile the scsi drive into the kernel.
> > > > And moreover, i have :
> > > >
> > > > [root@moucheron /boot]# rdev vmlinuz-2.2.14smp
> > > > Root device /dev/sda2
> > > > [root@moucheron /boot]#
> > > >
> > > > which is the current root device :
> > > >
> > > > [root@moucheron /boot]# rdev
> > > > /dev/sda2 /
> > > > [root@moucheron /boot]#
> > > >
> > > > Running lilo show :
> > > >
> > > > [root@moucheron /boot]# lilo -v
> > > > LILO version 21, Copyright 1992-1998 Werner Almesberger
> > > >
> > > > Reading boot sector from /dev/sda
> > > > Merging with /boot/boot.b
> > > > Boot image: /boot/vmlinuz-2.2.12-20smp
> > > > Mapping RAM disk /boot/initrd-2.2.12-20smp.img
> > > > Added linux *
> > > > Boot image: /boot/vmlinuz-2.2.12-20
> > > > Mapping RAM disk /boot/initrd-2.2.12-20.img
> > > > Added linux-up
> > > > Boot image: /boot/vmlinuz-2.2.14smp
> > > > Added new
> > > > /boot/boot.0800 exists - no backup copy made.
> > > > Writing boot sector.
> > > > [root@moucheron /boot]#
> > > >
> > > > But booting my new kernel is always a kernel panic !
> > > > i don't understand why !
> > > > I suppose the redhat ramdisk as set a strange /boot/map:
> > > >
> > > > [root@moucheron /boot]# ls -al
> > > > total 10781
> > > > drwxr-xr-x   2 root     root         1024 May 10 09:33 .
> > > > drwxr-xr-x  24 root     root         1024 Mar  2 15:19 ..
> > > > lrwxrwxrwx   1 root     root           20 Feb 11 18:19 System.map ->
> > > > System.map 2.2.12-20
> > > > -rw-r--r--   1 root     root       191102 Sep 27  1999
> > > > System.map-2.2.12-20
> > > > -rw-r--r--   1 root     root       182834 Sep 27  1999
> > > > System.map-2.2.12-20BOOT
> > > > -rw-r--r--   1 root     root       202226 Sep 27  1999
> > > > System.map-2.2.12-20smp
> > > > -rw-r--r--   1 root     root          512 Jul  9  1999 boot.0800
> > > > -rw-r--r--   1 root     root         4568 May  5 11:47 boot.b
> > > > -rw-r--r--   1 root     root          612 Sep 22  1999 chain.b
> > > > -rw-r--r--   1 root     root       313673 Feb 11 18:26
> > > > initrd-2.2.12-20.img
> > > > -rw-r--r--   1 root     root       314036 Feb 11 18:26
> > > > initrd-2.2.12-20smp.img
> > > > -rw-r--r--   1 root     root       308009 Jul  9  1999
> > > > initrd-2.2.5-15.img
> > > > -rw-r--r--   1 root     root       308488 Jul  9  1999
> > > > initrd-2.2.5-15smp.img
> > > > lrwxrwxrwx   1 root     root           22 Jul 31  1999
> > > > initrd-2.2.5-22smp.img -  initrd-2.2.5-15smp.img
> > > > -rw-r--r--   1 root     root       695162 Jul 31  1999
> > > > kernel-2.2.5-22smp.my
> > > > -rw-r--r--   1 root     root          237 May  5 12:18 kernel.h
> > > > -rw-------   1 root     root        30720 May 10 09:33 map
> > > > lrwxrwxrwx   1 root     root           21 Feb 11 18:19 module-info ->
> > > > module-in o-2.2.12-20
> > > > -rw-r--r--   1 root     root        11773 Sep 27  1999
> > > > module-info-2.2.12-20
> > > > -rw-r--r--   1 root     root        11773 Sep 27  1999
> > > > module-info-2.2.12-20smp
> > > > -rw-r--r--   1 root     root          620 Sep 22  1999 os2_d.b
> > > > -rwxr-xr-x   1 root     root      1544394 Sep 27  1999 vmlinux-2.2.12-20
> > > > -rwxr-xr-x   1 root     root      1469971 Sep 27  1999
> > > > vmlinux-2.2.12-20BOOT
> > > > -rwxr-xr-x   1 root     root      1647660 Sep 27  1999
> > > > vmlinux-2.2.12-20smp
> > > > lrwxrwxrwx   1 root     root           17 Feb 11 18:19 vmlinuz ->
> > > > vmlinuz-2.2.1 -20
> > > > -rw-r--r--   1 root     root       622784 Sep 27  1999 vmlinuz-2.2.12-20
> > > > -rw-r--r--   1 root     root       592397 Sep 27  1999
> > > > vmlinuz-2.2.12-20BOOT
> > > > -rw-r--r--   1 root     root       647807 Sep 27  1999
> > > > vmlinuz-2.2.12-20smp
> > > > -rw-r--r--   1 root     root       453234 May  5 09:29 vmlinuz-2.2.14smp
> > > > -rw-r--r--   1 root     root       709302 Jul 23  1999
> > > > vmlinuz-2.2.5-15smp.new
> > > > -rw-r--r--   1 root     root       695161 Aug  6  1999
> > > > vmlinuz-2.2.5-22smp.new
> > > > [root@moucheron /boot]#
> > > >
> > > > Can i remove some of this files (System.map*) ?? What are their use (i
> > > > know ps use it, for its WCHAN field, but is there another use ??) ? What
> > > > are module-info* files ? Can i remove some of this files ?
> > > >
> > > > Here my /etc/lilo.conf :
> > > >
> > > > [root@moucheron /boot]# cat /etc/lilo.conf
> > > > boot=/dev/sda
> > > > map=/boot/map
> > > > install=/boot/boot.b
> > > > prompt
> > > > timeout=50
> > > > default=linux
> > > >
> > > > image=/boot/vmlinuz-2.2.12-20smp
> > > >         label=linux
> > > >         initrd=/boot/initrd-2.2.12-20smp.img
> > > >         read-only
> > > >         root=/dev/sda2
> > > >
> > > > image=/boot/vmlinuz-2.2.12-20
> > > >         label=linux-up
> > > >         initrd=/boot/initrd-2.2.12-20.img
> > > >         read-only
> > > >         root=/dev/sda2
> > > >
> > > > image=/boot/vmlinuz-2.2.14smp
> > > >         label=new
> > > >         read-only
> > > >         root=/dev/sda2
> > > >         vga=ask
> > > >
> > > > [root@moucheron /boot]#
> > > >
> > > > My new kernel is /boot/vmlinuz-2.2.14smp (which i can't boot like
> > > > describe above).
> > > >

-- 
Pierre Vignéras
http://dept-info.labri.u-bordeaux.fr/~vigneras/

Equipe systèmes et objets distribués
http://jccf.labri.u-bordeaux.fr/jodo/

LaBRI
http://dept-info.labri.u-bordeaux.fr/
==============29767BDE1F121D5D89E7772B
Content-Type: text/x-vcard; charset=us-ascii;
 name="vigneras.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Pierre Vigneras
Content-Disposition: attachment;
 filename="vigneras.vcf"

begin:vcard 
n:Vignéras;Pierre
tel;cell:06.81.50.55.51
tel;work:05.56.84.24.87
x-mozilla-html:FALSE
url:http://dept-info.labri.u-bordeaux.fr/~vigneras/
org:LaBRI;Computer Science
version:2.1
email;internet:[EMAIL PROTECTED]
title:Student
adr;quoted-printable:;;R=E9sidence les pierres du 
campus=0D=0AA/26;Gradignan;;33170;France
note;quoted-printable:<A 
href=3D"http://jccf.labri.u-bordeaux.fr/jodo/">=0D=0ADistributed Systems and Objects 
team</A>=0D=0A=0D=0A=0D=0A
x-mozilla-cpt:;-32672
fn:Pierre Vignéras
end:vcard

==============29767BDE1F121D5D89E7772B==


------------------------------

From: Patrick O'Neil <[EMAIL PROTECTED]>
Subject: Re: samba printing
Date: Wed, 10 May 2000 10:55:02 -0600

Patrick O'Neil wrote:
> 
> I am running Mandrake 7.0 with samba-2.0.6-4.  I have been
> trying to make samba printing work but have NEVER been able
> with Mandrake.  I have tried setting up the shared printers
[...]

What follows is a copy of a section of my /etc/printcap file.
This is a samba printer I have tried to setup using linuxconf
and printtool (on separate occasions...trying to get it to 
freakin' work!).  This printer is setup in linuxconf (or 
printtool correctly, all the entries are correct as 
they are requested by each app yet the printer does not work:

##PRINTTOOL3##  SMB POSTSCRIPT 600x600 legal {} PostScript Default
lp:\
        :sd=/var/spool/lpd/lp:\
        :mx#0:\
        :sh:\
        :lp=/dev/null:\
        :af=/var/spool/lpd/lp/acct\
        :if=/var/spool/lpd/lp/filter:

Is there anything here that is screwy?  Anyone?  Anyone?

patrick

------------------------------

From: Rick Hoffman <[EMAIL PROTECTED]>
Subject: Re: LILO 1024 cyl thing
Date: Wed, 10 May 2000 12:53:12 -0400

>
> RH>
> RH> I wrote earlier >> But how do I get the data to the partitions and have a 
>working file
> RH> system afterwards?
> RH> I had a feeling the installer was going to hypothetically be the one to do all 
>the work.
> RH> But like I worded the question before how do I get the data into the partitions 
>like I
> RH> want them.  Lets say I have a functional Linux system on a source drive with one 
>big
> RH> partition and I break up another disk into many partitions.  These partitions 
>are ext2
> RH> formatted.  How do I get the directories I pick and choose from the source disk 
>to the
> RH> destination disk and have a functional OS on the destination disk?  In other 
>words I do
> RH> the work of the installer from one disk to another and am basically wanting to 
>clone the
> RH> OS but from one partition to many.
> RH>

Thanks again, Robert, for your attentiveness.  I am sure it was an honest oversight 
but you did
not address this question.  I am having a real time getting anyone to move into this 
area and
now you just skipped over it.  Is it possible to copy directories yourself from 
hda(with one big
partition) to hdb(with multiple partitions) without any loss of functionality?  If not 
why not.
I am trying to use a spare HD to backup my Linux system and I am beginning to think 
that for
some odd reason it is not going to be possible.  What a shame when I very easily use 
this method
with Windows.  I backup my Windows OS onto another HD with a software utility that 
simply copies
one partition to another.  The backup is basically a clone of the primary and is fully
functional.  That is the least expensive and most capable form of backup I am aware 
of.  I would
like to be able to do the same with Linux.  Is it possible?

hoffy


------------------------------

From: [EMAIL PROTECTED] (Bob Hauck)
Subject: Re: Damn samba
Reply-To: hauck[at]codem{dot}com
Date: Wed, 10 May 2000 16:56:34 GMT

On Wed, 10 May 2000 08:29:59 -0600, Patrick <[EMAIL PROTECTED]> wrote:

>> > What is the trick to making Mandrake print to a simple ole
>> > samba share printer?  

>> According to the smb.conf file on the Samba machine, what IP addresses
>> have permission to print? What users? Is "guest Ok" set to "yes"?
>
>The printers are on a windoze network, not on a linux/*nix box.  I am
>running linux as a desktop on my laptop.  

You are doing the wrong thing then.  Samba is for making your Unix files
and printers available to the Windows machines.  To print from Linux to a
Windows printer, you need to use smbclient with the -P parameter and it
does not even matter whether or not samba is running on your workstation.

You can use smbclient from the command line, or you can install it as a
print filter in /etc/printcap.  My Samba 2.0.5 (built from source) has a
script called "smbprint" that you can use as a print filter to do this.  
The comments in the script illustrate how to add it to your /etc/printcap.

-- 
 -| Bob Hauck
 -| Codem Systems, Inc.
 -| http://www.codem.com/

------------------------------

From: Kerry Cox <[EMAIL PROTECTED]>
Subject: Uses for a CD Tower under Linux
Date: Wed, 10 May 2000 11:02:20 -0600

I have a Procon Technologies CD Tower ETP that has 8 CD-ROMs along with
space for eight additonal CD drive.  It's a beefy box, but my company is
thinking about throwing it away or at least salvaging the CD drives due
to the very unfriendly user interface that came with it.
Just wondering if anyone has found a use for something like this?  Any
software out there for Linux that might run something like this?  I'm
thinking about placing all my MP3s that are burned onto CDs in there and
simply using it for in-house use.
It has a 10BaseT connectior on the back and has a card inside that I
presumes runs it all or allows for an interface.
Any information would be appreciated.  Otherwise, it goes to that great
salvage pile in the sky.
KJ 
-- 

_.,+=~`^"-.,_.,+=~`^"-*.,_.,+=~'`^"-.,_.,+=~`^"-.,_.,+=~`^"-.,_.,+=~`^"-.,
  Kerry J. Cox           .,.     System Administrator
  [EMAIL PROTECTED]      .,.     KSL Radio/TV 
  (801) 575-7771         .,.     http://www.ksl.com/
  ICQ# 37681165          .,.     http://quasi.ksl.com/linux/
_.,+=~`^"-.,_.,+=~`^"-.,_.,+=~`^"-.,_.,+*=~`^"-.,_.,+=%~`^"-.,_.,+=~`^"-.,

------------------------------

From: [EMAIL PROTECTED] (Thaddeus L. Olczyk)
Subject: Re: Can I use DiskImage to back up linux.
Date: Wed, 10 May 2000 17:07:57 GMT
Reply-To: [EMAIL PROTECTED]

On Wed, 10 May 2000 00:55:06 -0500, [EMAIL PROTECTED] (Richard
Steiner) wrote:

>Here in comp.os.linux.misc, [EMAIL PROTECTED] (Thaddeus L. Olczyk)
>spake unto us, saying:
>
>>Something I like to do with Microshit software.
>>Install OS on C: software on D:.
>>After done installing, I backup disk images using PartitionMagic
>>DiskImage to save both partitions.
>>Can I also use this process on linux?
>
>PQ's DriveImage works fine for me.  If DiskImage is similar, it may
>work as well.  Try testing it on an unimportant installation.
Oops. It's DriveImage. I keep mistating it as DiskImage. Don't know
why.

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.misc) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Misc Digest
******************************

Reply via email to