[SOLVED]setting up a swap file

[kevinfish]

Having 2GB of ram, I didn't anticipate needing a swap partition so I didn't set one up, but now I'm doing enough with the machine that I'm locking it up on a regular basis.   I went in and did the swap tool and it created the tc.swp file in my /mnt/sda1 partition.   It didn't however do anything to enable it.   I tried to mkswap on the file and it returns:

mkswap: /lib/i386-linux-gnu/libblkid.so.1: version `BLKID_2.21' not found (required by mkswap)

I tried rebooting thinking it would do some magic there but nothing.

I looked all through the dCore wiki and really nothing there either.

Where are the CORRECT instructions?

[Jason W]

Thank you for your testing, I will look into it.

[nitram]

I went in and did the swap tool and it created the tc.swp file in my /mnt/sda1 partition.   It didn't however do anything to enable it...

Hi kevinfish.

I've never used a swap file either, after creating the swap file did you reboot and use the swapfile boot code?
http://tinycorelinux.net/faq.html#bootcodes

[kevinfish]

I rebooted, but I didn't edit the boot code.   Where do I find it the file to edit it?

[Misalf]

You would add the  swapfile  boot code to your boot loader's config file (f.e. menu.lst or grub.cfg).

In my  /mnt/sda1/grub/menu.lst , I have:

Code: [Select]

swapfile=sda1

You can check if it's used with

Code: [Select]

cat /proc/swaps


[Jason W]

kevinfish - What dCore port are you using, and are all your loaded SCEs up to date?  I don't get a mkswap error on my setup, but if /lib/i386-linux-gnu/libblkid.so.1 in your session is from an outdated SCE then that error could be from needing an update.

[kevinfish]

I'm using Jessie

Oh, and btw, I have neither grub.cfg nor menu.lst on my system.

I can't recall what bootloader I used and I don't think it identifies itself when I boot.

[Misalf]

Or  syslinux.cfg , extlinux.cfg ...
Maybe in  /boot/  or  /boot/syslinux/  .

[kevinfish]

when I went to do the update, I get this:

(long list of packages to update)


The above SCEs are about to be updated.  Press Enter to proceed, y to view package updates, or Ctrl-C to abort..

(I hit enter)

sh: missing ]
Using the -u option.
Using the -n option.
 
 
Importing alsa-utils.
 
 
Using Package Index: /etc/sysconfig/tcedir/import/debinx/debian_jessie_main_i386_Packages
 
Using Package Index: /etc/sysconfig/tcedir/import/debinx/debian_jessie_security_i386_Packages
 
Using debian Mirror: http://ftp.us.debian.org/debian
 
Using debian Security Mirror: http://ftp.us.debian.org/debian

alsa-utils is a standard debian jessie package.
Gathering dependency info..
Merging libsamplerate0
Merging libtinfo5
Merging libncursesw5
Merging libasound2-data
Merging libasound2
Merging libpopt0
Merging libslang2
Merging libnewt0.52
Merging whiptail
Merging libkmod2
Merging Tiny Core custom start script for gcc-4.9-base: gcc-4.9-base.deb2sce
Merging gcc-4.9-base
Merging libgcc1
Merging libc6
Merging Tiny Core custom start script for kmod: kmod.deb2sce
Merging kmod
Merging lsb-base
Merging Tiny Core custom start script for alsa-utils: alsa-utils.deb2sce
Merging alsa-utils
Parallel mksquashfs: Using 1 processor
Creating 4.0 filesystem on /etc/sysconfig/tcedir/sce/update/alsa-utils.sce, block size 4096.
[=============================================================/] 4242/4242 100%
Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 4096
        compressed data, compressed metadata, compressed fragments, no xattrs
        duplicates are removed
Filesystem size 8394.19 Kbytes (8.20 Mbytes)
        54.47% of uncompressed filesystem size (15411.31 Kbytes)
Inode table size 16304 bytes (15.92 Kbytes)
        37.12% of uncompressed inode table size (43923 bytes)
Directory table size 7858 bytes (7.67 Kbytes)
        43.58% of uncompressed directory table size (18033 bytes)
Number of duplicate files found 7
Number of inodes 864
Number of files 599
Number of fragments 82
Number of symbolic links  46
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 219
Number of ids (unique uids + gids) 2
Number of uids 1
        root (0)
Number of gids 2
        root (0)
        staff (50)
Done.
Error in updating alsa-utils.  Exiting..

-----------------------------

So my guess is it didn't do anything?

[Jason W]

Thanks for reporting, I will look into this.

Are you using the latest dCore version?

Can be determined by the command:

version -r

for release candidates, which is recommended for testing.

[kevinfish]

it says:

Warning:
You are running:          dCore-jessie:2016.01.06.23.01
The latest release is:    dCore-jessie:2016.06.26.17.08


How do I upgrade that?

[nitram]

Most dCore commands have help files:

Code: [Select]

tc@box:~$ version --help
 
version - Confirm dCore version, check for release or release candidate (RC)
          updates, prompted to download an available update to the directory
          specified in /etc/sysconfig/boot_path. Review this file for details.
          The partition will auto-mount if /mnt/* is included in the pathway
          and the entry exists in /etc/fstab. The existing dCore*.gz and
          *.md5.txt files are automatically backed up before the update
          is downloaded. Number of backups kept can also be specified.
          Reboot system to complete the update.
 
Usage:
 
version     List running dCore name and version.
version -c  Check if running the latest stable release, if different version
            available prompted to download, wget latest stable release and
            md5.txt file to directory specified in /etc/sysconfig/boot_path.
version -r  Check if running the latest release candidate, if an update is
            available prompted to download, wget latest release candidate and
            md5.txt file to directory specified in /etc/sysconfig/boot_path.
version -l  List running dCore name and version.
version -s  See dCore version only.

Edit: Recommend one topic per thread, gets confusing. When possible resolve issues as they arise before moving on to the next item. In my experience, dCore is very good, just takes some time to figure out and optimize. You're trying to do everything at once, in time you should get a real nice system.

[kevinfish]

sorry to keep posting on this thread, but perhaps I'm so out of date its not really relevant to the community.   My version --help says:


version - confirm dCore version. check for release & release candidate updates.

Usage:

'version'        print the running dCore name and version.
'version -c'     check if running the latest release.
'version -r'     check if running the latest release candidate (RC).
'version -l'     list running dCore name and version.
'version -s'     see dCore version.


Nothing about updating it.   Indeed, I tried version -c and version -r even with /etc/sysconfig/boot_path set correctly and it did nothing.

Should I just grab the latest dCore.gz and vmlinuz and overwrite the ones I have or does something else have to change too?

[nitram]

Yes your system is quite out of date, the version command has been able to download updates for quite some time. Just manually download the dCore-*.gz file (http://tinycorelinux.net/dCore/x86/release_candidates/dCore-jessie/), replace the outdated version and reboot. Then run  sce-update -a  and patiently wait until all existing extensions are updated, reboot again and test system.

[kevinfish]

Thanks, that worked!

There's no way to mark the initial thread "(SOLVED)"