Welcome! Log In Create A New Profile

Advanced

Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood

Posted by notoneofmyseeds 
Forum List Message List New Topic
notoneofmyseeds
Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 23, 2016 06:27PM
I have just now had to extract Wheezy to a new and bigger USB stick, booted, ssh, etc and all is good.

I'd like to move to Linux Kernel 4.6 Kirkwood and was wondering whether I could skip the earlier 4.xxxx and go straight to Linux Kernel 4.6 Kirkwood. And if so, please, how?

Thanks a lot.
Reply Quote
bodhi
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 24, 2016 12:55AM
notoneofmyseeds,

If you install a new rootfs then skip wheezy 3.16. Just create a jessie rootfs instead:


Quote
http://forum.doozan.com/read.php?2,12096
Updated 20 Feb 2016:

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.

After booting into this 4.4 rootfs, install kernel 4.6:

Quote
http://forum.doozan.com/read.php?2,12096
Updated 20 May 2016:

Kernel linux-4.6.0-kirkwood-tld-1 package has been uploaded. The following features were added/updated

Is that clear? if you'd like, post the commands that you think you need to execute here and I'll doublecheck. That's the best way to learn. If you have trouble understanding the instruction in the kernel thread, just post your questions.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
notoneofmyseeds
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 24, 2016 04:24AM
Thanks a lot.

Now I have: tar -xjf Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2 on the USB stick

OK. I follow your instructions.

Here is what I will do.

1. I will remove the USB stick from the pogo
2. Use gparted to reformat it into a singel ext3 partition
3. Copy Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 to the USB
4. In Terminal, cd like this: cd /media/sunnsea/rootfs
Extract tar -xjf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 with:

In your direction, you asked: "Adjust fstab. Skip this step if you have installed my latest u-boot release."

How do I check my u-boot release? And should I install the latest u-boot first, before going onto
Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2

To creat the: " Create uImage"
While still in /media/sunnsea/rootfs, I will do:

1. cd /media/sunnsea/boot
2. cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
sync
3. apt-get install u-boot-tools

After plugging the USB into the pink

1. rm /etc/ssh/ssh_host*
ssh-keygen -A

apt-get update
apt-get upgrade

2. Somewhat clueless on this one, but I think I follow instructions here?
http://forum.doozan.com/read.php?3,12381

Thanks a million. I agree, this is the best way to learn and this way deals with the danger of not bricking, which freaks me out. I've never really enjoyed this since I bought it and with your help, I'm very close.
Reply Quote
bodhi
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 25, 2016 02:35AM
I've annotated below in bold.

1. I will remove the USB stick from the pogo
2. Use gparted to reformat it into a singel ext3 partition
3. Copy Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 to the USB

4. In Terminal, cd like this:

Right here, you need to log in as root user. From this point on, you must be root.
Check if you are root: 
whoami

Then go ahead continue on. 

cd /media/sunnsea/rootfs

Extract
tar -xjf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2

In your direction, you asked: "Adjust fstab. Skip this step if you have installed my latest u-boot release."

How do I check my u-boot release? And should I install the latest u-boot first, before going onto
Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2

fstab is not important if the kernel parameters already specifying it. That will need to be confirmed in u-boot envs. Let's do that in the next post as I mentioned below.

To creat the: " Create uImage"
While still in /media/sunnsea/rootfs, I will do:

1. 
cd /media/sunnsea/boot


2.
cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
sync

You are done with the rootfs here. But the question here is do you have the GoFlex Net? if you do then the above was correct. If you do not then it was wrong.

The next thing to do is to check the u-boot envs and its version. Since you don't know or did not record the log of whatever you've done on this box. Please get out put of 

fw_printenv


