Dear all, 1. Where is the appropriate place to put user startup scripts to start user application during system boot ? Seems "/etc/rc.d/rc?.d/Sxxxx" no longer an endorsed way with SuSE 7.1 anymore, doesn't it ? 2. I have installed a SCSI hard disk together with a SCSI DAT tape drive after installing the SuSE 7.1 software onto the primiary booting IDE harddisk. Now, while I can access the SCSI HD without any problem, I have no idea on how to access the DAT tape drive. I can see that there are devices "/dev/0s?" and "/dev/1s?" and that's it. Do I need to "mknod" or "mkdev" for more SCSI devices ? What devices should I correspond to the tape drive if it has SCSI ID equals 5 ? BTW, I am using the Tekram 390 SCSI controller card. Any pointers are welcomed. 3. Can anyone please explain to me about the version of GNU C compiler ? Sometime people refer to it as version 2.x.x and sometime saying about libc version 5 or 6. How are they correlated ? It seems that almost all RPM packages pre-built for RH would complaint during installation on SuSE about the C libraries versions. Can I safely skip the dependency check on this ? Any suggestions, hints or pointers are highly welcomed. Regards, Raymond.
Raymond Fung wrote:
1. Where is the appropriate place to put user startup scripts to start user application during system boot ? Seems "/etc/rc.d/rc?.d/Sxxxx" no longer an endorsed way with SuSE 7.1 anymore, doesn't it ?
One possibility is /etc/init.d/boot.local, which is intended for that purpose. But there's a design flaw in the startup stuff: boot.local runs before all the other scripts in /etc/init.d, so it can't depend on what any of them do. You might want to insert a call somewhere to a script afterboot.local that would run after everything else. I haven't looked at just where the call should go, though. (Hint to SuSE: perhaps you should implement something like bootafter.local.) By the way, Raymond, I'd suggest that next time you have a bunch of separate questions you should put each of them in a separate message whose header indicates clearly what it's about. A lot of people will pay no attention to a post with a title as general as "Questions", and some of them might have helpful information for you. Paul
* Paul Abrahams
just where the call should go, though. (Hint to SuSE: perhaps you should implement something like bootafter.local.)
Why not just use /etc/rc.d/rcX.d/ ? (X == runlevel)
By the way, Raymond, I'd suggest that next time you have a bunch of separate questions you should put each of them in a separate message whose header indicates clearly what it's about. A lot of people will pay no attention to a post with a title as general as "Questions", and some of them might have helpful information for you.
Yep -- I almost lost it. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
On Tue, May 08, 2001 at 02:54:57PM -0400, Paul Abrahams wrote:
Raymond Fung wrote:
1. Where is the appropriate place to put user startup scripts to start user application during system boot ? Seems "/etc/rc.d/rc?.d/Sxxxx" no longer an endorsed way with SuSE 7.1 anymore, doesn't it ?
One possibility is /etc/init.d/boot.local, which is intended for that purpose. But there's a design flaw in the startup stuff: boot.local runs before all the other scripts in /etc/init.d, so it can't depend on what any of them do. You might want to insert a call somewhere to a script afterboot.local that would run after everything else. I haven't looked at just where the call should go, though. (Hint to SuSE: perhaps you should implement something like bootafter.local.)
have a look to /etc/init.d/README which is about SuSE boot concept you can use the /etc/init.d/skeleton file as an example also man insserv could give you some hints HTH -- Togan Muftuoglu
* Raymond Fung
Dear all,
1. Where is the appropriate place to put user startup scripts to start user application during system boot ? Seems "/etc/rc.d/rc?.d/Sxxxx" no longer an endorsed way with SuSE 7.1 anymore, doesn't it ?
It is -- why are you seeing it as not? That is how we start all services.
2. I have installed a SCSI hard disk together with a SCSI DAT tape drive after installing the SuSE 7.1 software onto the primiary booting IDE harddisk. Now, while I can access the SCSI HD without any problem, I have no idea on how to access the DAT tape drive. I can see that there are devices "/dev/0s?" and "/dev/1s?" and that's it. Do I need to "mknod" or "mkdev" for more SCSI devices ? What devices should I correspond to the tape drive if it has SCSI ID equals 5 ? BTW, I am using the Tekram 390 SCSI controller card. Any pointers are welcomed.
/dev/st0 (rewind) /dev/nst0 (non-rewind)
3. Can anyone please explain to me about the version of GNU C compiler ?
Sometime people refer to it as version 2.x.x and sometime saying about libc version 5 or 6. How are they correlated ? It seems that almost all RPM packages pre-built for RH would complaint during installation on SuSE about the C libraries versions. Can I safely skip the dependency check on this ?
libc is the library, gcc is the compiler. You should not need to install any Red Hat RPMs on your SuSE system, so maybe you could elaborate on why? -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
Mads Martin Jørgensen wrote:
* Raymond Fung
[May 08. 2001 08:40]: Dear all,
1. Where is the appropriate place to put user startup scripts to start user application during system boot ? Seems "/etc/rc.d/rc?.d/Sxxxx" no longer an endorsed way with SuSE 7.1 anymore, doesn't it ?
It is -- why are you seeing it as not? That is how we start all services.
True, execpt that /etc/rc.d is just a link to /etc/init.d which is where it all really happens. Mark
On Tue, 8 May 2001, Raymond Fung wrote:
1. Where is the appropriate place to put user startup scripts to start user application during system boot ? Seems "/etc/rc.d/rc?.d/Sxxxx" no longer an endorsed way with SuSE 7.1 anymore, doesn't it ?
In SuSE Linux 7.1, scripts should be placed in directory /etc/init.d . There is a template script named "skeleton" that you can adjust to your needs. Also have a look at the man pages insserv(8) and init.d(7).
2. I have installed a SCSI hard disk together with a SCSI DAT tape drive after installing the SuSE 7.1 software onto the primiary booting IDE harddisk. Now, while I can access the SCSI HD without any problem, I have no idea on how to access the DAT tape drive. I can see that there are devices "/dev/0s?" and "/dev/1s?" and that's it. Do I need to "mknod" or "mkdev" for more SCSI devices ?
No, usually you do not need to add any device entries. Have you loaded the SCSI Tape Driver "st.o"?
What devices should I correspond to the tape drive if it has SCSI ID equals 5 ? BTW, I am using the Tekram 390 SCSI controller card. Any pointers are welcomed.
Does the tape drive show up in /proc/scsi/scsi?
3. Can anyone please explain to me about the version of GNU C compiler ?
Sometime people refer to it as version 2.x.x and sometime saying about libc version 5 or 6. How are they correlated ?
These are two different things. One is the C Compiler (7.1 uses version 2.95.2), the other one is the C library (SuSE 7.1 uses version 2.2)
It seems that almost all RPM packages pre-built for RH would complaint during installation on SuSE about the C libraries versions. Can I safely skip the dependency check on this ?
Depends on the exact warning. You can of course give it a try - if the program does not start, you can easily remove the package later. LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany Sex is like an industrial film covered in fur..
participants (6)
-
Lenz Grimmer
-
Mads Martin Jørgensen
-
Mark Hounschell
-
Paul Abrahams
-
Raymond Fung
-
Togan Muftuoglu