- Grml - lists.mur.at

/dev/dvd
by T 03 Sep '06

03 Sep '06

Hi Currently grml does not provides the /dev/dvd link. I remember I read somewhere that merely adding a rule symlink to /etc/udev/rules.d/ will do. But I just can't find it any more. Any one knows about how to do it? thanks tong

3 2

Wishlist: automount by names
by T 02 Sep '06

02 Sep '06

Hi I know grml can (re)generate fstab on boot each time. However, I'd like to access my partitions by their names instead of sda7, sda12, which I have no way to remember. So I have to disable the automatic fstab generation on boot. I hope that grml can utilize the automount, as knopsis does, and use udev to access them by their names, ie disk labels. The bonus is that USB drives will be taken care of as well by this. Would this happen in near future, or I'm out of luck and have to find the way to do it myself. thanks tong

3 9

Re: afio i/o- Error
by Eugen Romas 31 Aug '06

31 Aug '06

> > * Eugen Romas <eugen.romas(a)romas.de> [20060830 14:15]: >> > Eugen Romas schrieb: >> >>> > > Von diesem PC will ich eine verschlüsselte Komplettsicherung erstellen. >>> >>> > > Nach dem Booten von *grml 0.8 - Codename Funkenzutzler *finde >>> > > ich alle Raid- Partitionen richtig zugeordnet wieder. Nun habe >>> > > ich die "mapped crypt devices" mit cryptsetup angelegt, genau so >>> > > wie sie normalerweise erstellt werden. Mit mkdir neue >>> > > mountpoints unter /mnt angelegt und alle Partitionen gemountet. >>> > > Lesezugriffe funktionieren einwandfrei. afio bringt aber leider >>> > > i/o- Error bei einigen wenigen Files. >>> >>> > > Das bash- Skript, das ich verwende, funktioniert mit dem >>> > > Originalsystem ohne Schwierigkeiten, Plattenplatz ist also genug >>> > > da. >>> Sorry, with some more testing I got the same errors on my Debian-Sarge-System. >>> > > find $DIRECTORY -mount -depth | afio -ovZ -P gpg -Q --symmetric >>> > > -Q --passphrase-fd=3 -Q --no-verbose -Q--batch -Q --no-options >>> > > -3 3 $ARCHIVNAME 3<$BACKUPCFG >>> >>> > > Die Ausgabe erfolgt auf /mnt/md7. >>> >>> > > Was kann die Ursache sein? >>> >> > the error above dos not appear anymore and I don't know why. >> > Instead I get new errors: >> >> > afio: "/mnt/usr/bin/skype.z": Error zipping file, written damaged copy >> > to archive. >> > afio: "/mnt/usr/lib/openoffice/program/libsw680li.so.z": Error zipping >> > file, written damaged copy to archive. >> > afio: "/mnt/usr/java/jre-1_5_0_08-linux-i586.bin.z": Error zipping file, >> > written damaged copy to archive. >> > > Might this be related to > http://lists.gnupg.org/pipermail/gnupg-users/2004-January/021299.html > ? > > With using my own script for zipping and encrypting I got the errors too. > Otherwise it might be related to the unionfs overlay setup. > Which working directory are you using when starting your script and > what's $DIRECTORY standing for? Maybe using $DIRECTORY as the > working directory and '.' instead of $DIRECTORY fixes the problem? > > regards, > -mika- > > It seems to be an other problem, not a special problem of grml! If I vary the zipping level from gpg I get more errors with higher compression and less errors with lower compression. I found out that the md5sum of restored "damaged copies" is the same as of the original files (as Mr. Marcus Williams wrote). My solution is to verify the "damaged copies" against the filesystem. If a file is really damaged, then I do a special backup for it first and then by reducing the compression level. Many thanks for for your help, regards, Eugen

1 0

Xorg, choosing default resolution
by T 31 Aug '06

31 Aug '06

[reposted from other mlist] Anyone can help me out with the following? Mika, any thoughts or ideas? Is it an xorg problem, or purely X driver related. I'm using fglrx for my ATI BTW. This happens after I upgrade from grml0.7 to grml0.8. thanks a lot Subject: Xorg, choosing default resolution Newsgroups: gmane.linux.debian.user Date: Wed, 30 Aug 2006 15:12:35 +0200 Hi My Xorg starts up in 1280x960 mode, which I don't like. I like it to be 1152x864. How can I make my Xorg starts up in 1152x864 mode? Here is my Screen. See, there is no 1280x960 listed in the mode, but yet Xorg starts with it. Section "Screen" Identifier "aticonfig-Screen[0]" Device "aticonfig-Device[0]" Monitor "aticonfig-Monitor[0]" DefaultDepth 24 # DefaultMode 1152x864 SubSection "Display" Viewport 0 0 Modes "1152x864" "1024x768" "800x600" "720x400" "640x480" Depth 24 EndSubSection EndSection The man page says "the first valid mode in this list will be the default display mode for startup". Yet my xorg fails that also. Moreover, The word "DefaultMode" is not recognized by Xorg. So, how could I? thanks tong ps - my xorg: $ apt-cache policy xorg xorg: Installed: 1:7.0.22 Candidate: 1:7.0.22 - the same xorg.conf works fine for xorg6.9 before.