-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
notoneofmyseeds
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 27, 2016 03:43AM
bodhi Wrote:
-------------------------------------------------------
> I've annotated below in bold.
>
> 1. I will remove the USB stick from the pogo
> 2. Use gparted to reformat it into a singel ext3
> partition
> 3. Copy
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> to the USB
>
> 4. In Terminal, cd like this:
>
> Right here, you need to log in as root user.
> From this point on, you must be root.
> Check if you are root:
> 
> whoami
>
>
> Then go ahead continue on.
>
> 
> cd /media/sunnsea/rootfs
>
>
> Extract
> tar -xjf
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
>
> In your direction, you asked: "Adjust fstab. Skip
> this step if you have installed my latest u-boot
> release."
>
> How do I check my u-boot release? And should I
> install the latest u-boot first, before going onto
>
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
>
> fstab is not important if the kernel parameters
> already specifying it. That will need to be
> confirmed in u-boot envs. Let's do that in the
> next post as I mentioned below.
>
> To creat the: " Create uImage"
> While still in /media/sunnsea/rootfs, I will do:
>
> 1.
> 
> cd /media/sunnsea/boot
>
>
>
> 2.
> cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
> cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
> mv uImage uImage.orig
> mkimage -A arm -O linux -T kernel -C none -a
> 0x00008000 -e 0x00008000 -n
> Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
> sync
>
> You are done with the rootfs here. But the
> question here is do you have the GoFlex Net? if
> you do then the above was correct. If you do not
> then it was wrong.
>
> The next thing to do is to check the u-boot envs
> and its version. Since you don't know or did not
> record the log of whatever you've done on this
> box. Please get out put of
>
> 
> fw_printenv
>
>

You, bohdi, are amazing.

Here are the results, but before that let me say that it took some common sense. I almost gave up when the green led lights did not come, after waiting for ages. And so I thought, let me just ssh into the box and see what happens, and here are the results, including the "fw_printenv" output.

root@10.0.0.2's password:
Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Feb 19 20:08:26 2016 from 192.168.0.100
root@debian:~# fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
arcNumber=2998
usb_init=run usb_scan ; setenv usb_root LABEL=rootfs
root@debian:~#

Now, my dear friend; what next would you say? You have been a wonder; a real wonder who should be teaching people computing. It would be nice to have the green led lights back on. It was on with Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2.
And look at me, lost my manners; thank you, wonder man.



Edited 1 time(s). Last edit at 05/31/2016 01:18AM by notoneofmyseeds.
Reply Quote
bodhi
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 27, 2016 04:57AM
notoneofmyseeds,

> Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon
> Jan 25 20:35:24 PST 2016 armv5tel

Cool :) we are now going full steam ahead, once we see the Debian login banner like that!

> It would be nice to
> have the green led lights back on. It was on with
> Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2.

This is where the rootfs /etc/rc.local come in to play.

cat /etc/rc.local 
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# turn on LED

if [ -d /sys/class/leds/status:green:health ]; then
   echo default-on > /sys/class/leds/status:green:health/trigger
   if [ -d /sys/class/leds/status:orange:fault ]; then
      echo none > /sys/class/leds/status:orange:fault/trigger
   fi
   if [ -d /sys/class/leds/status:blue:health ]; then
      echo none > /sys/class/leds/status:blue:health/trigger
   fi
fi
if [ -d /sys/class/leds/dockstar:green:health ]; then
   echo default-on > /sys/class/leds/dockstar:green:health/trigger
   echo none > /sys/class/leds/dockstar:orange:misc/trigger
fi

if [ -d /sys/class/leds/plug:green:health ]; then
   echo default-on > /sys/class/leds/plug:green:health/trigger
   if [ -d /sys/class/leds/plug:red:misc ]; then
      echo none  > /sys/class/leds/plug:red:misc/trigger
   fi
fi

if [ -d /sys/class/leds/power:blue ]; then
   echo default-on  > /sys/class/leds/power:blue/trigger
   ### echo default-on  > /sys/class/leds/otb:blue/trigger
   echo none        > /sys/class/leds/power:red/trigger
fi

if [ -d /sys/class/leds/usb1:blue ]; then
   echo usb-host > /sys/class/leds/usb1\:blue/trigger
