Re: Boot script
Hi, Jan Wilmans wrote > - I have put debian-live-10.3.0-amd64-kde.iso on a USB stick directly > using rufus-3.9.exe With its "dd" mode, i assume. > the live images contains a filesystem.squashfs Yeah. Tricky. > But I thought there must surely be a simpler way? Install Debian to the USB stick as if it was a hard disk like any other, rather than putting the ISO image onto the stick. If it were only about having some files at hand, i'd advise to add a partition to the stick with a read-write filesystem. But you want to interfere with the system's start-up. And "rc.local" does not look like your plan is in the contemporary mainstream of starting up. Have a nice day :) Thomas
Re: Boot script
Hi, Jan Wilmans wrote: > I've created a bootable USB stick that boot debian 10 By which procedure, exactly ? There are several which produce quite different outcome. > how can I insert it into the USB sticks read only filesystem? If you have an ISO 9660 filesystem on the base device of the stick and did not add new partitions, then you could use multi-session or re-pack the ISO. It might become tricky, nevertheless. Consider to install Debian on a USB stick and to customize it as any other Debian system, rather than putting an ISO image onto the stick. That said, multi-session works like this: cp debian-10.0.0-amd64-xfce.iso test.iso file_or_tree_on_disk=...path... path_in_iso=...path... xorriso -dev test.iso \ -map "$file_or_tree_on_disk" "$path_in_iso" \ -boot_image any replay (You may work directly on the stick by an address like -dev stdio:/dev/sdd but for first experiments i'd advise a disk file as test object.) Repacking is discussed on https://wiki.debian.org/RepackBootableISO Have a nice day :) Thomas
Boot script
I've created a bootable USB stick that boot debian 10 (buster), and i would like to customize my rc.local to do and apt-get update and install icecc then start iceccd finally run top. Its a simple script, but how can I insert it into the USB sticks read only filesystem? On Sun, May 10, 2020, 11:23 Jan Wilmans wrote: > If you look carefully of the last page, the radio button for writing the > boot record to disk is by default is to ,NOT write the boot record. You > have to change it to 'yes' before you continue! > > If you dont, then ofcourse it reboots and since nothing changed in the > boot sequence it boots the iso again... > > On Sun, May 10, 2020, 07:54 Keith Bainbridge wrote: > >> On 10/5/20 1:24 pm, Harry Brown wrote: >> > Hey guys, >> > >> > I'm having a bit of an issue here while installing KaliLinux and I was >> > wondering if you guys can help out. >> > >> > I installed *Oracle VirtualBox* on my *Windows 10* and downloaded *Kali >> > Linux 64bit ISO file*, Then I created a new virtual machine *(Debian >> > 64bit)*and started installing KaliLinux. >> > Everything was great and almost 5GB of packages were downloaded and >> > installed, the final step is to reboot so KaliLinux can run. >> > I clicked on Finish Installation (after all packages and files were >> > installed ) and it showed me a message saying that Kali will run after >> > the machine reboot. >> > >> > Guess what! *The machine rebooted and it took me back to the first >> > installation page again*, I didn't know what happened or if I did >> > something wrong so I clicked "Install" again and followed the steps. >> > And I had to wait **again for the 5GB of packages to be downloaded and >> > installed ( which was frustrating ). >> > Installation was finished and the machine rebooted and nothing >> happened. >> > *it took me back to the first installation page once again.* >> > * >> > * >> > I know it's a long email (sorry about that), But I needed to make sure >> > that you guys are fully aware of what's the issue so you can help. >> > >> > Thanks in advance, >> > >> > HB. >> > >> >> >> Good afternoon Harry >> >> I sometimes have to go into the settings for the virtual device and >> untick the other boot options - CD and floppy from memory. >> >> -- >> Keith Bainbridge >> >> ke1th3...@zoho.com >> +61 (0)447 667 468 >> >>
debug boot script
I want to debug an init cript in /etc/rcS.d That script outputs some messages using echo, so the messages should be printed to the stdout. I guess the redirect mechanism provided by shell is supposed to work in order to grab these messages into a file. To verify it, I created a test script in /etc/rcS.d, writing the content as below: echo hello /tmp/message But when I boot up the system, nothing happened. Can somebody give me any hint?
Re: debug boot script
El mié, 02-07-2008 a las 16:43 +0800, ray escribió: I want to debug an init cript in /etc/rcS.d That script outputs some messages using echo, so the messages should be printed to the stdout. I guess the redirect mechanism provided by shell is supposed to work in order to grab these messages into a file. To verify it, I created a test script in /etc/rcS.d, writing the content as below: echo hello /tmp/message But when I boot up the system, nothing happened. Can somebody give me any hint? At what point in the bootup process was the script set to run? If it's run before the mountall script, /tmp was probably not mounted yet (assuming it's in a separate partition). Also, there's a script that cleans up /tmp and /var/tmp; make sure you're not running before that one either. You could try sending the output somewhere else as well. /var/log comes to mind. -- Gabriel Parrondo GNU/Linux User #404138 GnuPG Public Key ID: BED7BF43 JID: [EMAIL PROTECTED] The only difference between theory and practice is that, in theory, there's no difference between theory and practice. signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: debug boot script
On Wed, Jul 2, 2008 at 7:39 PM, Gabriel Parrondo [EMAIL PROTECTED] wrote: El mié, 02-07-2008 a las 16:43 +0800, ray escribió: I want to debug an init cript in /etc/rcS.d That script outputs some messages using echo, so the messages should be printed to the stdout. I guess the redirect mechanism provided by shell is supposed to work in order to grab these messages into a file. To verify it, I created a test script in /etc/rcS.d, writing the content as below: echo hello /tmp/message But when I boot up the system, nothing happened. Can somebody give me any hint? At what point in the bootup process was the script set to run? If it's run before the mountall script, /tmp was probably not mounted yet (assuming it's in a separate partition). I didn't modify the script I'm interested, I just created a test script in /etc/rcS.d and named it S01atest.sh, so this script will the first script to be run on boot. /tmp is not in a separate partition in my case. Also, there's a script that cleans up /tmp and /var/tmp; make sure you're not running before that one either. You could try sending the output somewhere else as well. /var/log comes to mind In my case /var is in a separate partition, so /var/log is available? I found the very preceding scripts in /etc/rcS.d such as S02mountkernfs.sh already use the /var directory. -- Gabriel Parrondo GNU/Linux User #404138 GnuPG Public Key ID: BED7BF43 JID: [EMAIL PROTECTED] The only difference between theory and practice is that, in theory, there's no difference between theory and practice.
Re: debug boot script
On Wed, Jul 02, 2008 at 04:43:58PM +0800, ray wrote: I want to debug an init cript in /etc/rcS.d That script outputs some messages using echo, so the messages should be printed to the stdout. I guess the redirect mechanism provided by shell is supposed to work in order to grab these messages into a file. To verify it, I created a test script in /etc/rcS.d, writing the content as below: echo hello /tmp/message But when I boot up the system, nothing happened. Can somebody give me any hint? The root filesystem is probably still read-only at this stage. One useful tool for debugging shell scripts: adding 'set -x' to them in various places (to start running them in trace mode). -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il || a Mutt's [EMAIL PROTECTED] || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [mplayer] Such das richtige Boot Script für diesen Eintrag?
Am 06 Dez 2002, schrieb Clemens Wohld: Hallo, * On Thu, Dec 05, 2002 at 11:34:27AM +0100, Lothar Schweikle-Droll wrote: mplayer schlägt mit folgendes vor: Linux RTC init error in ioctl (rtc_irqp_set 1024): Keine Berechtigung Try adding echo 1024 /proc/sys/dev/rtc/max-user-freq to your system startup scripts. Nur wo trage ich das ein, das das automatisch beim booten geschied? In der /etc/init.d/bootmisc.sh zB. Trage dies in die bootmisc.sh ein: echo 1024 /proc/sys/dev/rtc/max-user-freq Es gibt zwar den Ordner /etc/rc.boot nur steht da nichts drinn. Der Ordner /etc/rc.boot ist sowas wie /etc/ppp/ip-up.d Alles was sich an scripten dort befindet wird (wenn korrekt angelegt) beim booten gestartet. Aber fuer eine Zeile, ... wuerd ich die bootmisc nutzen. Danke. Jetzt habe ich zwei Lösungen bei funktionieren. -- Lotharmailto:[EMAIL PROTECTED] Der beste Hellseher ist der, der gut raten kann. msg27761/pgp0.pgp Description: PGP signature
[mplayer] Such das richtige Boot Script für diesen Eintrag?
Hallo Leute, mplayer schlägt mit folgendes vor: Linux RTC init error in ioctl (rtc_irqp_set 1024): Keine Berechtigung Try adding echo 1024 /proc/sys/dev/rtc/max-user-freq to your system startup scripts. Nur wo trage ich das ein, das das automatisch beim booten geschied? Es gibt zwar den Ordner /etc/rc.boot nur steht da nichts drinn. -- Lotharmailto:[EMAIL PROTECTED] Gläubiger haben ein besseres Gedächtnis als Schuldner. msg27626/pgp0.pgp Description: PGP signature
Re: [mplayer] Such das richtige Boot Script für diesen Eintrag?
On Thu, Dec 05, 2002 at 11:34:27AM +0100, Lothar Schweikle-Droll wrote: mplayer schlägt mit folgendes vor: Linux RTC init error in ioctl (rtc_irqp_set 1024): Keine Berechtigung Try adding echo 1024 /proc/sys/dev/rtc/max-user-freq to your system startup scripts. Keine Ahnung, ob das sinnvoll ist. Nur wo trage ich das ein, das das automatisch beim booten geschied? Es gibt zwar den Ordner /etc/rc.boot nur steht da nichts drinn. In /etc/sysctl.conf. http://dugfaq.sylence.net/dug-faq.htm/ch-kernel.htm#s-procpermanent echo 'dev.rtc.max-user-freq=1024' /etc/sysctl.conf cu andreas -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: [mplayer] Such das richtige Boot Script für diesen Eintrag?
Am 05 Dec 2002, schrieb Andreas Metzler: On Thu, Dec 05, 2002 at 11:34:27AM +0100, Lothar Schweikle-Droll wrote: mplayer schlägt mit folgendes vor: Linux RTC init error in ioctl (rtc_irqp_set 1024): Keine Berechtigung Try adding echo 1024 /proc/sys/dev/rtc/max-user-freq to your system startup scripts. Keine Ahnung, ob das sinnvoll ist. Habe ich auch nicht. Nur wo trage ich das ein, das das automatisch beim booten geschied? Es gibt zwar den Ordner /etc/rc.boot nur steht da nichts drinn. In /etc/sysctl.conf. http://dugfaq.sylence.net/dug-faq.htm/ch-kernel.htm#s-procpermanent Ups, habe wohl vergessen da nachzuschauen echo 'dev.rtc.max-user-freq=1024' /etc/sysctl.conf Danke. Ich editire eine Datei immer mit einem Editor. Ist mir zu gefährlich. Ein vergessenes alles alte ist weg. -- Lotharmailto:[EMAIL PROTECTED] Rings in den Wasserköpfen steigt die Flut. msg27631/pgp0.pgp Description: PGP signature
Re: [mplayer] Such das richtige Boot Script für diesen Eintrag?
Hallo, * On Thu, Dec 05, 2002 at 11:34:27AM +0100, Lothar Schweikle-Droll wrote: mplayer schlägt mit folgendes vor: Linux RTC init error in ioctl (rtc_irqp_set 1024): Keine Berechtigung Try adding echo 1024 /proc/sys/dev/rtc/max-user-freq to your system startup scripts. Nur wo trage ich das ein, das das automatisch beim booten geschied? In der /etc/init.d/bootmisc.sh zB. Trage dies in die bootmisc.sh ein: echo 1024 /proc/sys/dev/rtc/max-user-freq Es gibt zwar den Ordner /etc/rc.boot nur steht da nichts drinn. Der Ordner /etc/rc.boot ist sowas wie /etc/ppp/ip-up.d Alles was sich an scripten dort befindet wird (wenn korrekt angelegt) beim booten gestartet. Aber fuer eine Zeile, ... wuerd ich die bootmisc nutzen. Gruss, Clemens Wohld -- sig_42 Schon mal im Mailarchiv von SuSE geschaut? http://lists.suse.com/archives/suse-linux/ Hilfe und sonstige Infos der SuSE Liste: [EMAIL PROTECTED] (help suse-linux im Body) -- -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Boot-Script
Hi! Ich habe ein bißchen mit hdparm gespielt und bin echt erstaunt, wie die Performance steigt durch ein simples hdparm -d1. Leider sind die Einstellungen nach einem Reboot verloren. Ein Bootscript mit hdparm -d1 /dev/hda ist ja nicht das Problem, aber wo spiele ich das Script hin? Oder gibt es schon eine Datei, in die ich diese Zeile einfach reinkopiere? Bei RedHat hab ich mal eine rc.local gehabt, in die ich einfach die Befehle reingeschrieben habe, aber bei Debian konnte ich diese Datei nicht finden. Thnx schon mal. MfG Patrick -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Boot-Script
Hallo! Patrick Petermair [EMAIL PROTECTED] schrieb: Leider sind die Einstellungen nach einem Reboot verloren. Ein Bootscript mit hdparm -d1 /dev/hda ist ja nicht das Problem, aber wo spiele ich das Script hin? Oder gibt es schon eine Datei, in die ich diese Zeile einfach reinkopiere? Ich würde es in das hwtools-Skript einfügen, IIRC wird es dort sogar empfohlen! Ciao, Steve -- www.cargal.org GnuPG-key-ID: 0x051422A0 Be the change you want to see in the world-Mahatma Gandhi Jabber-ID: [EMAIL PROTECTED] msg21063/pgp0.pgp Description: PGP signature
Re: Boot-Script
Patrick Petermair [EMAIL PROTECTED] wrote: Ich habe ein bißchen mit hdparm gespielt und bin echt erstaunt, wie die Performance steigt durch ein simples hdparm -d1. Leider sind die Einstellungen nach einem Reboot verloren. Ein Bootscript mit hdparm -d1 /dev/hda ist ja nicht das Problem, aber wo spiele ich das Script hin? Oder gibt es schon eine Datei, in die ich diese Zeile einfach reinkopiere? Hallo! In unten genannter FAQ steht die Antwort, http://channel.debian.de/faq/ch-confighw.html#s-udmaactivate cu andreas -- FAQ dieser Liste http://dugfaq.sylence.net/ -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Help! Boot script doesn't run
I was installing the latest hamm/hamm sysvinit and also have file-rc installed. The /etc/init.d/boot script doesn't run. None of the file systems are mounted upon boot. That is the / filesystem is mounted read only but it and the other filesytems are never mounted writable. What starts the /etc/init.d/boot script? /etc/runlevel.conf seems OK. Runlevel 2 doesn't work correctly. I'm dead in the water now. Help sincerely appreciated. Regards, -- Victor Torrico -- Wildflower Hill, Head Waters, Virginia -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Help! Boot script doesn't run SOLVED!
On 97/10/13 at 23:15 PM +0200, Miquel van Smoorenburg wrote: In article [EMAIL PROTECTED], Victor Torrico [EMAIL PROTECTED] wrote: I was installing the latest hamm/hamm sysvinit and also have file-rc installed. Oh - oh ... The /etc/init.d/boot script doesn't run. None of the file systems are mounted upon boot. That is the / filesystem is mounted read only but it and the other filesytems are never mounted writable. What starts the /etc/init.d/boot script? /etc/runlevel.conf seems OK. Runlevel 2 doesn't work correctly. I'm dead in the water now. Help sincerely appreciated. For everybody that has this problem, try the following: o Boot with the -b option on the LILO command line o At the shell prompt, enter mount -n -o remount,rw / o edit /etc/inittab ** Write down how the entry with /etc/init.d/boot looks now, I really would like to know that! - The entry before changing the /etc/inittab file is: si::sysinit:/etc/init.d/rcS I changed this to: si::sysinit:/etc/init.d/boot Also the installation of sysvinit 0.72 had actually deleted the /etc/init.d/boot file. I copied /etc/init.d/boot.OLD to /etc/init.d/boot to restore the file. This and going from .../rcS to .../boot fixed the problem. To test I reinstalled sysvinit 0.72 and the /etc/inittab entry went back to: si::sysinit:/etc/init.d/rcS Also the /etc/init.d/boot file once again was deleted. - Thank you for your kindness in helping. Regards, Victor o change the /etc/init.d/boot to /etc/init.d/rcS so that it looks like si::sysinit:/etc/init.d/rcS o Save and exit o Type mount -n -o remount,ro / o Enter reboot -f Now the system should boot again. I'll upload a fixed sysvinit tommorow morning. In the mean time, do NOT install sysvinit-2.72 ! PS: please read the line with `**' again and mail me ! Mike. -- Miquel van | Cistron Internet Services --Alphen aan den Rijn. Smoorenburg,| mailto:[EMAIL PROTECTED] http://www.cistron.nl/ [EMAIL PROTECTED] | Our vision is to speed up time, eventually eliminating it. -- Victor Torrico -- Wildflower Hill, Head Waters, Virginia -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