1 0

Dependency on console bitmap fonts
by T 31 Aug '06

31 Aug '06

Hi I'm not used to the new console-terminus font, and would perfer the traditional one. However, I can't remove it: $ apt-get remove --purge console-terminus The following packages will be REMOVED: console-terminus* grml* grml-autoconfig* grml-debugtools* grml-etc* grml-x* 0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded. Would it be a better idea to have this extra eye candy to be recommended, as opposed to required? I was able to remove it in grml0.7 and didn't have any problem with that... thanks tong

2 2

grml0.8 grml2hd test report
by T 31 Aug '06

31 Aug '06

Hi I just tried grml2hd from grml0.8 with: grml2hd partion=/dev/sda4 mbr=/dev/sda4 filesystem=ext3 user=tong - grml2hd said partion /dev/sda4 can't be found. Manually choose the sda4 from the provided menu entry works fine. - "user=" parameter didn't work. grml2hd still prompts 'grml' as the default user. The mbr & filesystem parameter seem to be working fine. - Since I don't have network access (due to no eth0), I run grml2hd as-is, ie, without using the latest version. But it failed to create initrd, because it can't find the grml kernel module file, IIRC. - Installing lilo failed subsequently, because it can't find the initrd.

2 7

Still cannot move root user to home partition
by Mark 30 Aug '06

30 Aug '06

Mika, The symlink idea below actaully does not work: http://article.gmane.org/gmane.linux.distributions.grml.user/161 Tested under 0.8 final. M

3 8

Grml2hd Xorg.conf screen blanks
by Mark 30 Aug '06

30 Aug '06

grml live CD 0.8 final plus "apt-get update; apt-get install grml2hd" At the xorg.conf step, if I say "yes," part of the screen goes black. The dialogs become impossible, although staying active. (If only they were movable with the mouse.) If I say "no" everything works fine. The blackness is top to bottom across ~40% of the horizontal, sort of middle of screen. nVidia GeForce card, but without nvidia drivers, just the live CD with no special boot codes (except noswap). When I ctrl-c out of the script, the screen is still bad, so I have to reboot. M

2 3

afio i/o- Error
by Eugen Romas 30 Aug '06

30 Aug '06

Hallo liebe Freunde, ich bin neu hier und habe gleich ein Problem. :'( Vielleicht kann mir jemand helfen? Ich betreibe ein Debian-Sarge-Crypto-Software-Raid1-System mit zwei Festplatten auf einem Scaleo 600 AXP 21 1 1500MB (AMD Athlon(tm) XP2100+). Bootloader: GRUB, Kernel: 2.6.8-3-k7, Partitionierung: 1. /boot unverschlüsselt /dev/md0 2. / verschlüsselt /dev/mapper/root 3. /usr „ /dev/mapper/usr 4. /var „ /dev/mapper/var 5. /swap „ /dev/mapper/swap 6. /tmp „ /dev/mapper/tmp 7. /home „ /dev/mapper/home 8. unverschlüsselt /dev/md7 Alle sind ext3fs Filesysteme. Von diesem PC will ich eine verschlüsselte Komplettsicherung erstellen. Nach dem Booten von *grml 0.8 - Codename Funkenzutzler *finde ich alle Raid- Partitionen richtig zugeordnet wieder. Nun habe ich die "mapped crypt devices" mit cryptsetup angelegt, genau so wie sie normalerweise erstellt werden. Mit mkdir neue mountpoints unter /mnt angelegt und alle Partitionen gemountet. Lesezugriffe funktionieren einwandfrei. afio bringt aber leider i/o- Error bei einigen wenigen Files. Das bash- Skript, das ich verwende, funktioniert mit dem Originalsystem ohne Schwierigkeiten, Plattenplatz ist also genug da. ... find $DIRECTORY -mount -depth | afio -ovZ -P gpg -Q --symmetric -Q --passphrase-fd=3 -Q --no-verbose -Q--batch -Q --no-options -3 3 $ARCHIVNAME 3<$BACKUPCFG ... ... Die Ausgabe erfolgt auf /mnt/md7. Was kann die Ursache sein? Welche Lösung gibt es? Viele Grüße aus dem schönen Thüringen von Eugen **

2 2

fglrx victory
by Martin Yazdzik 30 Aug '06

30 Aug '06