fi
if [ -d /sys/class/leds/usb2:blue ]; then
   echo usb-host > /sys/class/leds/usb2\:blue/trigger
fi
if [ -d /sys/class/leds/usb3:blue ]; then
   echo usb-host > /sys/class/leds/usb3\:blue/trigger
fi
if [ -d /sys/class/leds/usb4:blue ]; then
   echo usb-host > /sys/class/leds/usb4\:blue/trigger
fi

if [ -d /sys/class/leds/nsa325:green:sys ]; then
   echo default-on  > /sys/class/leds/nsa325:green:sys/trigger
   echo none        > /sys/class/leds/nsa325:orange:sys/trigger
fi

if [ -d /sys/class/leds/nsa325:green:sata1 ]; then
   echo ide-disk1  > /sys/class/leds/nsa325:green:sata1/trigger
fi

if [ -d /sys/class/leds/nsa325:green:sata2 ]; then
   echo ide-disk2  > /sys/class/leds/nsa325:green:sata2/trigger
fi

if [ -d /sys/class/leds/nsa325:green:usb ]; then
   echo usb-host > /sys/class/leds/nsa325\:green\:usb/trigger
fi

exit 0

See the echo statements that change the green LED to "default-on"? that's how your LED was triggered to turn green. Depending on the hardware, appropriate commands will be executed.

The possible reason that why it did not turn green.

1. Your box is not Goflex Net. One of the step before was to append this DTB file (which decribes the hardware) to uImage. So the DTB must be the correct one. If it were not then the green LED would have a different GPIO address so it would not turn on by the "echo".

2. Run this command to list your box info (this is an alias that I added to the rootfs, not a standard Linux command): 
myinfo

Does what it say about this box matches with what you actually have?

3. Look back to the step 

cat dts/kirkwood-goflexnet.dtb >> zImage.fdt

If your box is a different one then you have to redo that. You can do this while the system is running. Replace yourboxname with the actual name of this kirkwood box (you have to find the correctly spelling name in /boot/dts). 

cd /boot
mv uImage uImage.orig.2
cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-yourboxname.dtb >> zImage.fdt 
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage 
sync
sync

