T o n g | 1 Apr 2009 04:54
Picon
Favicon

Re: Next stable release

Thanks for the answers, mika.

On Wed, 01 Apr 2009 00:07:50 +0200, Michael Prokop wrote:

> The most important one is the kernel issue: should we think about
> re-enabling PATA support? I guess it might be worth a try to start a
> poll for this issue

PATA is disabled? Does it mean that IDE / ATA HD is not supported 
currently by grml? I don't know exactly what it means to disable PATA, 
but please, please do support IDE/ATA, because there are tons of exiting 
PCs still using nothing but IDE/ATA.

Thanks

--

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/

Jason White | 1 Apr 2009 04:58

Re: Next stable release

T o n g <mlist4suntong <at> yahoo.com> wrote:

> PATA is disabled? Does it mean that IDE / ATA HD is not supported 
> currently by grml? 

Not if the new libata drivers are enabled in the kernel instead of the old IDE
drivers, which I have been informed on other mailing lists are now regarded as
legacy code.

T o n g | 1 Apr 2009 05:21
Picon
Favicon

cdrecord devices

Hi,

The evolving of cdrecord/wodim and its device specification have been 
convoluted enough for me to get lost on how to use its devices. 

My current cdrecord command is the "real one" from grml:

 $ apt-cache policy cdrecord
 cdrecord:
  Installed: 9:2.01.01-1~a50
  Candidate: 9:2.01.01-1~a50
  Version table:
 *** 9:2.01.01-1~a50 0
        683 http://deb.grml.org grml-testing/main Packages
        100 /var/lib/dpkg/status

 cdrecord -scanbus

suggests to us the ATA interface, so I 

 export CDR_DEVICE=ATA:2,0,0

but when try to access the device, I get:

$ cdrecord -toc
Cdrecord-ProDVD-ProBD-Clone 2.01.01a50 (x86_64-unknown-linux-gnu) 
Copyright (C) 1995-2008 Jörg Schilling
scsidev: 'ATA:2,0,0'
devname: 'ATA'
scsibus: 2 target: 0 lun: 0
(Continue reading)

T o n g | 1 Apr 2009 05:25
Picon
Favicon

Re: Next stable release

Thanks for the reply. 

On Wed, 01 Apr 2009 13:58:28 +1100, Jason White wrote:

>> PATA is disabled? Does it mean that IDE / ATA HD is not supported
>> currently by grml?
> 
> Not if the new libata drivers are enabled in the kernel instead of the
> old IDE drivers, which I have been informed on other mailing lists are
> now regarded as legacy code.

Then for people who only have IDE hard disks (not SATA), what should they 
do to use the HD?

thanks

--

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/

Jason White | 1 Apr 2009 05:40

Re: Next stable release

T o n g <mlist4suntong <at> yahoo.com> wrote:

> Then for people who only have IDE hard disks (not SATA), what should they 
> do to use the HD?

It's still supported but it appears as /dev/sda, /dev/sdb etc., with the new
drivers.

Peter | 1 Apr 2009 21:51

Remastering grml

Hi
I am not sure that I understand the instructions for remastering the 
grml live cd ( old method, not FAI).
The man page for grml-live says:
 Please use squashfs-lzma-tools 3.3.1 if you want to remaster release 
2008.11 of grml.

I want to remaster the medium flavor.
As far as I can see from uname -a , grml 2008 is kernel  2.6.26. 
However, here <http://www.squashfs-lzma.org/>it is said that only 
version 2.6.27.6 is officially supported.

Also , I was wondering, if this instruction does still apply to grml 2008.11

 wget http://mesh.dl.sourceforge.net/sourceforge/squashfs/squashfs2.2-r2.tar.gz
$ tar xvzf squashfs2.2-r2.tar.gz
$ cd /lib/modules/`uname -r`/build
$ patch -p1 --dry-run < /usr/src/squashfs2.2-r2/linux-2.X.Y/squashfs2.2-patch

In short, I am asking, what is the recommended way to remaster grml 
2008.11 with grml2008.11 as build environment ?

Thanks for your help

Peter
Michael Prokop | 1 Apr 2009 23:08
Favicon

Re: Remastering grml

* Peter <vmail <at> mycircuit.org> [20090401 22:52]:

> I am not sure that I understand the instructions for remastering the 
> grml live cd ( old method, not FAI).
> The man page for grml-live says:
>  Please use squashfs-lzma-tools 3.3.1 if you want to remaster release 
> 2008.11 of grml.