Dear mika and friends, As y ou can see from the attached, I have 3d working. I cheated - since the xorg log error was "unable to find screen" I took my working file from grml 7 and simple copied it. The differences are: Working: Section "Monitor" Identifier "Monitor0" # ModelName "Old Monitor (no DDC)" Option "DPMS" "true" # HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors # HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors HorizSync 28.0 - 96.0 # VertRefresh 50.0 - 76.0 # Very conservative. May flicker. # VertRefresh 50.0 - 60.0 # Extreme conservative. Will flicker. TFT default. VertRefresh 50.0 - 60.0 # Need more information? # http://xtiming.sourceforge.net/cgi-bin/xtiming.pl # http://en.tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/ EndSection Section "Device" ### Available Driver options are: ## sw_cursor is needed for some ati and radeon cards # Option "sw_cursor" # Option "hw_cursor" # Option "NoAccel" # Option "ShowCache" # Option "ShadowFB" # Option "UseFBDev" # Option "Rotate" ## xorg + nvidia: # Option "RenderAccel" "true" # Option "AllowGLXWithComposite" "true" Identifier "Card0" # The following line is auto-generated by grml-x Driver "fglrx" VendorName "All" BoardName "All" ## Workaround for drivers which send output to wrong device: # Option "MonitorLayout" "LVDS, AUTO" # Option "MonitorLayout" "LVDS, CRT" # Option "MonitorLayout" "NONE, STV" # Option "MonitorLayout" "LVDS" ## Specify BusID: # BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultColorDepth 24 SubSection "Display" Depth 1 # Modes "1024x768" "800x600" "640x480" "1600x1200" "1280x1024" "1280x960" EndSubSection SubSection "Display" Depth 4 # Modes "1024x768" "800x600" "640x480" "1600x1200" "1280x1024" "1280x960" EndSubSection SubSection "Display" Depth 8 # Modes "1024x768" "800x600" "640x480" "1600x1200" "1280x1024" "1280x960" EndSubSection SubSection "Display" Depth 15 # Modes "1024x768" "800x600" "640x480" "1600x1200" "1280x1024" "1280x960" EndSubSection SubSection "Display" Depth 16 # Modes "1024x768" "800x600" "640x480" "1600x1200" "1280x1024" "1280x960" EndSubSection SubSection "Display" Depth 24 # Modes "1920X1200" "1024x768" "800x600" "640x480" "1600x1200" "1280x1024" "1280x960" EndSubSection SubSection "Display" Depth 32 # Modes "1024x768" "800x600" "640x480" "1600x1200" "1280x1024" "1280x960" EndSubSection EndSection Non-wokring: Section "Monitor" Identifier "Monitor0" # ModelName "Old Monitor (no DDC)" Option "DPMS" "true" # HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors # HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors HorizSync 28.0 - 96.0 # VertRefresh 50.0 - 76.0 # Very conservative. May flicker. # VertRefresh 50.0 - 60.0 # Extreme conservative. Will flicker. TFT default. VertRefresh 50.0 - 60.0 # Need more information? # http://xtiming.sourceforge.net/cgi-bin/xtiming.pl # http://en.tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/ EndSection Section "Device" ### Available Driver options are: ## sw_cursor is needed for some ati and radeon cards # Option "sw_cursor" # Option "hw_cursor" # Option "NoAccel" # Option "ShowCache" # Option "ShadowFB" # Option "UseFBDev" # Option "Rotate" ## xorg + nvidia: # Option "RenderAccel" "true" # Option "AllowGLXWithComposite" "true" Identifier "Card0" # The following line is auto-generated by grml-x Driver "fglrx" VendorName "All" BoardName "All" ## Workaround for drivers which send output to wrong device: # Option "MonitorLayout" "LVDS, AUTO" # Option "MonitorLayout" "LVDS, CRT" # Option "MonitorLayout" "NONE, STV" # Option "MonitorLayout" "LVDS" ## Specify BusID: # BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultColorDepth 16 SubSection "Display" Depth 1 # Modes "1920x1200" EndSubSection SubSection "Display" Depth 4 # Modes "1920x1200" EndSubSection SubSection "Display" Depth 8 # Modes "1920x1200" EndSubSection SubSection "Display" Depth 15 # Modes "1920x1200" EndSubSection SubSection "Display" Depth 16 # Modes "1920x1200" EndSubSection SubSection "Display" Depth 24 # Modes "1920x1200" EndSubSection SubSection "Display" Depth 32 # Modes "1920x1200" EndSubSection EndSection Since the screen is correctly identified in the non-working file as 1920x1200, which is in fact the current and functioning resolution, and the olny other difference appears to the the default bit depth, I am perplexed. However, there is definitely a speed improvement over 7. Also, I fixed the time zone issue with brute force, by deleting every reference in every /etc file I could find - works fine now.... Thus, we have linux for sysadmins and one rock ape - martin... note also, I am using the ati 28 drivers and kernel-module. Now, if the hsf driver works, I am in business. Thanks for all the help, hard work, and sheer brilliance. Gruesse aus NY, M

2 1