Then reboot the system.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 05/30/2016 06:00PM by bodhi.
Reply Quote
notoneofmyseeds
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 30, 2016 05:23PM
bodhi Wrote:
-------------------------------------------------------
> notoneofmyseeds,
>
> > Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT
> Mon
> > Jan 25 20:35:24 PST 2016 armv5tel
>
> Cool :) we are now going full steam ahead, once
> we see the Debian login banner like that!
>
> > It would be nice to
> > have the green led lights back on. It was on
> with
> >
> Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2.
>
>
> This is where the rootfs /etc/rc.local come in to
> play.
>
> cat /etc/rc.local
> 
> #!/bin/sh -e
> #
> # rc.local
> #
> # This script is executed at the end of each
> multiuser runlevel.
> # Make sure that the script will "exit 0" on
> success or any other
> # value on error.
> #
> # In order to enable or disable this script just
> change the execution
> # bits.
> #
> # By default this script does nothing.
> 
> # turn on LED
> 
> if [ -d /sys/class/leds/status:green:health ];
> then
>    echo default-on >
> /sys/class/leds/status:green:health/trigger
>    if [ -d /sys/class/leds/status:orange:fault ];
> then
>       echo none >
> /sys/class/leds/status:orange:fault/trigger
>    fi
>    if [ -d /sys/class/leds/status:blue:health ];
> then
>       echo none >
> /sys/class/leds/status:blue:health/trigger
>    fi
> fi
> if [ -d /sys/class/leds/dockstar:green:health ];
> then
>    echo default-on >
> /sys/class/leds/dockstar:green:health/trigger
>    echo none >
> /sys/class/leds/dockstar:orange:misc/trigger
> fi
> 
> if [ -d /sys/class/leds/plug:green:health ]; then
>    echo default-on >
> /sys/class/leds/plug:green:health/trigger
>    if [ -d /sys/class/leds/plug:red:misc ]; then
>       echo none  >
> /sys/class/leds/plug:red:misc/trigger
>    fi
> fi
> 
> if [ -d /sys/class/leds/power:blue ]; then
>    echo default-on  >
> /sys/class/leds/power:blue/trigger
>    ### echo default-on  >
> /sys/class/leds/otb:blue/trigger
>    echo none        >
> /sys/class/leds/power:red/trigger
> fi
> 
> if [ -d /sys/class/leds/usb1:blue ]; then
>    echo usb-host >
> /sys/class/leds/usb1\:blue/trigger
> fi
> if [ -d /sys/class/leds/usb2:blue ]; then
>    echo usb-host >
> /sys/class/leds/usb2\:blue/trigger
> fi
> if [ -d /sys/class/leds/usb3:blue ]; then
>    echo usb-host >
> /sys/class/leds/usb3\:blue/trigger
> fi
> if [ -d /sys/class/leds/usb4:blue ]; then
>    echo usb-host >
> /sys/class/leds/usb4\:blue/trigger
> fi
> 
> if [ -d /sys/class/leds/nsa325:green:sys ]; then
>    echo default-on  >
> /sys/class/leds/nsa325:green:sys/trigger
>    echo none        >
> /sys/class/leds/nsa325:orange:sys/trigger
> fi
> 
> if [ -d /sys/class/leds/nsa325:green:sata1 ];
> then
>    echo ide-disk1  >
> /sys/class/leds/nsa325:green:sata1/trigger
> fi
> 
> if [ -d /sys/class/leds/nsa325:green:sata2 ];
> then
>    echo ide-disk2  >
> /sys/class/leds/nsa325:green:sata2/trigger
> fi
> 
> if [ -d /sys/class/leds/nsa325:green:usb ]; then
>    echo usb-host >
> /sys/class/leds/nsa325\:green\:usb/trigger
> fi
> 
> exit 0
>
>
> See the echo statements that change the green LED
> to "default-on"? that's how your LED was triggered
> to turn green. Depending on the hardware,
> appropriate commands will be executed.
>
> The possible reason that why it did not turn
> green.
>
> 1. Your box is not Goflex Net. One of the step
> before was to append this DTB file (which decribes
> the hardware) to uImage. So the DTB must be the
> correct one. If it were not then the green LED
> would have a different GPIO address so it would
> not turn on by the "echo".
>
> 2. Run this command to list your box info (this is
> an alias that I added to the rootfs, not a
> standard Linux command):
> 
> /root/myinfo
>
>
> Does what it say about this box matches with what
> you actually have?
>
> 3. Look back to the step
>
> 
> cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
>
>
> If your box is a different one then you have to
> redo that. You can do this while the system is
> running. Replace yourboxname with the
> actual name of this kirkwood box (you have to find
> the correctly spelling name in /boot/dts).
>
> 
> cd /boot
> mv uImage uImage.orig.2
> cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
> cat dts/kirkwood-yourboxname.dtb >>
> zImage.fdt 
> mkimage -A arm -O linux -T kernel -C none -a
> 0x00008000 -e 0x00008000 -n
> Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage 
> sync
> sync
>
>
> Then reboot the system.

Once, again, you've done it, Bohdi.
We're all doing great here, green as grass.
Thanks so much.

Now, now, thank you, very much.
I'm sorry for my sometime tiring questions. I hope you have found this rewarding.
Many thanks.

Now I can proceed to installing Jessie? We're done with all the configurations that will accommodate future kernel changes, and for systemd?

Many thanks!
Reply Quote
bodhi
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 30, 2016 07:05PM
notoneofmyseeds,

> Now I can proceed to installing Jessie? We're done
> with all the configurations that will accommodate
> future kernel changes, and for systemd?

Remember to backup your rootfs before any upgrading.

However, your rootfs 4.4 is already jessie. To verify: 

cat /etc/apt/sources.list