> I want to remaster the medium flavor.
> As far as I can see from uname -a , grml 2008 is kernel  2.6.26. 
> However, here <http://www.squashfs-lzma.org/>it is said that only 
> version 2.6.27.6 is officially supported.

> Also , I was wondering, if this instruction does still apply to grml 2008.11

>  wget http://mesh.dl.sourceforge.net/sourceforge/squashfs/squashfs2.2-r2.tar.gz
> $ tar xvzf squashfs2.2-r2.tar.gz
> $ cd /lib/modules/`uname -r`/build
> $ patch -p1 --dry-run < /usr/src/squashfs2.2-r2/linux-2.X.Y/squashfs2.2-patch

> In short, I am asking, what is the recommended way to remaster grml 
> 2008.11 with grml2008.11 as build environment ?

No need for manual actions, grml provides all the relevant stuff for
remastering out-of-the-box. :)

The documentation regarding squashfs is mainly interesting if you
want to build on non-grml systems or when remastering/building
older/newer grml versions. It's meant to be a reference for people
encountering any problems with building.
(Continue reading)

Peter | 1 Apr 2009 22:44

Installing grml on usb stick

Hi
I wanted to suggest some minor modifications to the instructions concerning the usb stick installation.
I found that in order to install grml-medium-2008.11 , I had to adjust the lines in red. I also added some requirements that might not be available , when your build environment is not grml ( I suppose $medium can be replaced with the other flavors but I have not verified ):

aptitude install syslinux   # syslinux 3.71 or later must be available on your GNU/Linux system

aptitude install dosfstools  # to get mkfs.vfat

  • Get the grml iso
  • Mount the iso loopback (e.g. mount -o loop grml_small_0.4.iso /mnt/grml-iso)
  • Make FAT16 filesystem on the usbstick (e.g. mkfs.vfat -F 32  /dev/sda1)
  • Create a disklabel (e.g. dosfslabel /dev/sda1 GRML)
  • Mount the usbstick (e.g. mount /dev/sda1 /mnt/external1)
  • Copy everything to the usbstick (e.g. cp -r /mnt/grml-iso/* /mnt/external1).
  • Move all files from /mnt/external1/boot/isolinux/ (mv /mnt/external1/boot/isolinux/* /mnt/external1)
and the files linux26 and the minirt.gz (since grml1.1: initrd.gz!) from the directory named like the grml-flavour (/boot/grml, /boot/grmlmedium, /boot/grml64,...) to root of usb-stick

         in /mnt/external1, mv isolinux.cfg to syslinux.cfg  #I am not sure if this is required, though

  • the files linux26 and initrd.gz must remain in boot/grmlmedium  # this is what is said in syslinux.cfg
  • Umount the usbstick and the grml-iso
  • Run syslinux on the usbstick (e.g. syslinux /dev/sda1)
  • Check if the usbstick has an valid mbr, else dd if=mbr.bin of=/dev/sda (mbr.bin is in the syslinux package, usually installed in /usr/lib/syslinux/mbr.bin)
  • may need to set the bootable flag using parted (or fdisk)

disk layout:

/mnt/external1: addons f1 .. isolinux isolinux.bin syslinux.cfg ldlinux.sys live/ filesystem.module grml-medium.squashfs boot/grmlmedium initrd.gz linux26
Pleases let me know , if I am wrong of if there are better ways to do that ( I know, there is grml2usb, but I want to be sure to understand what's going on)

Thanks
Peter
<div>
Hi<br>
I wanted to suggest some minor modifications to the instructions
concerning the usb stick installation.<br>
I found that in order to install grml-medium-2008.11 , I had to adjust
the lines in red. I also added some requirements
that might not be available , when your build environment is not grml (
I suppose $medium can be replaced with the other flavors but I have not
verified ):<br><br><p>aptitude install syslinux&nbsp;&nbsp; # <a href="http://clonezilla.org/clonezilla-live/liveusb.php">syslinux 3.71
or later must be available on your GNU/Linux system</a><br></p>
<p>aptitude install dosfstools&nbsp; # to get mkfs.vfat</p>
<div class="level2">
<ul>
<li class="level1"><span class="li"> Get the grml iso</span></li>
  <li class="level1"><span class="li"> Mount the iso loopback (e.g.
mount -o loop grml_small_0.4.iso /mnt/grml-iso)</span></li>
  <li class="level1"><span class="li"> Make FAT16 filesystem on the
usbstick (e.g. mkfs.vfat -F 32&nbsp; /dev/sda1)</span></li>
  <li class="level1"><span class="li"> Create a disklabel (e.g.
dosfslabel /dev/sda1 GRML)</span></li>
  <li class="level1"><span class="li"> Mount the usbstick (e.g. mount
/dev/sda1 /mnt/external1)</span></li>
  <li class="level1"><span class="li"> Copy everything to the usbstick
(e.g. cp -r /mnt/grml-iso/* /mnt/external1).</span></li>
  <li class="level1"><span class="li"> Move all files from
/mnt/external1/boot/isolinux/ (mv /mnt/external1/boot/isolinux/*
/mnt/external1)</span></li>
</ul>
<span class="li">and the files linux26 and the minirt.gz (since
grml1.1: initrd.gz!) from the directory named like the grml-flavour
(/boot/grml, /boot/grmlmedium, /boot/grml64,...) to root of usb-stick</span>
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in /mnt/external1, mv isolinux.cfg to
syslinux.cfg&nbsp; #<a href="http://www.livecd.ethz.ch/usbdisk.html">I am not sure if this is
required, though</a><br></p>
<ul>
<li class="level1"><span class="li">the files
linux26 and initrd.gz must remain in boot/grmlmedium&nbsp; # this is what is
said in syslinux.cfg<br></span></li>
  <li class="level1"><span class="li"> Umount the usbstick and the
grml-iso</span></li>
  <li class="level1"><span class="li"> Run syslinux on the usbstick
(e.g. syslinux /dev/sda1)</span></li>
  <li class="level1"><span class="li"> Check if the usbstick has an
valid
mbr, else dd if=mbr.bin of=/dev/sda (mbr.bin is in the syslinux
package, usually installed in /usr/lib/syslinux/mbr.bin)</span></li>
  <li class="level1"><span class="li"> may need to set the bootable
flag using parted (or fdisk)</span></li>
</ul>
</div>
<p>disk layout:</p>
/mnt/external1:

addons
f1
..
isolinux
isolinux.bin
syslinux.cfg
ldlinux.sys
live/
   filesystem.module
   grml-medium.squashfs

boot/grmlmedium
  initrd.gz
  linux26

<br>
Pleases let me know , if I am wrong of if there are better ways to do
that ( I know, there is grml2usb, but I want to be sure to understand
what's going on)<br><br>
Thanks<br>
Peter<br>
</div>
Michael Prokop | 2 Apr 2009 11:26
Favicon

Poll: PATA vs. LIBATA

Hi,

the grml team wants to collect feedback regarding the recent switch
from PATA to LIBATA. PATA? LIBATA?

* PATA provides the old IDE subsystem (/dev/hdX), considered as
  legacy code.
* LIBATA is the new subsystem (/dev/sdX) with new features, but some
  old IDE systems might not work with it.

Please participate in the poll! => http://doodle.com/vr75tpe4a2p6mwvt

We highly appreciate and need your feedback.
Thanks!

regards,
-mika-
-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc
Hi,

the grml team wants to collect feedback regarding the recent switch
from PATA to LIBATA. PATA? LIBATA?

* PATA provides the old IDE subsystem (/dev/hdX), considered as
  legacy code.
* LIBATA is the new subsystem (/dev/sdX) with new features, but some
  old IDE systems might not work with it.

Please participate in the poll! => http://doodle.com/vr75tpe4a2p6mwvt

We highly appreciate and need your feedback.
Thanks!

regards,
-mika-
--

-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc
Frank Terbeck | 2 Apr 2009 13:35
Favicon

Re: Poll: PATA vs. LIBATA

Michael Prokop <mika <at> grml.org>:
[...]
> * PATA provides the old IDE subsystem (/dev/hdX), considered as
>   legacy code.
> * LIBATA is the new subsystem (/dev/sdX) with new features, but some
>   old IDE systems might not work with it.

Okay, the advantage in using PATA is backwards compatibility, which is
a good thing[tm].

The advantage of libata are the "new features".

For an educated decision, it would be good to know some drawbacks
involved when reverting from libata. In other words: what does the
user lose if grml reverts to pata?

Regards, Frank

--

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925

Gmane