Today was released the first RC for Debian 7.0 aka Wheezy.

Improvements in this release of the installer

  • brltty:
    • Fix support for the theme=dark accessibility option (#696972).
    • Enable orca in gnome3 sessions too.

    Please note: the gdm3 prompt isn’t accessible (#694937).

  • cdebconf:
    • Fix display of info messages (e.g. Rescue mode in the banner).
    • Improve speech synthesis support.
  • debconf: Fix misleading man-db title for GRUB prompt (#679327).
  • debian-cd:
    • Improve GRUB menus used when booting in UEFI mode so they match up better with the equivalent syslinux menus.
    • Change the default UEFI display resolution to 800×600 for maximum compatibility.
    • Fix README.html generation (#699198).
  • debian-installer-utils: Fix procfs mounting on GNU/kFreeBSD (#696901).
  • grub2:
    • Improve support for EFI installs: make sure /boot/grub exists, and copy unicode.pf2 there (#696962, #661789).
    • Fix infinite recursion in gettext when translation fails (#611537 and many others).
  • lowmem: Adjust lowmem limit for GNU/kFreeBSD needed for ZFS volumes (#696786).
  • mountmedia:
    • Revert kernel bug workaround (#694082).
    • Firmware loading issues should disappear accordingly.
  • netcfg: Write network-manager configuration (included wireless settings when applicable) if it’s found in the installed system; configure ifupdown for wired networking otherwise (#682608).
  • oldsys-preseed:
    • Ignore a missing gateway with DHCP (#687212).
    • Use netcfg/disable_autoconfig instead of netcfg/disable_dhcp (#689531).
  • preseed: Deal with URLs that consist of an unqualified machine name and a port (#695908).
  • qcontrol: Disable firmware watchdog on TS-219p II and TS-419p II (#693263).
  • rootskel: Use the same keymap in the virtual consoles as the one selected in the graphical installer (#606395).
  • xorg-server: Avoid cursor jumps in VirtualBox (#694598).

Hardware support changes

  • linux: Add many drivers to the installer: 8021q, adm8211, at76c50x-usb, b43legacy, bnx2fc, cxgb4, cxgb4vf, fnic, igbvf, int51x1, isci, iwl4965, ixgbevf, libertas_tf_usb, micrel, mlx4_en, mwifiex_pcie, mwl8k, orinoco_usb, pata_piccolo, pch_gbe, pmcraid, prism2_usb, qlge, r8187se, r8192e_pci, r8712u, rtl8192ce, rtl8192cu, rtl8192de, rtl8192se, smsc75xx, smsc9420, smsc95xx, tehuti, ums-eneub6250, ums-realtek, vt6656_stage, vxge (#686605, #689159, #690886, #694348, #695437).
  • linux: Add Ralink wifi device IDs: 5362, 5392, 539b (#694312).
  • linux: Add support for Lenovo 10/100 Ethernet USB dongle (#696248).

You can find more info on http://www.debian.org website.

If you want to use windows 8 with Linux here is the solution.

If the Grub loader is not loading after windows 8 install, first you need to boot with a Live CD.

Then run these commands as root:

To find the drive where Linux is installed run the following command:

fdisk -l

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        9330    74936320   83  Linux

In my case sda1 is the drive where Linux is installed.
Then you need to run the following commands:

mount /dev/sda1 /mnt/
mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
cp /proc/mounts /mnt/etc/mtab/
chroot /mnt /bin/bash
grub-install /dev/sda Continue Reading...

Few days ago I typed crontab -r instead of crontab -e. Well, my crontab was immediately deleted, without any warning. The first thing that I’ve done was to check if there was some backups on the server. As usual, there was no backups on my server.

So..If you accidentally type crontab -r instead of crontab -e , I have the solution for you:

In the system logs /var/logs/ are stored all crontab-calls of your system and you can easily extract them. Depending on your system you need to  cat and grep all crontab lines from the /var/log/syslog* files like this:

cat /var/log/syslog | grep -i "`which cron`" > cron_recovery_file

`which cron` will automatically be replaced by /usr/sbin/cron on Debian.

You need also extract all data from older messages logs stored as .gz archives:

gzip -d /var/log/syslog*.gz -c | grep -i "`which cron`" >> cron_recovery_file

In this moment you have a file called cron_recovery_file  that contains all your crontab-calls.

Your file will look like this now:

Feb 12 19:00:01 debian-tutorials /USR/SBIN/CRON[53198]: (root) CMD (crontab_command > /dev/null 2>&1)
Feb 12 19:00:01 debian-tutorials /USR/SBIN/CRON[53199]: (root) CMD (/scripts/backups > /dev/null 2>&1)
Feb 12 19:00:01 debian-tutorials /USR/SBIN/CRON[53200]: (root) CMD (mysql -u root --password=************ -e "flush query cache"; > /dev/null 2>&1)
Feb 12 19:09:01 debian-tutorials /USR/SBIN/CRON[53277]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 12 19:17:01 debian-tutorials /USR/SBIN/CRON[53288]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 12 19:30:01 debian-tutorials /USR/SBIN/CRON[53293]: (root) CMD (another_crontab_command > /dev/null 2>&1)

Now, you need to start with the first line and copy/paste the call ( denotes the stuff in the brackets after ‘CMD’) to a new textfile which will be your new crontab. Continue Reading…

HTML stands for Hyper Text Markup Language. Here, Hyper basically refers to non-linear characteristic. It does not follow any particular segment for computer programming. It means a website page can be opened and viewed from anywhere, anytime, and through any type of computing medium. Text refers to the input format, here basically English alphabet and numerical. Markup is simply the overall writing or coding structure. language is the mode in which the entire coding is written.

HTML is used for developing webpages. HTML is also sometimes used in creating document pages. But these pages cannot be read normally like those being created via word processors. HTML pages can be viewed only through a browser that support this particular language. In this world, there are not a single web browser present that does not support HTML based pages. It is through the help of web browsers that HTML coded articles can be read. However, there are special software tools also available for this purpose. HTML code read, CSS file reader, etc. are available in plenty.

One thing to keep in mind: HTML codes are written using a word processors like MS-Word, Notepad, or even Open Office. Once the code is written, save it in one of the following formats: TEXT or ASCII TEXT DOS. For beginners who have just started writing HTML, they often have a tendency to save every single page in a separate folder. But, this is a process that is not required at all. Simply save the pages in a single folder of the hard drive. A very important suggestion to give and follow: when saving these files, always click the “Save As” tab. This will ensure that the files are not being saved to its default format. If the normal “Save” tab is clicked, then the file will get saved in its default format. But that is not required. The file should be saved in TEXT or ASCII TEXT DOS format only. Always remember, when saving a file in word processor in formats other than the above two mentioned ones, then lot of other settings also gets saved like margin setting, word fonts, etc. But these settings are not required at all. Only the text is needed. This can be obtained only if the word file is saved in TEXT or ASCII TEXT DOS format. Continue Reading…

If you are getting “too many open files” error this  is how to fix it.

To change the file descriptor setting you need to add the line fs.file-max=50000 to the kernel parameters file /etc/sysctl.conf

echo "fs.file-max = 500000” >> /etc/sysctl.conf

OR

Open /etc/sysctl.conf file with any editor and add the fs.file-max=50000  line to the file.

To apply all changes run the following command:

sysctl -p

The final step is to change the ulimit setting hard and soft limits. Continue Reading…

Page 3 of 1712345678910...Last »