This rootfs runs syvinit. Look in the kernel/rootfs thread for instruction how to run systemd, if you wish to.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
notoneofmyseeds
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 31, 2016 02:47AM
bodhi Wrote:
-------------------------------------------------------
> notoneofmyseeds,
>
> > Now I can proceed to installing Jessie? We're
> done
> > with all the configurations that will
> accommodate
> > future kernel changes, and for systemd?
>
> Remember to backup your rootfs before any
> upgrading.
>
> However, your rootfs 4.4 is already jessie. To
> verify:
>
> 
> cat /etc/apt/sources.list
>
>
> This rootfs runs syvinit. Look in the
> kernel/rootfs thread for instruction how to run
> systemd, if you wish to.

I will do the backup. I have figured out how to do this. It's backing up to the stick at the moment.
I only had to adapt the commands. Is there a way to test that it was done properly.
I adapted and issued the command and got: [1] 16138 and the stick is busy blinking, so I assume it's working.

After this, I will check on the Jessie. But sorry for the silly question.

I noticed that you simply did not weigh in on the syninit vs systemd issue, simply saying "if you wish to."
I know you have an informed opinion on this matter. So I put you on the spot and ask;
What would you have folks do; stick with syninit or make the changes and move to systemd?
Your opinion is golden.

And clicked on bohdi's corner and noticed that I could buy you beer, which is what I was looking for. All I have now to do is find a way to reach Doctors Without Borders, so they can send you that beer :)

You're a pretty cool guy, bohdi. Thanks a lot.
Reply Quote
notoneofmyseeds
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 31, 2016 02:55AM
And oh, I forgot to ask, can I go ahead and delete the tars from the USB stick, to save space.
Namely, Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 and Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2?
Thanks a lot!
Reply Quote
bodhi
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 31, 2016 03:18AM
notoneofmyseeds,

> What would you have folks do; stick with syninit
> or make the changes and move to systemd?

OK so I am on the spot, that's fine :)

I would stick with sysvinit. For Linux headless embedded devices, systemd is way overkilled for these.

OTOH, on a Linux laptop/desktop, systemd is OK and I would not go out of my way to remove it there.

>
> And clicked on bohdi's corner and noticed that I
> could buy you beer, which is what I was looking
> for. All I have now to do is find a way to reach
> Doctors Without Borders, so they can send you that
> beer :)
>

:)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 05/31/2016 07:50AM by bodhi.
Reply Quote
bodhi
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 31, 2016 03:19AM
notoneofmyseeds Wrote:
-------------------------------------------------------
> And oh, I forgot to ask, can I go ahead and delete
> the tars from the USB stick, to save space.
> Namely,
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> and
> Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2?
>
> Thanks a lot!

Yes, remove it after installation to save space.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
notoneofmyseeds
Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood
May 31, 2016 12:57PM
Thanks a lot.

I have made the backup, unplug the USB and put it in the pogo, but now it won't start.

The backup, after modifying this: cd /media/sdb1
to this: cd /media/sunnsea/rootfs

and then doing this: time tar -cjf /media/sda1/bonk-rootfs.tar.bz2 . &

placed the backup to the USB stick, which I copied to the desktop, along with these:
Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2?

which were on the stick, and you've asked that I delete from there.

It is very, very important that this is noted. My pogo did not boot with the backup on the stick. It was only after I thought, let me remove the backup from the stick, and did so, that it did boot. And now we're golden. Perhaps this, if verifiable, is added to your backup guide.

I'm off to the races, bodhi....'see' you in the forums.

And a million thank you and a big warm hug. I think you're the kindda person who'd take a hug!

Sorry about 'throwing you into the syninit and systemd debate. But I do think you made a very graceful exit from it. And I will follow your exit :)
Reply Quote
notoneofmyseeds
SOLVED Re: Can I skip from 3.16, wheezy straight to Linux Kernel 4.6 Kirkwood SOLVED
June 01, 2016 03:35AM
Thanks, bohdi. Many thanks; indeed.
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: